SCCM ConfigMgr Remote Site System Installation Error Cannot Open Registry | Configuration Manager? I tried to install a remote site system after restoring the SCCM/ConfigMgr central server. After creating a new site server in SCCM/ConfigMgr console, I waited enough time to 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 related to registry access on the remote server.
However, the error was not clear about the remote registry access issue with the SCCM site server. Following is the error snippet from sitecomp.log.
SCCM ConfigMgr Remote Site System Installation Error
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 the remote registry of the new site system from the SCCM/ConfigMgr central server, it was giving the following error, and that gave me some clue that the remote registry of the 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. The first one is to check whether the remote administrator is 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 another computer” was already enabled for the 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 a running state. I started the “remote registry” service and changed its startup type to automatic (delayed).
The remote registry server was not started, which was the issue with the SCCM/ConfigMgr remote system. After starting this service, SCCM/ConfigMgr was successfully able to connect to the remote registry of the site server. Also, the installation of the 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 the SCCM/ConfigMgr console, then here is the way to do that. I don’t recommend editing the SCCM database; however, it’s better to remove the server name from the SCCM/ConfigMgr primary registry.
Once the registry is deleted, these changes will automatically reflect in SQL DB. Then we also will get the option to delete the remote site system from the SCCM console. Yes, SMS/SCCM is a slow-moving server. So patience is key. You need to wait at least a good amount of time to get the above changes in the SCCM console.
Registry entry :- HKLM/Software/Microsoft/SMS/Components/SMS_SITE_COMPONENT_MANAGER/Component/Servers
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…