![]() With the recent release of Exchange 2010, WebDAV is gone from Exchange, so PFDAVAdmin is no longer an option at all. It also relied on the presence of certain directory objects which were always there in Exchange 20, but were associated only with the CAS role in 2007. NET Framework 1.1, and because of Framework 2.0's more restrictive XML parsing, I could not easily move it to the new Framework. It wasn't a pretty or polished tool, but it was extremely good at dealing with certain customer scenarios.Ī few years later, PFDAVAdmin began showing its age. PFDAVAdmin gained wide usage in Exchange Support, and an updated version was later released publicly. ![]() The tool soon grew to incorporate other functionality, including exporting/importing permissions and replica lists, exporting properties, enumerating items, accessing mailboxes, etc. That tool became PFDAVAdmin, so named because it used WebDAV to access and make changes to public folders, and because I kind of saw it as the successor to the old pfadmin/pfinfo tools. Since I was trying to learn C# at the time, I decided to write a tool to do a bulk fix as a learning exercise. At the time, the only fix we had for this situation was a painful manual process that had to be done one folder at a time. This was back in the Exchange 2000 days when IFS was still around, and it exposed the M: drive by default. Six or seven years ago, I was faced with several cases where the permissions on public folders had been made non-canonical by programs running against the M: drive. UPDATE : Clarified that the new version of the tool will run on Exchange 2010 SP1 and later.
0 Comments
Leave a Reply. |