Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Configuring the data store for PXE provisioning

Configuring the data store sets required values for accessing the data sources for provisioning.

In particular, you define the location of the data store, which is where you store sets of installation files that are used for provisioning operating systems. Data store values are stored in the Data Store system object, which you can edit by using the Property Dictionary.

Before you begin

To configure the data store

  1. Select Configuration > Property Dictionary View.
  2. In the Property Class Navigation panel at the left, open the Built-in Property Classes folder. Then open the DataStore sub-folder. Click Jumpstart DataStore, Pxe DataStore, NIM DataStore, or Ignite DataStore.
  3. In the right panel, click the Instances tab.
    A DataStore instance specifies the server that functions as a data store. You must create at least one instance of a data store. You can create more than one instance. For example:
    • One data store instance could contain files for provisioning Windows systems, and another instance could contain files for provisioning Linux systems.
    • For an enterprise WAN, you could create one data store instance to serve the London network segment, another to serve the New York network segment, and a third to serve the Tokyo network segment.
  4. Create a data store instance. As you create this instance, fill in the following properties:
    To configure a data store instance for PXE provisioning, set the following property values.

    PXE Property Name



    (Required) The name or IP address of the server that functions as the data store.


    This server must have a running RSCD agent that is licensed for the BMC Server Automation Console.

    Ensure that the server name that you specify here as the data store location is the same as the name that you specify when adding the server in BMC Server Automation. For example, if you specify a data store location of (a fully qualified domain name, FQDN), use the same name when adding the server; do not use abc123 (non-FQDN).

    If the PXE server, TFTP server, and the data store are all on the same machine, follow these naming rules:

    • To provision Linux systems, set the LOCATION property to the IP address (not the host name).
    • To provision Microsoft Windows systems, set the LOCATION property to the host name (not the IP address).

    ESX Server 2.5 only: The data store is exposed via NFS. Set LOCATION to the name of the NFS server.


    (Required) The full path to the directory that functions as a data store. For a data store that resides on a Windows system, specify the path using Windows path format; for a data store that resides on a UNIX-like system, use UNIX path format.
    When you identify the location of installation files required to provision a particular operating system, specify the location in relation to the directory you identify in this step.


    (Required) Provides the name of the virtual directory used to access the data store.

    UNIX systems: Part of the installation process includes providing HTTP access to the root of your data store (the directory specified in the LOCATION and VIRTUAL_DIR properties). The VIRTUAL_DIR property refers to the directory component of the URL that points to this directory.
    For example, suppose your data store resides on a machine called host1, and your FULL_PATH is /var/installs/redhat
    Suppose that you set up HTTP access to this directory with the following URL:


    You would then set the VIRTUAL_DIR property to: installs

    Windows systems: Part of the installation process includes setting up directory sharing for the data store directory.
    For example, suppose LOCATION is defined as host2 and you set up directory sharing for a data store directory called datastore:
    You would then set the VIRTUAL_DIR property to: datastore

    ESX Server 2.5: The name of the share on the NFS server specified by LOCATION.


    Provides the user name and password required to access the data store.

    Linux data store only: USERNAME and PASSWORD do not require values unless you have password-restricted access to your data store.

    ESX Server 2.5 only: The user name and password required to access the NFS share specified by VIRTUAL_DIR.

    Windows data store with domain accounts only: In the USERNAME field, specify the domain name and user name as domainname\username.

Where to go from here

Stock the data store with the installers and other files that you expect to use, as described in the following tasks. See Stocking the data store.

Was this page helpful? Yes No Submitting... Thank you