HP Insight Control Server Provisioning 7.2 Online Help

5 OS Build Plans
5.1 Best practices for OS Build Plans
• “Change the default administrator/root password” (page 48)
• “Use existing Build Plans as templates” (page 48)
• “Use HP’s naming convention for Build Plans” (page 48)
• “Make sure firmware and driver levels agree” (page 50)
• “Make sure you have HP ESXi distros” (page 50)
• “On SAN, present only OS system disk when installing an OS” (page 50)
5.1.1 Change the default administrator/root password
The HP-provided Build Plans use custom attributes to set the administrator or root password for new
installations. The custom attribute AdminPassword is used to set the “Administrator” password
on a new Windows installation. The custom attribute root_password is used to set the “root”
password on a new Linux installation. You can set this custom attribute for individual servers, or
at the facility level if you want to apply these passwords to all new installations.
The default value is
ChangeMe123!
encrypted.
CAUTION: HP strongly recommends changing this password before deploying to any servers.
See “Editing OS Build Plan custom attributes” (page 57) for instructions.
5.1.2 Use existing Build Plans as templates
HP supplies OS Build Plans with the Insight Control server provisioning product. These Build Plans
work out of the box but were designed to be easily used as templates.
Build Plans supplied by Insight Control server provisioning are read only and may not be edited,
but you can save a copy to work from. See “Copying OS Build Plans” (page 51) for information.
5.1.3 Use HP’s naming convention for Build Plans
Good names are important for understanding what a Build Plan does and for helping you find the
Build Plan you are looking for. HP uses the following naming convention for the Build Plans supplied
with Insight Control server provisioning.
48 OS Build Plans