Shulou(Shulou.com)06/03 Report--

1, install SQL-install .net 3.5 first

2. The SQL version should correspond to the SCCM version

3, SQL collation: SQL_Latin1_General_CP1_CI_AS

4. All service accounts are enabled with a dedicated SQLAdmin-the startup type is all changed to automatic

5Perfect DC creates container System Management and empowers it

Open the ADSI editor on DC to create a container System Management

Open the ADSI editor-connect to the default naming context-right-click System to create a new object-Select container

Write value as: System Management

Open dsa.msc users and computers on DC to open advanced features and find the full control permissions granted by System Management to Sccm computer accounts and modify them to full control permissions for this object and all descendants (Note: if you want to add SEC secondary sites in the future, you also need to add SEC permissions)

6Magic SCCM 2012 corresponds to ADK version

The ADK package corresponding to the SCCM2012 version is as follows:

SCCM2012--ADK8-MDT

SCCM2012 SP1-ADK8.1-MDT2013/2012

SCCM2012 R2-ADK8.1-MDT2013/2012

Install the wrong version such as SCCM2012 R2 to install ADK8, then there may be problems such as not starting the PE package in SCCM later.

7. Weight and port problem of connecting to SQL server

If SQL and SCCM are installed separately, you must add SCCM's computer account to the Administrators group of SQL's computers-and add the SCCM installation account SCCMadmin to SQL's login users.

Finally, open the firewall restrictions on the server where SQL Server resides, and open ports 1433, 135,445 and 49155 in Inbound Rules. It's easy to understand ports 1433, 135, and 445, but it's strange for me to use port 49155 when SCCM links to SQL Server. Port 49155 is not open in the installation, and you usually can't connect to the database successfully. Here's a tip. Usually we can't connect because of the firewall. We can turn off the firewall first. After connecting normally, we can check which ports are used by netstat-an, then turn on the firewall and open only these ports.

9cr DHCP needs to open ports 066 and 067.

When configuring DHCP, you need to use ports 066 and 067. The value of 066 (BootServer startup server hostname)-is the FQDN or IP address of the server of SCCM-(Note: it is best to fill in the IP address of SCCM. I do not know the reason for the success of IP if there is a problem in the FQDN trial). The value of 067 (BootFile Name startup file name) is SMSboot\ x86\ wdsnbp.com.

10, when DHCP and WDS are installed on the same server

When DHCP and WDS are installed on the same server, port 67 will be used at the same time, so you need to check Do not listen on DHCP ports during WDS installation or in the WDS management tool, and also check Configure DHCP options to indicate that this is also a PXE server. This option will add a 060 PXEClient Server Options to DHCP with a value of PXEClient.

11. Install SCCM to connect SQL Server error: unable to connect to SQL server

The SCCM service could not connect to SQL Server. There are usually two types of failures that cannot be connected, either physical obstacles, such as networks, ports, protocols, firewalls, and running account permissions.

From the figure above, you can clearly see the port number, so telnet 4022 directly on SCCM, and find that you can telnet, indicating that the physical link is fine, which is mostly due to account permissions.

Log in to SQL directly with SSMS and add the permission of SCCMAdmin. Permissions SQL role sysadmin, Public

12. Install WSUS to connect to SQL Server error: unable to connect to SQL server

This problem is that the SQL Server server did not open port 1433. Go to the SQL Server server firewall-Advanced Management-Open port 1433 to connect successfully.

13, pre-installed components of SCCM:

Install IIS components WSUS components and BTIS components

5.1.Adding IIS roles

5.2. Add the following components

 windows authentication

 HTTP redirect

 WEBDAV release

 static content compression

 dynamic content compression

 tracking

 request Monitor

 logging tool

 .NET Extensibility3.5

 .NET Extensibility4.5

 ASP.NET 3.5

 ASP.NET 4.5

 management tools

 IIS Management console

 IIS 6 Management compatibility

 IIS 6WMI compatibility

 IIS 6 scripting tool

 IIS management scripts and tools

Enable a new installation wizard to install the WSUS windows update service during installation

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.