I remember at my last job I had to upgrade from Exchange 2003 to Exchange 2007. It wasn’t that huge of a deal actually. Then I had a customer who wanted to upgrade to 2007. That was a much larger problem as the customer did not have an abundance of hardware/time/patience. In place installations/upgrades are almost always more tedious than a fresh install. Oh well, live and learn.

Anyway, after upgrading my third client to 2007 Exchange, I remember that I had a tool to help with permissions of all/some of the mailboxes. Namely the HR manager required permission to view all of the calendars of every employee. OK, I can do that.

Grab a file from Microsoft called PFDAVAdmin. This stands for Public Folders DAV-based Administration Tool.

Now, I had another problem after installing said program (it’s just an extraction, so don’t worry about it screwing anything up):
Could not expand https://servername/mailboxstore/Username/L...20Folders/: Name cannot begin with the '0' character, hexadecimal value 0x30. Line 1, position 402."

Argh. Someone mentioned to me that I should remove the SSL requirement on the public folders area. Lot of good that does, as the problem was expanding the folders for individual mailboxes. As it turns out, you need .net 1.1 installed. I was trying to run this from the Exchange 2007 Server directly. Runs great from the old Exchange 2003 server.

So, open this program up. Then click File, Connect.
If you can’t figure out what to put under Exchange Server or Global Catalog, then you should find a file called ADChecker (it’s in the Downloads Section)
If you just want to edit permissions of the public folders, keep the radio on Public Folders. I needed to alter the rights for a single mailbox user remotely. So I chose All Mailboxes.
After a brief query time, you should see Mailboxes with a plus sign. Drill down to your user, then Top of Information Store, Then Calendar.
Right-click and select folder permissions.

Next you can click Add and then add a user after searching.
The permission layout is the same as standard public folders for Exchange.

I may or may not clean this up and add more screen shots.