Configuring system package types for Windows and Linux

The System Package Types tab lists the available system package types and lets you edit their definitions or create your own custom system package type. This topic describes how to create a system package type for the following platforms:

To configure a system package type for Microsoft Windows provisioning

  1. In the menu bar, select Configuration > Provisioning Configurations.
  2. To configure or change the information for a system package type, select the type in the list and click Edit. To add a new system package type, click Add.

  3. Complete the configuration window that appears.

    Click here to see descriptions of the fields in the configuration window.

    The System Package Types configurations window lets you add a system package type or change configuration information for a Windows system package type.

    Note

    To create a customized System Package Type (SPT) for Windows 2012 R2 X64 OS for provisioning, see Workaround-for-provisioning-the-Windows-2012-R2.

    Field definitions

    WIM Based System Package

    Select this check box along with the next check box if this system package type is for creating system packages based on a WIM image in a data store (for either Windows 2008 or 2012).

    Windows 2008 and R2 (For WIM Image Windows server 2012)

    Select this check box if this system package type is for Windows 2008. Then from the drop-down menu, select the Windows 2008 or Windows 2008 R2 operating system type.

    You can select this check box either on its own or in combination with the previous check box.

    Windows Server 2012 and R2 System Package (Scripted)

    Select only this check box if this system package type is for Windows 2012 and Windows 2012 R2. Then from the drop-down menu, select the Datacenter or Standard operating system type.

    Windows Server 2016 System Package (Scripted)

    Select only this check box if this system package type is for Windows 2016. Then from the drop-down menu, select the Datacenter or Standard operating system type.

    Support for Windows Server 2016 is available in TrueSight Server Automation as of version 8.9.01.

    New in 8.9.04.001Windows Server 2019 System Package

    Select only this check box if this system package type is for Windows 2019 x64. Then from the drop-down menu, select the Datacenter or Standard operating system type.

    Support for Windows Server 2019 is available in TrueSight Server Automation as of version 8.9.04.001.

    Windows Architecture

    Indicates the architecture of the machines you plan to provision with this system package type.

    System package type

    Name of the system package type.

    OS Installer location

    Directory where the operating system installer is located.
    The location you specify should be relative to the root directory of the data store. For example, if the root directory of the data store is the location:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore
    and the OS installer files reside in:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore\win2k8
    you would enter win2k8.

    Note: WIM-based system packages: Enter the path to the WIM image, including the image name. Specify a path relative to the full path of the data store. For example, if the image resides in:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore\WIMimages
    you would enter WIMimages\Win2008standard.wim.

    RSCD agent installer location

    Directory where the RSCD agent installer files reside.

    New in 8.9.02

    MSVC ++ Installer location


    Directory where Microsoft Visual C++ 2015 Redistributable Update 3 and later reside.

    (Optional) If you are using Windows RSCD agent versions earlier than 8.9.02.

    (Mandatory) If you are using Windows RSCD agent versions 8.9.02 and later.

    You must perform the following tasks to install Microsoft Visual C++ 2015 Redistributable Update 3 before installing Agent:

    To copy the Microsoft Visual C++ 2015 Redistributable Update 3 installer to the datastore
    1. Unzip the BSA<version>-<platform>.zip installer file.
    2. Create a folder on the data store according to the architecture.
    3. Copy the Microsoft Visual C++ 2015 Redistributable Update 3 installer based on the architecture from <Installer_Directory>\BBSA89-SP2-WIN64\Disk1\files\installers\redist folder.
    4. Paste the installer to the newly created folder (in Step 2) on the data store and rename it to vcredist.exe. For example,
      If you are using 64-bit architecture, copy vcredist_x64 and rename it to vcredist.exe.
      If you are using 32-bit architecture, copy vcredist_x86 and rename it to vcredist.exe.

    Datastore MSVC location.png

    To configure MSVC ++ Installer location in TrueSight Server Automation ( System Package Types Configuration window)
    1. Select datastore.
    2. Select Installer Directory and browse to the specific directory where you have copied the Microsoft Visual C++ 2015 Redistributable Update 3 installer.
    3. Click OK.
      MSVCInstallPost.png

    Note: If you are using Microsoft Windows 2012 R2 Datacenter edition, ensure that the iso image meets all the pre-requisites for installing Microsoft Visual C++ 2015 Redistributable Update 3.

    Select the latest iso image from Microsoft. Because, the earlier iso images might not have the following pre-requisite patches:

    • Windows8.1-KB2975061-x64 (required for KB2999226)
    • Windows8.1-KB2919355-x64.msu
    • KB2999226

    For more information about the pre-requisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.

    Initial Partition Size (MB)

    Size of the initial disk partition (in MB).
    Default: 2000
    Set this value according to Microsoft's available disk space recommendations for the operating system type.
    To ensure that the operating system installation completes successfully, the provisioning process requires the following values for initial partition size:

    • For Windows 2008 and Windows 2008 R2 operating systems: At least 10000 MB for an x86 system package type and at least 15000 MB for an x64 system package type.
    • For Windows 2012, Windows 2012 R2, and Windows 2016 operating systems: At least 20000 MB for an x64 system package type.
    • For all other Windows operating systems: At least 2000 MB.
      When you create system packages that are based on this system package type, the permanent primary partition (typically C:) must be the same size or larger than the initial partition size you specify here. For example, if you specify an initial partition size of 4000 here, the permanent primary partition you specify on the Disk Partition panel must be greater than or equal to 4000.


    Where to go from here

     System-package-panels-generic

  4. When you finish adding or editing system package types, click OK on the System Package Types tab.

To configure a system package type for VMware ESX and ESXi provisioning

  1. In the menu bar, select Configuration > Provisioning Configurations.
  2. To configure or change the information for a system package type, select the type in the list and click Edit. To add a new system package type, click Add.

  3. Complete the configuration window that appears.

    Click here to see descriptions of the fields in the configuration window.

    The System Package Types window lets you add a system package type or change configuration information for the ESX and ESXi system package type.

    Field definitions

    ESX version

    The operating system type and version are preselected and unavailable for change if you clicked Edit on the System Package Type tab. If you clicked Add on the System Package Type tab, select the operating system type and version that you want to define.

    System package type

    Name of the system package type.

    OS installer location

    Directory where the operating system installer is located.
    The location you specify should be relative to the root directory of the data store. For example, if the root directory of the data store is the location:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore
    and the OS installer files reside in:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore\VMWare\esx3_5
    you would enter VMWare\esx3_5.
    The requirement is that the installer path name must be the parent directory of the following two directories, for the version of VMWare that you are provisioning:

    • isolinux (does not apply to ESXi 4.1)
    • VMWare

    RSCD agent installer Location
    (Does not apply to ESXi 4.1)

    Directory where the installer for the RSCD agent resides.

    Note

    ESXi 4.1 does not require the RSCD agent.

    Boot kernel file name

    The name assigned to the boot kernel file stored in the X86PC\pxelinux directory on the TFTP server.
    By default, the boot kernel file is named:

    • vmkernel.gz for VMware ESXi 4.1.
    • vmlinuz for all other VMware versions.

    Boot image file name

    The name assigned to the boot image file stored in the X86PC\pxelinux directory on the TFTP server.
    By default, the boot image file is named:

    • vmkboot.gz for VMware ESXi 4.1.
    • initrd.img for all other VMware versions.

    ESXi additional images

    The additional image files for ESXi. For ESXi 4.1, four additional image files are required and must exist on the TFTP server. Use three dashes and a space before each file name. The path and file names must be relative to the TFTP root directory, as the following examples show.

    • If the files exist directly under the TFTP root directory, keep the default value that appears in this field, which is:

      --- sys.vgz --- cim.vgz --- ienviron.vgz --- install.vgz

    • If the files are in a subdirectory under the TFTP root directory, add the subdirectory name to each file name to make the names relative to the TFTP root directory. For example:

      --- ESX41Images\sys.vgz --- ESX41Images\cim.vgz --- ESX41Images\ienviron.vgz --- ESX41Images\install.vgz

    Boot files location

    Browse to the folder where the boot files are located.

    This is the only option available for VMware ESXi 5.0.

    Where to go from here

     System-package-panels-generic

  4. When you finish adding or editing system package types, click OK on the System Package Types tab.

To configure a system package type for Red Hat Linux provisioning

  1. In the menu bar, select Configuration > Provisioning Configurations.
  2. To configure or change the information for a system package type, select the type in the list and click Edit. To add a new system package type, click Add.

  3. Complete the configuration window that appears.

    Click here to see descriptions of the fields in the configuration window.

    The System Package Types window lets you create a custom system package type or change configuration information for the Red Hat system package type.

    Field definitions

    Red Hat version

    (For creating a custom system package type.) Select the Red Hat version for which you want to create a system package type.

    System package type

    Name of the system package type.

    OS installer location

    Directory where the operating system installer is located.
    The location you specify should be relative to the root directory of the data store. For example, if the root directory of the data store is the location:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore
    and the OS installer files reside in:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore\RedHat5
    you would enter RedHat5.
     The requirement is that the installer path name must be the parent directory of the following directory for the version of Red Hat Linux that you are provisioning:
    images

    RSCD agent installer Location

    Directory where the installer for the RSCD agent resides.

    Boot kernel file name

    The name assigned to the boot kernel file stored in the X86PC\pxelinux directory on the TFTP server.
    By default, the boot kernel file is named vmlinuz.

    Boot image file name

    The name assigned to the boot image file stored in the X86PC\pxelinux directory on the TFTP server.
    By default, the boot image file is named initrd.img.

    Where to go from here

     System-package-panels-generic

  4. When you finish adding or editing system package types, click OK on the System Package Types tab.

To configure a system package type for Citrix XenServer provisioning

  1. In the menu bar, select Configuration > Provisioning Configurations.
  2. To configure or change the information for a system package type, select the type in the list and click Edit. To add a new system package type, click Add.

  3. Complete the configuration window that appears.

    Click here to see descriptions of the fields in the configuration window.

    The System Package Types window lets you add a system package type or change configuration information for the Citrix XenServer system package type.

    Field definitions

    System package type

    Name of the system package type.

    OS installer location

    Directory where the Citrix XenServer installer is located.
    The location you specify should be relative to the root directory of the data store. For example, if the root directory of the data store is the location:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore
    and the installer files reside in:
    C:\Program Files\BMC Software\BladeLogic\PXE\pxestore\XenServer56
    you would enter XenServer56.

    Boot kernel file name

    The name assigned to the boot kernel file stored in the X86PC\pxelinux directory on the TFTP server.
    For example: XenServer\vmlinuz

    Boot image file name

    The name assigned to the boot image file stored in the X86PC\pxelinux directory on the TFTP server.
    For example: XenServer\install.img

    Xen kernel file name

    The name of the Xen hypervisor kernel stored in the X86PC\prelinux directory on the TFTP Server. For example: XenServer\xen.gz

    Where to go from here

     System-package-panels-generic

  4. When you finish adding or editing system package types, click OK on the System Package Types tab.

To configure a system package type for Ubuntu 12 or Ubuntu 14 provisioning

  1. In the menu bar, select Configuration > Provisioning Configurations.
  2. To configure or change the information for a system package type, select the type in the list and click Edit. To add a new system package type, click Add.

  3. Complete the configuration window that appears.

    Click here to see descriptions of the fields in the configuration window.

    The System Package Types window lets you create a custom system package type or change configuration information for the Ubuntu system package type.

    Field definitions

    Ubuntu version

    Select the Ubuntu version for which you want to create a custom system package type.

    System package type

    Name of the system package type.

    OS installer location

    Directory where the operating system installer is located.

    The location you specify should be relative to the root directory of the data store. For example, if the root directory of the data store is the location: C:\Program Files\BMC Software\BladeLogic\PXE\pxestore 
    and the OS installer files reside in:  C:\Program Files\BMC Software\BladeLogic\PXE\pxestore\Ubuntu12
    (or C:\Program Files\BMC Software\BladeLogic\PXE\pxestore\Ubuntu14),
    You would enter Ubuntu12 (or Ubuntu14).

    The requirement is that the installer path name must be the parent directory of the following directory for the version of Ubuntu Linux that you are provisioning: images

    RSCD agent installer Location

    Directory where the installer for the RSCD agent resides.

    Copy the rscd.deb package

    Boot kernel file name

    The name assigned to the boot kernel file stored in the X86PC\pxelinux\ directory on the TFTP server (for example, C:\Program Files (x86)\BMC Software\BladeLogic\PXE\tftproot\).
    By default, the boot kernel file is named linux.

    Boot image file name

    The name assigned to the boot image file stored in the X86PC\pxelinux\ directory on the TFTP server (for example, C:\Program Files (x86)\BMC Software\BladeLogic\PXE\tftproot\).
    By default, the boot image file is named initrd.gz.

    Where to go from here

     System-package-panels-generic

  4. When you finish adding or editing system package types, click OK on the System Package Types tab.

Where to go from here

Creating-a-system-package-for-Windows-and-Linux

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*