Exchange 2007 Public Folder permissions and PFDAVAdmin issue

35 pts.
Tags:
Exchange Public Folders
Microsoft Exchange 2007
Microsoft Exchange folders
Microsoft Exchange permissions
PFDAVAdmin
Public folders
I have been tasked with making public folders work for our organization.  The main issue I see is that Explicit folder permissions assigned via Outlook are not working.  Specifically, Administrators can create top level public folders, users can't (desired), after assigning a specific user editor permission in a subfolder, the user can still not do anything but view that folder - cannot create a sub-sub folder (undesirable).  The Exchange Shell is truly frightening!!!!!! (sorry but who thought that was a good solution as a management tool for us non-rocket scientists?)  The public folder add-on for the Exchange administrator does not appear to allow for viewing or modification of permissions.  Research seems to indicate that the solution is PFDAVADmin.  Unfortunately, when I run this, while I can connect to mailboxes, attempting to connect to public folders gives the error: An error occured while trying to establish a connection to the Exchange server.  Be sure that port 443 (for SSL) or port 80 (for non-SSL) can be reached.  If you are connecting to public folders, be sure that the public store is mounted.  If you are connecting to mailboxes and the progress bar shows a particular mailbox, be sure that user has at least one email address. Exception: Failed to connect using secure URL htts//Exchangeserver/ExAdmin/Admin/MAHHC.ORG/public%20folders/with error: The remote server returned an error: (500) Internal Server Error..  Failed to connect using unsecure URL http://Exchangeserver/ExAdmin/Admin/MAHHC.ORG/public%20folders/ with error: The remote server returned an error: (403) Forbidden.... I find this error all over the web, but I do not find any working solution.  The public store is mounted.  WebDav is enabled on the server.  Ports 80 and 443 would seem to have to be open since OWA is working (and yes public folders are visible) - yet I cannot Telnet into those ports.  I get this same error whether running PFDAVAdmin on the server or on my workstation and yes, my workstation has .Net 1.1 SP1. I was not involved in the setup of this server - was only told they have not been able to make these work since downloading a (n unspecified) tool to help working with public folders.  I am hesitant to play around too much as the rest of the Exchange server (2007) is working correctly and I do not claim to be an expert. Any help would be appreciated !!!!!! Thanks muchly in advance, Andi

Software/Hardware used:
Exchange 2007

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 9  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Technochic
    Sorry you are having problems with this Andi! I can tell you first however that PFDAVAdmin is NOT to be run at all from the server, so I would expect you to get errors there. Only run it from your PC. In our organization we have a separate mailbox server which just holds the public folders and no mailboxes. Have you mounted a public folder on your mailbox server which holds regular mailboxes? How many Exchange Mailbox servers do you have?
    57,010 pointsBadges:
    report
  • Vtandi
    Thanks Technochic, We are a small shop and have only one exchange box. Unless there are pointers I am not aware of, it would appear that both the mailbox store and the public folders both reside on the same drive: F:Exchange ServerMailboxSecond Storage GroupPublic Folders Database (user mailboxes: Same path except First Storage Group
    35 pointsBadges:
    report
  • Technochic
    Gotcha. Sounds like you have it all set up properly, however if you cannot telnet to those ports then something is amiss. Do you have a firewall turned on for your mailbox server?
    57,010 pointsBadges:
    report
  • Technochic
    Forgive me if I ask the obvious questions here. On the Exchange Server line I expect you are putting the server name of the server which holds the public folders. On the global catalog server are you putting a DC which is also a global catalog server? Also are you using your credentials to authenticate? Do you have permissions to connect to the global catalog server with your credentials?
    57,010 pointsBadges:
    report
  • Vtandi
    Yes to all of the above I am afraid
    35 pointsBadges:
    report
  • Technochic
    OK, well it's a mystery to me. Time to enlist Microsoft's assistance with this one I'm afraid. Good luck to you
    57,010 pointsBadges:
    report
  • Vtandi
    Thanks again. Further research has uncovered the fact that we are missing some necessary containers within the Schema. As soon as our network administrator can get a sound DC/system state backup, I am going to try recreating the folders as described here: http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/22f1373c-8685-438b-a677-6c7b0522efc5 I found many people with various public folder problems who were able to regain control of them via this method. I will let you know how it works next week after I have tried it.
    35 pointsBadges:
    report
  • Technochic
    Vtandi, Yes please let us know the outcome. Inheriting someone else's work without all the details of how they set things up is a difficult place to be put in. Glad you found what looks to be a solution. hope it works!
    57,010 pointsBadges:
    report
  • Squish
    If you are looking for more information and resources about Exchange public folders consider reading advice from industry expert, Brien Posey.
    80 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following