SCCM Seconday Site Install Failure

[Paul]

Hello all

I'm running SCCM 20007 RTM 5931 and have it installed as a primary site
server. When I try to install a secondary site via a push from the
primary site the installation fails.

The SMS_BOOTSTRAP.INI and a few .tmp files are copied to the root of the
secondary server but the ConfigMgrSetup.log files has the following:

<01-07-2008 17:40:03> The command line options are /SCRIPT
D:\SMS_BOOTSTRAP.INI /NOUSERINPUT

<01-07-2008 17:40:03> Setup has not detected an existing installation of
a primary site server, secondary site server, site system, or
Configuration Manager console on this computer.

<01-07-2008 17:40:03> Error Section Identification key Action in the
setup script is either missing or empty.

<01-07-2008 17:40:03> The ConfigMgr setup script contains syntax errors.

<01-07-2008 17:45:31>

I've followed the SCCM doco on TechNet and I far as I can see I've added
the correct user and machine accounts to the correct groups. Any ideas?

Thanks
Paul

[Paul]

[Kim Oppalfens [MVP]]

Have you modified sms_bootstrap.ini in any way?
Can you open the file?
The only thing that comes to mind right now is file corruption when
copying this ini file.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

[Paul]

Hi Kim

The sms_bootstrap.ini hasn't been modified in any way. When I open the
file it has the following 5 lines:

Action=Deinstall
SetupPath=\bin\i386\setup.exe
BuildNumber=5931
InstallMapPath=\install.map
SecurityMode=Standard

The sms_bootstrap.log file has a lot of entries, possibly of interest:

1/01/1601 12:00:00 AM Waiting for PID 1748 to terminate...
SMS_BOOTSTRAP 510 (0x01FE)
1/01/1601 12:00:00 AM PID 1748 exited with code 1. SMS_BOOTSTRAP 510
(0x01FE)
1/01/1601 12:00:00 AM FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not
running, setup must have failed, bootstrap procedure aborted!
SMS_BOOTSTRAP 510 (0x01FE)
1/01/1601 12:00:00 AM Deinstalling myself... SMS_BOOTSTRAP 510 (0x01FE)

and

1/01/1601 12:00:00 AM Set current directory to d:\. SMS_BOOTSTRAP 630
(0x0276)
1/01/1601 12:00:00 AM FATAL ERROR: Cannot read the SMS Identification
key from the local registry, bootstrap procedure aborted! SMS_BOOTSTRAP
630 (0x0276)
1/01/1601 12:00:00 AM Deinstalling myself... SMS_BOOTSTRAP 630 (0x0276)

I've installed the secondary site manually and everthing is running
fine; I'm mostly concerned that this error will continue to occur when I
try to push other services to this box as I build it up and I'd rather
not have half a management point :)

Thanks for your help so far.

[Kim Oppalfens [MVP]]

Is the secondary site in a different forest?
Have you extended the ad schema?
Have you successfully published data to ad?
Additional roles are pushed from the secondary itself so you should be
allright now.

[user]

The schema has been extended
Data is being published to the AD and the seconday site is in the same
domain as the primary.

I didn't realise additional roles were pushed from the secondary site,
so like you say, hopefully everything will work here on in.

Thanks for taking the time to look at this.

[Kim Oppalfens [MVP]]

> Thanks for taking the time to look at this.

No problem.

[Paul]

G'day everyone

With some help from our friends at Microsoft we managed to troubleshoot
why the management point on our secondary server wasn't talking back to
our primary site.

On the primary server, at
"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files",
we needed to uncheck the Read Only attribute on the general tab and
change the security permissions for the SYSTEM user to full control.

After a restart the management point started talking to the primary site
and all was good.

I haven't found anyone else who has experienced this problem, it doesn't
seem to be widespread and as far as I know it's not yet in any doco.