Sign in
 
HomeOnline201020072003LibraryForumsPartnersEHLO Blog
Exchange Server TechCenter > Exchange Server Forums > Admin > Bug: Get-PublicFolderStatistics limits resultsize even when searching for a specific folder

Discussion Bug: Get-PublicFolderStatistics limits resultsize even when searching for a specific folder

    •  
      Saturday, November 13, 2010 6:39 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      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 "[redacted]".
          + 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

      • Edited by elyograg Monday, November 15, 2010 4:48 PM
      •  
       

    All Replies

    • Saturday, November 13, 2010 6:43 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Oh, you'll want the version.

      Exchange 2010 SP1, all current updates applied through Windows Update.

       
    • Saturday, November 13, 2010 10:23 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I think there are a number of things that SP1 broke with public folders.

      I am hopeful that future rollups will fix.

       

       
    • Monday, November 15, 2010 6:42 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      This is a very stupid and annoying bug ... I've spent a day figuring out why public folders replicas does not work (when I look from Public Folder Management Console I saw "Not available on this server") ... then I realize that the powershell command used by PFMM does not set ResultSize = Unlimited ...

      P.S.: this bug make the Management Console useless... if a PF is not on first 100, you cannot set permission, update content, mail-enable, etc.