deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Add periods to alt text

Browse Source 
No other changes
This commit is contained in:
Gary Moore
2021-08-21 13:08:01 -07:00
parent 963086456e
commit 17262985e6
406 changed files with 2100 additions and 2100 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/deploy-windows-cm/add-a-windows-10-operating-system-image-using-configuration-manager.md
View File

@ -42,7 +42,7 @@ An existing Configuration Manager infrastructure that is integrated with MDT is
1. Using File Explorer, in the **D:\\Sources\\OSD\\OS** folder, create a subfolder named **Windows 10 Enterprise x64 RTM**.
2. Copy the REFW10-X64-001.wim file to the **D:\\Sources\\OSD\\OS\\Windows 10 Enterprise x64 RTM** folder.
![figure 17](../images/ref-image.png)
![figure 17.](../images/ref-image.png)
The Windows 10 image being copied to the Sources folder structure.
@ -53,7 +53,7 @@ An existing Configuration Manager infrastructure that is integrated with MDT is
7. In the Distribute Content Wizard, add the CM01 distribution point, click **Next** and click **Close**.
8. View the content status for the Windows 10 Enterprise x64 RTM package. Do not continue until the distribution is completed (it might take a few minutes). You also can review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for the **STATMSG: ID=2301** line.
![figure 18](../images/fig18-distwindows.png)
![figure 18.](../images/fig18-distwindows.png)
The distributed Windows 10 Enterprise x64 RTM package.

16
windows/deployment/deploy-windows-cm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md
View File

@ -38,7 +38,7 @@ This section will show you how to import some network and storage drivers for Wi
This section assumes you have downloaded some drivers to the **D:\\Sources\\OSD\\DriverSources\\WinPE x64** folder on CM01.
![Drivers](../images/cm01-drivers.png)
![Drivers.](../images/cm01-drivers.png)
Driver folder structure on CM01
@ -52,10 +52,10 @@ On **CM01**:
6. In the popup window that appears, click **Yes** to automatically update the distribution point.
7. Click **Next**, wait for the image to be updated, and then click **Close**.
![Add drivers to Windows PE step 1](../images/fig21-add-drivers1.png)<br>
![Add drivers to Windows PE step 2](../images/fig21-add-drivers2.png)<br>
![Add drivers to Windows PE step 3](../images/fig21-add-drivers3.png)<br>
![Add drivers to Windows PE step 4](../images/fig21-add-drivers4.png)
![Add drivers to Windows PE step 1.](../images/fig21-add-drivers1.png)<br>
![Add drivers to Windows PE step 2.](../images/fig21-add-drivers2.png)<br>
![Add drivers to Windows PE step 3.](../images/fig21-add-drivers3.png)<br>
![Add drivers to Windows PE step 4.](../images/fig21-add-drivers4.png)
Add drivers to Windows PE
@ -65,7 +65,7 @@ This section illustrates how to add drivers for Windows 10 using the HP EliteBoo
For the purposes of this section, we assume that you have downloaded the Windows 10 drivers for the HP EliteBook 8560w model and copied them to the **D:\Sources$\OSD\DriverSources\Windows 10 x64\Hewlett-Packard\HP EliteBook 8560w** folder on CM01.
![Drivers in Windows](../images/cm01-drivers-windows.png)
![Drivers in Windows.](../images/cm01-drivers-windows.png)
Driver folder structure on CM01
@ -75,7 +75,7 @@ On **CM01**:
2. In the Import New Driver Wizard, on the **Specify a location to import driver** page, select the **Import all drivers in the following network path (UNC)** option, browse to the **\\\\CM01\\Sources$\\OSD\\DriverSources\\Windows 10 x64\\Hewlett-Packard\\HP EliteBook 8560w** folder and click **Next**. Wait a minute for driver information to be validated.
3. On the **Specify the details for the imported driver** page, click **Categories**, create a category named **Windows 10 x64 - HP EliteBook 8560w**, click **OK**, and then click **Next**.
![Create driver categories](../images/fig22-createcategories.png "Create driver categories")
![Create driver categories.](../images/fig22-createcategories.png "Create driver categories")
Create driver categories
@ -93,7 +93,7 @@ On **CM01**:
>[!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/cm01-drivers-packages.png "Drivers imported and a new driver package created")
![Drivers imported and a new driver package created.](../images/cm01-drivers-packages.png "Drivers imported and a new driver package created")
Drivers imported and a new driver package created

10
windows/deployment/deploy-windows-cm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md
View File

@ -61,7 +61,7 @@ On **CM01**:
4. On the **Options** page, select the **x64** platform, and click **Next**.
5. On the **Components** page, in addition to the default selected **Microsoft Data Access Components (MDAC/ADO)** support, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** check box and click **Next**.
![Add the DaRT component to the Configuration Manager boot image](../images/mdt-06-fig16.png "Add the DaRT component to the Configuration Manager boot image")
![Add the DaRT component to the Configuration Manager boot image.](../images/mdt-06-fig16.png "Add the DaRT component to the Configuration Manager boot image")
Add the DaRT component to the Configuration Manager boot image.
@ -72,8 +72,8 @@ On **CM01**:
8. In the Distribute Content Wizard, add the CM01 distribution point, and complete the wizard.
9. Using Configuration Manager Trace, review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Do not continue until you can see that the boot image is distributed. Look for the line that reads **STATMSG: ID=2301**. You also can monitor Content Status in the Configuration Manager Console at **\Monitoring\Overview\Distribution Status\Content Status\Zero Touch WinPE x64**. See the following examples:
![Content status for the Zero Touch WinPE x64 boot image step 1](../images/fig16-contentstatus1.png)<br>
![Content status for the Zero Touch WinPE x64 boot image step 2](../images/fig16-contentstatus2.png)
![Content status for the Zero Touch WinPE x64 boot image step 1.](../images/fig16-contentstatus1.png)<br>
![Content status for the Zero Touch WinPE x64 boot image step 2.](../images/fig16-contentstatus2.png)
Content status for the Zero Touch WinPE x64 boot image
@ -82,8 +82,8 @@ On **CM01**:
12. Using Configuration Manager Trace, review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for this text: **Expanding PS100009 to D:\\RemoteInstall\\SMSImages**.
13. Review the **D:\\RemoteInstall\\SMSImages** folder. You should see three folders containing boot images. Two are from the default boot images, and the third folder (PS100009) is from your new boot image with DaRT. See the examples below:
![PS100009 step 1](../images/ps100009-1.png)<br>
![PS100009 step 2](../images/ps100009-2.png)
![PS100009 step 1.](../images/ps100009-1.png)<br>
![PS100009 step 2.](../images/ps100009-2.png)
>Note: Depending on your infrastructure and the number of packages and boot images present, the Image ID might be a different number than PS100009.

4
windows/deployment/deploy-windows-cm/create-a-task-sequence-with-configuration-manager-and-mdt.md
View File

@ -87,14 +87,14 @@ On **CM01**:
>[!NOTE]
>You also can add a Query WMI condition with the following query: SELECT \* FROM Win32\_ComputerSystem WHERE Model LIKE '%HP EliteBook 8560w%'
![Driver package options](../images/fig27-driverpackage.png "Driver package options")
![Driver package options.](../images/fig27-driverpackage.png "Driver package options")
The driver package options
7. In the **State Restore / Install Applications** group, select the **Install Application** action.
8. Select the **Install the following applications** radio button, and add the OSD / Adobe Reader DC - OSD Install application to the list.
![Add an application to the task sequence](../images/fig28-addapp.png "Add an application to the task sequence")
![Add an application to the task sequence.](../images/fig28-addapp.png "Add an application to the task sequence")
Add an application to the Configuration Manager task sequence

4
windows/deployment/deploy-windows-cm/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md
View File

@ -54,7 +54,7 @@ On **CM01**:
* Type: Windows Installer (\*.msi file)
* Location: \\\\CM01\\Sources$\\Software\\Adobe\\AcroRead.msi
![The Create Application Wizard](../images/mdt-06-fig20.png "The Create Application Wizard")
![The Create Application Wizard.](../images/mdt-06-fig20.png "The Create Application Wizard")
The Create Application Wizard
@ -65,7 +65,7 @@ On **CM01**:
>[!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")
Add the "OSD Install" suffix to the application name

30
windows/deployment/deploy-windows-cm/deploy-windows-10-using-pxe-and-configuration-manager.md
View File

@ -65,7 +65,7 @@ All server and client computers referenced in this guide are on the same subnet.
>[!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.
![MDT monitoring](../images/pc0001-monitor.png)
![MDT monitoring.](../images/pc0001-monitor.png)
Monitoring the deployment with MDT.
@ -73,20 +73,20 @@ All server and client computers referenced in this guide are on the same subnet.
Examples are provided below of various stages of deployment:
![pc0001a](../images/pc0001a.png)<br>
![pc0001b](../images/pc0001b.png)<br>
![pc0001c](../images/pc0001c.png)<br>
![pc0001d](../images/pc0001d.png)<br>
![pc0001e](../images/pc0001e.png)<br>
![pc0001f](../images/pc0001f.png)<br>
![pc0001g](../images/pc0001g.png)<br>
![pc0001h](../images/pc0001h.png)<br>
![pc0001i](../images/pc0001i.png)<br>
![pc0001j](../images/pc0001j.png)<br>
![pc0001k](../images/pc0001k.png)<br>
![pc0001l](../images/pc0001l.png)<br>
![pc0001m](../images/pc0001m.png)<br>
![pc0001n](../images/pc0001n.png)
![pc0001a.](../images/pc0001a.png)<br>
![pc0001b.](../images/pc0001b.png)<br>
![pc0001c.](../images/pc0001c.png)<br>
![pc0001d.](../images/pc0001d.png)<br>
![pc0001e.](../images/pc0001e.png)<br>
![pc0001f.](../images/pc0001f.png)<br>
![pc0001g.](../images/pc0001g.png)<br>
![pc0001h.](../images/pc0001h.png)<br>
![pc0001i.](../images/pc0001i.png)<br>
![pc0001j.](../images/pc0001j.png)<br>
![pc0001k.](../images/pc0001k.png)<br>
![pc0001l.](../images/pc0001l.png)<br>
![pc0001m.](../images/pc0001m.png)<br>
![pc0001n.](../images/pc0001n.png)
Next, see [Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md).

12
windows/deployment/deploy-windows-cm/finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md
View File

@ -44,7 +44,7 @@ On **CM01**:
2. Right-click the **MDT Production** deployment share, and click **Properties**. On the **Monitoring** tab, select the **Enable monitoring for this deployment share** check box, and click **OK**.
![Enable MDT monitoring for Configuration Manager](../images/mdt-06-fig31.png)
![Enable MDT monitoring for Configuration Manager.](../images/mdt-06-fig31.png)
Enable MDT monitoring for Configuration Manager
@ -80,7 +80,7 @@ On **CM01**:
ApplyGPOPack=NO
```
![Settings package during deployment](../images/fig30-settingspack.png)
![Settings package during deployment.](../images/fig30-settingspack.png)
The Settings package, holding the rules and the Unattend.xml template used during deployment
@ -99,7 +99,7 @@ On **CM01**:
2. In the Distribute Content Wizard, click **Next** twice then on the **Specify the content destination** page add the Distribution Point: **CM01.CONTOSO.COM**, and then complete the wizard.
3. Using the CMTrace tool, 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.
![Content status](../images/cm01-content-status1.png)
![Content status.](../images/cm01-content-status1.png)
Content status
@ -116,7 +116,7 @@ On **CM01**:
* Purpose: Available
* Make available to the following: Only media and PXE
![Configure the deployment settings](../images/mdt-06-fig33.png)
![Configure the deployment settings.](../images/mdt-06-fig33.png)
Configure the deployment settings
@ -125,7 +125,7 @@ On **CM01**:
6. On the **Alerts** page, accept the default settings and click **Next**.
7. On the **Distribution Points** page, accept the default settings, click **Next** twice, and then click **Close**.
![Task sequence deployed](../images/fig32-deploywiz.png)
![Task sequence deployed.](../images/fig32-deploywiz.png)
The Windows 10 Enterprise x64 RTM task sequence deployed to the All Unknown Computers collections available for media and PXE
@ -149,7 +149,7 @@ On **CM01**:
>[!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)
![Configure a collection variable.](../images/mdt-06-fig35.png)
Configure a collection variable

22
windows/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
View File

@ -209,7 +209,7 @@ On **CM01**:
* Site Server Name: CM01.contoso.com
* Site code: PS1
![figure 8](../images/mdt-06-fig08.png)
![figure 8.](../images/mdt-06-fig08.png)
MDT integration with Configuration Manager.
@ -223,11 +223,11 @@ On **CM01**:
2. In the right pane, right-click **Default Client Settings** and then click **Properties**.
3. In the **Computer Agent** node, in the **Organization name displayed in Software Center** text box, type in **Contoso** and click **OK**.
![figure 9](../images/mdt-06-fig10.png)
![figure 9.](../images/mdt-06-fig10.png)
Configure the organization name in client settings.
![figure 10](../images/fig10-contosoinstall.png)
![figure 10.](../images/fig10-contosoinstall.png)
The Contoso organization name displayed during deployment.
@ -241,7 +241,7 @@ On **CM01**:
2. Right-click **PS1 - Primary Site 1**, point to **Configure Site Components**, and then select **Software Distribution**.
3. On the **Network Access Account** tab, select **Specify the account that accesses network locations** and add the *New Account* **CONTOSO\\CM\_NAA** as the Network Access account (password: pass@word1). Use the new **Verify** option to verify that the account can connect to the **\\\\DC01\\sysvol** network share.
![figure 11](../images/mdt-06-fig12.png)
![figure 11.](../images/mdt-06-fig12.png)
Test the connection for the Network Access account.
@ -261,7 +261,7 @@ On **CM01**:
* Require a password when computers use PXE
* Password and Confirm password: pass@word1
![figure 12](../images/mdt-06-fig13.png)
![figure 12.](../images/mdt-06-fig13.png)
Configure the CM01 distribution point for PXE.
@ -270,13 +270,13 @@ On **CM01**:
4. Using the CMTrace tool, review the C:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Look for ConfigurePXE and CcmInstallPXE lines.
![figure 13](../images/mdt-06-fig14.png)
![figure 13.](../images/mdt-06-fig14.png)
The distmgr.log displays a successful configuration of PXE on the distribution point.
5. Verify that you have seven files in each of the folders **D:\\RemoteInstall\\SMSBoot\\x86** and **D:\\RemoteInstall\\SMSBoot\\x64**.
![figure 14](../images/mdt-06-fig15.png)
![figure 14.](../images/mdt-06-fig15.png)
The contents of the D:\\RemoteInstall\\SMSBoot\\x64 folder after you enable PXE.
@ -341,7 +341,7 @@ The task sequence uses instructions that allow you to reduce the number of task
MachineObjectOU=ou=desktops,ou=Contoso,dc=contoso,dc=com
```
![figure 2](../images/fig2-gather.png)
![figure 2.](../images/fig2-gather.png)
The Gather action in the task sequence is reading the rules.
@ -349,7 +349,7 @@ The Gather action in the task sequence is reading the rules.
When testing a deployment, it is important to be able to quickly test any changes you make to the deployment without needing to run through an entire deployment. MDT rules can be tested very quickly, saving significant testing time in a deployment project. For more information, see [Configure MDT settings](../deploy-windows-mdt/configure-mdt-settings.md).
![figure 3](../images/mdt-06-fig03.png)
![figure 3.](../images/mdt-06-fig03.png)
The folder that contains the rules, a few scripts from MDT, and a custom script (Gather.ps1).
@ -357,7 +357,7 @@ The folder that contains the rules, a few scripts from MDT, and a custom script
With MDT integration, you can follow your deployments in real time, and if you have access to Microsoft Diagnostics and Recovery Toolkit (DaRT), you can even remote into Windows Preinstallation Environment (Windows PE) during deployment. The real-time monitoring data can be viewed from within the MDT Deployment Workbench, via a web browser, Windows PowerShell, the Event Viewer, or Microsoft Excel 2013. In fact, any script or app that can read an Open Data (OData) feed can read the information.
![figure 4](../images/mdt-06-fig04.png)
![figure 4.](../images/mdt-06-fig04.png)
View the real-time monitoring data with PowerShell.
@ -365,7 +365,7 @@ View the real-time monitoring data with PowerShell.
For some deployment scenarios, you may need to prompt the user for information during deployment such as the computer name, the correct organizational unit (OU) for the computer, or which applications should be installed by the task sequence. With MDT integration, you can enable the User-Driven Installation (UDI) wizard to gather the required information, and customize the wizard using the UDI Wizard Designer.
![figure 5](../images/mdt-06-fig05.png)
![figure 5.](../images/mdt-06-fig05.png)
The optional UDI wizard open in the UDI Wizard Designer.

22
windows/deployment/deploy-windows-cm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md
View File

@ -60,7 +60,7 @@ On **PC0003**:
2. On the **Site** tab, click **Configure Settings**, then click **Find Site**.
3. Verify that Configuration Manager has successfully found a site to manage this client is displayed. See the following example.
![Found a site to manage this client](../images/pc0003a.png)
![Found a site to manage this client.](../images/pc0003a.png)
## Create a device collection and add the PC0003 computer
@ -124,16 +124,16 @@ On **PC0003**:
2. In the **Software Center** warning dialog box, click **Install Operating System**.
3. The client computer will run the Configuration Manager task sequence, boot into Windows PE, and install the new OS and applications. See the following examples:
![Task sequence example 1](../images/pc0003b.png)<br>
![Task sequence example 2](../images/pc0003c.png)<br>
![Task sequence example 3](../images/pc0003d.png)<br>
![Task sequence example 4](../images/pc0003e.png)<br>
![Task sequence example 5](../images/pc0003f.png)<br>
![Task sequence example 6](../images/pc0003g.png)<br>
![Task sequence example 7](../images/pc0003h.png)<br>
![Task sequence example 8](../images/pc0003i.png)<br>
![Task sequence example 9](../images/pc0003j.png)<br>
![Task sequence example 10](../images/pc0003k.png)
![Task sequence example 1.](../images/pc0003b.png)<br>
![Task sequence example 2.](../images/pc0003c.png)<br>
![Task sequence example 3.](../images/pc0003d.png)<br>
![Task sequence example 4.](../images/pc0003e.png)<br>
![Task sequence example 5.](../images/pc0003f.png)<br>
![Task sequence example 6.](../images/pc0003g.png)<br>
![Task sequence example 7.](../images/pc0003h.png)<br>
![Task sequence example 8.](../images/pc0003i.png)<br>
![Task sequence example 9.](../images/pc0003j.png)<br>
![Task sequence example 10.](../images/pc0003k.png)
Next, see [Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md).

24
windows/deployment/deploy-windows-cm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md
View File

@ -69,7 +69,7 @@ On **CM01**:
>[!NOTE]
>This task sequence has many fewer actions than the normal client task sequence. If it doesn't seem different, make sure you selected the **Client Replace Task Sequence** template when creating the task sequence.
![The back-up only task sequence](../images/mdt-06-fig42.png "The back-up only task sequence")
![The back-up only task sequence.](../images/mdt-06-fig42.png "The back-up only task sequence")
The backup-only task sequence (named Replace Task Sequence).
@ -91,7 +91,7 @@ On **CM01**:
* MAC Address: &lt;the mac address that you wrote down&gt;
* Source Computer: PC0004
![Create the computer association](../images/mdt-06-fig43.png "Create the computer association")
![Create the computer association.](../images/mdt-06-fig43.png "Create the computer association")
Creating the computer association between PC0004 and PC0006.
@ -160,7 +160,7 @@ On **PC0004**:
4. Confirm you want to upgrade the operating system on this computer by clicking **Install** again.
5. Allow the Replace Task Sequence to complete. The PC0004 computer will gather user data, boot into Windows PE and gather more data, then boot back to the full OS. The entire process should only take a few minutes.
![Task sequence example](../images/pc0004b.png)
![Task sequence example.](../images/pc0004b.png)
Capturing the user state
@ -191,15 +191,15 @@ On **PC0006**:
When the process is complete, you will have a new Windows 10 computer in your domain with user data and settings restored. See the following examples:
![User data and setting restored example 1](../images/pc0006a.png)<br>
![User data and setting restored example 2](../images/pc0006b.png)<br>
![User data and setting restored example 3](../images/pc0006c.png)<br>
![User data and setting restored example 4](../images/pc0006d.png)<br>
![User data and setting restored example 5](../images/pc0006e.png)<br>
![User data and setting restored example 6](../images/pc0006f.png)<br>
![User data and setting restored example 7](../images/pc0006g.png)<br>
![User data and setting restored example 8](../images/pc0006h.png)<br>
![User data and setting restored example 9](../images/pc0006i.png)
![User data and setting restored example 1.](../images/pc0006a.png)<br>
![User data and setting restored example 2.](../images/pc0006b.png)<br>
![User data and setting restored example 3.](../images/pc0006c.png)<br>
![User data and setting restored example 4.](../images/pc0006d.png)<br>
![User data and setting restored example 5.](../images/pc0006e.png)<br>
![User data and setting restored example 6.](../images/pc0006f.png)<br>
![User data and setting restored example 7.](../images/pc0006g.png)<br>
![User data and setting restored example 8.](../images/pc0006h.png)<br>
![User data and setting restored example 9.](../images/pc0006i.png)
Next, see [Perform an in-place upgrade to Windows 10 using Configuration Manager](upgrade-to-windows-10-with-configuraton-manager.md).

16
windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md
View File

@ -71,7 +71,7 @@ On **CM01**:
4. Complete the wizard, and click **Close**.
5. Review the Upgrade Task Sequence.
![The upgrade task sequence](../images/cm-upgrade-ts.png)
![The upgrade task sequence.](../images/cm-upgrade-ts.png)
The Configuration Manager upgrade task sequence
@ -127,13 +127,13 @@ On **PC0004**:
4. Confirm you want to upgrade the operating system on this computer by clicking **Install** again.
5. Allow the Upgrade Task Sequence to complete. The PC0004 computer will download the install.wim file, perform an in-place upgrade, and install your added applications. See the following examples:
![Upgrade task sequence example 1](../images/pc0004-a.png)<br>
![Upgrade task sequence example 2](../images/pc0004-b.png)<br>
![Upgrade task sequence example 3](../images/pc0004-c.png)<br>
![Upgrade task sequence example 4](../images/pc0004-d.png)<br>
![Upgrade task sequence example 5](../images/pc0004-e.png)<br>
![Upgrade task sequence example 6](../images/pc0004-f.png)<br>
![Upgrade task sequence example 7](../images/pc0004-g.png)
![Upgrade task sequence example 1.](../images/pc0004-a.png)<br>
![Upgrade task sequence example 2.](../images/pc0004-b.png)<br>
![Upgrade task sequence example 3.](../images/pc0004-c.png)<br>
![Upgrade task sequence example 4.](../images/pc0004-d.png)<br>
![Upgrade task sequence example 5.](../images/pc0004-e.png)<br>
![Upgrade task sequence example 6.](../images/pc0004-f.png)<br>
![Upgrade task sequence example 7.](../images/pc0004-g.png)
In-place upgrade with Configuration Manager