ConfigMgr Inbox Monitor

A ConfigMgr tool which allows you to view the file counts in folders, or the inbox folder structure for System Center 2012 Configuration Manager as well as previous versions of the product. The tool gives you a birds-eye view of the total amount of files in each of the folders

5 Star
7,820 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
  • Can I include more inboxes into monitor?
    1 Posts | Last post February 14, 2017
  • Can this monitor a remote MP inbox?
    2 Posts | Last post December 17, 2015
    • Will this tool monitor a remote MP inbox with the default settings, or do I have to set something special?
    • Rick, I don't recall if I coded this to attach to an MP. I would suggest pointing it at the MP, but I assume that you have, and this is why you have asked me, so alternatively enter a UNC path into manual text box (\\server\share\path to inboxes)
  • Site server
    2 Posts | Last post September 12, 2015
    • Hi Robert, would you mind clarifying what should i put under 'Site server', is it Site Code or Server Name or something else?
      Thanks in advance
    • Hi Matt,
      Firstly thanks for using the tool, the Siteserver is the Site Server Name, if you have trouble connecting to the site server then use the manual entry and specify a UNC path to the inbox.
      Hope that helps!
  • Off-box SQL
    6 Posts | Last post November 25, 2014
    • Hi Robert
      Should this Tool also function if your running off-box SQL server. Thing is i am getting "WMI  Error: Invalid Namespace" when running it on the SCCM server.
      Question, would it be easy to change so that it's possible to write in the Path for the inbox folder, instead of retrieving it automaticly?
      Btw. great Tool to get a quick overview of the inboxes.
      Kind Regards
    • I think it may have a problem with remote SQL, I'll return to the code and see if I can compile a new version along with your manual connection idea :-)
    • Just released V1.4 which includes the ability to manually specify any path you have access too
    • You may be able to use auto connect since it is using Remote Registry to directly retrieve the Site Code and Installation Directory, let me know :-)
    • Awesome, it now functions perfectly ;) - thanks.
    • Superb, love feedback, thanks for letting me know and glad its useful
  • Unhandled Exception
    3 Posts | Last post November 21, 2014
    • I am getting an unhandled exception when running this tool. "System.IO.DirectoryNotFoundException: Could not find a part of the path 'E:\Program Files\Microsoft Configuration Manager\inboxes\'."
      My primary CCM folder is in D:\Program Files. But the SQL DB is on E:\
      Am I missing a step?
    • Hi there, thanks for checking the tool out. 
      I'm obtaining the installation directory from WMI on the Site server you specify, you can check the root\SMS\Site_<Your Sitecode> namespace using wbemtest and then look at SMS_SCI_SiteDefinition class instance which should contain a property which I use called InstallDirectory. What drive does that say ConfigMgr is installed on, it must say E:.
      Looking at my code all the tool does at this point is get that InstallDirectory property, store the first letter so it knows which admin share to connect too, D$ or E$ in your case, then it uses the rest of the installation path to get to the inbox folder.
    • I tried a new version with you but am just not able to see what is causing it to fail, I've released a newer version but I think you may still have the same issue, do let me know!
  • How do I run this
    3 Posts | Last post November 21, 2014
    • Do I need to change this a specific file extension in order to execute it?  If not what do I use to open the file?
    • Hi Kevin,
      It is a 7Zip compressed file, better results than ZIP but when I next update the tool I'll make it a ZIP to make it easier to handle.
    • Now a zip file :-)
  • Secondary Site Inboxes?
    3 Posts | Last post November 21, 2014
    • Does this support Secondary Sites as well? I am getting an error when trying to use this with my secondary sites.
      WMI  Error: Invalid Namespace
    • Hi Andozane,
      Actually no, the tool was designed and tested on a Primary only.
      Am looking now and I can see in the code what I would need to do to make it connect to a Secondary, pretty simple, it is now on the TODO list for the next version.
    • I released V1.4, you should now be able to connect to Secondary Site servers by specifying their hostname, or using the manual path feature