PFDAVAdmin update is now released

An updated version of the PFDAVAdmin tool has been released to the web. You can get it from the download center at this link:

This update contains various bug fixes that have been made over the last three years (the prior version on the Download Center was from April of 2007). It also has some changes that make it work better against Exchange 2007. For instance, the old versions of PFDAVAdmin expected certain directory objects to be present for all Exchange servers. In Exchange 2007, some of those objects are only present with a CAS role. This resulted in a situation where PFDAVAdmin would only connect to Exchange 2007 mailbox servers that also had the CAS role. That problem is fixed in this version of PFDAVAdmin, which has no problem connecting to Exchange 2007 with only the mailbox role installed.

The dependency on .NET Framework 1.1 remains, which means you should run PFDAVAdmin from a workstation with Framework 1.1 installed – you should not install this old version of the framework on your Exchange servers, because it makes IIS unhappy.

PFDAVAdmin still cannot connect to Exchange 2010 servers, because WebDAV is gone from 2010. If you need similar functionality for Exchange 2010, use ExFolders instead.

Bill Long

Comments (28)
  1. Andrew says:


    I’m hoping you can help, I can’t connect to our Exchange 2007 Mailbox SCC cluster using PFDAVAdmin. When I try to connect i receive a 401 unauthorized error from the server. I’m sorry if this isn’t the correct area to post such a question, if this is the case could you please point me in the right direction?

    Thanks in advance.


  2. Bill Long says:

    Hi Andrew,

    As you would expect, the 401 Unauthorized is a permissions error. Are you trying to navigate into a user mailbox? If so, you must have full access to that mailbox in order to navigate into it with PFDAVAdmin.

  3. Andrew says:

    Hi Bill,

    Thanks for the response. I am indeed trying to navigate into a user mailbox. If i authenticate as myself in PFDAVAdmin and attempt to navigate into my own account I still receive the 401 error, I am in the Exchange Organization Administrators group. Do I need to grant permissions to all mailboxes by using a command such as the one below? :

    Get-Mailboxdatabase | Add-AdPermission -User "Username" -AccessRights GenericAll



  4. HotFix says:

    If we have a pure Exchange 2007 enviornment, which tool should we be using primarily? This update PFDAVAdmin or ExFolders?

    I understand we can use either, but I am looking for some direction as to which tool is the preferred tool.

  5. v-9 says:

    Hi Hotfix,

    With Exchange 2007 you will have to use Pfdavadmin.

    If you have exchaneg 2010 then you can use Exfolders for exchange 2007 and exchange 2010 as well.


  6. Peter says:

    Hi I dowloaded PFDAVAdmin from the link provided. Even though the file version shows up with a higher value than the previous version (6.5.8164.0 compared to 6.5.7911.0) it still shows the same version number within the program.

    If you go to help about it shows PFDAVAdmin version 2.8.

    So I am wondering if MS just forgot to update this or if this is really a new version since the UI and Menus have not changed at all.

  7. Exchange says:


    Yes – this is all expected; you are looking at the newer version. While the version within the tool did not change (and there were no changes to the tool UI) – if you pull up the props of the pfdavadmin.exe, on the Details tab you can see that the tool version has been incremented to newer version.

  8. Petri says:

    It should not be so uncommon that us, as Exchange administrators does not have permissions to the public folders made regular users. So this tool, as it behaves as normal client tool it cannot give any benefits to us? Or does it behaves in some other way?

  9. paulwwoodward says:

    I’m trying to add reviewer perms for "Everyone" to calendars, but I can’t add "everyone" to the ACL any longer.  With this version of the tool I get:

    "An error occurred. Exception: Ambiguous SID: S-1-1-0"

    Can anyone else confirm/deny this behaviour? Paul.

  10. CDubb88 says:

    I too am receiving the "Exception: Ambiguous SID: S-1-1-0" error when I try to add the Everyone group to set calendar permissions.

  11. giuliano says:

    I’m having this problem as well. First the search for Everyone doesn’t work, you need to browse the directory and find the group manually and then when you confirm the selection it throws this Exception.

    I understand that the Everyone group is actually already included in the Calendar but it doesn’t appear in the PFDavAdmin. If you check the Calendar’s permission via Outlook what appears as "Default" is actually the Everyone group.

    Is there any solution for that?

  12. Bill Long says:

    Andrew, that’s correct, you’d need to use a command line like that to grant yourself access to all mailboxes.

    Hotfix, v-9 is correct. You can’t use ExFolders in a pure 2007 environment. You have to have at least one 2010 server to use ExFolders. Thus, PFDAVAdmin is your only choice.

    Petri, PFDAVAdmin does not behave as a normal client when accessing public folders. It goes through the ExAdmin virtual directory, which means it uses admin permissions, not client permissions. So you do not need to have a user assign you permissions on a folder in order to access that folder with PFDAVAdmin. You do, however, need to be an Exchange Administrator.

    Paul, CDubb88, and Giuliano, so far I have not been able to reproduce the problem with the Everyone group. I’m able to browse for it and add it and I get no error. Can one of you email me at exfolders at so I can get some more information? Thanks.

  13. Nick Tochev says:

    I am also getting the "Ambiguous SID:.." message. Would someone have the older version 2.7 of PFDAVAdmin somewhere saved. I would like to see if the old one is going to do the trick. I would really appreciate if you can contact me @ ntochev at apeg dot bc dot ca. Thanks.

  14. Torkjell_Dahl says:

    I’m trying to add reviewer for "Everyone" to all calendars, but I can’t add "everyone" to the ACL.  On Exchange 2010 with ExFolders version 2.8, I get: "An error occurred. Exception: Ambiguous SID: S-1-1-0"  when i try to add the everyone user.

    Any possible solution?

    Best regards,

    torkjell dot dahl alpha ringerike dot kommune dot no

  15. Niels van Buuren says:

    I Run into the same "An error occurred. Exception: Ambiguous SID: S-1-1-0" issue when I try to add everyone to localized (Dutch) calendars.

    same for me: if anybody has a solution or the older version that supposedly works, please contact me @ nvanbuuren at bvb-substrates dot nl

  16. Bill Long says:

    Hey all, Giuliano contacted me at the email address I posted above, and by working with him I was able to discover and fix the problem with handling the Everyone group. The PFDAVAdmin download will be updated to include this fix in the next couple of weeks. If you need this fix immediately, just email me at the email address I posted above, exfolders at

  17. Ned says:

    I’m getting the Ambiguous SID error as well, though I’m trying to add the Anonymous user. Has anybody gotten past this yet? Does Bill’s fix work?

  18. bilong says:

    Hey all,

    The Download Center was updated with a new build today that contains the fix for the Ambiguous SID problem. Grab the new build and you should be good to go.

  19. bilong says:

    Scratch that. I submitted the updated build, but somehow it didn’t make it to the Download Center. I’m re-submitting it and hope to have it up within the next couple of days.

  20. Exchange says:


    It seems like the download center replication was a little slow; try it again if you are not getting the newest version. I tried about an hour ago – and got the older one. Now – I tried 3 times in last 30 minutes, and got the newer (updated yesterday) version all 3 times…

    Sorry for the spotty nature of this but it seems like the issue is going away now.

  21. john david says:

    thanx for the informetion

  22. meljsmith322 says:


  23. Andrew says:

    Bill – I’m still struggling with the 401 error, any ideas where I can find some help on this? I’ve spent hours searching the net for a solution but have had no success!



  24. Carol says:

    I am also struggling with 401 errors. Is there a problem with clusters? I have two Exchange 2007 shared-storage clusters (two seperate clusters of two physical nodes each). I need PFDAVADMIN to troubleshoot Public Folder replication between the clusters. I am not able to connect to either cluster. I have experimented with all combinations of Exchange PF Admin, Org Admin and Server Admin. Nothing I do makes any difference. I have also tried the cluster name, physiacl node name and ip address. Being clusters these servers only have the Mailbox role, but you say that is ok, yes?

  25. Andrew says:

    Hi Carol,

    I’ve JUST finally resolved this issue! With regards to the 401 error by simply opening PFDAVadmin, clicking on File, Connect and removing the option to ‘Authenticate as currently logged-on user’ then manually imputing my password the 401 errors were no longer present. These were, however, replaced with 500 errors. After a bit of digging around on the mailbox cluster (Server 2008) I realised that .NET wasn’t installed as a role so installed and can no browse all mailboxes and public folder using PFDAVadmin.

    I hope this helps.


  26. Hoss says:

    Hi!  Has anybody been able to find a fix for the Ambiguous SID error?  I’ve got an Exchange 2003 box that I’m migrating to an Exchange 2010 box and I’ve moved the mailboxes over, but keep getting this error when trying to set Calendar Permissions.


  27. Carol says:

    Hi Andrew,

    I had already tried entering the username and password seperately, but I still get 401 errors. The .NET feature is installed as part of the IIS role. So I’m still no futher along but I’m glad you got it working!

  28. Carol says:

    I’m in now. I added the Basic Authentication and Windows Authentication features to the IIS role. I am not really clear on the implications of doing this on a production Exchange 2007 mailbox server so I will remove them again once I sort out my problem.

Comments are closed.