Join David M. Franklyn for an in-depth discussion in this video Expanding a standalone primary site, part of Microsoft System Center Configuration Manager Essential Training.
- [Instructor] Very often an organization will decide one standalone primary site to be sufficient for the client management needs of the organization. However, if they may later decide that it would enhance efficiency to have more than one primary site, they can then add a central administration site and then later an additional primary site. Microsoft refers to this as Expanding a Standalone Primary Site. In order to do so, you must meet the following prerequisites. You need to install the new central administration site using the same media version that matches the version of the standalone primary site.
Now, this is kind of new because in using Configuration Manager Current Branch, we're going to have different releases and therefore different media versions with it. So they need to be the same. Next, the standalone primary site cannot be configured to migrate data from another site. So usually when it's a standalone, we're not going to have this issue 'cause the standalone implies there is not another site. But if we're doing any type of migration of data, that has to be done or turned off before we can do the expansion.
The computer account of the computer that will host the new central administration site must be a member of the administrator's group on the standalone primary site computer. So this means going into Computer Management, going to Users and Groups and then the Local Administrators Group and putting that computer account into it as one of the administrators. The user account, the person that runs set-up to install the new central administration site, must have the role based administrative rights at the standalone primary site.
The port of the sequel server service broker 4022 between the standalone primary site and the central administration site server must be open. You must uninstall the Asset Intelligence sync point, the Endpoint Protection point, and the Service Connection point from the standalone primary site before expanding it if they are installed. In our case, neither the Asset nor Endpoint was installed, and we deliberately skipped the Service Connection point.
And that was the reason because otherwise, we'd just have to uninstall it at this point. In the demonstrations, we'll first install a site hierarchy in a central administration site which will expand into from the existing standalone primary site. In the second demonstration, we'll install the East primary child site into the site hierarchy. And finally, in the last demonstration, we'll install the Singapore secondary site as a child of the East primary site.
- Planning and deploying a standalone primary site
- Ensuring domain and site server prerequisites
- Planning and expanding a standalone primary site
- Planning and deploying a multiple-site hierarchy
- Planning resource discovery and client deployment
- Managing content and replicating data in Configuration Manager
- Configuring Internet and cloud-based client management
- Advanced monitoring
- Upgrading to Configuration Manager current branch