One of the things I often get asked to do is to look over ConfigMgr 2007 installs and provide feedback on any issues I see. One of the things I look at is the folders in \Microsoft Configuration Manager\Inboxes. These folders contain all the activity of ConfigMgr and typically consist of files which are coming and going. However, some times things go wrong and a bunch of files can start accumulating in these folders, eventually running you out of disk space. This is never good and you should look into the root cause to fix it before worrying to much about the files themselves. However, some things fix themselves, or some files are left behind after fixing the problem, and those problems are a nuisance that needs to be cleaned up and removed. I will try and provide a list of some of the folders I look at and recommend cleaning up if there are old files in them.
I should make a note here that while you can just delete the files, and will be fine in most cases, it is a good practice to instead move the files to a temp folder long enough (a day or week) to make sure there are no negative repercussions from the file removals. It is just smart to play it safe.
There are lots of inboxes, and I’m sure many of them also get file backlogs for various reasons. these are just the ones I see most often. As I see and validate them I will update this list as appropriate.
For a good list of all the inboxes and their purpose, see this technet article.
Nice, pertinent post. A good reminder to go in and check how things are going in my inboxes. I'm going to add you post to my Outlook calender for a monthly perusal. Thanks.
Hi Mike, is this related to XP? Reason I ask is because I'm not finding these folders on any XP or Windows 7 clients.
Jim - These folders can be found on site servers only, and not on clients.
Thanks Mike. Do you have any ideas on why I would be getting a -2147217406 error code value in the re-install log? Thanks!
Jim - I'm not sure what component you are referring to, or what other symptoms you might be having. It is hard to do troubleshooting via blog comments so I would suggest you open up a phone support case if you need more assistance on that error.
Great Post, tks!!