Article written by Santos Martinez, a US-based Microsoft Premier Field Engineer and resident ConfigNinja.
Do you want to expand your stand-alone System Center Configuration Manager 2012(a.k.a ConfigMgr) primary site into an hierarchy?
So you get to the point where your company starts expanding or acquiring other companies to join your current IT Infrastructure. To achieve this with ConfigMgr can be challenging since you performed a lot of planning for your existing environment and now you need to expand it. In the past you would have to rebuild your ConfigMgr sites to install a CAS (Central Administration Site) and then a primary site. With the future release of System Center 2012 Configuration Manager SP1, this will no longer be needed. Here we are going to outline the steps that are needed for you to accomplish this.
System Center 2012 Configuration Manager SP1 brings the ability to expand a current stand-alone server into a new hierarchy. You can install a new central administration site as a parent of an existing standalone primary site. This expands your stand-alone site into a larger hierarchy that supports the installation of additional new primary sites. You can expand only one pre-existing primary site into the new hierarchy because the database of the new central administration site is based on the database of your stand-alone primary site. After this new central administration site installs, you cannot join or expand additional preexisting primary sites to this same hierarchy. However, you can install new primary sites as child sites below the central administration site.
Steps to expand a stand-alone primary site:
Figure 1.1 Expand the hierarchy selection during ConfigMgr setup:
Note that the new CAS must have access rights to the stand alone site server and database server so the information can be replicate to the new CAS from the stand alone primary site.
For more information, you can check out Planning to Expand a Stand-Alone Primary Site.
Did you ever have to expand a stand-alone primary site?
Article posted by Frank Battiston, MSPFE Editor