Provisioning Windows 2003 or later servers from a local data store

You can provision Windows 2003, 2008, or 2012 servers from a local data store instead of a PXE server.

Provisioning the Windows operating system to bare-metal servers is most often done in a PXE environment, where files for operating system installation reside on a remote PXE data store. However, BMC Server Automation provisioning also lets you provision Windows 2003, 2008, or 2012 servers from a local data store. For more information about this approach, see About provisioning from a local data store.

This topic describes how to provision target servers from a local data store. It includes the following sections:

To create a WinPE image for booting the target server from the PXE server (PXE boot), see Creating an image for booting from the PXE server. For a Windows 2003 server image, use WinPE 2.x. For a Windows 2008 R2 server image, use WinPE 3.0.

Before you begin

  • The CD/DVD media must be removable or CD-ROM drive types. These types include: CD, DVD, Integrated Lights Out (HP iLO), Dell Remote Access Controller (DRAC), and USB devices.
  • The CD/DVD media must be connected to the target server and available.
  • The CD/DVD media must contain valid operating system installation files for the Windows installation that you want to perform.

To provision target servers from a local data store:

  1. Create a WinPE image to use in provisioning by booting from local media (local boot), use one of the following methods.

    To use the image creation wizard to create the image for local boot
     Click here to review the steps for using the wizard.

    1. Select Configuration > Provisioning Image Creation.
    2. In the Toolkit Select window, do the following:
      1. For the following options, provide information as you normally would in creating a WinPE boot image:
        • Image Toolkit Host
        • Architecture
        • Windows Kit Directory Path
        • CreateWinPE Script Directory Path
      2. For Image Type, select one or more of the following:
        • ISO Image: Creates an image in ISO format (bootImageName.iso) for booting from media connected to the target server. You can burn this ISO image to CD/DVD or use it directly through iLO (integrated Lights-Out server management technology), virtual CD-ROM, or a mapped network drive.
        • UFD Image : Creates an image in UFD format for booting from USB flash drive. The image is a directory with the name bootImageName_UFD; the directory contains the files for booting from a USB flash drive.
      3. For Boot Image Target Directory, type the full path to the directory in which you want the image created, or click Browse  to select a location. Use NSH format for the path. The image creation process uses the name of last directory in the path as the image name. For example: //myComputerHostname/myImageDirectory/boot_2_0_x86

        Note

        Spaces are not supported in the boot image name. (The image creation process considers the last directory in the Boot Image Target Directory Path as the image name.)

    3. In the Driver Selection window and Custom Script window, provide information as you normally would in creating a WinPE image. (For information, see Creating WinPE images using the Image Creation wizard.)
    4. In the Configuration Details window, do the following:
      1. Select the network.ini file. (Click Browse.) You would specify this file if the provisioning environment does not contain a DHCP server. For information about this file, see Creating a network.ini file
        This step is optional. If you do not select a file, you can:
        • Manually copy the file to the root directory of the media (CD, DVD, USB) you use for local provisioning of the server.
        • Provide network details during the provisioning of the target server — if there is no DHCP server present in the provisioning environment.
      2. Accept or change the Application Server IP address and port. (Specify this information if there is no DHCP server present in the provisioning environment.)
      3. Select Copy to root of ISO/UFD.
      4. Specify the location of Configuration Components (bmiwin.exe, RSCD agent installers, and operating system driver files) to be copied. 
        For information about Configuration Details options, see Creating WinPE images using the Image Creation wizard.
    5. Click Finish.

    To use the script to create an image for local boot
     Click here to review the steps for using the script.

    1. Create the input file containing image creation parameters. In the file, specify all required parameters and all parameters labelled "Local boot image only." For parameter descriptions and an example script, see Creating the input parameters .ini file.

    2. Run the CreateWinPE2_x.vbs script as described in Running the script for creating a WinPE image.

    3. Copy the WinPE image file to the media you plan to use for provisioning the target server. See Copying image files to a location for provisioning.

  2. Create a system package that points to the local data store as the location of the installation files. 

     Click here to review the steps for creating a Windows system package for use with a local data store.
    1. Edit the system package type to specify the location of the operating system installer as relative to the local data store and the RSCD agent installer as relative to the CONFIG_STORE location.
      1. Select Configuration > Provisioning Configurations.
      2. On the System Package Type tab, under Relative Paths for OS images, select the type of system package and click Edit .
      3. On the System Package Type window, for OS Installer location, type the path to the directory where the operating system installation files reside in the local data store (CD/DVD, USB flash drive). The path must be relative to the root directory of this local data store. If these files are at the root directory of the local data store, type a backslash.
      4. For RSCD Installer location, type the path to the directory where the RSCD agent installer files reside.
        If these files are in an ISO or UFD boot image, specify a path relative to the root of ISO or UFD.
        During image creation, if you selected Copy to root of ISO/UFD or Copy to WinPE image, specify the name of the leaf directory that you provided for RSCD Installer Path. (This directory contains the rscd.msi file.) For example, if the RSCD Installer Path specified during image creation was D:\DataStore\RSCD\rscd_76_x86, you would type:
        rscd_76_x86
    2. Create the system package.
    3. In the system package, define settings on the Disk Partition, Basic Config, OS Components, Network, and Post-Install Config tabs.

       Click here to view the steps for defining the system package settings.
      1. In the Depot folder, navigate to the system package you want to define. Right-click the system package and select Open.
        A tab for the system package appears in the content editor.
      2. To define standard system package settings, click the tabs at the bottom of the system package tab. Each tab represents a category of settings, as described in the following sections:
      3. When you finish defining settings for the system package, click the system package tab and select File > Save.
    4. On the Local Properties tab, accept or change the default setting for the CONFIG_STORE property. This property specifies the locations that the provisioning process searches for the configuration components (bmiwin.exe, RSCD agent installers, and operating system drivers) when booting from local media. 

       Click here for more information about the CONFIG_STORE property.

      The CONFIG_STORE property specifies the locations that the provisioning process searches for the configuration components (bmiwin.exe, RSCD agent installers, and operating system drivers) when booting from local media.

      This property is a local property of a system package. Use this property only to provision from a local data store.

      You can set the default value of this property to specify locations to search. The values are:

      • WinPE—The provisioning process searches the LDS directory inside the WinPE image on the local data media.
      • Media—The provisioning process searches all supported removable media connected to the target server. For example:
        • The WinPE ISO image on CD/DVD
        • The media containing the local data store
        • Any other media, such as a USB flash drive (UFD)
      • All—(The default value) The provisioning process searches both locations in this order:
        1. In the LDS directory inside the WinPE image.
        2. On all supported removable media connected to the target server.

      To change the default value of CONFIG_STORE, use the Local properties panel of the Windows system package.

    5. On the Computer Settings tab, define settings for User Information, License setup, and Localization as described below: 

      For Windows 2008 or later
       Click here for field definitions for Windows 2008 or later.

      Name

      The user name.

      Organization

      Name of the user's organization.

      PnP driver paths

      Specifies the location of plug-and-play (PnP) drivers and mass storage drivers in your data store.
      For configuring PnP or OEM drivers, for PnP driver paths, click Browse to select drivers. For information, see
      For PnP drivers, you can alternatively enter a semicolon-delimited list of paths in the field. Each path should be relative to the root of the data store. This example shows selection of two PnP drivers:
      drivers\Compaq\Win2008\Display;drivers\HPDLG30g5\Win2008\RAID

      License key

      Enter the key to the software license you are using, including all hyphens in the key. Then, under License key, do one of the following:

      • If the license is granted on a per-server basis, select Per server. For Number of concurrent connections, enter the number of users that can use a license simultaneously. This number must be set higher than 5.
      • If the license is granted on a per-seat basis, select Per seat.

        Note

        To install an evaluation version of Windows Server 2008 R2 (or one that uses a Multiple Activation Key), leave the License Key field blank. You can activate the license key on the target server later or you can customize the Unattend.xml file by providing the activation key. By default, the system package accepts the KMS license key.

      Time zone

      Select a time zone for the server.

      Locale

      Select a language option. For example, in the United States, select English United States.

      For all other Windows operating systems
       Click here for field definitions for Windows operating systems earlier than Windows 2008.


      Name

      The user name.

      Organization

      Name of the user's organization.

      Specify path to $OEM$ directory

      Specifies whether the $OEM$ drivers are directly beneath the i386 or amd64 directory or in a different location in the data store.
      If you leave Specify path to $OEM$ directory unchecked, you are telling the provisioning process that either your $OEM$ directory and its drivers are already directly beneath the i386 or amd64 directory, or that you plan to use the GUI to copy your drivers to this location.
      If you check Specify path to $OEM$ directory, you are telling the provisioning process that your $OEM$ directory is in a different location. Enter this location in the Path to $OEM$ directory field.
      For more information, see When to use Specify path to $OEM$ directory.

      PnP driver paths

      Specifies the location of plug-and-play (PnP) drivers in your data store. To enter paths, do one of the following:

      • Click Browse  and use the driver selection GUI to automatically fill in the PnP driver paths. For information, see Using the driver selection GUI - PnP driver paths.

        Note

        Browsing the data store for the PnP and mass storage drivers has the following requirements:

        • The drivers must be located in the same data store as the rest of the installation files for this system package.
        • There must already exist in the BMC Server Automation environment a server object whose name matches the LOCATION property of the data store instance you selected.
      • Type a semicolon-delimited list of the paths to the directories holding plug-and-play drivers.
        If you specified a path in the Path to $OEM$ directory field, the paths you enter here must be relative to the $OEM$\$1 directory. If you did not specify a path in the Path to $OEM$ directory field, the paths you enter must be relative to the root of the data store.

      Mass storage drivers

      Specifies the location of mass storage drivers in the data store.
      Click Browse and use the driver selection GUI to automatically fill in the mass storage drivers. For information about how to use this GUI, see Using the driver selection GUI - mass storage drivers.

      License key

      Enter the key to the software license you are using, including all hyphens in the key. Then do one of the following:

      • If the license is granted on a per-server basis, select Per server. For Number of concurrent connections, enter the number of users that can use a license simultaneously. This number must be set higher than 5.
      • If the license is granted on a per-seat basis, select Per seat.

      Time zone

      Select a time zone for the server.

      Locale

      Select a language option. For example, in the United States, select English United States.

    6. For Driver Setup, type the paths to the drivers as relative to the CONFIG_STORE location, according to the OS Drivers Pathyou specified on the Configuration Details panel during image creation. (You cannot browse to select drivers if the LocalDataStore is associated with the system package.)
      • During image creation, if you selected Copy to root of ISO/UFD or Copy to WinPE image, specify the name of the leaf directory that you provided for OS Drivers Path. For example, if the OS Drivers Path specified during image creation was D:\DataStore\Drivers, then for PnP driver paths:
        • System packages for Windows 2003 or later: If D:\DataStore\Drivers contains PnP drivers WinPE image at:
          D:\DataStore\Drivers\Dell
          D:\DataStore\Drivers\VmDrivers
          Then for PnP driver paths, type: Drivers\Dell;Drivers\VmDrivers
        • Windows 2003 system packages: If D:\DataStore\Drivers contains PnP drivers at:
          D:\DataStore\Drivers\$OEM$\$1\Dell
          D:\DataStore\Drivers\Drivers\$OEM$\$1\VmDrivers
          Then you would select Specify path to $OEM$ directory and for the Path to $OEM$ directory, you would type: Drivers. For *PnP driver paths,*you would type: Dell;VmDrivers
        • Mass Storage Drivers:
          • Windows 2008 or later system packages: If D:\DataStore\Drivers contains mass storage drivers at:
            D:\DataStore\Drivers\MassStorage\SCSI
            Then for Mass storage drivers, you would type: MassStorage\SCSI
          • Windows 2003 system packages: If D:\DataStore\Drivers contains mass storage drivers at:
            D:\DataStore\Drivers\$OEM$\$1\MassStorage\SCSI
            Then you would select Specify path to $OEM$ directory and for the Path to $OEM$ directory, you would type: Drivers. For Mass Storage Drivers, you would type: MassStorage\SCSI.
    7. To create a system package for Windows 2003 that includes mass storage drivers, add entries for the drivers in the unattend.txt file, as follows:
      • Click the Unattend Entries tab.
      • Clear the Customize the Unattend Entries file check box and add the entries to the Additional entries for the unattend.txt file.
        For example:
        [MassStorageDrivers]
        "VMware SCSI Controller" = "OEM"
        [OEMBootFiles]
        vmscsi.sys
        vmscsi.inf
        vmscsi.cat
        txtsetup.oem
    8. When you finish defining system package settings, select File > Save.
  3. Associate the local data store instance with the system package. See Associating the LocalDataStore instance with the system package.

     Click here to the steps for associating the LocalDataStore instance with the system package.
    1. Create the Provision Job.

       Click here to view the steps for creating a Provision Job.
      1.  To start the Provision Job wizard, do either of the following:
        • In the Jobs folder, right-click a folder, and select New > Provision Job > OS_type.
        • In the Devices folder, expand the Imported folder, right-click one or more devices, and select New > Provision Job > OS_type. This option offers a convenient way to provision one or more devices immediately. The job wizard adds the device information into the job for you, and it checks the Execute Now option by default on the Schedules panel, which makes the job execute immediately after you finish the wizard.
      2. Define the Provision Job, as described in the following table.

        Tip

        When you are familiar with the fields in the wizard, you can streamline some of the wizard selections by using parameterized properties in the system package definitions. For an example, see Example - How to use parameters to refer to system package properties.

        PanelDescription

        Provision Job - General

         

        The General panel lets you provide information that identifies a Provision Job.

        Field definitions

        Name

        Identifying name.

        Description

        Optional descriptive text.

        Save in

        Folder in which to store the object.

        Set Execution Override

        Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.

        Clear Execution Override

        Remove an existing execution override.

        Where to go from here

        Provision Job - System Package Properties

        Provision Job - System Package Properties

         

        The System Package Properties panel lets you select the system package and set system package properties.

        Field definitions

        Path to System Package

        Click Browse to select the system package to use to provision the servers.

        Property Settings

        You can change values for local properties associated with the system package. Values that you set here override values set in the system package. To change a property value, select a property and click Edit .

        Note: You can add a property to the system package only through the Local Properties panel when you create or edit a system package.

        Where to go from here

        Provision Job - Devices

        Provision Job - Devices

        The Devices panel lets you specify the devices, identified by MAC address, to provision the next time this Job executes. The panel also lets you provide network information, such as IP addresses and the DNS configuration, for those devices. Note: You can create and save a Provision Job without specifying any devices. You can open a saved Provision Job, add or change devices information, and save the changes. Then execute the Job to provision the new list of devices.

         Click here to see descriptions of the fields.
        IP Configuration

        The IP Configuration settings also appear in the system package. The IP Configuration settings you enter in a Provision Job override the settings in the system package. These options are used for IPv4 address configuration.

        Obtain IP address automatically

        Specifies that the network connection should obtain an IP address automatically from a DHCP server.

        Specify IP Manually (for each device)

        Specifies that the network connection should use the static IP addresses that you specify on the Devices list at the bottom of this panel.

        Specify IP Range

        Specifies a range of IP addresses that the system can use to assign a unique address to each device. Select this option and provide an address for Start IP and End IP of the range. The Devices list at the bottom of this panel displays the IP address assigned to each device.

        Subnet mask

        Specifies the subnet mask for the IP addresses in the range.

        Note: The Windows 2003 installer does not support three zeroes in any of the octets in the subnet mask. For example, if the subnet mask is 255.255.255.0, entering 255.255.255.000 for Subnet mask does not work. You must enter 255.255.255.0.

        Default gateway

        The address of the IP router that is used to forward traffic to destinations outside of the local network.

        Associated boot image

        (PXE devices only) From the Selected Boot Image list, select the boot image for provisioning the servers.

        Skip Linux Pre-Install

        For Red Hat Linux, SUSE, Citrix, and VMWare ESX, to skip using a pre-boot image and boot directly using the installer ramdisk and kernel, select this option. For information, see Using the Skip Linux Pre-Install image option

        IPv6 Configuration

        The IPv6 Configuration settings also appear in the system package for certain platforms that support IPv6 addresses. The IPv6 Configuration settings you enter in a Provision Job override the settings in the system package.

        Obtain IP address automatically

        Specifies that the network connection should obtain an IP address automatically from a DHCP server.

        Use the following IP address

        Specifies that the network connection should use the static IP addresses that you specify on the Devices list at the bottom of this panel.

        The IP address, IPv6 Subnet Prefix Length, and Default gateway fields only appear if you select this option.

        IP address

        Specifies an IP address that the system can use to assign a unique address to each device. The Devices list at the bottom of this panel displays the IP address assigned to each device.

        This field appears only when you select Use the following IP address option above.

        IPv6 Subnet Prefix Length

        Specifies the prefix length for the IPv6 address.

        This field appears only when you select Use the following IP address option above.

        Default gateway

        The address of the IP router that is used to forward traffic to destinations outside of the local network.

        This field appears only when you select Use the following IP address option above.

        DNS Configuration

        Obtain DNS server automatically

        Specifies that the network connection should obtain a DNS server automatically.

        Use the following DNS server addresses

        Specifies that the network connection should use the following DNS server addresses.

        The Primary DNS server and Secondary DNS server fields only appear if you select this option.

        Primary DNS server

        Enter the IPv6 address for the primary DNS server.

        This field appears only when you select Use the following DNS server address option above.
        Secondary DNS server

        Enter the IPv6 address for the secondary DNS server

        This field appears only when you select Use the following DNS server address option above.

        Devices to Provision

        Build the list of devices to provision by clicking Add , Delete , and Edit . When you click Add, the Add a New Device panel appears.

        Device NameEnter the IP address for the device.

        Computer Name

        Enter a unique name for the server. If you are provisioning multiple servers, the wizard names the first server using the name you provide, and then it appends sequential numbers to that base name for the other servers. For example, if you enter MyServer in the Computer Name field, the wizard uses MyServer for the first server, names the second server MyServer_1, the third server MyServer_2, and so on.

        (Windows only) Auto-generate Computer Name

        Select this option to allow the Windows installer to auto-generate the computer names. If you select this option, the Computer Name field is ignored.

        OM server name

        (Optional) Enter a different name to use in the BMC Server Automation Console for this server. This name must be resolvable to the IP address of the server.

        IP address

        The IPv4 address of the device.
        Subnet maskThe subnet mask of the IPv4 device address.
        Default gatewayThe default gateway for the IPv4 device address.
        IPv6 addressThe IPv6 address of the device.
        IPv6 Subnet Prefix LengthThe IPv6 subnet prefix length
        IPv6 GatewayThe IPv6 gateway for the IPv6 address.
        OS licenseThe license information of the OS installed in the device.
        Provision Job - Job Settings (PXE only)

         

        The Job Settings panel lets you pause a PXE-based provisioning job after each logical step. These options are useful for troubleshooting.

        Note

        If you selected Skip Linux Pre-Install on the Devices Selection panel, the options on this panel are not valid for provisioning Linux, VMWare ESX, or Citrix operating systems.

        Field definitions

        Pause and Continue

        Tells the provisioning process to wait a specified number of seconds after each logical step in the provisioning job. Type the number of seconds to wait under Pause Duration. The pause duration should be between 0 and 30 seconds.

        For example, if you specified a Pause Duration of 5 seconds, a provisioning job might proceed like this:
        pre-disk partition -> pause 5 seconds -> disk-partition-> pause 5 seconds -> post-disk partition... and so on

        Prompt user after each step

        Tells the provisioning process to prompt the user to press the Enter key on the console of the provisioning target after each logical step. The provisioning process does not go on to the next step until the user presses the Enter key on the target console.
        For example, if you clicked Prompt user after each step, a Provision Job might proceed like this:
        pre-disk partition -> prompt user to press Enter -> disk-partition-> prompt user to press Enter -> post-disk partition... and so on.

        Stopping and restarting a provisioning job

        As part of the debugging process, you can tell BMC Server Automation system to stop a job to let you debug, then start the job again after the last successfully completed logical step.

        • To stop a Provision Job, at the target console, press Ctrl+C.
        • To restart the Provision Job at the same place, at the target console, type: bmi
          If you plan to stop and restart a Provision Job, be sure to either set Pause and Continue to a number greater than zero, or select Prompt user after each step. Then stop the job when it is paused. This ensures that the job restarts in a consistent state.

        Where to go from here

        Provision Job - Server Settings

        Provision Job - Server Settings

         

        The Server Settings panel lets you apply ACL templates and properties on the server objects that are added to the BMC Server Automation Console.

        Field definitions

        Server Properties

        Browse to an instance of the PROVSERVER class and select the server properties whose values you want to apply to all of the devices being provisioned. The properties that you select must be members of an instance of the PROVSERVER class. For information, see Server properties.

        Choose ACL Template

        Browse to the ACL template that you want to apply to all of the devices being provisioned. An ACL template is a group of predefined authorizations granted to roles. Using an ACL template, you can add a group of authorizations to the server objects.

        Where to go from here

        Provision Job - Default Notifications

        Provision Job - Default Notifications

         

        The Default Notifications panel provides options for defining notifications that are generated when a Provision Job completes.

        Default notifications can take the form of emails or SNMP traps. When a job completes, an SNMP trap is sent to a specified server, where it can be read using software that receives and interprets SNMP traps. Default notifications are sent when you run a job immediately (that is, you do not schedule the job) or a scheduled job completes but you have not set up email or SNMP notifications for that scheduled occurrence.

        Job Run Notifications

        FieldDescription

        Send email to

        Lists email addresses of the accounts to notify when a job completes with the status that you specify. Separate multiple email addresses with semicolons, such as sysadmin@bmc.com;sysmgr@bmc.com. After entering email address information, check the statuses that cause an email to be generated. The statuses can be Success, Failed, or Aborted.

        Send SNMP trap to

        Provides name or IP address of the server to notify when the job completes. After entering server information, select the statuses that should cause an SNMP trap to be generated. The statuses can be Success, Failed, or Aborted.

        BMC Server Automation provides a management information base (MIB) that describes its SNMP trap structure. You can use this MIB to create scripts that integrate traps into your trap collection system. The MIB is located on the Application Server host computer at installDirectory/Share/BladeLogic.mib.

        List failed servers in email notification

        Indicates that email notifications should list all servers on which a job has failed.

        Where to go from here

        Provision Job - Schedules

        Provision Job - Schedules

         

        The Provision Job Schedules panel lets you schedule a job to execute immediately or at a specific time in the future. The interface does not allow you to schedule a Provision Job for recurring executions. You can also define notifications that are issued when a job runs.

        You can open a job after you create it and schedule it for execution. If the job already executed, you can edit the job and schedule re-execution. For example, if a job was running and you canceled it, you could schedule the job to run again. Also see Reprovisioning servers.

        Field definitions

        Execute job now

        Executes the job immediately after you finish a new job or save an edited job.

        If your system is configured to require approval for this job type, select Execute on Approval and then click Browse to display the Approval Information dialog box. For more information, see Provision Job - Execute on Approval and Approval type settings.

        Schedules

        To add a new schedule, click Add New Schedule . To delete an existing schedule, select it and click Remove Schedule . To modify an existing schedule, click Edit Schedule .
        Use the tabs on the scheduling window to provide the following categories of information:

        Where to go from here

        Provision Job - Properties

        Provision Job - Properties

         

        The Properties panel lets you edit property values for the Provision Job.

        The Properties panel provides a list of properties automatically assigned to a Snapshot Job. In this list, you can modify the value of any properties that are defined as editable.

        For any property that has a check in the Editable column, select the property and click in the Value column.

        • To set a property value back to its default value, click Reset to Default Value .
          The value of the property is reset to the value it inherits from a built-in property class. The Value Source column shows the property class from which the value is inherited.
        • Depending on the type of property you are editing, you can take different actions to set a new value, such as entering an alphanumeric string, choosing from an enumerated list, or selecting a date.
          To insert a parameter into the value, enter the value, bracketed with double question mark delimiters (for example, ??MYPARAMETER??) or click Select Property .

        Controlling Job Time-outs

        If you execute a Provision Job against target devices that are not booted, the Provision Job remains in the Task in Progress pane for the time set in the JOB_TIMEOUT Job property or until the device boots up. By default, the JOB_TIMEOUT value is 0, which means that the job does not time out. For information, see Defining timeouts for jobs.

        Where to go from here

        Provision Job - Permissions

        Provision Job - Permissions 

        The Permissions list is an access control list (ACL) granting roles access to any objects created in the system, such as jobs, servers, or depot objects. ACLs control access to all objects, including the sharing of objects between roles.

        Using the Permissions panel, you can add individual permissions to an object. You can also set permissions by adding ACL templates or ACL policies. For more information, see the following table:

        TaskDescription

        Adding an authorization

        An authorization grants permission to a role to perform a certain type of action on this object.

        To add an authorization to this object, click Add Entry  in the Access Control List area. Then use the Add New Entry dialog box to specify the role and authorization you want to add.

        Adding an ACL template

        An ACL template is a group of predefined authorizations granted to roles. Using an ACL template, you can add a group of authorizations to the object.

        To add an ACL template to the object, click Use ACL Template  in the Access Control List area. Then use the Select ACL Template dialog box to specify an ACL template that you want to add to this object.

        To set the contents of the selected ACL templates so they replace all entries in the access control list, check Replace ACL with selected templates. If you do not check this option, the contents of the selected ACL templates are appended to existing entries in the access control list.

        Adding an ACL policy

        An ACL policy is a group of authorizations that can be applied to this object but can be managed from one location.

        To add an ACL policy to this object, click Use ACL Policy  in the ACL Policies area. Then use the Select ACL Policy dialog box to specify an ACL policy that you want to add to the object.

        To set the contents of the selected ACL policies so they replace all entries in the access control list, check Replace ACL with selected policies. If you do not check this option, the contents of the selected ACL policies are appended to existing entries in the access control list.

        Where to go from here

        Executing a Provision Job

      3. After completing the last step of the wizard, click Finish.
        A Provision Job is stored in the Jobs folder. You can open the job and edit it.
    2. Provide information to the Provision Device wizard as you normally would.
    3. For System Package Properties, select the DATA_STORE property and click Edit .
    4. Click in the Value column and then click Browse . The Choose Property Class Instance dialog box appears.
    5. Select LocalDataStoreInstance and click OK.
    6. Complete the remaining steps of the Provision Device wizard and click Finish.
      When the Provision Job executes, the target servers are provisioned from the local data store.
Was this page helpful? Yes No Submitting... Thank you

Comments