Technical white paper Insight Control server provisioning How to Create an OS Build Plan for Installing Windows 2012 R2 Table of contents Summary 2 Add the Windows 2012 R2 Distribution Files to the Media Server 2 Add the Windows 2012 R2 Product Key Custom Attribute 2 Create the Windows 2012 R2 Scripted Install OS Build Plan 2 Create the Windows 2012 R2 Image Capture OS Build Plan 3 Create the Windows 2012 R2 Image Install OS Build Plan 4 Create an OS Build Plan to Install the Windows 2012 R2 Supplement Release for Service Pack for ProLiant 4 Limitations 5 For more information 5
Summary The Insight Control (IC) server provisioning appliance comes pre-packaged with OS Build Plans (OSBPs) that perform scripted and image installations. However, the OSBPs for scripted and image installs of Windows 2012 R2 will not be available until a future release of IC server provisioning. This technical paper will provide instructions to create an OSBP to deploy Windows 2012 R2 Standard and Datacenter editions via scripted or image install using the pre-packaged Windows 2012 OSBPs on the appliance. This document assumes that the reader is familiar with the IC server provisioning appliance and has the appropriate administrative rights to the appliance. Add the Windows 2012 R2 Distribution Files to the Media Server The distribution files must be added to the media server to successfully deploy Windows 2012 R2 via scripted install to a target server via a scripted install. To add the Windows 2012 R2 distribution files to the Media Server 1. On the Media Server, create the directory win2012r2-x64-en_us under the Media directory. The steps to create the OSBP expect the distribution files to be located at Media\win2012r2-x64-en_us. 2. Mount the Windows 2012 R2 iso and copy the files to the new Media\win2012r2-x64-en_us directory. Add the Windows 2012 R2 Product Key Custom Attribute The product key custom attribute is required for both Windows 2012 R2 scripted and image installs. To add the Windows 2012 R2 product key custom attribute: 1. On the IC server provisioning appliance, select Settings -> Facility Custom Attribute -> Edit. 2. Select Create facility custom attribute. 3. In the name field enter LicenseKey_Win2012R2-Std-x64 or LicenseKey_Win2012R2-DC-x64. This custom attribute name is different from the HP-provided Windows product key custom attributes defined in Settings -> Product Keys. 4. For the value field, enter the Actual Windows License key as provided by Microsoft. Create the Windows 2012 R2 Scripted Install OS Build Plan To create an OSBP that installs Windows 2012 R2 Standard edition via scripted installation 1. Create the Windows 2012 R2 Standard edition configuration file. a. On the IC server provisioning appliance, select the Configuration Files view. b. Make a copy of the Windows 2012 Standard x64 en_us Unattend configuration file by selecting c. Save the configuration file with the name Windows 2012 R2 Standard x64 en_us Unattend. Update d. Edit the new configuration file with the following changes: i. Under the <servicing> section, modify the version value of <assemblyidentity> tag to the appropriate Windows 2012 R2 iso version. This can be found by viewing the properties for the setup.exe file on the iso. 2
ii. Under the <ProductKey> section, modify the <key> value to @LicenseKey_Win2012R2-Std-x64@. This should match the custom attribute name defined in the Add the Windows 2012 R2 Product Key Custom Attribute section of this document. iii. Under <settings pass= specialize >, modify the <ProductKey> value to @LicenseKey_Win2012R2-Std-x64@. This should match the custom attribute name defined in the Add the Windows 2012 R2 Product Key Custom Attribute section of this document. iv. Under <Key>IMAGE/NAME</Key>, modify the <Value> value to Windows Server 2012 R2 SERVERSTANDARD. NOTE: Alternatively, you can provide your own Windows 2012 R2 unattend answer file created from scratch using Windows ADK. 2. Create the Scripted Install OSBP. a. Select the OS Build Plans view. b. Make a copy of the ProLiant OS Windows 2012 Standard x64 Scripted Install OSBP by selecting c. Save the OSBP with the name ProLiant OS - Windows 2012 R2 Standard x64 Scripted Install. Update d. Edit the new build plan with the following changes: i. For the first step, Validate Custom Attributes, change the Parameter field from ProductKey_Win2012-Std-x64 to LicenseKey_Win2012R2-Std-x64. ii. Remove the Config File Step 9, Windows 2012 Standard x64 en_us Unattend, with the new Config File step, Windows 2012 R2 Standard x64 en_us Unattend. Specify the Install Path as X:\Windows\Temp\Unattend.xml. iii. Modify the Parameter field for script Step 13, Run Windows 2012 x64 Setup to z:\media\win2012r2-x64-en_us\setup.exe. This should match the path created in the Add the Windows 2012 R2 Distribution Files to the Media Server section of this document. iv. Remove the Install ZIP Step 12, ProLiant Drivers for Windows 2012 2013.09b. The drivers from the 2013.09b SPP are not supported on Windows 2012 R2. 3. To enable the Hyper-V role during the scripted install, at the end of the new build plan add in this order the Add Windows Hyper-V Role, the Reboot, and the Wait for HP SA Agent build plan script steps with the same script parameters as the last steps in the Windows OS build plan. The OSBP is complete and ready to deploy Windows 2012 R2 to a target server. To deploy Windows 2012 R2 Datacenter edition, follow Steps 1 and 2 above; however, use the Windows 2012 Datacenter x64 en_us Unattend configuration file, LicenseKey_Win2012R2-DC-x64 for the license key custom attribute, and Windows Server 2012 R2 SERVERDATACENTER for the image name value. Since a default Datacenter OSBP is not provided, continue to use the ProLiant OS Windows 2012 Standard x64 Scripted Install as the template OSBP. Create the Windows 2012 R2 Image Capture OS Build Plan The ProLiant OS Windows 2012 Standard x64 Image Capture OSBP can be used to capture the image of a target server running Windows 2012 R2 Standard or Datacenter editions. A separate OSBP is not necessary. However, the WimFileName custom attribute will need to be defined before the image capture or image install OSBPs can be used. To add the Windows 2012 R2 image file custom attribute: 1. On the IC server provisioning appliance, select Servers->Select Server->Custom Attribute -> Edit. 2. Select Create custom attribute. 3. In the name field enter WimFileName. 3
4. For the value field, enter win2k12r2.wim. The Windows 2012 Image Capture OSBP is ready to capture the Windows 2012 R2 image. Create the Windows 2012 R2 Image Install OS Build Plan To create an OSBP that installs Windows 2012 R2 via image installation: 1. Refer to Step 1 in the Create the Windows 2012 R2 Scripted Install OS Build Plan section of this document to create the configuration file. 2. Create the Image Install OSBP. a. Select the OS Build Plans view. b. Make a copy of the ProLiant OS Windows 2012 Standard x64 Image Install OSBP by selecting c. Save the OSBP with the name ProLiant SO - Windows 2012 R2 Standard x64 Image Install. Update d. Edit the new build plan with the following changes: i. For the first step, Validate Custom Attributes, change the Parameter field from ProductKey_Win2012-Std-x64 to LicenseKey_Win2012R2-Std-x64. ii. Remove the Config File Step 12, Windows 2012 Standard x64 en_us Unattend, with the new Config File step, Windows 2012 R2 Standard x64 en_us Unattend. Specify the Install Path as @SystemDrive:C@:\Windows\Panther\unattend.xml. The OSBP is complete and ready to deploy a Windows 2012 R2 image to a target server. To deploy Windows 2012 R2 Datacenter edition, follow Steps 1 and 2 above; however, use the Windows 2012 Datacenter x64 en_us Unattend configuration file, LicenseKey_Win2012R2-DC-x64 for the license key custom attribute, and Windows Server 2012 R2 SERVERDATACENTER for the image name value. Since a default Datacenter OSBP is not provided, continue to use the ProLiant OS Windows 2012 Standard x64 Image Install as the template OSBP. Create an OS Build Plan to Install the Windows 2012 R2 Supplement Release for Service Pack for ProLiant HP Service Pack for ProLiant (SPP) is the current publishing method for HP-provided drivers and related software. However, an SPP will not be available for use with the Windows 2012 R2 until early 2014. Until then, the Windows 2012 R2 Supplement Release for SPP is available. To install the Windows 2012 R2 Supplement Release to the Media Server and create an OSBP that installs the supplement: 1. On the Media Server, create the directory win2012r2-supplement under the Media\SPP directory. The steps to create the OSBP expect the distribution files to be located at Media\SPP\win2012r2- supplement. 2. Create the directories hp\swpackages within the win2012r2-supplement directory, for example Media\SPP\win2012r2-supplement\hp\swpackages. 3. Download the Windows 2012 R2 Supplement Release for SPP at ftp://ftp.hp.com/pub/softlib2/software1/supportpack-generic/p1235385378/v89111/msw2k12r2- rtmsupplement-2013.09.0.b.win.exe and place it under swpackages directory. 4. Execute the MSw2k12r2-rtmsupplement-2013.09.0.B.win.exe file to extract all components into the swpackages directory. 5. On the IC server provisioning appliance, select the OS Build Plans view. 6. Make a copy of the ProLiant SW Install Windows SPP OSBP by selecting 4
7. Save the OSBP with the name ProLiant SW Install Windows 2012 R2 Supplement SPP. Update the description field as needed. 8. Edit the new build plan to modify the Parameter field for script Step 4, Install Windows SPP to -- spp_version=win2012r2-supplement. This should match the new SPP directory created on the Media Server in Step 1. Limitations When viewing the target server properties on the appliance, the operating system value will reflect Windows 2012 x64 without the R2 indication. For more information To read more about Insight Control server provisioning, go to www.hp.com/go/insightcontrol/docs HP Insight Management Support Matrix HP Insight Control Server Provisioning Installation Guide HP Insight Control Server Provisioning Administrator Guide HP Insight Control Server Provisioning online help HP Insight Control Release Notes Get connected hp.com/go/getconnected Current HP driver, support, and security alerts delivered directly to your desktop Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. 5900-3147, Created November 2013 Edition: 1.0 5