HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

• The value can contain special characters and spaces, and you may also leave it blank. Special
characters might require double quotes if the value will be executed, for example “echo hello
> temp.txt”.
• A custom attribute value can be multiple lines.
• Since it is used as a delimiter, the @ sign cannot be used in the default value you specify in
a custom attributes.
• You may not use a custom attribute within a custom attribute value.
• You may not have duplicate custom attribute names for an individual OS Build Plan, server
or facility level.
• Custom attributes are associated with servers, device groups, your facility, and OS Build Plans.
If the same custom attribute name is defined at multiple levels, conflicts are resolved by
precedence.
Custom attribute precedence, highest to lowest
1. Servers
2. Device group
3. Facility
4. OS Build Plans
For example, if a custom attribute is defined for a server and defined for an OS Build Plan,
the custom attribute value defined for the server would be used.
If the same custom attribute is assigned to multiple device groups and the same server is in
both of those groups, the device group the server inherits that custom attribute from is
unpredictable.
NOTE: Custom attributes set at the OS Build Plan level are at the lowest precedence.
Creating your own custom attributes
Objects that are allowed to have custom attributes will have an area on the resource’s Overview
screen for creating them.
NOTE: Do not create custom attributes with the prefix “_ _OPSW” (double underscore preceding
“OPSW”) as that identifies custom attributes internal to IC server provisioning.
If you create a custom attribute that already exists for another higher precedence object, then the
value of the higher precedence object custom attribute will be used.
Table of some commonly used custom attributes
The table lists some commonly used custom attributes. For a complete list of custom attributes, see
the Insight Control Server Provisioning Build Plans Reference Guide.
Example valuesDescriptionName
For Windows deployment:
C, D, EDrive label set for the target server’s
system drive where Windows will be
installed.
SystemDrive
0, 1, 2, 3The physical drive number to install
the OS to. This custom attribute is not
SystemDiskNumber
meant to be set by the end user. It is
set automatically during Build Plan
execution and is used to make sure
the Windows installer does not install
40 Using custom attributes