We had to expand our san drive that sccm 2007 sp2 (r2/r3) is installed on. We did a stop site (preinst.exe /stopsite) and disabled all the sccm services as a precaution. We then copied all the files and folders over to the new drive (used beyond compare). Restarted all the services and noticed sitecomp was quite busy for the next few hours checking over things. In the console under component status (SMS_CLIENT_CONFIG_MANAGER) we are getting Could not connect to the "REGISTRY" inbox source on computer <server>. The operating system reported error 203: The system could not find the environment option that was entered. As far as we can tell everything is working (software dist is our main use). I did run ccmsetup on the server, but haven't rebooted it yet. Was thinking about trying a site reset? Any suggestions on what might be going on? Thanks

If you look at the permissions for HKLM\SOFTWARE\Wow6432node\Microsoft\SMS\InboxSource, is there an entry for SMS_SiteToSiteServerConnection_<YourSiteCode> in there? If so, what is it set to?

A site reset will reset all permissions on all folders including the inboxes and *should* resolve your issue.Jason | http://blog.configmgrftw.com

Yes it has special permissions. I guess we'll try the site reset after we get approved downtime. I'll post the results. Thx

You should of course go through your change management process; however, a site reset will *not* cause and does *not* require any downtime. It's not an instant process by any means (you should monitor sitecomp.log) but given that ConfigMgr is not a real-time system, there are no real-time processes to disrupt.Jason | http://blog.configmgrftw.com

Site reset did the trick...thanks