This option enables you to then install new primary sites to expand the scale of your deployment.Ĭentral administration site with one or more child primary sites
Option to expand a standalone primary site into a larger hierarchy with a central administration site. Simplified client site assignment and discovery of available resources and servicesĮlimination of possible delays introduced by database replication between sites This topology provides the following benefits: For more information, see Configure boundary groups and Fundamental concepts for content management. To help manage network traffic, use multiple management points in boundary groups, and a carefully planned content infrastructure.
This topology is also successful when your company's geographic locations can be served by a single primary site. For more information, see Sizing and scale numbers. Use a standalone primary site when it can support management of all devices and users. The key driver of the type and count of sites that you use in a hierarchy is usually the number and type of devices you must support. Most complex: A group of connected primary and secondary sites with a central administration site at the top-level site of the hierarchy Simplest: A single standalone primary site When you use the technical preview branch, find issues specific to that branch in the documentation for each version of the technical preview. The release notes apply to all branches of Configuration Manager. When planning a new installation of Configuration Manager, be aware of the release notes, which detail current issues in the active versions. Configuration Manager only supports installation of new sites to an existing hierarchy of sites. You can't add a previously installed site to an existing hierarchy to merge two standalone sites. Install new secondary sites below a primary site, up to the supported limit for the primary site and overall hierarchy. Install a new primary site below a central administration site, up to the supported number of primary sites for the hierarchy.Įxpand a standalone primary site to install a new central administration site, to then install additional primary sites. When planning, keep in mind limitations for adding additional sites to a hierarchy or a stand-alone site: Then plan a topology that efficiently serves your current business needs and can later expand to manage future growth. The content management options that can reduce the number of sites you need to install
The scope of management that each type of site provides The types of available sites and their relationships with each other The available topologies for Configuration Manager Applies to: Configuration Manager (current branch)īefore installing the first site of a new Configuration Manager hierarchy, it's a good idea to understand:
0 kommentar(er)
