Kevin79 Posted November 8, 2011 Report post Posted November 8, 2011 Is a Central Administration Site necessary when you have a primary site and 10 or so child sites? (That is my configuration in SCCM 2007). It would be great if I didn't have another server to maintain. Quote Share this post Link to post Share on other sites More sharing options...
ramrod115 Posted November 10, 2011 Report post Posted November 10, 2011 I believe you can use your primary site as Central Admin Site...if anyone says different please let us know. Thanks. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted November 10, 2011 Report post Posted November 10, 2011 the CAS is NOT the same as today's Central site, for example, you cannot have a Management Point on a CAS, but you can on a Central site, if you want child sites in SCCM 2012 you can have one standalone primary with secondaries underneath but if you want more than one primary you'll need to install the CAS first, as you cannot install the CAS later, it's now or never. For more info see the links below:- Fundamentals of Configuration Manager - http://technet.micro...y/gg682106.aspx Supported Configurations for Configuration Manager - http://technet.micro...y/gg682077.aspx Planning for Configuration Manager Sites and Hierarchy - http://technet.micro...y/gg682075.aspx as ConfigMgr 2012 is still in Release Candidate phase, please go ahead and test CAS with an attached primary/secondary to see how it all works together in your Lab (not in Production). When you install System Center 2012 Configuration Manager for the first time, you create a Configuration Manager site that is the foundation from which to manage devices and users in your enterprise. This site is either a central administration site or a primary site. A central administration site is suitable for large-scale deployments and provides a central point of administration and flexibility for you to support a global network infrastructure. A primary site is suitable for smaller deployments and it has fewer options to accommodate any future growth of your enterprise. When you install a central administration site, you must also install at least one primary site to manage users and devices. With this design, you can install additional primary sites to manage more devices and to control network bandwidth when devices are in different geographical locations. You can also install another type of site that is named a secondary site. Secondary sites extend a primary site to manage a few devices that have a slow network connection to the primary site. When the first site that you install is a primary site instead of a central administration site, you cannot install additional primary sites. However, you can still install one or more secondary sites to extend the primary site when you need to manage a few devices that have a slow network connection to the primary site. If you do not install any secondary sites from this single primary site, the site is referred to as a standalone site. When you have more than one site that communicates with each other, you have an arrangement of sites that is referred to as a hierarchy. Publishing Site Information to Active Directory Domain Services If you extend the Active Directory schema for System Center 2012 Configuration Manager, you can publish System Center 2012 Configuration Manager sites to Active Directory Domain Services so that Active Directory computers can securely retrieve System Center 2012 Configuration Manager site information from a trusted source. Although publishing site information to Active Directory Domain Services is not required for basic Configuration Manager functionality, this configuration increases the security of your System Center 2012 Configuration Manager hierarchy and reduces administrative overhead. You can extend the Active Directory schema before or after you install System Center 2012 Configuration Manager. Before you can publish site information, you must also create an Active Directory container named System Management in each domain that contains a System Center 2012 Configuration Manager site. You must also configure the Active Directory permissions so that the site can publish its information to this Active Directory container. As with all schema extensions, you extend the schema for System Center 2012 Configuration Manager one time only per forest. Site System Servers and Site System Roles Configuration Manager uses site system roles to support management operations at each site. When you install a Configuration Manager site, some site system roles are automatically installed and assigned to the server on which Configuration Manager Setup has run successfully. One of these site system roles is the site server, which you cannot transfer to another server or remove without uninstalling the site. You can use other servers to run additional site system roles or to transfer some site system roles from the site server by installing and configuring Configuration Manager site system servers. Each site system role supports different management functions. The site system roles that provide basic management functionality are described in the following table. Site System Role Description Site server A computer on which you run the Configuration Manager setup program and which provides the core functionality for the site. Site database server A server that hosts the SQL Server database, which stores information about Configuration Manager assets and site data. Component server A server that runs Configuration Manager services. When you install all the site system roles except for the distribution point role, Configuration Manager automatically installs the component server. Management point A site system role that provides policy and service location information to clients and receives configuration data from clients. Distribution point A site system role that contains source files for clients to download, such as application content, software packages, software updates, operating system images, and boot images. Reporting services point A site system role that integrates with SQL Server Reporting Services to create and manage reports for Configuration Manager. When companies first deploy Configuration Manager in a production environment, they often run multiple site system roles on the site server and have additional site system servers for distribution points. Then they install additional site system servers and add new site system roles, according to their business requirements and network infrastructure. The additional site system roles that you might need for specific functionality are listed in the following table. Site System Role Description State migration point A site system role that stores user state data when a computer is migrated to a new operating system. Software update point A site system role that integrates with Windows Server Update Services (WSUS) to provide software updates to Configuration Manager clients. System Health Validator point A site system role that validates Configuration Manager Network Access Protection (NAP) policies. It must be installed on a NAP health policy server. Endpoint Protection point A site system role that Configuration Manager uses to accept the Endpoint Protection license terms and to configure the default membership for Microsoft Active Protection Service. Fallback status point A site system role that helps you monitor client installation and identify the clients that are unmanaged because they cannot communicate with their management point. Out of band service point A site system role that provisions and configures Intel AMT-based computers for out of band management. Asset Intelligence synchronization point A site system role that connects to System Center Online to download Asset Intelligence catalog information and upload uncategorized titles so that they can be considered for future inclusion in the catalog. Application Catalog web service point A site system role that provides software information to the Application Catalog website from the Software Library. Application Catalog website point A site system role that provides users with a list of available software from the Application Catalog. Enrollment proxy point A site system role that manages enrollment requests from mobile devices so that they can be managed by Configuration Manager. Enrollment point A site system role that uses PKI certificates to complete mobile device enrollment and to provision Intel AMT-based computers. Quote Share this post Link to post Share on other sites More sharing options...
Kevin79 Posted November 21, 2011 Report post Posted November 21, 2011 Thanks. Since I just want one primary site and secondary sites under that, I can eliminate a second server and not user a CAS. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted November 21, 2011 Report post Posted November 21, 2011 Correct, and you can also look into leaving some secondary sites out, as you've got more options now on controlling networktraffic on DPs Quote Share this post Link to post Share on other sites More sharing options...
