Article ID: 259781 - View products that this article applies to.
This article was previously published under Q259781
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
After you upgrade a Microsoft Windows NT 4.0-based server running Systems Management Server (SMS) 2.0 site server to Microsoft Windows 2000, the permissions on the HKEY_LOCAL_MACHINE hive of the registry are reset to a default setting. This default setting includes removing access for individual accounts that have been granted specific permissions. This can affect the ability of remote SMS site system computers to connect to the site server.
Services and/or processes on remote site computers (such as Inbox Manager Assistant on Client Access Point (CAP) servers and the SMS_SQL_Monitor service on remote SQL Server) use the SMS Server Connection Account, SMSServer_xxx (where xxx is the site code) to connect to the site server. When the registry permissions are reset during the site server upgrade to Windows 2000, the explicit permissions that the SMSServer_xxx account has been granted to the registry of the site server are removed. This results in the inability of this account to connect and can cause slow processing of or possibly failures in:
This problem can occur because the Windows 2000 upgrade program resets some registry permissions to default under the HKEY_LOCAL_MACHINE hive as part of the enhanced security features in Windows 2000. Because of this, any custom permissions that were added to the registry (such as the SMSServer_xxx account by SMS) are removed.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To work around this issue, manually add the permissions to the registry of the site server using the following steps:
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0 Service Pack 2.