Lab 9: Make changes from Windows (audit mode)
You can use audit mode to customize Windows using the familiar Windows environment. In audit mode, you can add Windows desktop applications, change system settings, add data, and run scripts.
To make sure your audit mode changes are included in the recovery image, you'll need to capture these changes into a provisioning package using ScanState. This image gets used by the system recovery tools to restore your changes if things go wrong. You can optionally save drive space by running the applications directly from the compressed recovery files; this is known as single-instancing.
If you want to capture the changes in an image and apply it to other devices, you'll need to use the Sysprep tool to generalize the image.
Step 1: Prepare a copy of the Deployment and Imaging Tools
From the technician PC, copy the Deployment and Imaging Tools from the Windows ADK to external storage (for example, a storage USB key with drive letter D:).
CopyDandI.cmd amd64 D:\ADKTools\amd64
Don't overwrite the existing DISM files on the WinPE image.
Step 2: Get into audit mode
Boot up the reference device, if it's not already booted.
If the device boots to the Languages or the Get going fast screen, press Ctrl+Shift+F3 to enter Audit mode.
In audit mode, the device reboots to the Desktop, and the System Preparation Tool (Sysprep) appears. Ignore Sysprep for now.
Step 3: Customize the PC in audit mode.
- Install a Windows desktop application. Change system settings. Add data. Run scripts.
Example: Add Microsoft Office 2016
On your technician PC, prepare a USB key with the Office Deployment Tool:
a. Mount the ISO for the deployment tool from "X21-20432 Office v16.2 Deployment Tool for OEM OPK\Software - DVD\X21-20474 SW DVD5 Office 2016 v16.2.1 Deployment Tool for OEM\X21-20474.img"
b. Copy files from the mounted drive to the USB-B key, for example, (where E:\ is driver letter for USB-B) E:\OfficeV16.2.1
On your reference PC, open the Office Deployment Tool, for example: E:\Officev16.2.1\officedeploymenttool.exe
Provide folder path to extract files E:\Officev16.2.1. Setup.exe and configuration.xml are extracted to E:\Officev16.2.1
Get: Office v16.2.1 in the desired language, this sample uses English X21-20393 Office 2016 v16.2.1 English OPK
Mount "X21-20393 Office v16.2.1 English OPK\Software - DVD\X21-20435 SW DVD5 Office Pro 2016 32 64-bit English C2ROPK Pro HS HB OEM v16.2.1\X21-20435.img"
Copy the Office folder to USB-B (where E:\ is drive letter for USB-B) E:\OfficeV16.2.1
[Optional] if you applied a language pack to your Windows image, you may want to add the language pack for Office 2016 as well for better end user experience. The below samples will show with the Language pack applied
Mount “x21-20487 Office v16.2.1 German OPK”
Copy the office folder to E:\OfficeV16.2.1
Skip replacing duplicate files in the copy so that only the German languages are copied.
Microsoft Office 2016: Install the Home and Student edition
The current OEM recommendation is to install Office Home and Student 2016, rather than Office Home Premium. To do this, you'll need to edit the configuration.xml file used to install Office v16.2.1. To learn more, see Office 16.2.1 communication.
Use Notepad to create a configuration file with the edition info: E:\Officev16.2\ConfigureO365Home.xml
Make sure the ProductID is HomeStudentRetail, as follows:
<?xml version="1.0"?> <Configuration> <Add OfficeClientEdition="32" SourcePath="\\Server\Share\"> <Product ID="HomeStudentRetail"> <Language ID="en-us"/> </Product> </Add> <Display Level="None"/> </Configuration>
On the reference computer, install Office 2016 using the configuration file:
D:\Officev16.2\Setup.exe /configure D:\Officev16.2\ConfigureO365Home.xml
Microsoft Office 2016: Pin tiles to the Start Menu layout
You must pin the Office tiles to the Start menu. Not doing so Windows will remove the Office files during OOBE boot phase. To learn more, see Lab 11: Add Start tiles and taskbar pins.
Microsoft Office 2016: Configure setup experience for the user
After you install Office on the device, you also need to configure the setup experience for the user. This is the experience the user sees when they open an Office app for the first time on the device. This also is intended to ensure that Office is properly licensed and activated.
|OEM||In this mode, a customer can choose to try, buy, or activate Office with an existing account, PIN, or product key. This mode doesn’t support Activation for Office (AFO) or AFO late binding. Therefore, if you choose this mode, you need to provide the customer with an Activation Card (formerly called a product key card or a Microsoft Product Identifier (MPI) card).|
|OEMTA||This mode supports the try, buy, or activate experience of the OEM mode as well as supporting AFO and AFO late binding. This mode supports Office activation through the device’s Windows product key, which means the customer wouldn’t need to enter a 5x5 product key code.|
OEM Mode – Provide user with activation card
In command prompt go to drive letter for USB-B\Officev16.2
Type and run oemsetup.cmd Mode=OEM Referral=####
OEMTA Mode – Activation is done through the device’s Windows product key
Type and run oemsetup.cmd Mode=OEMTA Referral=####
Note: “Referral” switch is optional, If OEM partner is participating in office Incentive program For OEM referral ID information please refer to Office Incentive Program Operations Guide 2017.
Step 4: Capture your changes for the recovery tools
Connect to your external storage (for example, a storage USB key with the drive letter D:)
Capture the changes into a provisioning package. This creates a compressed copy of the desktop applications and drivers that you added in audit mode that can be used by the recovery tools.
D:\ADKTools\amd64\scanstate.exe /apps /ppkg C:\Recovery\Customizations\usmt.ppkg /o /c /v:13 /l:C:\Recovery\ScanState.log
Recommended: Delete the ScanState log file:
Step 5: Prepare for image capture
This step is required when you're capturing images to apply to other PCs.
Prepare the device for the end user: Right-click Start, select Command Prompt (Admin), and from the command prompt, run the following command:
C:\Windows\System32\Sysprep\sysprep /oobe /generalize /shutdown
The Sysprep tool reseals the device. This process can take several minutes. After the process completes, the device shuts down automatically.
Boot the device into Windows PE. To do this, you may need to press the key that opens the boot-device selection menu for the device (for example, the Esc key or Volume Up key).
Select the option in the firmware menus to boot to the USB flash drive.
If Windows begins booting instead of Windows PE, you must generalize the device again before capturing the image: After Windows boots, press Ctrl+Shift+F3 to enter audit mode. The device will reboot. Generalize the device again:
C:\Windows\System32\Sysprep\sysprep /oobe /generalize /shutdown.
Optional: speed up the optimization and image capture processes by setting the power scheme to High performance:
powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
Find the drive letters by using DiskPart:
diskpart DISKPART> list volume DISKPART> exit
For example, the drives can be lettered like this: C = Windows; D is the lab USB key, and E is an external hard drive.
Note that some partitions might not receive a drive letter.
Step 6: Optimize the image to take up less drive space (optional)
Save space by single-instancing the image. This removes the original copy of the desktop applications, and adds pointer files so that these applications can run from the recovery provisioning package you created earlier.
DISM /Apply-CustomDataImage /CustomDataImage:C:\Recovery\Customizations\USMT.ppkg /ImagePath:C:\ /SingleInstance
where C is the drive letter of the Windows partition.
Warning: Do not put quotes with the
Cleanup the Windows files:
md c:\temp DISM /Cleanup-Image /Image=C:\ /StartComponentCleanup /ResetBase /ScratchDir:C:\Temp
where C is the drive letter of the Windows partition. You can specify the /Defer parameter with /Resetbase to defer any long-running cleanup operations to the next automatic maintenance. But we highly recommend you only use /Defer as an option in the factory where DISM /Resetbase requires more than 30 minutes to complete.
Step 7: Capture the image
Capture the image of the Windows partition.
dism /Capture-Image /CaptureDir:C:\ /ImageFile:"C:\WindowsWithFinalChanges.wim" /Name:"Final changes"
where C is the drive letter of the Windows partition and Final changes is the image name.
The DISM tool captures the Windows partition into a new image file. This process can take several minutes.
If you receive an: "A parameter is incorrect" error message when you try to capture or copy the file to the USB key, the file might be too large for the destination file system. Copy the file to a different drive that is formatted as NTFS.
You can also choose to capture an image of the whole drive, including partition information, in a full flash update image (FFU). See DISM Image Management Command-Line Options for available command line options for capturing an FFU.
Try it out
Step 6: Apply the image to a new PC Use the steps from Lab 2: Deploy Windows using a script to copy the image to the storage USB drive, apply the Windows image and the recovery image, and boot it up. The short version:
- Copy the image file to the storage drive.
- Boot the reference device to Windows PE using the Windows PE USB key.
- Find the drive letter of the storage drive (
diskpart, list volume, exit).
- Apply the image:
- Disconnect the drives, then reboot (
Step 7: Verify customizations
After the PC boots, either create a new user account, or else press Ctrl+Shift+F3 to reboot into the built-in administrator account (This is also known as audit mode).
See that the changes you made in audit mode are there.