Share via


auditSystem (Standard 7 SP1)

7/8/2014

The auditSystem pass processes unattended settings in system context in audit mode. The auditSystem pass runs immediately before the auditUser pass that is used to apply settings in user context.

Typically, auditSystem is used to add more device drivers and assign a name to the system that is specific for audit mode.

Audit mode enables OEMs and IT professionals to install additional device drivers, applications, and other updates. When Windows Embedded Standard 7 starts in audit mode, the auditSystem and auditUser unattended settings are processed.

By using audit mode, you can maintain fewer Standard 7 images, because you can create a reference image with a minimal set of drivers. The image can be updated with additional drivers during audit mode. You can then test and resolve any issues related to malfunctioning or incorrectly installed devices on the Standard 7 image.

The following illustration shows the processes of audit mode.

Ff794215.2c0ffd17-446a-40c8-a9a7-eb9d0c7a5e8b(en-US,WinEmbedded.60).gif

The auditSystem pass runs only when you configure Image Builder to start in audit mode. You can start in audit mode by using sysprep /audit, or sysprep /generalize /audit. For more information, see Customize in Audit Mode.

Note

Audit mode is optional.

See Also

Concepts

auditUser
generalize
offlineServicing
oobeSystem
specialize
windowsPE