SCCM R2 Installation deployment process and issues (iii)

Previous SCCM R2 installation deployment process and issues (ii)

Personally, the most important experience for using SCCM 2012 is patience.

SCCM uses a distributed deployment architecture, where different site roles can be deployed on different servers, communication between site roles is often asynchronous and takes more time, and SCCM's notification mechanism is less powerful than SCVMM. Thus, it is difficult to understand real-time information such as content distribution (distribute contents) and the execution status of the deployment task sequence (deploy) through the GUI interface, which has to be said to be a major flaw in SCCM, which is more evident in operating system distribution.

Although the real-time notification mechanism is missing, we can still find some problems through the various logs in SCCM, analyze their causes and resolve them. Sometimes you do the right thing and you can't get the right results, and then you have to consider the problem of communication delays between roles, and maybe just wait. Next, take the operating system distribution as an example to illustrate some of the features of SCCM and possible solutions to problems.

Four, SCCM R2 the actual combat-operating system distribution

SCCM can distribute the operating system to a computer with a network boot capability, which is ideal for scenarios where a large-scale deployment of Windows operating systems is possible, or even for server bare-metal shelves.

Operating system distribution can simply be understood as installing the operating system for the target computer and making some necessary configuration. Operating system distribution in SCCM is the execution of a custom task sequence on the target computer. Based on the experience of installing the operating system in general, you can imagine that this custom task sequence requires: Format the disk, install the operating system, configure the operating system (set up an account, select a time zone, enter a product key, etc.), and if it is further possible: Install the driver, install the software, configure the network, join the domain, or even require Because SCCM deploys the operating system over the network, it also requires that the target computer be loaded into window PE prior to the above tasks to build the environment that the custom task can perform, and that the rest of the work is much simpler to perform in a Windows environment when the target computer is successfully booted through window PE. Through the above, now we know that the work we need to do includes:

• Prepare the window PE image and distribute it to the distribution point to boot the target computer

• Prepare the operating system image and distribute it to the distribution point for deployment on the target computer

• Prepare the driver package or application package and distribute to the distribution point (not required)

• Prepare the task sequence and deploy

• Booting the target computer through the PXE boot system

Of course, before we do this, we should build the network environment required for the entire deployment (to enable networking between the target computer and the SCCM server, to confirm that the target computer supports network PXE boot, and also to install and configure DHCP on the network in the pre-conditions for the installation of SCCM Server and Windows Deploy servies (WDS) server roles, etc.). When everything is ready, the rest of the work is done by SCCM:

1. Initial configuration of SCCM (Administration menu and asses and compliance menu)

Here we need to configure the network discovery method, site boundaries, and site roles, and make some necessary configuration of the distribution points to support the operating system distribution capabilities.

In the Administration > Hierarchy Configuration > Discovery Methods submenu, turn on the following discovery methods.

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/6b/d6/wkiom1u4ov-ysp4laae4bev4ejs473.jpg "width=" 723 "height=" 218 "/>

SCCM finds its own target computer and manages it through a variety of discovery methods, and after a while, the target computer appears in the asses and Compliance > Devices menu and automatically makes a simple grouping.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D6/wKiom1U4Ov-SLV0aAADeyGQFdhQ271.jpg" width= "745" height= "168"/ >

Create a new site boundary group in the Administration > Boundary Groups submenu, and create a new site boundary in the Administration > Boundaries submenu, which is like dividing the sphere of influence for the site server.

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/6b/d6/wkiom1u4owcslnbpaacdyk5r8ty210.jpg "width=" 739 "height=" 151 "/>

In the menu above Administration > site Configuration > Sites, select Configure Site components > software distribution, Configure the Network Access Account tab to configure the client access networks for a Profile manager.

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/6b/d6/wkiom1u4owhwhliiaaplchlq3yi694.jpg "width=" 952 "height=" 472 "/>

At least one distribution point role is required at Administration > site Configuration > Servers and site System roles to verify the deployment of each site role.

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/6b/d6/wkiom1u4owlyr9sdaagybeokeja209.jpg "width=" 766 "height=" 346 "/>

Select distribution Point Right-click Properties in Administration > Distribution points, turn on PXE and multicast (multicast), configure Boundary Groups

SCCM can be used for operating system distribution through PXE and multicast (multicast). PXE is a one-to-one approach, as long as there is a target computer to initiate a connection to carry out data transmission, multiple target computers connected to the case will send multiple copies simultaneously, and multicast is a one-to-many way, only to reach a sufficient number of target computers or wait for a limited time, only to send a copy of the data by multicast Thus multicasting is efficient, and if a multicast transmission has started, then the new target computer is added, then the target computer will first receive the same data as the other target computers, the missing parts are then replenished, which can be seen by viewing their progress.

When PXE is turned on for the distribution point, the following settings will be used when the target computer PXE boots:

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M00/6B/D6/wKiom1U4OwPRnuVRAAHZe_7dTMo236.jpg" width= "704" height= "361"/ >

Turn on multicast (multicast) for the distribution point and set the target computer number limit and time limit in the Enable scheduled multicast:

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D6/wKiom1U4OwOiJyyuAAJHkIfllOY114.jpg" width= "730" height= "518"/ >

To configure a site boundary group for a distribution point:

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D6/wKiom1U4OwTykcyxAAFQGeCCQGI414.jpg" width= "705" height= "243"/ >

The above work is ready, and then we get to the point. You can see that there are three sub-menus in the Software Library menu that correspond to the three main features of SCCM, and the operating system distribution function mainly involves software Library > Operating Systems Sub-menu.

2. Prepare the window PE image and distribute it to the distribution point (Software Library menu)

By default, SCCM provides two window PE images (boot Images) to boot 32-bit and 64-bit systems, where we need to simply configure these window PE images and distribute them to distribution points for sending and booting the target computer into the PE environment. The distribution here (distribute Content) can be simply considered to be the meaning of the loading preparation. Of course, these window PE images are specially processed and matched for the different versions of the operating system to be distributed, but the two default versions provided in R2 are basically sufficient to meet our needs, and more about the relationship between the window PE image and the operating system to be distributed, you can consult Microsoft's documentation. Let's take a 64-bit environment as an example:

In the boot Image (x64) Right-click Property, the Configuration customization tick enable command support (testing only), which opens the commands line, and configures the data source to tick the deploy this Boot image from the pxe-enabled distribution point. Next, the boot image (x64) window PE image is distributed to the distribution point.

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/6b/d6/wkiom1u4owsak2braaexrc3e5bu668.jpg "width=" 666 "height=" 219 "/>

3. Prepare the operating system image and distribute it to the distribution point (Software Library menu)

In order to distribute a version of the operating system, we need to manually install the version of the operating system on one target computer beforehand, make it an operating system image, and then add the operating system image to SCCM before distributing it to more target computers.

Making an operating system image is essentially using the Sysprep command, but SCCM also provides us with a quick way to create a task sequence media (which can be thought of as a small program on a CD or USB flash drive) on a target computer as a template to create an operating system image from the task Sequence media feature. Then let's look at how to create this task sequence media.

3.1. Create task sequence media that captures the operating system image (USB stick applet)

Insert a USB flash drive in the server where the SCCM console is installed, select software Library > Operating Systems > Task Sequences right-click Create task Sequence Media, select Capture Media

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D6/wKiom1U4OwWDcrdXAAHbCedgvRk091.jpg" width= "756" height= "377"/ >

Next select the USB flash drive, select the boot image and distribution point (which is consistent with the configuration of the task sequence that created the distribution operating system later), and you can use the USB flash drive to capture the operating system image after completion

3.2. Capturing the operating system image

Normally start the target computer as a template into the Windows system, insert a USB flash drive to run the program named TSMBAutorun.exe, open the operating System Image Capture Wizard, and select a network location to place the operating system image file remotely. After completing the wizard, the target computer restarts and enters the PE, starting the capture of the operating system.

After successful completion, you can find a. wim Windows image file in that network location.

3.3. Create a system image and distribute it to distribution points

In the SCCM console, select software Library > Operating Systems > Operating system Images Right-click Add Operating System Image, select the one you created in the previous step. WI M file.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D6/wKiom1U4OwazCy4EAAG0c0okaOk904.jpg" width= "883" height= "317"/ >

After creation, the operating system image created above is visible in the software Library > Operating systems > Operating system Images List, right-click Configuration distribution Settings tick allow the "this" transferred via multicast (WinPE only)

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D3/wKioL1U4PGSC2yqWAANZ9lPMS20625.jpg" width= "755" height= "517"/ >

The image is then distributed to the distribution point, and if the distribution point cannot be selected in the wizard, it is possible that the image has already been distributed, and if the property is subsequently modified, the update distribution points is used.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D3/wKioL1U4PGXgx5A8AAE0xvXYaHA219.jpg" width= "726" height= "247"/ >

4. Prepare the driver package or application package and distribute it to the distribution point (not required)

If you need operating system distribution to complete both the driver and software installation, you can use the Software library > Operating Systems > Driver packages and Software library > Application Management > Packages Create the driver packages and packages to be referenced in the next creation task sequence. This is not the key to operating system distribution, which is omitted here.

5. Prepare the task sequence and deploy

As we know from the previous description, the task sequence is a key part of consolidating all the resources prepared above. It is important to note that the task sequence created is deployed (deploy) rather than distributed (distribute), and only as content, such as a PE image, operating system image, driver package, packages are distributed.

Select Software Library > Operating Systems > Task Sequences right-click Create task Sequence. These four options create different default task sequences, but you can delete and change the tasks at any time:

• Deploy the operating system image to the target computer

• Make a new image after you deploy the operating system image

• Deploy the operating system image to the virtual disk

• Fully customizable task sequence

Select the Install an existing image package

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/6b/d3/wkiol1u4pgbanci_aajrxrjd3u4553.jpg "width=" 719 "height=" 436 "/>

Select a Windows PE image to boot the target computer

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/6b/d3/wkiol1u4pgbt7t-gaafivg1hblk697.jpg "Width=" 701 "height=" 346 "/>

Select the previously prepared operating system image file (Note: The Windows image file can contain multiple partitions), set the product key and the administrator password.

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/6b/d7/wkiom1u4owmxa9hgaajbtqdcpko707.jpg "width=" height= "562"/>

You can choose to join a workgroup or domain

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D3/wKioL1U4PGeASiH9AAF16d4TRA0472.jpg" width= "701" height= "418"/ >

Select the default configuration Mananger Client Package

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D3/wKioL1U4PGiAHnygAAFzsLVTFgM021.jpg" width= "height=" 324 "/ >

Skip the State Migration, Include updates, and install application steps, which involve the status migration site role and software distribution, and are not discussed at this stage.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M00/6B/D3/wKioL1U4PGmzjvqLAAH9W5lfbmY726.jpg" width= "701" height= "512"/ >

After you finish creating the task sequence, by right-editing the task sequence that you just created, the visible task sequence contains all the tasks that we normally do with the operating system installation. The task can be adjusted, and even the prerequisites for task execution can be set.

It is important to note that partitioning a disk requires that the target computer's boot boot mode is BIOS or UEFI, and the partition capacity cannot exceed the actual disk capacity of the target computer when the partition is set.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D3/wKioL1U4PGnSPSzaAALOT5xFtdE634.jpg" width= "705" height= "518"/ >

When you apply an operating system, because the WIM image file can contain multiple partition images, you need to explicitly select the one that is the operating system partition (that is, 1-1), and the location of the disk where the operating system is applied (the system is installed in the previously partitioned partition), as determined by the variables, Varialbe Name:c can be set when partitioning.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D7/wKiom1U4OwzQdLr5AAKHmDWpjrY109.jpg" width= "704" height= "538"/ >

Next deploy (deploy) the task sequence

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D7/wKiom1U4OwyjzwWDAAEtjHMWuoY476.jpg" width= "726" height= "304"/ >

Select All Unknown Computers for collection in the Deployment Wizard, because we are deploying to bare metal, so these computers have not installed any SCCM client software, so it is Unknown Computers

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M00/6B/D3/wKioL1U4PGvieqeWAAD4kScmw_M341.jpg" width= "789" height= "241"/ >

Next purpose select available, available but not required. Make available to the following, making sure to select an option that contains PXE, or the target computer will not boot through PXE.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D3/wKioL1U4PGzisEEAAAGMHPQSDbo510.jpg" width= "787" height= "387"/ >

The other next options are to default and complete the deployment of the task sequence, and the results of the deployment can be viewed and manipulated by deployments under the task sequence when completed. If you modify the task sequence, you need to remove the previous deployment and then redeploy.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D3/wKioL1U4PGzxUYUdAAG6FtHFT_Y691.jpg" width= "691" height= "420"/ >

You can also view the distribution of content related to the task sequence, ensuring that the targeted field is 1, which means that the distribution point has been distributed to.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D7/wKiom1U4Ow-AfvC_AAHo1TcTz9I437.jpg" width= "783" height= "418"/ >

The status of content distribution and deployment can be viewed through monitoring > Distribution status and Monitoring > Deployments.

6. Boot the target computer through the PXE boot system

Boot the target computer through the PXE boot system.

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M00/6B/D3/wKioL1U4PG2SnIBWAAB6vdo9Rdc078.jpg" width= "561" height= "337"/ >

The PE image will be loaded after successful boot

650) this.width=650; "Style=" background-image:none;padding-left:0px;padding-right:0px;border-top-width:0px; border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/6b/d7/wkiom1u4oxcr9zz-aabhsorv_bc953.jpg "width=" 640 "height=" 135 "/>

Entering the PE environment, enter the previously set password

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M01/6B/D7/wKiom1U4OxHA-Dk9AAHQ6OUmy2c581.jpg" width= "770" height= "440"/ >

Select a task sequence and execute

650) this.width=650; "Style=" background-image:none;margin:0px;padding-left:0px;padding-right:0px; border-top-width:0px;border-bottom-width:0px;border-left-width:0px;padding-top:0px; "title=" image "border=" 0 "alt = "image" src= "http://s3.51cto.com/wyfs02/M02/6B/D7/wKiom1U4OxKy1_gfAAGtRHx9gvI452.jpg" width= "757" height= "402"/ >

If everything works, a few reboots will eventually complete the deployment of the operating system. If you encounter an error, you can analyze the cause through error reporting and several important logs.

SCCM provides a viewer log tool for the Configuration Manager Trace Log tool in the SCCM default installation path C:\Program Files\Microsoft System Center R2\ The Configuration Manager\tools\cmtrace.exe can be found.

The log files for SCCM are under the default installation path C:\Program Files\Microsoft System Center R2\configuration Manager\logs. During the operating system distribution process, the SMSPXE.log and SMSProv.log files can be viewed primarily. The log file Smsts.log file is also generated on the target computer, and its location on the target computer differs from the different stages of the task sequence execution, and can be consulted sccm:how to copy SMSTS.log when a task Sequence fails.

This article is from the "Qingspace" blog, make sure to keep this source http://qingspace.blog.51cto.com/1165011/1637409

SCCM R2 Installation deployment process and issues (iii)