Join David M. Franklyn for an in-depth discussion in this video System Center prerequisites, part of Microsoft System Center Configuration Manager Essential Training.
- [Instructor] There are numerous prerequisites that must be met before installing Configuration Manager. It is a heavy consumer of server components especially when also acting as the SQL database site server role. Before installing Configuration Manager, you should have a firm understanding of SQL Server and its prerequisites and requirements. For example, you need to have a SQL Server instance in place before installing Configuration Manager on a server. When Configuration Manager is installed in the first system, it is known as a site system.
The different functions performed by a site system are known as site system roles. The database server is such a role. When we create a standalone primary site server with a database on the site as the same server, Microsoft recommends 16 CPU cores, 96 gigabytes of RAM, and 80% of memory allocation devoted to SQL Server. However, it is not allowed to put the primary server on a failover cluster whereas many high availability options of SQL Server recommend failover clusters.
Therefore, when exploring high availability options for Configuration Manager, it is best to put SQL Server separate from the primary server computer and then set up a failover cluster on that SQL Server. In any other configuration, the CPU cores and totality of RAM are less than the above combined recommendation, yet they are still considerable. The allocation and configuration of the disk drives also contributes to the performance of Configuration Manager.
However, almost all data written by Configuration Manager is stored in the SQL Server databases, but there are log files that retain data beyond that needed for SQL Server and you will need adequate space for the logs. Therefore, you need access to SQL Server, but not necessarily on the primary site server. The requirements for SQL Server include the following. For current branch 1511 only, SQL Server 2008 service pack three or higher.
For all subsequent current branch systems, SQL Server 2012 SP1 or higher for the reporting services point SQL Server reporting services. The software roles and features needed on the primary site server include the following, the .NET Framework 3.5, SQL Server which we just talked about 2012 service pack one or higher. You can also SQL Server Express but only on a secondary site, not on a primary site and not a central administration site, the Windows Assessment and Deployment Kit, ADK, for Windows 10 and above, Remote Differential Compression.
For PXE server and multicast, install the Windows Deployment Services or WDS server role. For the software update point, the Windows Server Update Services, WSUS. And finally, the IAS servers WMI 6.0 compatibility. There are several infrastructure prerequisites as well. The Active Directory for its functional level must be Windows Server 2008 or higher.
The installation media of Configuration Manager includes the tools to extend the Active Directory schema. If you are installing Configuration Manager current branch in an Active Directory forest that already had the schema extended for Configuration Manager 2007 or 2012, you do not need to extend the schema again. Otherwise, you should run the extadsch.exe program found in the installation media in the path \SMSSETUP\BIN\X64.
You must also make sure that the system folder is present or created in the Active Directory domain. You must also give the site server role computer account full access to this folder. Finally, you need to ensure the correct user accounts for management of Configuration Manager are created in the domain. You will need these accounts to install Configuration Manager properly.
- 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