PFDAVAdmin Content Report – First step to explore the ‘jungle’ of your public folders

PFDAVAdmin Content Report – First step to explore the ‘jungle’ of your public folders

Did you ever want to know how many items each public folder contains? Or do you want to know when the newest item was created in a public folder? These are common questions for Exchange admins who manage public folders. When you have a small number of public folders, these may not be so difficult to answer. But if you have hundreds of thousands of public folders and owner permissions are possibly delegated to multiple teams, it is really hard to catch up to find out what folders are active and what folders are stale.

The Content Report menu in PFDAVAdmin (From ‘Tools’ menu -> Choose ‘Content Report’) should help you as the first step to answer these questions for more effective management of your public folders. You can create a report for all the public folders or any single folder (and its subfolders) with information such as the following:

·           Folder Path – The path of the folder.

·           PR_DISPLAY_NAME – The display name of the folder.

·           PR_CONTENT_COUNT – The item count as shown on the folder properties.

·           PR_MESSAGE_SIZE – The size of the folder as shown on folder properties.

·           Total Number Of Items – The number of objects that PFDAVAdmin found in the folder.

·           Oldest Creation Date – The oldest creation date of any item in the folder.

·           Oldest Modification Date – The oldest modification date of any item in the folder.

·           Newest Creation Date – The most recent creation date of any item in the folder.

·           Newest Modification Date – The most recent modification date of any item in the folder.

·           Largest Item Size – The largest item size in the folder.

·           Total Calculated Size Of Items – The total of all individual item sizes added together.

For example, by looking at the Newest Creation Date and Newest Modification Date, you can probably get an idea how actively the folder is used. If the report is showing dates many years ago, well, the folder may not be really used anymore by anyone. You may want to consider adding age limits to folders to delete contents that have not been used for years while giving them a deadline to deal with the contents. Or, you may want to delete the contents or archive them to different storage if you are really sure that nobody needs them anymore.

You may also want to look at the PR_MESSAGE_SIZE and Total Calculated Size as well to see what folders are taking the space of your hard disks to get the biggest bang for the buck. By using Export Permissions (From ‘Tools’ menu -> Choose ‘Export Permissions’), you can know who has the owner permissions of those folders. Then, you probably know who you should contact to confirm if you can go ahead and delete those folders.

The report created by Content Report is a tab delimited text format. You can import it to Excel easily and manipulate the report to your own preferred format.

Keep in mind though that, like every other function in PFDAVAdmin, Content Report runs only against the server you’re pointing it to. That is, folders that don’t have replicas on the target server will basically just have a blank line in the report. If you have multiple replicas of a folder that are out of sync with each other, you may see different information for a folder depending on what server you point it at. In other words, if you suspect that your replicas are out of sync, you can easily check to see if that is the case by running Content Report against those servers and comparing the results. Well, to get your replicas back in sync, you know ESM has “Synchronize Hierarchy” available with Exchange Server 2003 SP2. Or, you can even add a replica with PFDAVAdmin! 

Please also note that PFDAVAdmin does not report Last Access Time, because that data is not available through DAV. In fact, the act of using PFDAVAdmin to analyze the folder content will cause the Last Access Time (visible in ESM under the public store for each server) on that folder to update on that target store. So if you’re planning on correlating the Last Access Time with the data from the Content Report, you need to gather the Last Access Time first. Also, keep in mind that Last Access Time is specific to each store, so if you plan to use that data you need to go around to each individual public store and grab it. Another possibility that the Last Access Time can be updated “unintentionally” is file level virus scanning (which was more of a problem on Exchange 2000 servers with exposed M: drive). When folders are scanned in that way – the Last Access time is updated at every virus scan so the Last Access Time is probably not a good indication whether if real users accessed the contents at that time.

Haruya Shida

Comments (7)
  1. Lou Mandich says:

    Great Information!

    In order to help customers dump the information from multiple servers I wrote a simple set of batch files. Batch files at the bottom.


    (Please download Pfdavadmin first)

    1. Put all of these files in C:pfadvadmin

    2. Open pfdavadmin (run pfdavadmin.exe) and enable logging under tools, options, then close pfdavadmin.

    3. Create a servers.txt file that contains all of the Public Folder Servers you wish to scan.

    4. Double click or run runpf.bat from a command line

    5. This will give you one report per server in a tsv file.

    Runpf.bat- save in a text file (only the for command to the %%i

    for /f "tokens=1" %%i in (c:pfdavadminservers.txt) do c:pfdavadminpfreports.bat %%i

    pfreports.bat- (save in a text file between the set command and the echo done command)

    set ntserver=%1

    rem ***************************************************************

    ECHO Running PFAdmin Reports

    pfdavadmin -contentreport -s %ntserver% -f %ntserver%.tsv


    echo Done!

  2. Anonymous says:

    A small list this week, but hey, size doesn’t matter, right?

    You’ve heard of the ‘aha’ moment? How about…

  3. chaunam says:

    Why can not I use this tool is there anything to set on the exchange 2003 SP1 server before I can use this?

    verything I try to use the tool to open PF to manage it popup with an error saying that "400 bad request"

  4. Bill Long says:

    Hi Nam,

    There’s typically nothing you need to do on the Exchange server to allow PFDAVAdmin to work. It sounds like the tool is generating some malformed XML when it requests the PF hierarchy. It may be a bug or something specific to the environment that’s causing the problem. I’d start by taking a netmon trace so we can see in the trace exactly what DAV request looks like. If you open a case with PSS I’m sure we can track down the problem.

  5. Frank Carius says:

    Nice tool. BTW there is a second way to do some reporting. Instead of using HTTP (i assumd PFDavAdmin ist doing that) you can also use WMI (Exchange 2003 required ?)

    I have a sample Script on Unfortunaly the description on that  page is german, so you should use google, if you want to read that. But the code is VBScript and thats readable for everyone :-)

  6. Frank Carius says:

    I have written somethin similar based on WMI. Even if the description is german on the code itself is readable at

  7. Anonymous says:

    A frequent topic of discussion with customers is the future of Public Folders, thus I think it would…

Comments are closed.