Skip to content
CA Client Automation - 14.0
Documentation powered by DocOps

Create OS Images

Last update January 12, 2018


To create OS images, use the CreateOSImage command.

Use CreateOSImage -x option for a list of already created OS images that are available in the Image Prepare System.

The path to the OS images in the image store is also listed. This parameter is useful when you want to make manual adjustments to an OS image. For example, the following command creates a Windows 8 image from the Windows 8 DVD:

createOSImage  -I myxpsp2  -o WINDOWS8  -k <product key>

The following command creates a Windows 8 image from a Windows 8 directory structure:

createOSImage  -i myxpsp2  -o WINDOWS8  -k <product key> -s d:\i386

Add OSIM Parameters to Created Images

OSIM OS images have various parameters to control the installation process. Default OSIM OS Images have all parameters for a successful installation.

To have extended control over the installation procedure, you can add more parameters to images that have already been created. OS images must be modified to add parameters before being registered with the Domain Manager. If the OS image has already been registered, remove the image from the manager, modify, and re-register the image.

When an OS image is created using the wizard or CreateOSimage command, it is, by default, which is stored in a directory named Image Store.

You cannot remove an image from the Domain Manager as long as the image is assigned to target computers.

When adding parameters, ascertain the following points:

  • CreateOSImage and RegisterOSImage look for parameters only in files that are listed in the [parameterfile] section in osinfo.ini.
  • CreateOSImage -x shows all created images and their location.
  • CreateOSImage -p <imagename> shows the properties of one image including the files with parameter in it.
  • If you insert a parameter $parametername$ in one of the files without defining the parameter in default.ini, RegisterOSImage takes over the new parameter with default properties (type=string, max length= 255, default value = “”, comment = file where it was found).
  • You can define parameter type, default values, comments in the default.ini of each OS image. The locations of the default.ini files are under the paths listed with CreateOSImage -x.
  • You can verify your parameter changes with RegisterOSImage -i <name> -t. This command also extends default.ini with default definitions of new parameters not yet defined.

For more details, see default.ini.

Example Add OSIM OS Image Parameters

Only administrators with a good understanding of .inf and default files should change parameters or should add new ones.

For example, you create an OS image that is named myImage and you want to add parameters setting the Language variable of the regional settings in the auto answer file of the OSIM OS image, myImage.inf.

The parameter that should drive this variable is named "localeID" and its default value should be 1033.

To add a parameter to the image

  1. Load …\ManagedPC\CAMENU\myImage.inf into an UTF-8 enabled editor, for example, Notepad. The CAMENU directory is in parallel to the IMAGES directory.

    See createosimage -x for the exact path to the myImage directory.
  2. Go to the [RegionalSettings] section in myImage.inf.
  3. If there is already a value for Language, change it to the following:


    Otherwise, add this line to the section.

  4. Save the file and close the editor.
  5. Load …\ManagedPC\IMAGES\myImage\default.ini into a UTF-8 enabled editor, for example, Notepad.
    See createosimage -x for the exact path to myImage.
  6. Go to the [Default] section, and insert the following line in this section:

  7. Add the following new section at the end of the file:

     Comment=Language/locale to be installed
     item=5124 Chinese_Macau
     item=1030 Danish
     item=1033 English US
     item=2057 English UK
     item=1036 French Standard

    For details about the parameters, types, and attributes, see Default.ini Parameters.

  8. Save the file and close the editor.

Extend the Image with Special Drivers

Older operating systems do not include device drivers for new computer hardware. If unsuitable drivers for the network adapter are used, network access does not work. In this case, the agent cannot connect to the manager and the installation seems to hang.

If the OS does not have sufficient drivers, ask your hardware vendor for the correct device driver that is suitable for your OS image. Introduce the driver into the OS image on the Image Prepare System before you register and distribute the image.

For the most recent list of supported versions, see the Compatibility Matrix.

Extend createOSImage with New OS Image Types

The IPS has a set of OS image templates. These templates can be viewed using the CreateOSImage command. All available images are defined in the Template.ini, which controls the CreateOSImage command.

You should be familiar with the process of creating image types and installation templates before you attempt to create them.

You can add a new image type by adding a [ostype] section including the keys for specification. See the key descriptions following.

Template files in the os-template\camenu\<ostype>.xx and in the os-template\images\<ostype> also belong to an OS type. The assignment is defined in the template.ini file.

For more information, see Template.ini.

Was this helpful?

Please log in to post comments.