Is it the best approach ever? Don’t know, probably not.
![exchange public folder database explained exchange public folder database explained](https://techcommunity.microsoft.com/legacyfs/online/media/2017/11/image_thumb219.png)
But I managed to cobble together a working script sample. I didn’t realize at the onset just how big the cake was going to be and what flavor. Note that any high-volume folder will likely have slightly off numbers when comparing replicas because source data needs a little time to get to replica copies-even under the best of circumstances.
#EXCHANGE PUBLIC FOLDER DATABASE EXPLAINED WINDOWS#
That didn’t go over so well so, I thought this would be a great opportunity to create a simple little script sample in Windows PowerShell that can display replica metrics for any folder (or folder tree) to determine if any replicas have mismatched metrics. I promptly informed them they already had a great monitoring system, the best ever designed in fact: the end user. Therefore, they wanted a repeatable method that they could easily invoke to determine which folders had “mismatched” replica content in their hierarchy. Shortly after we wrapped that up, they had recurrences of the issue in several other folders. They updated the replicas and were placated. We tied it back to a 2003 to 2010 routing group connector outage when they were migrating public folders. They found discrepancies between the replicas because some were lacking content. Running the Get-PublicFolderStatistics cmdlet against the folders in the Exchange Management Shell returned non-zero metrics as if there was content present! I directed them to run the cmdlet with the -server switch against each server that contained replicas of the affected folder. They had users calling their Help Desk complaining that certain public folders appeared empty of all content. Recently I had an interesting inquiry posed by one of my customers regarding an apparent inconsistency with the Get-PublicFolderStatistics cmdlet in their Exchange Servedr 2010 environment. Yes, I did get an autograph! He extended an invitation to me to write a guest blog illustrating an Windows PowerShell example related to Exchange Server, and needless to say, I could not refuse. I was attending an internal Microsoft event a couple months ago, and one of my peers introduced me to Ed Wilson, THE Scripting Guy. He is currently gearing up his blog site and hopes to have it online in the near future. He currently specializes in the Microsoft Exchange Server platform, providing Microsoft premier customers in the midwest guidance and support. He has most recently latched on to Windows PowerShell v2. He began his foray into programming as a young lad punching the keys in BASIC on a Tandy TRS-80 back in the late 80s, and he gradually progressed through Pascal, VisualBasic, and C/C++/C#.
![exchange public folder database explained exchange public folder database explained](https://i0.wp.com/domalab.com/wp-content/uploads/2016/07/domalab.com-Exchange-2016-Public-Folders-01.png)
![exchange public folder database explained exchange public folder database explained](https://cirasync.com/wp-content/uploads/2019/07/create-share-public-folder-outlook-contacts-featured26391-1-1080x630.png)
Seth Brandes is a premier field engineer who works in Microsoft Services. Today we are happy to have Seth Brandes as our guest blogger. Microsoft Scripting Guy, Ed Wilson, is here. Summary: Microsoft PFE, Seth Brandes, discusses using Windows PowerShell to troubleshoot a customer problem with Exchange Server public folders.