Appendix: Create a provisioning package with desktop applications by using audit mode

You can add desktop applications in audit mode to a PC and then export that to a provisioning package so you can add them to an image by using Windows Imaging and Configuration Designer (ICD).

In this topic, we'll see how you can add a desktop application to a provisioning package.

Step 1: Install a desktop application in audit mode

  1. On the reference PC, install the image that was created in Part 1. If the image is already installed, start the reference PC. The Hi there screen appears.
  2. Press Ctrl+Shift+F3 to enter Audit mode. The device reboots to the desktop, and the System Preparation Tool (Sysprep) appears. You can close Sysprep.
    Note  

    You may also see alerts such as "This app can't open."

    Many Windows features, including the Start menu and the Settings menu, do not work in this environment.

  3. Ensure that your customizations from Part 1 are available. To do this, press the Windows key + the F1 key, and then click Contact Support to get to the help screens and see your technical support info that you entered from Part 1a: Customize and install your first Windows image.

  4. In this lab, we'll install the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint File Formats. You can find it on the USB key at Samples\Desktop Applications\FileFormatConverters.exe.

Step 2: Save your updates to a provisioning package

ScanState is provided on your USB key in the ScanState_x64 and ScanState_x86 folders.

Dn898440.wedge(en-us,VS.85).gifCapture your updates into a provisioning package

  1. Plug the USB key into the reference PC.
  2. Capture the changes into the provisioning package, and save it on the USB key.

    64-bit:

    D:\ScanState_x64\scanstate.exe /apps /ppkg D:\Samples\Provisioning\ /o /c /v:13 /l:D:\ScanState.log
    

    32-bit:

    D:\ScanState_x86\scanstate.exe /apps /ppkg D:\Samples\Provisioning\ /o /c /v:13 /l:D:\ScanState.log
    

    where D is the drive letter of the Windows partition.

Apply your provisioning package

At this point, you can apply this provisioning package to a new device by using the following commands. For the purposes of this lab, we won't apply the provisioning package.

64-bit:


"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe" /Build-ImageFromWIM /CustomizationXML:"C:\DFest\Samples\Provisioning\customizations.xml" /MediaPath:"C:\NewBootableUSBKey" /SourceImage:"C:\DFest\Win10 Home Tech Prev x64\sources\install.wim" /ImageIndex:1 /ProvisioningPackage:"D:\Samples\Provisioning\usmt.ppkg" /DeploymentConfigXml:"C:\DFest\Samples\Provisioning\DeploymentConfig.xml"

32-bit:

"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe" /Build-ImageFromWIM /CustomizationXML:"C:\DFest\Samples\Provisioning\customizations.xml" /MediaPath:"C:\NewBootableUSBKey" /SourceImage:"C:\DFest\Win10 Home Tech Prev x86\sources\install.wim" /ImageIndex:1 /ProvisioningPackage:"D:\Samples\Provisioning\usmt.ppkg" /DeploymentConfigXml:"C:\DFest\Samples\Provisioning\DeploymentConfig.xml"

where D is the drive letter of the Windows partition.

 

 

Show: