SCCM 2012 Primary Site server is piling up so huge

Question

Hello Folks,
We recently implemented SCCM in our environment for a month ago. Its a stand-alone primary site model running DB on the primary site server itself. But, have segregated the drives for content, DB, and C drive for holding up the SCCM server related
installations. I haven't noticed the data growth on the server, as a result the C drive ran out of space yesterday and increased 40 GB more than the earlier. As of now, C drive has about 120 gb in total and there is only 25% left on whereas it had 33%
after expanding to 120 GB. When digging through the blogs, I doubted it could be BAD MIF inbox folder(screenshot attached), so went ahead and ran space check on the server, and looks like the major % of drive space is being occupied by the inbox folder and
also it is increasing day by day. I need further more directions on how this can be monitored to find out growth % and fix this.
I checked basic stuffs like clearing up profile & recycle bin data and any of this kind.
Step by step guide in detail should be more helpful in this regard. And, I hope this should be helpful for a larger SCCM admin crowd like me in the universe.
I also want to know what are the settings in SCCM console associates with these folders so that the settings can be streamlined to match the best practices (like inventory schedule for every 1 week & software inventory best practices) if at all, if we
have enabled in the implementation phase to receive fast & large results.
Thanks, V@s!m

Answer 1

We are seeing a stable disk size nowadays.
With that hopefully, this is a time to sum up the actions taken.
1. SCCM 2012 implemented a couple of months ago.
2. During the implementation phase, Client & Discovery settings were enabled to be quite an aggressive schedules to get good amount of results in a short period.
3. Implementation had been successfully completed and the system was running just fine until I noticed the space crunch
4. I thought it was normal and increased the disk space by 50% which got ate up in a couple of days and that's when I started suspecting about something is going wrong
5. As an interim solution, have increased the disk space by 70% and started troubleshooting the SCCM buddy.
6. Discovery settings were brought down to not to be aggressive (but this wasn't the issue) - still the issue was going on
7. Inventory settings were too brought down to be nominal (Useful :
http://www.informit.com/articles/article.aspx?p=1912064&seqNum=8)
8. By this time, I brought my colleague who was involved during the Implementation. We did the clean-up on server, went through the Inbox\Auth folders and were trying to figure out still what is going wrong.
9. We couldn't notice much improvement about the situation though we gave enough time for each and every fix that we applied.
10. Through some warnings and errors in the site system status, remembered that the 'Configuration.mof' was modified for testing some customized inventory classes, during the implementation phase which was getting mismatched data from lot of different clients.
- "Potential cause figured out"
11. Replaced the original Configuration.mof, and we started noticing big differences - the space was no more increasing.
12. Still we could see lot of old files in sub-folders of Inbox\Auth folder, we hope all these files would try to process for the information that we added in the 'Configuration.mof' > will fail > will go to respective 'Bad/Corrupt' folders and
eventually will be removed as per the clean-up cycle.
I will update the thread if anything goes wrong beyond this point. But, we believe it wouldn't as we have found the culprit and fixed.
**** I appreciate all your responses to help me with this situation. Happy SCCMing..!
Thanks, V@s!m