mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00

martyav c83e650685 items 57 to 87 reviewed

2019-12-20 16:29:18 -05:00

9.9 KiB

Raw Blame History

title, description, ms.assetid, ms.reviewer, manager, ms.author, keywords, ms.prod, ms.localizationpriority, ms.mktglfcycl, ms.sitesec, audience, author, ms.topic

title	description	ms.assetid	ms.reviewer	manager	ms.author	keywords	ms.prod	ms.localizationpriority	ms.mktglfcycl	ms.sitesec	audience	author	ms.topic
Finalize operating system configuration for Windows 10 deployment	Follow this walk-through to finalize the configuration of your Windows 10 operating deployment.	38b55fa8-e717-4689-bd43-8348751d493e		laurawi	greglin	configure, deploy, upgrade	w10	medium	deploy	library	itpro	greg-lindsay	article

Finalize the operating system configuration for Windows 10 deployment with Configuration Manager

Applies to

Windows 10 versions 1507, 1511

Important

For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see Scenarios to deploy enterprise operating systems with System Center Configuration Manager. Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see Support for Windows 10 for System Center Configuration Manager.

This topic walks you through the steps to finalize the configuration of your Windows 10 operating deployment, which includes enablement of the optional Microsoft Deployment Toolkit (MDT) monitoring for Microsoft System Center 2012 R2 Configuration Manager, logs folder creation, rules configuration, content distribution, and deployment of the previously created task sequence.

For the purposes of this topic, we will use two machines: DC01 and CM01. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard. Both are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see Deploy Windows 10 with the Microsoft Deployment Toolkit.

Enable MDT monitoring

This section will walk you through the process of creating the E:\MDTProduction deployment share using the MDT Deployment Workbench to enable monitoring for Configuration Manager.

On CM01, using the Deployment Workbench, right-click Deployment Shares and select New Deployment Share. Use the following settings for the New Deployment Share Wizard:
- Deployment share path: E:\MDTProduction
- Share name: MDTProduction$
- Deployment share description: MDT Production
- Options: <default settings>
Right-click the MDT Production deployment share, and select Properties. In the Monitoring tab, select the Enable monitoring for this deployment share check box, and click OK.

Figure 26. Enable MDT monitoring for Configuration Manager

To support additional server-side logging in Configuration Manager, you create and share the E:\Logs folder on CM01 using Windows PowerShell. Then in the next step, you enable server-side logging by modifying the CustomSettings.ini file used by the Configuration Manager task sequence.

On CM01, start an elevated Windows PowerShell prompt (run as Administrator).

Type the following commands, pressing Enter after each one:

New-Item -Path E:\Logs -ItemType directory
New-SmbShare -Name Logs$ -Path E:\Logs -ChangeAccess EVERYONE
icacls E:\Logs /grant '"CM_NAA":(OI)(CI)(M)'

Configure the rules (Windows 10 x64 Settings package)

This section will show you how to configure the rules (the Windows 10 x64 Settings package) to support the Contoso environment.

On CM01, using File Explorer, navigate to the E:\Sources\OSD\Settings\Windows 10 x64 Settings folder.

Using Notepad, edit the CustomSetting.ini file with the following settings:

[Settings]
Priority=Default
Properties=OSDMigrateConfigFiles,OSDMigrateMode
[Default]
DoCapture=NO
ComputerBackupLocation=NONE
MachineObjectOU=ou=Workstations,ou=Computers,ou=Contoso,dc=contoso,dc=com
OSDMigrateMode=Advanced
OSDMigrateAdditionalCaptureOptions=/ue:*\* /ui:CONTOSO\*
OSDMigrateConfigFiles=Miguser.xml,Migapp.xml
SLSHARE=\\CM01\Logs$
EventService=http://CM01:9800
ApplyGPOPack=NO

Figure 27. The Settings package, holding the rules and the Unattend.xml template used during deployment

Update the distribution point for the Windows 10 x64 Settings package by right-clicking the Windows 10 x64 Settings package and selecting Update Distribution Points.

Note

Although you have not yet added a distribution point, you still need to select Update Distribution Points. That process also updates the Configuration Manager 2012 content library with changes.

Distribute content to the CM01 distribution portal

In Configuration Manager, you can distribute all packages needed by a task sequence in a single task. In this section, you distribute packages that have not yet been distributed to the CM01 distribution point.

On CM01, using the Configuration Manager Console, select Task Sequences, right-click the Windows 10 Enterprise x64 RTM task sequence, and select Distribute Content.
In the Distribute Content Wizard, add the CM01 distribution point, and complete the wizard.
Using Configuration Manager Trace, verify the distribution to the CM01 distribution point by reviewing the distmgr.log file, or use the Distribution Status / Content Status option in the Monitoring workspace. Do not continue until you see all the new packages being distributed successfully.

Create a deployment for the task sequence

This sections provides steps to help you create a deployment for the task sequence.

On CM01, using the Configuration Manager Console, select Task Sequences, right-click Windows 10 Enterprise x64 RTM, and then select Deploy.
On the General page, select the All Unknown Computers collection and click Next.
On the Deployment Settings page, use the following settings and then click Next:
- Purpose: Available
- Make available to the following: Only media and PXE
Figure 28. Configure the deployment settings
On the Scheduling page, accept the default settings and click Next.
On the User Experience page, accept the default settings and click Next.
On the Alerts page, accept the default settings and click Next.
On the Distribution Points page, accept the default settings, click Next twice, and then click Close.

Figure 29. The Windows 10 Enterprise x64 RTM task sequence deployed to the All Unknown Computers collections available for media and PXE

Configure Configuration Manager to prompt for the computer name during deployment (optional)

You can have Configuration Manager prompt you for a computer name or you can use rules to generate a computer name. For more details on how to do this, see Configure MDT settings.

This section provides steps to help you configure the All Unknown Computers collection to have Configuration Manager prompt for computer names.

Using the Configuration Manager Console, in the Asset and Compliance workspace, select Device Collections, right-click All Unknown Computers, and select Properties.
In the Collection Variables tab, create a new variable with the following settings:
- Name: OSDComputerName
- Clear the Do not display this value in the Configuration Manager console check box.
Click OK.

Note

Configuration Manager can prompt for information in many ways. Using a collection variable with an empty value is just one of them. Another option is the User-Driven Installation (UDI) wizard.

Figure 30. Configure a collection variable