Configuring insight control server provisioning, Utilizing enhanced server customization – HP Matrix Operating Environment Software User Manual
Page 35
NOTE:
If you copy and paste these commands, be sure to enter the dash (minus) key. In some
cases, copying and pasting results in characters that appear to be the same but are incorrect.
•
Insight Control server provisioning
mxnodesecurity -a -p dsc_sas -c username:password -t on -n <ipaddress
of server provisioning server>
•
HP Server Automation (SA):
mxnodesecurity –a –p dsc_sas –c username:password -t on -n <ipaddress
of HP Server Automation server>
•
Ignite-UX
mxnodesecurity –a –p dsc_ignite –c username:password -t on -n
<ipaddress of Ignite server>
•
Insight Control server deployment
mxnodesecurity –a –p dsc_rdp –c username:password -t on -n <ipaddress
of server deployment server>
Configuring Insight Control server provisioning
For additional information about configuring Insight Control server provisioning for use with Matrix
infrastructure orchestration, see the Insight Control server provisioning online help and the HP
Insight Control Server Provisioning Administrator Guide available at
matrixoe/docs
Utilizing enhanced server customization
Matrix infrastructure orchestration user-defined properties can be used with deployment servers
that support custom attributes to set the custom attributes used by OS Build Plans. This enables a
vast potential for server customization both during and after OS installation. Examples include:
pre-configuring IPv4 or IPv6 networks, joining a Windows Active Directory domain, NIC teaming,
provisioning VMware ESXi hosts without VMware Auto Deploy, and others. When using IC server
provisioning, Matrix is able to allow customization of network information before the OS is installed
and to use scripts to enable capabilities for certain OS environments (Windows, Linux, and ESXi).
Setting deployment server custom attributes with Matrix infrastructure orchestration
Some deployment servers (Server Automation, Insight Control server provisioning) support the use
of custom attributes. Custom attributes are variables that can be accessed from inside of an OSBP
(OS Build Plan) on the deployment server. Some custom attributes are well known such as
ProductKey_Win2012-Std-x64, which specifies the Microsoft product key for Windows 2012
Standard edition, or SystemDrive, which specifies the location of Proliant drivers. Others are
user-defined and can only be utilized by modification of steps or scripts on the deployment server.
NOTE:
Insight Control server deployment and Ignite-UX do not support custom attributes.
Custom attributes are created from the user-defined properties in the Matrix infrastructure
orchestration template in the Configure Server Group dialog Properties tab. In the example below,
the product key user-defined property would replace the custom attribute default product key when
deploying Windows 2012 x64 Standard.
Configuring deployment servers
35