Expand a Stand-Alone Primary Site into a Hierarchy with a Central Administration Site
Updated: March 31, 2016
Applies To: System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1
The information in this topic applies to System Center 2012 Configuration Manager SP1 or later, and System Center 2012 R2 Configuration Manager or later.
Beginning with System Center 2012 Configuration Manager SP1, you can expand an existing stand-alone primary site into a hierarchy with a central administration site.
Before you run Setup to expand a stand-alone primary site, review the following sections in the Planning for Sites and Hierarchies in Configuration Manager topic:
To expand your stand-alone primary site, run Setup from the source media for Configuration Manager SP1 or a later version, and use the procedure To install a central administration site from the Install a Central Administration Site section in the Install Sites and Create a Hierarchy for Configuration Manager topic. During Setup, ensure that you make the following selections in the Configuration Manager Setup Wizard:
On the Getting Started page, select Install a Configuration Manager central administration site.
On the Client Language Selection page, select the same client languages that the primary site supports.
On the Central Administration Site Installation page, select the option Expand an existing stand-alone primary site into a hierarchy.
After Setup finishes, your stand-alone primary site is now a child primary site. After the new central administration site is installed, restart any Configuration Manager consoles that are open and remain connected to the primary site. If there are software update points at the primary site, install a software update point at the central administration site and configure it to synchronize software updates with Windows Server Update Services (WSUS). This is because the child primary automatically reconfigures its software update points to synchronize with a software update point at the central administration site. For information about how to configure software update points, see Configuring Software Updates in Configuration Manager.
After you have expanded your standalone primary site to a central administration site, you will need to run a SQL script to enable automatic client upgrades. The script correctly sets the authoritative site for the client upgrade package to the new central administration site. Automatic client upgrades will not run successfully until you run the following script on the central administration site database:
DECLARE @RootSite AS NVARCHAR(3) DECLARE @SourceServer AS NVARCHAR(255) DECLARE @FullClientPkgSource AS NVARCHAR(255) DECLARE @UpgradePkgSource AS NVARCHAR(255) SELECT @RootSite = SiteCode, @SourceServer = SiteServer FROM sites WHERE ISNULL(ReportToSite, N'') = N'' SELECT @FullClientPkgSource = N'\\' + @SourceServer + N'\SMS_' + @RootSite + N'\Client' SELECT @UpgradePkgSource = N'\\' + @SourceServer + N'\SMS_' + @RootSite + N'\ClientUpgrade' UPDATE SMSPackages_G SET Source = @FullClientPkgSource, SourceSite = @RootSite WHERE PkgID IN (SELECT FullPackageID FROM ClientDeploymentSettings) UPDATE SMSPackages_G SET Source = @UpgradePkgSource, SourceSite = @RootSite WHERE PkgID IN (SELECT UpgradePackageID FROM ClientDeploymentSettings) UPDATE ProgramOffers_G SET SourceSite = @RootSite WHERE OfferID IN (SELECT UpgradeAdvertisementID FROM ClientDeploymentSettings)