Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SMS secondary site
- Thread starter leader1
- Start date
Probably the bootstrap service. You'll need to clean-up the Secondary Server and try it again.
Cleaning-up the Secondary Server:
Secondary Server installs generally work best when run from the remote server. Rod Trent
Microsoft.MVP.SMS
=======================================
Main site: =======================================
Cleaning-up the Secondary Server:
Secondary Server installs generally work best when run from the remote server. Rod Trent
Microsoft.MVP.SMS
=======================================
Main site: =======================================
MS info:
Also, ensure that the server name, domain, service account name and password are known, and that "log on as a service" right is valid for the server where secondary site is to be located. To check the log on as a service right:
1. On server to host SMS Secondary Site, go to Start > Programs > Administrative Tools > Local Security Policy
2. Expand Local Policies
3. Select User Rights Assignment
4. Ensure that Log on as a service includes the SMS service account
If it does not
1. Right click on Log on as a service and select Security...
2. Click Add...
3. Select SMS service account
4. Click OK
To check the progress of the bootstrap service:
1. From the primary site server (or other location, but not the secondary site server), open up the folder \\[SecondarySiteServer]\[SMSInstallationDrive]2. Open SMS_BOOTSTRAP.log and look for messages that may indicate current status, or why a failure occurred. (If a suitable CD was not located by the system, don't stop the installation. Just insert the correct CD and let the process continue.)
3. The file SMSSetup.log may also be helpful.
If you installed secondary site using a SMS2 SP2 CD at the secondary site (which is likely the case) then be sure to upgrade it as required to match the primary site (right click Secondary site from primary site in admin console, select All Tasks then Upgrade Site). You'll need to change to the SP4 CD at the secondary site (unless you're using the primary site for the source files).
Also, ensure that the server name, domain, service account name and password are known, and that "log on as a service" right is valid for the server where secondary site is to be located. To check the log on as a service right:
1. On server to host SMS Secondary Site, go to Start > Programs > Administrative Tools > Local Security Policy
2. Expand Local Policies
3. Select User Rights Assignment
4. Ensure that Log on as a service includes the SMS service account
If it does not
1. Right click on Log on as a service and select Security...
2. Click Add...
3. Select SMS service account
4. Click OK
To check the progress of the bootstrap service:
1. From the primary site server (or other location, but not the secondary site server), open up the folder \\[SecondarySiteServer]\[SMSInstallationDrive]2. Open SMS_BOOTSTRAP.log and look for messages that may indicate current status, or why a failure occurred. (If a suitable CD was not located by the system, don't stop the installation. Just insert the correct CD and let the process continue.)
3. The file SMSSetup.log may also be helpful.
If you installed secondary site using a SMS2 SP2 CD at the secondary site (which is likely the case) then be sure to upgrade it as required to match the primary site (right click Secondary site from primary site in admin console, select All Tasks then Upgrade Site). You'll need to change to the SP4 CD at the secondary site (unless you're using the primary site for the source files).
- Status
Similar threads
- Locked
- Question
- Locked
- Question