What was PFDAVADMIN for 2003 is not ExFolders for 2010
Sweet!!
Make sure you read the README, which says:
-ExFolders must be run from an Exchange Server 2010 machine with the Microsoft Exchange Active Directory Topology service, which means it will not currently run on a tools-only install. This might change in the future.
– ExFolders.exe must be placed in the server’s Exchange \bin folder. If you try to run it from anywhere else, it will simply crash.
– This build is not signed. In order to allow it to run, you can import the included .reg file on the server where you want to run the tool or run “sn -Vr ExFolders.exe” (using the 64 bit version of the SN tool) to allow it to launch. If you don’t, it will crash. To read more about the SN tool, please go here: http://msdn.microsoft.com/en-us/library/k5b5tt23.aspx
http://msexchangeteam.com/archive/2009/12/04/453399.aspx
With the recent release of Exchange 2010, WebDAV is gone from Exchange, so PFDAVAdmin is no longer an option at all. A lot of the things you used to be able to accomplish only in PFDAVAdmin can now be done at the command line. For instance, Get-PublicFolder and Set-PublicFolder can be used to export and import permissions and replica lists, while Get-MailboxFolderPermission and Set-MailboxFolderPermission can be used to export and import mailbox permissions. However, there are still a few things you just can’t do without PFDAVAdmin-like functionality.
Fortunately, we have a solution – a tool called ExFolders. This new tool is really just a port of PFDAVAdmin to Exchange 2010. We changed the name to ExFolders because it no longer relies on DAV, and it’s not just for public folders (even PFDAVAdmin, in its public release, was not just for public folders). The name just didn’t make sense anymore, so we changed it to the easier-to-pronounce ExFolders.
