I was trying to install a remote site system after restoring the SCCM/ConfigMgr central server. After creating new site server in SCCM/ConfigMgr console, I waited enough time get the site system role (SUP) installed on the remote server. But nothing was not happening, no specific log entries at all. I was continuously checking sitecomp.log and suddenly noticed an error which is related to registry access on the remote server. However the error was not at all clear that the remote registry access issue with SCCM site server. Following is the error snippet from sitecomp.log.
ERROR: Cannot open the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions registry key for reading on server SUPRemote. The operating system reported error 0: The operation completed successfully. STATMSG: ID=1026 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCMPri SITE=PL0 PID=2276 TID=8576 GMTDATE=Sat Jan 28 03:33:42.032 2017 ISTR0="\\SUPRemote" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 Cannot access Software\Microsoft\SMS\Security registry key on server SUPRemote. The operating system reported error 0: The operation completed successfully.
When I tried to connect to remote registry of new site system from SCCM/ConfigMgr central server. It was giving following error and that gave me some clue that remote registry of SCCM site server is not accessible.
Unable to connect to SUPRemote. Make sure that this computer is on the network, has remote administrator enabled, and that both computers are running the remote registry service.
There are 2 possible issues in the above remote registry error. First one is to check whether the remote administrator enabled or not ? I have checked in server manager of the remote site server. There is a setting called “configure server manager remote management“. “Enable remote management of this server from other computer” was already enabled for remote site system.
The 2nd part of the error is to check whether both computers are running the remote registry service. When I checked the remote registry service of the SCCM remote site server, it was set to manual and I was not in running state. I started the service “remote registry” and changed it’s startup type to automatic (delayed).
Remote registry server was not started and that was the issue with SCCM/ConfigMgr remote system. After starting this service, SCCM/ConfigMgr was successfully able to connect to remote registry of the site server. Also the installation of remote SUP role has been completed successfully.
Starting service SMS_SERVER_BOOTSTRAP_SCCMPri with command-line arguments "CA0 D:\SMS /install \\SUPRemote\D$\SMS\bin\i386\comregsetup.exe "... "\\SUPRemote\D$\SMS\bin\i386\comregsetup.exe /install /siteserver:SCCMPri" executed successfully on server SUPRemote. Starting service SMS_SERVER_BOOTSTRAP_SCCMPri with command-line arguments "PL0 D:\SMS /install \\SUPRemote\ADMIN$\system32\smsmsgs\srvmsgs.cmd "... STATMSG: ID=1014 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_MP_FILE_DISPATCH_MANAGER" SYS=SUPRemote SITE=PL0 PID=2248 TID=4788 GMTDATE=Sat Jan 28 05:13:50.430 2017 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 Successfully called IAbstractNetwork::CreatePath() with NAL path "MSWNET:\\SUPRemote\admin$\".
<01-28-2017 06:14:08> Invoking process "C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe" "D:\SMS\bin\i386\wsusmsp.dll" <01-28-2017 06:14:34> Registered DLL D:\SMS\bin\i386\wsusmsp.dll <01-28-2017 06:14:34> Installation was successful.
Some more tips :- If you are struggling to get rid of your orphan remote site systems from SCCM/ConfigMgr console then here is the way to do that. I don’t recommend to edit the SCCM database however it’s better remove the server name from the registry of SCCM/ConfigMgr primary. Once registry is deleted, these changes will automatically get reflected in to SQL DB and then we also will get option delete the remote site system from SCCM console. Yes, SMS/SCCM is slow moving server. So patience is key, you need to wait at least good amount of time to get the above changes in SCCM console.
Registry entry :- HKLM/Software/Microsoft/SMS/Components/SMS_SITE_COMPONENT_MANAGER/Component/Servers