Install Child Primary Sites

Once the CAS installation is complete, you are ready to install any child primary sites. As these will be site servers and can actually support clients, there are additional roles that will need to be installed. Since the CAS doesn't directly service clients and orchestrates sies, there are no distribution points, management points, or software update points.

1. Since we are attaching to an existing site, rather than the installation media downloaded for the CAS we should use the content in cd.latest. This is located in the site's server in C:\Program Files\Microsoft Configuration Manager\cd.latest (or whatever location was specified). This content gets updated as MCM does so it has the latest installation media. Navigate to the folder and launch splash.hta.
2. Click Install then review the Before You Begin notifications and click Next.
   
3. I already have the CAS set up so we will select the option to 'Install a Configuration Manager primary site' and click Next. The typical installation does not allow for customizations needed to join to the CAS.
4. Select install the evaluation edition of the product. and click Next. Like with SQL you could alternatively enter the product key to activate.
5. Accept the three licenses and click Next.
6. Since we downloaded the prerequisites for the CAS, I point to the folder there to avoid having to download the files again. There will be a few additional files needed.
7. Select the desired language(s) and click Next.
8. Specify a site code (this must be 3 characters, unique in your environment, and can't be changed). Specify a name for the site which can be longer. Specify the installation path and verify the console will be installed before clicking Next.
9. As I am attaching to the existing CAS it will be joined to an existing hierarchy. Enter the FQDN of the CAS and click Next.
10. Validate the FQDN of the SQL server. It defaults to the local system and since we are collocating SQL and MCM on the same server and the default instance, nothing needs to be changed.
11. Specify the path to the database and log files and click Next.
12. Validate the FQDN of the SMS Provider.
13. On the Client Computer Communication Settings, select 'Configure the communication method on each site system role'.
14. We will need both the management point and distribution point. I leave it at HTTP until later.
    
15. Review the summary and click Next.
16. The Prerequisite Check will run. Review any warnings and take action if needed. Otherwise, click Begin Install.
17. The Installation does take a while, so it is a good time to step way once it is starts. My server isn't the greatest hardware, but it usually takes at least 30 minutes. You can review the logs in the root of C:.
18. Once the primary parts are completed and you can open the console and start using it. There are some additional steps that will run, so I prefer waiting until it is all completed. Once initial replication has completed, the child primary site(s) will show up in the CAS hierarchy. This can be done by launching the Configuration Manager console and goin g to Monitoring > Site Hierarchy.