6 Imaging operations
HPDM can be used to capture an image from a device and deploy it to any number of similar devices.
An image is a binary file containing all the data from a device’s flash storage.
IMPORTANT: HPDM will not deploy images to devices that are not licensed for the operating system contained in the image.
TIP: There is no license check for HP ThinPro or HP Smart Zero Core, so those operating systems can be interchanged as long as there is enough disk space.
For information about imaging support on different operating systems, see
Imaging support matrix on page 49 .
To learn more about the different imaging methods available with HPDM, see the following sections:
●
Imaging without PXE on page 50 (recommended)
●
Imaging with PXE on page 52
48 Chapter 6 Imaging operations
Imaging support matrix
The following table describes which operating systems and HP thin clients are supported for each imaging method.
Table 6-1 Imaging support matrix
File-based capture
Disk-based capture
File-based deployment
Disk-based deployment
PXE imaging
WES 8 t610
WES 7 t820, t620, t610, t510, t505, t5740e, t5570e, 6360t, mt41, mt40, 4320t
WES 2009 t610, t510, t505, t5740, t5570, gt7720
WES 2009
6360t, t5400, 4320t
Windows XPe t5740, t5730, t5630
HP ThinPro 4 t620, t610, t510, t505, t5745, t5565
HP ThinPro 3 (x86) t5745, t5735, t5565, t5545, t5145, gt7725
HP ThinPro 3 (ARM) t5325
HP Smart Zero Core (x86) t620, t610, t510, t5565z
HP Smart Zero Core (ARM) t410, t5335z
Windows Embedded CE 6.0
t510, t5550, t5540, t5530
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
IMPORTANT: Complete image version checking is not available for PXE imaging (for example,
Windows XPe version 5.1.502 is compatible with BIOS version 786A1 but not with another BIOS version).
IMPORTANT: Drivers will be missing when deploying a WES 7 or WES 8 image captured from a different HP thin client model. For example, an image captured from a t610 will not work if deployed to a t5570e.
Imaging support matrix 49
IMPORTANT: PXE imaging does not work with the default HPDM Agent in an HP ThinPro 3 image due to some folder name changes. Please update the HPDM Agent to the latest version before attempting PXE imaging.
NOTE: File-based imaging is the current method used by HPDM for WES imaging. The original imaging method used by HPDM in version 4.4.2 and prior was disk-based imaging.
NOTE: PXE imaging is not supported on the 6360t, t5400, or 4320t because the boot order change tools are unavailable.
Imaging without PXE
Imaging without PXE is the recommended method of imaging with HPDM and requires that the
HPDM Agent on the target device is running when the imaging task is sent. The benefit of imaging without PXE is that an HPDM Gateway is not required to be installed in the same subnet as the target devices.
TIP: For WES, make sure that the devices can access the Master Repository’s shared folder and have permission to write. The Group Policy might affect write permissions if the shared folder to be accessed is in a domain.
Capturing an image without PXE
To capture an image without PXE:
1.
Select the Task Templates tab in the task pane, and then double-click on the _Capture Image template.
2.
In the Template Editor - Imaging dialog box, enter a name in the Image Name field for the captured image that will be stored in the Master Repository, and then enter information in the
Description field for the captured image.
3.
If the device uses a wireless network, select Cached Imaging.
NOTE: If the Cached Imaging option is selected, it requires enough free disk space on the device to cache the captured image.
4.
Click the Save as button, enter a name for this template, and then click OK. A new template will appear in the task pane.
5.
Drag and drop this template onto a device in the device pane. The Task Editor dialog box will appear.
6.
In the Save result as template field, enter a name for the result template that will be automatically created to enable you to apply the captured image to other devices.
7.
Click OK to apply the task to the device immediately. When the task is sent, a result template will be created with the name you designated. Its initial status will be “Transferring.”
8.
When the HPDM Agent on the device receives the task, the device will display a warning message indicating that the device will restart in 30 seconds. After the device restarts, a capture utility will copy the content of the flash storage to the Master Repository.
NOTE: A WES image is stored as an .ibr file, and an HP ThinPro or HP Smart Zero Core image is stored as a .dd.gz file.
9.
The device will reboot after capturing has completed.
IMPORTANT: DO NOT turn off the device during this procedure!
50 Chapter 6 Imaging operations
The device will then reboot again.
10.
The task pane in the HPDM Console will continue to indicate that the task is processing. The captured image is being compressed. After the task is finished and the checksum of the captured image is verified, a new template will appear in the Task Templates tab of the task pane with the name you specified.
11.
You can now use this template to apply the captured image to other devices by dragging and dropping it onto devices in the device pane or folders in the device tree.
You can view information about the image associated with the template by double-clicking on the name of the template to display the Template Editor dialog box. This will display the name and OS type of the image. Click the View Details button, and detailed information of the image will appear.
Preserved settings during an image capture without PXE
Table 6-2 Preserved settings during an image capture without PXE
Operating system Preserved settings
WES 8
WES 7
WES 2009
HP ThinPro
HP Smart Zero Core
All settings from the source device are preserved on both the source device and the captured image except the hostname, network settings, domain settings, and write filter status.
All settings from the source device are preserved on both the source device and the captured image except the hostname and network settings.
TIP: For WES 7 and WES 2009, if the source device was joined to a domain prior to having its image captured, then domain membership will be lost after capturing the image. It is recommended to remove the source device from any domain prior to capturing the image. There is also a known issue where the Group Policy that controls the domain password complexity will affect local user accounts, resulting in the user requirement to change the password to meet a more strict criteria.
Deploying an image without PXE
There is not a preset template for deploying an image without PXE, but one can be created by capturing an image or by importing an existing image file.
To deploy an image without PXE:
1.
Create a deployment template by capturing an image without PXE (see Capturing an image without PXE on page 50 ).
—or—
From the menu, click Template > Import > Image Files > to deploy without PXE, and the wizard will automatically create a deployment template.
2.
Double-click on the deployment template to open the Template Editor.
3.
Click the View Details button to view detailed information about the image package.
4.
If the device uses a wireless network, select Cached Imaging.
NOTE: If the Cached Imaging option is selected, it requires enough free disk space on the device to cache the image file.
NOTE: With cached mode, HPDM only supports deploying .ibr images to WES devices or .dd.gz images to HP ThinPro devices.
Imaging without PXE 51
5.
If you want to deploy an image to a device that is a different hardware platform from the source device, select Allow Cross Platform Imaging. This option only applies to WES, and you need to make sure the image can work well on the target device.
6.
Click the Save as button to save the template with a new name.
7.
Drag and drop the template onto the devices to which you want to deploy the image. The Task
Editor dialog box will appear, allowing you to edit the same options you were presented with in the Template Editor.
8.
Click OK to deploy the image to the devices.
NOTE: There will be an automatic BIOS update during a Deploy Image task to install WES7 SP1 on the t5740 or t5740e. The factory BIOS version is 1.03 on the t5740 and t5740e, and WES7 SP1 requires version 1.04.
Preserved settings during an image deployment without PXE
Table 6-3 Preserved settings during an image deployment without PXE
Operating system Preserved settings
WES 8
WES 7
WES 2009
HP ThinPro
HP Smart Zero Core
●
Write filter status
●
Hostname
●
Network settings
●
Terminal Services license
●
Windows activation license (WES 8 only)
●
Hostname
●
Network settings
Imaging with PXE
Imaging with PXE requires an HPDM Gateway (which includes a PXE server) to be installed in the same subnet as the target devices. The benefit of imaging with PXE is that the device’s operating system is not required to be running during an image deployment, meaning you can deploy an image to a device with a corrupted operating system.
TIP: Some additional configurations might be required for PXE imaging. If you experience problems with PXE imaging, see
Configuring your environment for PXE imaging on page 53 .
Capturing an image with PXE
To capture an image with PXE:
1.
Select the Task Templates tab, and double-click the _PXE Capture template.
2.
Input an image name and a description.
3.
Click Save as to save the template.
A new PXE Capture template will be listed in the Task Templates tab.
4.
Drag the template onto a device, and then input a result template name. Click OK to send this
PXE Capture task to a device.
52 Chapter 6 Imaging operations
5.
When the task is sent, a result template will be created with the name you designated. Its initial status will be “Transferring”.
6.
After the task is finished, the result template is valid and can be used to send tasks.
NOTE: An image captured for PXE imaging is always in the .dd.gz format, regardless of the operating system.
Deploying an image with PXE
There is not a preset template for deploying an image with PXE, but one can be created by capturing an image or by importing an existing image file.
To deploy an image with PXE:
1.
Create a deployment template by capturing an image with PXE (see
Capturing an image with
PXE on page 52 ).
—or—
From the menu, click Template > Import > Image Files > to deploy using PXE, and the wizard will automatically create a deployment template.
2.
Drag the deployment template onto a device.
NOTE: PXE deployment supports deploying .dd.gz, .dd, .img, or .hpimg images.
NOTE: If you want to deploy an image to a device that is shut down, the device must support being woken up and be set to “network boot first” in the BIOS.
Configuring your environment for PXE imaging
The following sections discuss some configurations that might be necessary for PXE imaging:
●
Configuring a DHCP server for PXE imaging
●
Configuring routers for PXE imaging
●
Configuring BIOS settings on legacy Neoware devices for PXE imaging
Configuring a DHCP server for PXE imaging
This section describes how to configure a DHCP server for PXE imaging. The DHCP server is used the PXE boot ROM to retrieve basic networking information.
The DHCP server is installed on a different machine from the HPDM Server
If problems occur during PXE imaging, the DHCP server might need to be checked for certain settings that conflict with PXE. However, on most networks, these issues should not occur.
To configure the DHCP server:
1.
Make sure that the DHCP server has not been previously configured for a PXE bootstrap.
2.
Make sure that DHCP options 43 and 60 are not set.
The DHCP server should then be ready to be used with PXE.
The DHCP server is installed on the same machine as the HPDM Server
If the DHCP server is installed on the same machine as the HPDM Server, it requires some manual configuration.
Imaging with PXE 53
These instructions assume the following:
●
The network is already configured using DHCP.
●
The DHCP server has not been previously configured for a PXE bootstrap.
●
There are no other TFTP servers running on the same network.
To configure the DHCP server:
1.
Make sure that DHCP option 43 is not set.
2.
Add DHCP option 60 by doing the following: a.
From the Windows Start menu, select Start > Run.
TIP: In Windows Server 2012, right-click the lower-left corner of the desktop and select
Run.
b.
Type Cmd and click OK to open a Command Prompt.
c.
Type netsh and press the Enter key.
d.
Type dhcp and press the Enter key.
e.
Type server \\<server_name> (using the UNC name for the server).
—or—
Type server <ip_address> (using the IP address of the server).
A dhcp server > prompt appears in the command window.
f.
Type add optiondef 60 <name of your choice> STRING 0 and press the Enter key.
g.
Type set optionvalue 60 STRING “PXEClient“ and press the Enter key.
h.
To confirm that the settings are correct, type show optionvalue all and press the
Enter key.
3.
Add DHCP option 201 by doing the following: a.
At the dhcp server > prompt, type add optiondef 201 <name of your choice>
STRING 0 and press the
Enter key.
b.
Type set optionvalue 201 STRING ‘<HPDM_Gateway_IP_Address>’ ‘40003’ and press the Enter key.
NOTE: The <HPDM_Gateway_IP_Address> is the address of the server running the
HPDM Gateway service. This command must be written exactly as shown above, including the single quotes and single space, as shown in the following example: set optionvalue 201 STRING ‘192.168.1.100’ ‘40003’ c.
To confirm that the settings are correct, type show optionvalue all and press the
Enter key.
The DHCP server should then be ready to be used with PXE.
Configuring a Linux DHCP server for PXE imaging
1.
Edit the DHCP server configuration file /etc/dhcpd.conf. Add the following lines to the beginning of the file exactly as shown:
54 Chapter 6 Imaging operations
ddns-update-style ad-hoc;
Authoritative;
Option NDM code 201 =string;
Option vendor-class-identifier “PXEClient”;
Option NDM “‘<HPDM_Gateway_IP_Address>’ ‘40003’”;
NOTE: The <HPDM_Gateway_IP_Address> is the address of the server running the HPDM
Gateway service. This command must be written exactly as shown above, including the double quotes, single quotes, and single space, as shown in the following example:
Option NDM “‘192.168.1.100’ ‘40003’”;
2.
Restart dhcpd to use the new configuration.
Configuring routers for PXE imaging
For PXE imaging to function properly, any network that uses DHCP and has multiple subnets should have an IP helper configured in the router that is between any devices that require a dynamic IP address and the DHCP server. The router will need to be configured to have an additional IP helper address point to the HPDM Gateway.
The following example uses a Cisco router:
1.
Enter Global Configuration mode.
2.
Type ip forward-protocol udp 67 and press Enter .
3.
Type ip forward-protocol udp 68 and press Enter .
4.
Type ip helper-address <DHCP_Server_IP_Address> and press Enter .
5.
Type ip helper-address <HPDM_Gateway_IP_address> and press Enter .
NOTE: The above IP addresses should be entered without the < or > characters.
Configuring BIOS settings on legacy Neoware devices for PXE imaging
Before you can capture or deploy an image with PXE on legacy Neoware devices, you must make sure that the source and target devices have their BIOS settings configured correctly.
To configuring BIOS settings on legacy Neoware devices for PXE:
1.
Turn on the device and hold down the Delete key to display the CMOS Setup Utility screen.
2.
Select Advanced BIOS Features and set the following:
First Boot Device [LAN]
Second Boot Device [HDD-0]
3.
Press the Esc key to return to the initial screen, and then select Integrated Peripherals > VIA
OnChip PCI Device.
4.
Make sure Onboard Lan Boot ROM is set to [Enabled].
5.
Press the F10 key, press the Y key, and then press Enter to save the settings.
Imaging with PXE 55
