Important This article contains information about how to modify the
registry. Make sure to back up the registry before you modify it. Make sure
that you know how to restore the registry if a problem occurs. For more
information about how to back up, restore, and modify the registry, click the
following article number to view the article in the Microsoft Knowledge Base:
When you try to install a secondary site from a parent site,
the installation may stop responding, and it may take a long time for the
parent site to report the unsuccessful installation. If the secondary site is
deleted from the Systems Management Server (SMS) 2003 Administrator console of
the parent site before the problem is reported, jobs that are still trying to
install the secondary site may continue uninterrupted.
Warning Serious problems might occur if you modify the registry
incorrectly by using Registry Editor or by using another method. These problems
might require that you reinstall your operating system. Microsoft cannot
guarantee that these problems can be solved. Modify the registry at your own
risk.
To work around this issue, manually stop the
secondary site installation and remove it from the targeted computer.
Note You must remove any old information from the installation,
especially if you want to reuse the site code.
To manually stop and
remove the failed secondary site, follow these steps:
Click Start, point to All
Programs, point to Systems Management Server, and
then click SMS Administrator Console.
Locate the Site Settings\Addresses
subtree.
Right-click the address for the failed secondary site, and
then click Delete.
To use the Preinst.exe tool on the SMS parent site to
delete the failed secondary site from the database, follow these steps:
On the SMS primary site (parent) computer, click
Start, and then click Run.
Type cmd in the
Open box, and then click OK.
At the command prompt, type cd\,
and then press the ENTER key.
Type cd sms\bin\i386\00000409,
and then press the ENTER key.
Type Preinst /DELSITE SiteCode
ParentCode, and then
press the ENTER key.
NoteSiteCode is the site code of the
secondary site, and ParentCode is the site code of
the parent site.
To remove any pending or active jobs to a site, type
Preinst /DELJOB SiteCode ,
and then press the ENTER key.
NoteSiteCode is the site code of the
secondary site. For more information about how to use
the PREINST tool, click the following article number to view the article in the
Microsoft Knowledge Base:
Description of Preinst.exe for Systems Management Server 2.0
To make sure that the secondary site is completely removed,
follow these steps:
Make sure that no SMS or Winmgmt services are running
on the computer, including the SMSBootstrap service. If these services are
running, stop the services, and then change the Startup type
to Manual.
Use Registry Editor to make sure that the following SMS
registry keys are removed:
Note You may have to restart the computer to remove some of these
files and folders.
Make sure that the CAP_SiteCode and SMSPKGdrive$ shares and their corresponding folders are deleted from the
client access point computers.
NoteSiteCode is the site code of the
secondary site, and drive is the drive
letter.
Make sure that any site-specific accounts or groups
are deleted, including the
SMS_SiteSystemToSiteServerConnection_sitecode and
SMS_SiteToSiteConnection_SiteCode groups.
NoteSiteCode is the site code of the
secondary site.
Remove the following objects from Internet Information
Services (IIS) Manager (if they exist).
Under Application Pools (only
on IIS 6.0):
CCM Server Framework Pool
SMS Distribution Points Pool
SMS Management Point Pool
SMS Server Location Point Pool
Under the default Web Site (on IIS 5.0 or IIS 6.0):
CCM_Incoming
CCM_Outgoing
CCM_System
SMS_DP_<package_share>
SMS_MP
SMS_SLP
Restart the server.
Note The server must be restarted to make sure that any of the SMS
services that you deleted from the registry in step 6b are no longer running.
If these services are still running when you try to reinstall the secondary
site, the Setup program will try to remove these services, but the removal will
fail because they are already gone from the registry.
After these items are removed, you can reuse the site code to
reinstall the secondary site.
How to rebuild the secondary site
Reinstall the secondary site. As soon as possible, the
secondary site installation should be started to minimize the effect on
clients.
To speed the installation, see the "Installing a Secondary
Site Using SMS Setup" topic in the SMS 2003 Deployment Guide . To obtain this guide, visit the following Microsoft Web site:
This section explains how to set up the site directly from the
CD-ROM. This step lets you bypass the 76 megabyte (MB)-network installation
package and to install directly from the CD-ROM.
Important If you use Standard security, verify that the correct accounts
and passwords have been specified. Problems can be very difficult to diagnose
and repair and may require that you repeat the procedure. To make sure of
success, test the account beforehand. To do this, log on to the new primary
site by using the specified account, and then connect to the secondary site's
c$, d$, and admin$ shares. Create, read, and write to folders and files from
the secondary site drives to the primary site drives and back again.
Reconfigure the secondary site. Immediately after you
install the secondary site and while the site configuration update is being
propagated to the parent site, use the SMS Administrator MMC to configure
settings that will prevent clients from having to unnecessarily change their
configuration.
Back to the top
