From a58be96a9ec94e2d07c29d6d0e3318b710535430 Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Mon, 19 Sep 2016 13:33:04 -0700 Subject: [PATCH 1/2] fix spacing; figures --- ...-windows-pe-using-configuration-manager.md | 13 ++++--- ...-windows-10-using-configuration-manager.md | 34 ++++++++----------- 2 files changed, 21 insertions(+), 26 deletions(-) diff --git a/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md b/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md index 425d7331d5..5cad45cd88 100644 --- a/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md +++ b/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md @@ -36,13 +36,12 @@ This section will show you how to import some network and storage drivers for Wi 5. On the **Select drivers to include in the boot image** page, select the **Zero Touch WinPE x64** boot image. Also select the **Update distribution points when finished** check box, and click **Next** twice. -![figure 21](images/fig21-add-drivers.png) +![Add drivers to Windows PE](images/fig21-add-drivers.png "Add drivers to Windows PE") -Figure 21. Add drivers to Windows PE. - -**Note**   -The Updating Boot Image part of the wizard will appear to hang when displaying Done. It will complete in a minute or two. +*Figure 21. Add drivers to Windows PE* +>[NOTE]   +>The Updating Boot Image part of the wizard will appear to hang when displaying Done. It will complete in a minute or two.   ## Add drivers for Windows 10 @@ -56,9 +55,9 @@ This section illustrates how to add drivers for Windows 10 through an example in 3. On the **Specify the details for the imported driver** page, click **Categories**, create a category named Windows 10 x64 - HP EliteBook 8560w, and then click **Next**. - ![figure 22](images/fig22-createcategories.png) + ![Create driver categories](images/fig22-createcategories.png "Create driver categories") - Figure 22. Create driver categories. + *Figure 22. Create driver categories* 4. On the **Select the packages to add the imported driver** page, click **New Package**, use the following settings for the package, and then click **Next**: diff --git a/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md b/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md index 4ee378dc32..caedb91233 100644 --- a/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md +++ b/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md @@ -22,15 +22,13 @@ Microsoft System Center 2012 R2 Configuration Manager supports deploying applica For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member 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](deploy-windows-10-with-the-microsoft-deployment-toolkit.md). -**Note**   -Even though the new application model is fully supported to deploy via the task sequence, the most reliable way to deploy software via the task sequence is still the legacy packages, especially if you deploy many applications. - -  +>[NOTE]   +>Even though the new application model is fully supported to deploy via the task sequence, the most reliable way to deploy software via the task sequence is still the legacy packages, especially if you deploy many applications. ## Example: Create the Adobe Reader XI application -The steps below show you how to create the Adobe Reader XI application. This section assumes that you have downloaded the MSI version of Adobe Reader XI to the C:\\Setup\\Adobe Reader XI folder on CM01. +The following steps show you how to create the Adobe Reader XI application. This section assumes that you have downloaded the MSI version of Adobe Reader XI to the C:\\Setup\\Adobe Reader XI folder on CM01. 1. On CM01, using File Explorer, copy the **C:\\Setup\\Adobe Reader XI** folder to the **E:\\Sources\\Software\\Adobe** folder. @@ -42,17 +40,17 @@ The steps below show you how to create the Adobe Reader XI application. This sec 5. In the Create Application Wizard, on the **General** page, use the following settings: - 1. Automatically detect information about this application from installation files + * Automatically detect information about this application from installation files - 2. Type: Windows Installer (\*.msi file) + * Type: Windows Installer (\*.msi file) - 3. Location: \\\\CM01\\Sources$\\Software\\Adobe\\Adobe Reader XI + * Location: \\\\CM01\\Sources$\\Software\\Adobe\\Adobe Reader XI - 4. \\AdbeRdr11000\_en\_US.msi + * \\AdbeRdr11000\_en\_US.msi - ![figure 19](images/mdt-06-fig20.png) + ![The Create Application Wizard](images/mdt-06-fig20.png "The Create Application Wizard") - Figure 19. The Create Application Wizard. + *Figure 19. The Create Application Wizard* 6. Click **Next**, and wait while Configuration Manager parses the MSI file. @@ -60,14 +58,12 @@ The steps below show you how to create the Adobe Reader XI application. This sec 8. On the **General Information** page, name the application Adobe Reader XI - OSD Install, click **Next** twice, and then click **Close**. - **Note**   - Since it is not possible to reference an application deployment type in the task sequence, you should have a single deployment type for applications deployed by the task sequence. If you are deploying applications via both the task sequence and normal application deployment, and you have multiple deployment types, you should have two applications of the same software. In this section, you add the "OSD Install" suffix to applications that are deployed via the task sequence. If using packages, you can still reference both package and program in the task sequence. - -   - - ![figure 20](images/mdt-06-fig21.png) - - Figure 20. Add the "OSD Install" suffix to the application name. + >[NOTE] + >Because it is not possible to reference an application deployment type in the task sequence, you should have a single deployment type for applications deployed by the task sequence. If you are deploying applications via both the task sequence and normal application deployment, and you have multiple deployment types, you should have two applications of the same software. In this section, you add the "OSD Install" suffix to applications that are deployed via the task sequence. If using packages, you can still reference both package and program in the task sequence. + + ![Add the OSD Install suffix to the application name](images/mdt-06-fig21.png "Add the OSD Install suffix to the application name") + + *Figure 20. Add the "OSD Install" suffix to the application name* 9. In the **Applications** node, select the Adobe Reader XI - OSD Install application, and click **Properties** on the ribbon bar. From 735b78d15bb6a5a7e638083b4252aeee4b238ac9 Mon Sep 17 00:00:00 2001 From: Jan Backstrom Date: Mon, 19 Sep 2016 13:47:52 -0700 Subject: [PATCH 2/2] fix note format --- ...-windows-pe-using-configuration-manager.md | 25 ++++++++----------- ...-windows-10-using-configuration-manager.md | 10 ++++---- 2 files changed, 16 insertions(+), 19 deletions(-) diff --git a/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md b/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md index 5cad45cd88..878c230d72 100644 --- a/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md +++ b/windows/deploy/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md @@ -40,7 +40,7 @@ This section will show you how to import some network and storage drivers for Wi *Figure 21. Add drivers to Windows PE* ->[NOTE]   +>[!NOTE]   >The Updating Boot Image part of the wizard will appear to hang when displaying Done. It will complete in a minute or two.   @@ -61,25 +61,22 @@ This section illustrates how to add drivers for Windows 10 through an example in 4. On the **Select the packages to add the imported driver** page, click **New Package**, use the following settings for the package, and then click **Next**: - 1. Name: Windows 10 x64 - HP EliteBook 8560w + * Name: Windows 10 x64 - HP EliteBook 8560w - 2. Path: \\\\CM01\\Sources$\\OSD\\DriverPackages\\Windows 10 x64\\HP EliteBook 8560w - - **Note**   - The package path does not yet exist, so you have to type it in. The wizard will create the new package in that folder. + * Path: \\\\CM01\\Sources$\\OSD\\DriverPackages\\Windows 10 x64\\HP EliteBook 8560w + >[!NOTE]   + >The package path does not yet exist, so you have to type it in. The wizard will create the new package in that folder.   5. On the **Select drivers to include in the boot image** page, do not select anything, and click **Next** twice. After the package has been created, click **Close**. -**Note**   -If you want to monitor the driver import process more closely, you can open the SMSProv.log file during driver import. - -  - -![figure 23](images/mdt-06-fig26.png) - -Figure 23. Drivers imported and a new driver package created. + >[!NOTE]   + >If you want to monitor the driver import process more closely, you can open the SMSProv.log file during driver import. + + ![Drivers imported and a new driver package created](images/mdt-06-fig26.png "Drivers imported and a new driver package created") + + *Figure 23. Drivers imported and a new driver package created* ## Related topics diff --git a/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md b/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md index caedb91233..4e7b504b13 100644 --- a/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md +++ b/windows/deploy/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md @@ -22,7 +22,7 @@ Microsoft System Center 2012 R2 Configuration Manager supports deploying applica For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member 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](deploy-windows-10-with-the-microsoft-deployment-toolkit.md). ->[NOTE]   +>[!NOTE]   >Even though the new application model is fully supported to deploy via the task sequence, the most reliable way to deploy software via the task sequence is still the legacy packages, especially if you deploy many applications. ## Example: Create the Adobe Reader XI application @@ -58,12 +58,12 @@ The following steps show you how to create the Adobe Reader XI application. This 8. On the **General Information** page, name the application Adobe Reader XI - OSD Install, click **Next** twice, and then click **Close**. - >[NOTE] - >Because it is not possible to reference an application deployment type in the task sequence, you should have a single deployment type for applications deployed by the task sequence. If you are deploying applications via both the task sequence and normal application deployment, and you have multiple deployment types, you should have two applications of the same software. In this section, you add the "OSD Install" suffix to applications that are deployed via the task sequence. If using packages, you can still reference both package and program in the task sequence. + >[!NOTE] + >Because it is not possible to reference an application deployment type in the task sequence, you should have a single deployment type for applications deployed by the task sequence. If you are deploying applications via both the task sequence and normal application deployment, and you have multiple deployment types, you should have two applications of the same software. In this section, you add the "OSD Install" suffix to applications that are deployed via the task sequence. If using packages, you can still reference both package and program in the task sequence. - ![Add the OSD Install suffix to the application name](images/mdt-06-fig21.png "Add the OSD Install suffix to the application name") + ![Add the OSD Install suffix to the application name](images/mdt-06-fig21.png "Add the OSD Install suffix to the application name") - *Figure 20. Add the "OSD Install" suffix to the application name* + *Figure 20. Add the "OSD Install" suffix to the application name* 9. In the **Applications** node, select the Adobe Reader XI - OSD Install application, and click **Properties** on the ribbon bar.