Hi to all,

I currently have a single stand-alone Primary Site SCCM 2012 R2 site server, remote database server and 4 management point servers. All is working great until, for a mistake, a technical guy remove SMS_<site code> share.

Ok ... SMS_SITE_COMPONENT_MANAGER cannot start, and the related log explain clearly the problem. I immediately suggest to the customer to perform a site reset, but for various reason the customer would like to do it the next weekend.

In the meanwhile I manually recreated the share with the same share permission (file system permission was not modified) and all the SCCM service related and thread starts and works OK. But ... there is always a but ... :-) ...

I found a large number of .smf files (the status message files) on the root drive where SCCM is installed ... I really mean on the root drive!! All the other received files are on the corrected inbox directories ... and, yes, the SMS_<site code> share is set correct on the \program files\configuration manager installation directory ...

When I move these .smf files on the inboxes\auth\statesys.box\incoming\ the files are normally processed.

I'm really afraid to completely fill the drive soon ... 

Any further help (or suggestion) will be higly appreciated,
thanks in advance

You can try to run a site reset. It should recreate all default ConfigMgr shares.

Thanks for your fast reply Torsten,

like I wrote I immediately suggested to the customer to perform a site reset, but for various reason the customer would like to do it the next weekend.

In the meanwhile I would like to understand (and if is possible solve, I am afraid to completely fill the drive soon ...) how and why this can happen.