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

Use environment:

Domain name: sccm.com

Role system version IP

AD/DNS Windows server 2016 10.33.11.10

SCCM2016 Windows server 2016 10.33.11.15

DHCP network equipment

Note:

Cisco device 2960sr

Add attribute valu

Nxet server 10.33.11.15 (SCCM2016 server IP address)

Bootfile SMSBoot\ x86\ wdsnbp.com (users must press F12 to continue-optional ads)

The following parameters are configured according to usage requirements

Pxeboot.com (users must press F12 to continue-optional ads)

Pxeboot.n12 (TFTP download starts immediately-mandatory advertising)

Abortpxe.com (stop PXE boot)

1. Configure .Netframwork configure SCCM account SCCM host add domain

Copy the SXS directory in the system image to AD and SCCM

1.2. Install .Netframwork using the following command

Get-WindowsFeature | where {$_ .name-like "core"} | Add-WindowsFeature

1.3.Add account and grant Domain Admins group permission, because this permission is required when installing SCCM components.

1.4.The SCCM add domain

Add the SCCMadmin account to the administrator group of the SCCM01 host

2. Extend the AD architecture

Mount or copy the SCCM2016 installation package to the AD server

2.2. Because you want to expand the role of the site, you must have administrative rights with the administrator and each schema.

Use administrator privileges on DC01 to run the extadsch.exe program in the following directory

.\ Desktop\ SC_Configmgr_SCEP_1606\ SMSSETUP\ BIN\ X64\ extadsch.exe

2.3.After running this program, you will find a text file named ExtADSch in C:

2.4.The text will prompt you to extend the schema successfully "Successfully extended the Active Directory schema."

2.5.Use ADSI to link to the schema to verify the extended result

2.6. View the extension

Create system management objects in the default context of ADSI, giving SCCM01 administrative permissions to other servers in the domain.

Right-click the ADSI editor-default naming context

Create a new object in system

2.9. specify the object as "container"

2.10. Give the object the value "System Management"

3. Configure Configuration Manager server permissions

3.1. set the security permissions of the "System Management" container to "full Control" and the inheritance option to "this object and all child objects".

Right-click "System Management" to select properties.

Click Security, click add, the object type is computer, and type the name of the SCCM server computer.

3.2. Add permission inheritance in advanced

3.3. Select application permissions

4. Deploy SQL server database (stand-alone database instance)

4.1. Open the installation file

Installation-fresh installation of SQL server2014

Enter the product key of SQL Server 2014

4.4. Receiving protocol

4.5. Don't search for updates here.

4.6. the alarm of the firewall will not affect the use, because some other service ports of sql may not be open, so port 4022 of SQLTCP1433 and SCCM may be prompted to alarm. The firewall has opened these two ports.

Choose the feature installation of SQL server.

4.8. install database components, SQL server replication components, Analysis, Repoting, customer order management tools, modify the installation directory

4.9. Check the installation function rules

4.10. Use the default instance

4.11. Fill in the enabled account of the service. System is used here.

4.12. Be sure to define the collation

As shown in the following figure, the collation of SQL cannot use the default value, select SQL_Latin1_General_CP1_CI_AS. Some friends set the error here and SCCM2016 deployment Times is wrong, but they don't know how to modify the default collation in SQL Server 2008 R2, so they have to uninstall and reinstall SQL Server, which is very troublesome.

4.13. Add the administrator account of the database (if you open the account of sa and install SCCM, it will prompt you to warn you that it is recommended not to open the account of SA database by default)

4.14. Modify the directory of the database

4.15. Configure the account of Analysis

4.16. Set the directory of the database

4.17. Installation (it takes about 20 minutes for the server to perform well and will be faster)

4.18. The database has been installed

5. 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

5.4.Select the installed SQL server 2014 database

5.5. Set a path to update the patch file

Enter the instance path name of the database because the default instance is only the full FODN name.

FQSN\ instance name is normally used

5.7. Installation

5.8. Installation completed

5.9. When you click the exclamation mark, there will be a post-installation task.

5.10. Configure the corresponding data directory container of the database during this action

5.11. Update service configuration is complete

5.12. Install remote split compressed BTIS

5.13. Install the selected components

5.14. Installation completed

5.15. The components have been installed

6. Install Windows ADK

Download address https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit

6.1. Download the installation package to this directory

6.2. Provide anonymous downloads

6.3. Accept the agreement

6.4. Downloading

6.5. Download completed

6.6. Run adksetup.exe in the download directory

6.7. Specify the installation directory

6.8. Send anonymously

6.9. Accept the agreement

6.10. Install all the features in the component (uncheck if there is an evaluation service for windows and do not ignore it)

6.11. Installation completed

7. Install the SCCM2016 site service role

Double-click "splash.hta" in the installation CD, the installation interface appears, and click "install".

7.2. Select "install"

7.3. Select the next step in the wizard step

7.4. Choose to install the main site

7.5. Select the evaluation version in the test

7.6. Accept the agreement

7.7. Download the patch to the specified directory

7.8. Downloading

7.9. Size of downloaded patch 770m

7.10. The language choices of the server are Chinese and English.

7.11. Chinese and English are selected for the client, and all languages are supported on the mobile.

7.12.The site code is LJ1, the site name is BeiJingsite, and the installation directory is specified.

7.13. Because we have only one server, we do not have an administrative center, so we choose an independent site here.

7.14. Database information

The primary site requires a SQL server database to store site settings and data. Specify the details of the site database server. The instance name used for the site database must be configured to use a static TCP port. Dynamic ports are not supported.

SSB Port: specifies the TCP port for SQL Server Service Broker. Configuration Manager uses Service Broker to replicate data between parent and child site database servers in the hierarchy. This port is different from the port used by the SQL server service, which is automatically detected by Configuration Manager. -is it comparable to a concept such as a heartbeat?

Configure SQL database information for SCCM. Including the FQDN:sccm.contoso.com of SQL, instance name: MSSQLSERVER, database name: CM_CAS, the default database port is "4022" (SSB port).

7.15. Specify the location of the SQL Server data file and transaction log file

SMS provider settings. Keep the default. In fact, at this step you can understand why you need to extend the AD architecture in the first place. The Cofiguration Manager console uses the SMS provider to communicate with the site database.

Note: the SMS provider cannot be installed on the server configured for the SQL server cluster.

-Why is that? Can it be installed in an AlwaysOn environment?

-- supported in AlwaysOn mode.

7.17. Here we choose the http protocol.

7.18. Data used for diagnosis

7.19. Skip temporarily and then link after installation

7.20. Check and report to the police. Generally speaking, I come across several calls.

1) prompt the security of SQL's account.

2) prompt the problem of database memory limit

3) Firewall port problem.

If the SQL account is enabled, the SA account will give an alarm, and the alarm can be resolved by turning off the SA account authentication of SQL Server.

Database memory can be configured on the SQL Server management console with maximum and minimum memory usage limits, which can solve the alarm problem.

Port Please open TCP1433 and TCP4022 on the firewall on the system where you installed SQL Server and SCCM

After processing the above alarms, check the prerequisites interface for the next step on a stand-alone machine.

7.21. Start the installation

7.22. Wait about 15 minutes for the installation to complete

Check the log to see if SCCM is installed successfully at last. ConfigMgrSetup.text should end up with "Completed Configuration Manager Server Setup"

7.24, C disk, these four log files record the information of the installation process.

7.25. After installation, there will be console options in the start screen.

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.