Insight Control server provisioning provides Build Plans to capture system images and perform image installations of those captured images. You use the image capture Build Plans (for example ProLiant OS - Windows 2012 Standard x64 Image Capture) to make an image of a system with everything setup the way you want it. You can use the image install Build Plans (for example ProLiant OS - Windows 2012 Standard x64 Image Install) to deploy or replicate this image onto many systems.
|
|
|
![[IMPORTANT: ]](images/important.gif) |
IMPORTANT: Windows image capture Build Plans contain a Prepare Windows for Image Capture step that uses the |
|
|
The following requirements must be met for Windows image capture and install Build Plans.
-
Images can only be captured from servers running a version of Windows supported by IC server provisioning. For details, see the Insight Management Support Matrix at http://www.hpe.com/info/insightmanagement/docs.
-
When capturing an image, the target server must be booted up and running a production OS.
-
You must have an
Imagesfolder on your Media Server directly under the top level folder of your file share. If you used the Insight Control server provisioning Media Server setup utility to set up your Media Server, the folder was created for you. -
The custom attribute
WimFileNamemust be defined. This custom attribute specifies the file name for the captured Windows image (WIM image) you are creating or installing. The WIM image will always be located in theImagesfolder on your Media Server unless you modify the parameters to the Windows Image Capture and Windows Image Deploy Build Plan steps to use another folder. -
The partition that is captured is determined by the combination of the disk number, as reported by diskpart from WinPE, plus the partition label. The disk number is specified in the
SystemDiskNumbercustom attribute, which defaults to disk 0 if theSystemDiskNumbercustom attribute is not set. The partition label is set using the--systemPartitionLabelparameter in the Windows Image Capture Build Plan step, and is set toSystemif no parameter is specified.Note that on Gen8 servers or newer, the disk number reported by diskpart on the production OS may differ from the disk number reported on the Intelligent Provisioning WinPE, because diskpart will also account for the embedded media used by Intelligent Provisioning. Because the image capture and image deployment is done from WinPE, it is important that the
SystemDiskNumbercustom attribute is set to the disk number as reported by WinPE.Servers using PXE, instead of the PXE-less Intelligent Provisioning, may see the disk numbers reported differently by diskpart in WinPE, since PXE WinPE does not expose the embedded media that would normally be present in the PXE-less Intelligent Provisioning.
-
The target server must have similar hardware to the reference server from which the image was captured. Before you use the image tool to install a Windows image, Hewlett Packard Enterprise recommends that you review the ImageX documentation. http://technet.microsoft.com/en-us/library/cc722145%28v=ws.10%29.aspx
An example of a Hewlett Packard Enterprise provided Windows image capture Build Plan: ProLiant OS - Windows 2012 Standard x64 Image Capture. All Hewlett Packard Enterprise provided Windows image capture Build Plans are configured to work on the Standard edition of Windows. To configure for other editions, see Install a specific Windows edition.
An example of a Hewlett Packard Enterprise provided Windows image install Build Plan: ProLiant OS - Windows 2012 Standard x64 Image Install
IC server provisioning supports capturing and installing Linux system images, however, Build Plans for doing this are not built into the appliance at this time. If you want to do Linux imaging, the process is detailed in several Insight Control server provisioning Capturing and Installing Linux System Images white papers, which can be found at http://www.hpe.com/info/insightcontrol/docs. Choose the white paper for the version of Linux you are using.