Most people know that when you run Get-PublicFolderStatistics, it limits the results to 100 entries. What's less commonly known is that it does this same resultsize limitation even when you give it a specific public folder. This is a bug. [PS] C:\Windows\system32>Get-PublicFolderStatistics -Identity '\Work in progress' Couldn't find public folder "\Work in progress" on server "hedwig.slc.mainstreamdata.com". + CategoryInfo : InvalidData: (Work in progress:PublicFolderIdParameter) [Get-Public FolderStatistics], InvalidOperationException + FullyQualifiedErrorId : 7830D023,Microsoft.Exchange.Management.MapiTasks.GetPublicFolderStatistics [PS] C:\Windows\system32>Get-PublicFolderStatistics -Identity '\Work in progress' -resultsize unlimited Name ItemCount LastAccessTime ---- --------- -------------- Work in progress 17 11/12/2010 5:34:44 PM I actually first noticed this because half of my public folders were saying "Not available on this server" for the folder statistics in the Public Folder Management Console. I am in the middle of an Exchange 2003->2010 migration, and was extremely worried by this, thinking that I had botched something somewhere. Turns out everything was fine with the public folder database, it was just not returning results for folders beyond the 100 item mark. Any chance of fixing the cmdlet so it works properly? An aside: It seems that there is no way to submit a bug report to Microsoft about Exchange. Microsoft Connect has many product listed, but Exchange (and Outlook!) are not among them. I opened a chat request through support.microsoft.com and they gave me a snail mail address, then when I pressed them, suggested I come here. Attn: <Product Name> Development Group Microsoft Corporation One Microsoft Way Redmond, WA 98052

Oh, you'll want the version. Exchange 2010 SP1, all current updates applied through Windows Update.

I think there are a number of things that SP1 broke with public folders. I am hopeful that future rollups will fix.