How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr

How to Expand SCCM CB Standalone Primary server with CAS server Configuration Manager ConfigMgr? In this post, we will see how to expand the stand-alone primary server and attach it to CAS. 

We need to install an SCCM CB CAS server from the latest source files, we can get the latest source files from the stand-alone primary server’s CD.Latest folder.

Here are more details about CD. The latest folder in my previous blog is here. When do you want to convert/expand your SCCM CB stand-alone primary server to a hierarchy and install SCCM CB CAS?

The only reason for this activity is “If your SCCM CB stand-alone primary server is going out of support in terms of a maximum number of supported clients”.

Patch My PC
How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr - Fig.1
How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr – Fig.1

Introduction – How to Expand SCCM CB Standalone Primary Server with CAS Server

As per the latest documentation from Microsoft, a stand-alone primary server can support up to 175K clients. If you have exceeded this magical number, you must expand your stand-alone primary server to the SCCM CB hierarchy with CAS.

SCCM Site Hierarchy
Monitoring
Overview
Site Hierarchy
CAS
BLR
How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr – Table 1
How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr - Fig.2
How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr – Fig.2

More Details – How to Expand SCCM CB Standalone Primary Server with CAS Server

I’ve created a video tutorial to explain the process of expanding the SCCM CB stand-alone primary server. Before starting the expansion activity, we need to consider some essential prerequisites.

Adaptiva
  • We must install the new SCCM CB CAS server from the installation media (source files) –CD.Latest Folder- that matches the version of the stand-alone SCCM CB primary site.
  • The SCCM CB stand-alone primary site cannot be configured to migrate data from another SCCM hierarchy. Remove all those migration configurations before expansion.
  • The SCCM CB CAS server’s computer account must be a member of the Administrators group on the stand-alone primary site. You may or may not remove this account after the expansion.
  • The user account that runs setup to install the SCCM CB CAS server must have FULL Admin or Infra Admin permissions at the stand-alone primary site.
  • Before you can expand the site, we have to uninstall the following site system roles from the SCCM CB stand-alone primary site: the Asset Intelligence synchronization point, the Endpoint Protection point, and the Service connection point.
  • The SQL Server Service Broker(4022) port must be open between SCCM CB CAS and a stand-alone primary server.

ConfigMgrSetup.log 

Snippets from ConfigMgrSetup.log which may help you to trace the installation of CAS and connectivity between SCCM CB primary server:-  

INFO: Registering SQL connection to primary site's SQL server BLRITPROCM.BLRITPRO.COM.
INFO: checking whether BLRITPROCM.BLRITPRO.COM is a standalone site and whether it has the matched version
INFO: Creating sender address on primary site BLRITPROCM.BLRITPRO.COM to access CAS site BLREMSCAS.BLRITPRO.COM.
INFO: Creating sender address on CAS site BLREMSCAS.BLRITPRO.COM to access primary site BLRITPROCM.BLRITPRO.COM.
INFO: Stored SQL Server computer certificate for Server [BLREMSCAS.BLRITPRO.COM] successfully on [BLRITPROCM.BLRITPRO.COM].
Successfully bulk copied file [C:\SEDO_LockableObjectTypes_bcp.bcp] into table [SEDO_LockableObjectTypes] with rows [20]. Configuration Manager Setup 17-08-2016 15:37:58 3936 (0x0F60)
Creating Service Broker routes for site BLR on SQL server BLREMSCAS.BLRITPRO.COM. ConfigurationManager Setup 17-08-2016 15:38:43 3936 (0x0F60)
INFO: RCM received a message from "BLRITPROCM.BLRITPRO.COM", BCP initialization has started. Configuration Manager Setup 17-08-2016 15:47:36 3576 (0x0DF8)

We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

15 thoughts on “How to Expand SCCM CB Standalone Primary Server with CAS Server Configuration Manager ConfigMgr”

  1. Hi – Pretty good instruction on CAS install.

    I was wondering do, I need to run WSUS on CAS. I have installed WSUS on PRI. Haven’t completed the configuration with software updates and stuff on PRI.

    Thanks

    RL

    Reply
      • You don’t need a CAS at all if your client count is not more than 150k. Please please avoid CAS it’s big overhead.
        The only supported method to attach CAS is:
        1. You should have standalone primary
        2. Install a CAS and during the installation of the CAS you can attach standalone primary to CAS

      • I need the CAS, it is prerequisite of the company. I installed CAS but didn’t attach the primary site. After installing CAS I set up 3 primary sites. What do you recommend? Reinstall all?

      • Can I use migrate services of sccm, right?
        I create a new primary server on CAS hierarchy and use migrate from old to new?
        Can I keep everything? applications, compliance?

        Sorry for these many questions

  2. Hi Annop,
    I have 3 Standalone Primary server now i need them to attach with new CAS server. I saw your video to attach Primary server with CAS, but what about other 2 Primary server, how can i attach them?

    Thanks
    Arun Kumar

    Reply
  3. Hello, I have a question about design. Multiple forests connected with two-way trust relationship. I’m a little confused about the design that it should have, to manage them all from the same sccm console. Should I have a CAS, and a hierarchy of Primary sites below in each forest so as not to overload the bandwidth on the links that join them?

    I do not exceed 100,000 clients to manage among the entire forest, but from what I understand I cannot create several united primary sites, due to redundancy issues and others… everything that is more than one primary site needs a CAS, right?

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.