Secondary Site Installation Problems

[mahmga]

I have SMS 2003 working for one site/domain. I need to install a secondary site for another domain. I create the secondary site, choosing to install on a DC for the 2nd domain. The secondary DC already has the advanced client installed but is pointed to an SMS server that is out of commission. When the primary site goes to install it produces the following entry in the bootstrap.log on the secondary DC:

Starting SMS_BOOTSTRAP. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Microsoft Systems Management Server v2.50 (Build 2726) $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Copyright (C) 1994-2003 Microsoft Corp. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Set current directory to C:\. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
FATAL ERROR: Cannot read the SMS Identification key from the local registry, bootstrap procedure aborted! $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Deinstalling myself... $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Deleted C:\SMS_BOOTSTRAP.ini. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Deleted C:\SMS_BOOTSTRAP.EXE. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Deinstalled the SMS_BOOTSTRAP service. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Deinstallation complete. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Bootstrap procedure unsuccessful. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
Stopping SMS_BOOTSTRAP... $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>
SMS_BOOTSTRAP stopped. $$<SMS_BOOTSTRAP><Thu Jun 17 09:06:42 2004><thread=BD0>


I have no clue how to resolve the error: Cannot read the SMS Identification key from the local registry.

Can anyone help or point me in the right direction?

Thank you much
Matthew

 

[tbrennans]

Well in 2.0,

The 'SMS_BOOTSTRAP.LOG' file is only generated if the installation runs into a problem. In this case the installation was being performed on a NT Member Server. The Master Account 'Domain\Domain Administrators' group wasn't a member of the Local 'Administrators' group on the Member server. Adding this group in and re-installing the site cured the problem.

might be the same in 2003