SCCM R2 Installation deployment process and issues (i)

Before you perform a Windows Server R2 virtualization test, you will naturally think about how to improve efficiency and effective management because of the need to install, deploy, and manage many servers. In the era of Windows Server 2008, Microsoft has provided server roles, called Windows Deployment Services (Windows Deloyment Services, WDS), that use this server role to complete PXE and multicast installation and deployment tasks for servers. But Microsoft also has a more powerful tool called System Center Configuration Manager (SCCM). SCCM is actually a member of the System Center family, and in System Center R2, in addition to configuration Manager, Virtual Machine Manager, and app Controller These two components we want to use in virtualization include Data Protection Manager, Endpoint Protection, Operations Manager, orchestrator, and service Manager of these components.

In Microsoft's official documentation, these components cannot coexist with each other except data Protection Manager, Operations Manager, and service Manager, and other builds can coexist. Thus, this also facilitates the formation of tests.

But personally, the installation and Configuration Manager is more complex than virtual Machine Manager, a lot of preconditions, especially the configuration of permissions, the slightest careless will affect the normal operation of the software. In addition, Configuration Manager uses log files to record the process and errors of the job, which is also a lot of trouble to use the software. People who do development know that log files are simple and easy to do, rather than intuitive. Although SCCM comes with the log tool configuration Manager Trace log Tools (located in the installation directory Tools\ Cmtrace.exe), but it is not easy to distinguish between many logs and find the information you want, and it is expected that the user experience should be the focus of improvement for the next release.

said the shortcomings, but configuration Manager to bring it asset management convenience is obvious, so encountered problems can only soldiers to block.

I. Pre-conditions for installation

1. Install Assessment and Deployment Kit (ADK)

ADK became a Windows Automated installation Kit (AIK) before Windows 8, which contains many components that are primarily used to install, deploy, and manage the IT assets associated with Microsoft products. can be downloaded here. The download here is just a download tool, and it takes a long time to download the entire package, so it is recommended to prepare in advance. After the download is complete, install ADK on the server where you plan to install SCCM.

2. Installing and Configuring SQL Server

Multiple System Center components can share a single db instance, so we choose to install SQL Server on another server, which adds some hassle but is worth it. The installation and configuration procedures for SQL are not mentioned here, but there are a few things to keep in mind:

(1) SCCM R2 supports SQL Server 2012, so choose the standalone installation (stand-alone installation) SQL Server 2012 here.

(2) Select database Engine services, Analysis Services, Reporting services, Integration Services, and management Tools- Instances and tools such as complete.

(3) running the service with a domain account requires a new domain user in active Directory users and Computers, with the user name Sqlsvc. Microsoft recommends that each service use a separate running account, by default SQL Server 2012 will preset a separate local account for each service. For simplicity, I have configured the same domain account CLOUD\SQLSVC for services, Analysis Services, Reporting services, Integration Services, and more.

(4) When installing the Chinese version of SQL Server, please note that selecting the collation is SQL_Latin1_General_CP1_CI_AS, the English version is the default.

(5) After SQL Server installation is complete, add the computer name of the SCCM server in the domain in Microsfot SQL Server Management Studio cloud\cloud-pm-ds01$ as the login account for SQL Server. and set its properties server roles to sysadmin. SCCM uses the computer name as a credential to access the remote database.

(6) In Microsfot SQL Server Management Studio, adjust the memory range in the CLOUD-PM-DA01 server properties, SCCM will check for this entry, and the installation process will be warned without a restriction.

(7) enable the Named Pipes and TCP/IP protocols in SQL Server Configuration Manager.

(8) Finally open the firewall restrictions on the server where SQL Server is located, open 1433, 135, 445, and 49155 ports in inbound rules. For 1433, 135, and 445 ports, it's a good idea, but I'm using 49155 ports for SCCM to link SQL Server, but it's strange that 49155 ports are not open in the installation, and it's usually not possible to successfully connect to the database. Here is a little trick, usually because the firewall is unable to connect, we can first shut down the firewall, after the normal connection, through the command Netstat-an to see exactly the use of those ports, and then turn on the firewall, and only open these ports.

3. Install and configure the Web Server (IIS) role

(1) Install the Web server (IIS) role in the SCCM server and select the relevant components.

(2) The SCCM installer will configure the application in IIS to distribute the data and therefore need to be configured in IIS:

• New WebDAV Authoring Rules

• To modify a value in a WebDAV settings

• Enable Windows Authentication

(3) Modify the configuration item in C:\Windows\System32\inetsrv\config\applicationHost.config <add fileextension= ". mdb" allowed= "true"/ >

4. Install and configure the DHCP server and Windows Deploy servies (WDS) server roles

This step is not required, and if you plan to use SCCM for PXE and multicast deployments, you will need to install DHCP server and WDS. Also in SCCM if the configuration enables PXE and multicast deployments, WDS will also be installed automatically, and here we choose to install WDS on the server where SCCM is installed.

Since we are installing DHCP sever on the same server as SCCM, there is no need to configure the two server Options for DHCP server 066 and 067, but if DHCP server is installed in a different server than SCCM, you must configure 066 The value of Boot server Host name is the server name or IP address of SCCM, and the configuration 067 bootfile name value is smsboot\x86\wdsnbp.com.

In addition, when DHCP and WDS are installed on the same server, port 67 is used simultaneously, so you will need to tick the do not listen on DHCP ports during WDS installation or in the WDS management tool, and also check configure DHCP options to Indicate that's also a PXE server, this option adds a 060 PXE client's server options to DHCP with a value of pxeclient.

5. Install. Net 3.5, Background Intelligent Transfer service, and remote differential compression server features.

Installing. Net 3.5 In Windows Server R2 requires the use of the Windows Server R2 installation disk. For example, select a path under the Windows Server R2 installation disk by specify an alternate source path x:\sources\sxs,x for the installation disk letter. This is often required because many Microsoft software also requires the support of. Net 3.5.

6. Configure the SCCM computer account permissions in the domain

In the domain server, open ADSI Edit, and under the Cn=system node, add an object that has a value of container type of system management.

On the domain server, open active Directory Users and computers to the System Management node to add a computer account for the SCCM server and give it complete control. At the same time, set the permissions to apply to the object and all objects under it.

7. Extended Domain architecture for SCCM

Extending the schema can be simply understood as adding fields to the data table. Execute the Smssetup\bin\x64\extadsch.exe program on the SCCM installation disk to extend the domain schema. After completion, the ExtADSch.log file is generated in the system root directory of the domain service, and the logging successfully extended the Active Directory schema indicates that the extended schema was successful.

SCCM R2 Installation deployment process and issues (i)