Sysprep.inf File Prioritization

The Sysprep.inf file can be delivered with the operating system image, or it can be delivered as a package that is connected to the operating system image (known as an override Sysprep file). If the Sysprep.inf file is published separately, it will be merged with the Sysprep.inf file in the image's NTFS into a single, combined Sysprep.inf.

Sysprep.inf files are prioritized in the following order, from lowest to highest:

  1. Sysprep embedded in the image (lowest priority). If there is no separately published Sysprep.inf (override Sysprep), just the Sysprep.inf in the image will be used.
  2. Override Sysprep (a Sysprep file that is separate from the gold image. See “Using an Override Sysprep File” in the HP Client Automation Enterprise OS Management Reference Guide for details).

    Note: Only one override Sysprep.inf will be resolved.

  3. Sysprep attached to policy criteria (highest priority).

    Note:

    • To attach a Sysprep file to policy, you must publish the Sysprep file to the CSDB and then use the Administrator CSDB Editor to manually connect the Sysprep instance to the appropriate Policy instance.
    • Even if you override the Sysprep.inf, the ComputerName (COMPNAME) and JoinDomain (COMPDOMN) are still updated by HPCA based on the Computer Name and Domain stored in the ROM object.


© 2003 - 2012 Hewlett-Packard Development Company, L.P.