diff --git a/windows/deploy/finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md b/windows/deploy/finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md index 61adccf988..635e1c0291 100644 --- a/windows/deploy/finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md +++ b/windows/deploy/finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md @@ -6,7 +6,6 @@ keywords: configure, deploy, upgrade ms.prod: w10 localizationpriority: high ms.mktglfcycl: deploy -localizationpriority: high ms.sitesec: library author: mtniehaus --- @@ -29,19 +28,19 @@ This section will walk you through the process of creating the E:\\MDTProduction 1. 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: - 1. Deployment share path: E:\\MDTProduction + * Deployment share path: E:\\MDTProduction - 2. Share name: MDTProduction$ + * Share name: MDTProduction$ - 3. Deployment share description: MDT Production + * Deployment share description: MDT Production - 4. Options: <default settings> + * Options: <default settings> 2. 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](images/mdt-06-fig31.png) + ![Enable MDT monitoring for Configuration Manager](images/mdt-06-fig31.png) -Figure 26. Enabling MDT monitoring for Configuration Manager. + *Figure 26. Enable MDT monitoring for Configuration Manager* ## Create and share the Logs folder @@ -83,14 +82,14 @@ This section will show you how to configure the rules (the Windows 10 x64 Settin ApplyGPOPack=NO ``` - ![figure 27](images/fig30-settingspack.png) + ![Settings package during deployment](images/fig30-settingspack.png) - Figure 27. The Settings package, holding the rules and the Unattend.xml template used during deployment + *Figure 27. The Settings package, holding the rules and the Unattend.xml template used during deployment* 3. 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. + >[!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.   @@ -116,13 +115,13 @@ This sections provides steps to help you create a deployment for the task sequen 3. On the **Deployment Settings** page, use the following settings and then click **Next**: - 1. Purpose: Available + * Purpose: Available - 2. Make available to the following: Only media and PXE + * Make available to the following: Only media and PXE - ![figure 28](images/mdt-06-fig33.png) - - Figure 28. Configure the deployment settings. + ![Configure the deployment settings](images/mdt-06-fig33.png) + + *Figure 28. Configure the deployment settings* 4. On the **Scheduling** page, accept the default settings and click **Next**. @@ -132,9 +131,9 @@ This sections provides steps to help you create a deployment for the task sequen 7. On the **Distribution Points** page, accept the default settings, click **Next** twice, and then click **Close**. -![figure 29](images/fig32-deploywiz.png) + ![Task sequence deployed](images/fig32-deploywiz.png) -Figure 29. The Windows 10 Enterprise x64 RTM task sequence deployed to the All Unknown Computers collections available for media and PXE. + *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) @@ -147,20 +146,18 @@ This section provides steps to help you configure the All Unknown Computers coll 2. In the **Collection Variables** tab, create a new variable with the following settings: - 1. Name: OSDComputerName + * Name: OSDComputerName - 2. Clear the **Do not display this value in the Configuration Manager console** check box. + * Clear the **Do not display this value in the Configuration Manager console** check box. 3. 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](images/mdt-06-fig35.png) - -Figure 30. Configure a collection variable. + >[!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. + + ![Configure a collection variable](images/mdt-06-fig35.png) + + *Figure 30. Configure a collection variable* ## Related topics diff --git a/windows/deploy/monitor-windows-10-deployment-with-configuration-manager.md b/windows/deploy/monitor-windows-10-deployment-with-configuration-manager.md index 395beb960d..a2caee8ea8 100644 --- a/windows/deploy/monitor-windows-10-deployment-with-configuration-manager.md +++ b/windows/deploy/monitor-windows-10-deployment-with-configuration-manager.md @@ -25,32 +25,28 @@ To monitor an operating system deployment conducted through System Center 2012 R 1. On CM01, using the Deployment Workbench, expand **MDT Production**, and use the **Monitoring** node to view the deployment process (press **F5** to refresh). - **Note**   - It takes a little while for the task sequence to start reporting monitor information, so if PC0001 does not appear when you press F5 the first time, wait 20 seconds and try again. + >[!NOTE] + >It takes a little while for the task sequence to start reporting monitor information, so if PC0001 does not appear when you press F5 the first time, wait 20 seconds and try again. -   - - ![figure 33](images/mdt-06-fig39.png) - - Figure 33. PC0001 being deployed by Configuration Manager. + ![PC0001 being deployed by Configuration Manager](images/mdt-06-fig39.png) + + *Figure 33. PC0001 being deployed by Configuration Manager* 2. When you see the PC0001 entry, double-click **PC0001**, and then click **DaRT Remote Control** and review the **Remote Control** option. 3. The task sequence will now run and do the following: - 1. Install the Windows 10 operating system. + * Install the Windows 10 operating system. - 2. Install the Configuration Manager client and the client hotfix. + * Install the Configuration Manager client and the client hotfix. - 3. Join the machine to the domain. - - 4. Install the application added to the task sequence. - - **Note**   - You also can use the built-in reports to get information about ongoing deployments. For example, a task sequence report gives you a quick overview of the task sequence progress. - -   + * Join the machine to the domain. + * Install the application added to the task sequence. + + >[!NOTE] + >You also can use the built-in reports to get information about ongoing deployments. For example, a task sequence report gives you a quick overview of the task sequence progress. +   4. If time permits, allow the deployment of PC0001 to complete. Then log in as Administrator in the CONTOSO domain and verify that Adobe Reader XI was installed. ## Related topics diff --git a/windows/keep-secure/create-and-verify-an-efs-dra-certificate.md b/windows/keep-secure/create-and-verify-an-efs-dra-certificate.md index 4f1cf1dfd9..06392494c0 100644 --- a/windows/keep-secure/create-and-verify-an-efs-dra-certificate.md +++ b/windows/keep-secure/create-and-verify-an-efs-dra-certificate.md @@ -77,7 +77,7 @@ It's possible that you might revoke data from an unenrolled device only to later 1. Have your employee sign in to the unenrolled device, open a command prompt, and type: - `Robocopy “%localappdata%\Microsoft\WIP\Recovery” <“new_location”> /EFSRAW` + `Robocopy “%localappdata%\Microsoft\EDP\Recovery” <“new_location”> /EFSRAW` Where *<”new_location”>* is in a different directory. This can be on the employee’s device or on a Windows 8 or Windows Server 2012 or newer server file share that can be accessed while you're logged in as a data recovery agent. @@ -87,7 +87,7 @@ It's possible that you might revoke data from an unenrolled device only to later 3. Have your employee sign in to the unenrolled device, and type: - `Robocopy <”new_location”> “%localappdata%\Microsoft\WIP\Recovery\Input”` + `Robocopy <”new_location”> “%localappdata%\Microsoft\EDP\Recovery\Input”` 4. Ask the employee to lock and unlock the device. diff --git a/windows/manage/set-up-shared-or-guest-pc.md b/windows/manage/set-up-shared-or-guest-pc.md index 047004f0c0..f641f80569 100644 --- a/windows/manage/set-up-shared-or-guest-pc.md +++ b/windows/manage/set-up-shared-or-guest-pc.md @@ -100,6 +100,7 @@ Use the Windows ICD tool included in the Windows Assessment and Deployment Kit ( 11. (*Optional*) In the **Provisioning package security** window, you can choose to encrypt the package and enable package signing. - **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen. - **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Select...** and choosing the certificate you want to use to sign the package. + > [!IMPORTANT]   > We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently.