Release Notes Software: HP Device Manager Revision: 4.5 Service Pack 1 (4.5.1.16819) Build Date: February 1, 2013 Table of contents Introduction 2 Component Version Information 2 System Requirements 3 Management Console 3 Management Server 3 Management Gateway 4 Management Agent 4 Master Repository Controller 5 Additional Requirements 5 Network Requirements 5 Ports 6 Installation Procedure 9 Console, Server, Gateway, and Master Repository Controller 9 Management Agent 12 Imaging Notes 13 Imaging Support Matri 13 Preserved Settings during Imaging 14 Checks before Imaging 15 What s New in 4.5 Service Pack 1 16 Issues Fied in 4.5 Service Pack 1 16 Known Issues 16 License 18 For more information 18
Introduction This document describes the release of HP Device Manager 4.5 Service Pack 1, the net generation of enterprise device management software. It specifies system requirements, gives installation instructions, and provides an overview of the main features of the software. HP Device Manager is an enterprise-class application for managing and administrating thin client devices on large- and small-scale networks. The system consists of five major components: Management Console: The graphical application used by administrators to access the management system. Management Server: The central server which consolidates and controls all management activities. Management Gateway: The gateway which serves as the link between Agents and the Management Server. Management Agent: Client-side software required for managing devices. Master Repository Controller: The component that manages the content in the Master Repository and synchronizes that content to other repositories as requested by the HPDM Server. For more detailed instructions on how to use HP Device Manager, please refer to the User Guide. Component Version Information This release provides the following versions of these components (* are new versions since 4.5, build revision: 4.5.16261): Installer: 4.5.1.16819* Console and Server: 4.5.3610.16819* Gateway for Windows : 4.5.3630.16674* Master Repository Controller: 4.5.3680.16444* Agents HP WES7E, WES7P, WES09, XPe Agent Build: 4.5.3660.16798* HP ThinPro 4 (86) Agent Build: 4.5.3668.16798* HP Smart Zero Core (86, ARM) Agent Build: 4.5.3667.16798* HP ThinPro 3 (86, ARM) Agent Build: 4.5.3665.16798* 2
System Requirements Management Console The Management Console can be installed on any number of machines. The following environment is the minimal hardware and required software for running the Management Console: Operating Systems: Windows Server 2003 with Service Pack 2 (64-bit) Windows Server 2003 R2 with Service Pack 2 (32- & 64-bit) Windows Server 2008 with Service Pack 2 (32-bit) Windows Server 2008 R2 with Service Pack 1 (64-bit) Windows XP Professional with Service Pack 3 (32-bit) Windows 7 Enterprise with Service Pack 1 (64-bit) Third-party Software: Java Runtime: SUN Java Runtime Environment version 6 update 2 (bundled with installer) Hardware: Pentium III or greater 512 MB RAM 256 MB free disk space Management Server There must be only one Management Server in the system. The following environment is the minimal hardware and required software for running the Management Server: Operating Systems: Windows Server 2003 with Service Pack 2 (64-bit) Windows Server 2003 R2 with Service Pack 2 (32- & 64-bit) Windows Server 2008 with Service Pack 2 (32-bit) Windows Server 2008 R2 with Service Pack 1 (64-bit) Third-party Software: Java Runtime: SUN Java Runtime Environment version 6 update 2 (bundled with installer) DBMS - Any of the following are supported: PostgreSQL 8.3 or later (bundled with installer) Microsoft SQL Server 2005 or later Hardware: Pentium III or greater 512 MB RAM 512 MB free disk space Note: The above hardware describes the minimum required to run the HP Device Manager Management Server. If the instance of the Management Server will be used to manage a large number of thin clients, then it is recommended to use a more powerful system. 3
Management Gateway The Management Gateway may be installed on multiple machines. However, only one Gateway should be present per subnet. The following environment is the minimal hardware and required software for running the Management Gateway: Operating Systems: Windows Server 2003 with Service Pack 2 (64-bit) Windows Server 2003 R2 with Service Pack 2 (32- & 64-bit) Windows Server 2008 with Service Pack 2 (32-bit) Windows Server 2008 R2 with Service Pack 1 (64-bit) Hardware: Pentium III or greater 512 MB RAM 512 MB free disk space Management Agent The Management Agent should be installed on each device that will be managed by the system. The management agent is supported by thin client devices. The following environment is required for running the Management Agent: Operating Systems: HP XPe*, WES7E, WES7P, and WES09 HP ThinPro 4 HP Smart Zero Core HP ThinPro 3 HP CE 6* Note: For the operating systems marked with a * symbol, HP Device Manager 4.5 only provides limited support. The newly added features may or may not work with these operating systems. These operating systems are not under full test by the HP Device Manager Product Development Team. The latest stable HP Device Manager release that has been fully tested with these operating systems is HP Device Manager 4.4 (Installer version: 4.4.12440, built on 08/29/2011). Hardware: Thin client device supporting one of the above operating systems. 2 MB free disk space Supported Devices: HP XPe*/WES7E/WES7P/WES09 t610, t510, t5740, t5740e, t5570, t5570e, t5400 mt40, 6360t, 4320t HP ThinPro 4 t610, t510, t5745, t5565 HP ThinPro 3 t5745, t5565 HP Smart Zero Core t610, t510, t410, t410 All-in-One, t5565z, t5335z 4
HP CE* t510, t5550* Note: For the devices and operating systems marked with a * symbol, HP Device Manager 4.5 only provides limited support. The newly added features may or may not work with these devices and operating systems. These devices and operating systems are not under full test by the HP Device Manager Quality Assurance team. The latest stable HP Device Manager release that has been fully tested with these devices and operating systems is HP Device Manager 4.4 (Installer version: 4.4.12440, built on 08/29/2011). Master Repository Controller There must be only one Master Repository in the system. The Master Repository needs to be managed by a Master Repository Controller, which must be installed on the same machine as the Master Repository. The Master Repository Controller may or may not be installed on the same host machine as the Management Server. The Master Repository Controller must be installed on a machine that has installed the service supporting any of the following file transferring protocols: FTP, FTPS, SFTP, or SMB (Shared Folder). The following environment is the minimal hardware and required software for running the Master Repository Controller: Operating Systems: Windows Server 2003 R2 with Service Pack 2 (64-bit) Windows Server 2008 R2 with Service Pack 1 (64-bit) Third-party Software: FTP Server The following servers are recommended for use with HP Device Manager: Microsoft Internet Information Server (IIS) 6.0 or later FileZilla FTP Server freesshd Hardware: Pentium III or greater 512 MB RAM 2 GB free disk space Note: The above hardware describes the minimum required for the Master Repository. If there will be a large number of imaging or copying file operations, then it is recommended to use a more powerful system (i.e. more free disk space). Additional Requirements To support communication between the different components of the system, the network must provide open access on certain ports. In addition to transferring large files between components, FTP servers must be accessible by the system. The following are additional requirements for running the management system: Network Requirements The network should not contain any other running PXE servers. The network should permit free communication on ports used by HP Device Manager (see below). 5
Ports The following tables list the standard and custom ports used by HP Device Manager. The ports are categorized by HPDM components as the receiver. This is to facilitate the firewall configuration if the HPDM components are installed separately on different host machines. Table 1: HPDM Console Receiver Port Protocol Sender Receiver Purpose 5500 TCP VNC Server (thin client side) VNC Viewer (bundled with HPDM Console) VNC Viewer in Listen Mode (reverse VNC). 40004 TCP VNC SSL Proy on Agent side VNC SSL Proy on Console side VNC SSL Proy in Listen Mode on Console side Table 2: HPDM Server Receiver Port Protocol Sender Receiver Purpose 1099 TCP HPDM Console HPDM Server Console queries the RMI Registry. 40002 TCP HPDM Console HPDM Server Console calls the remote objects on Server by RMI. 40005 TCP HPDM Gateway HPDM Server Gateway sends report to Server. 40006 TCP HPDM Server PostgreSQL (bundled with HPDM Server) The default database PostgreSQL listening port (the port is only needed when PostgreSQL is used). 40009 TCP HPDM Agent HPDM Server Agent sends resource information (CPU, RAM, Disk IO, Network IO, Processes, etc.) to Server. And, Server sends stopping process command to Agent. Table 3: HPDM Gateway Receiver Port Protocol Sender Receiver Purpose 67 UDP PXE Client (thin client side) HPDM PXE Server (bundled with HPDM Gateway) PXE Bootstrap. 69 UDP PXE Client (thin client side) HPDM PXE Server (bundled with HPDM Gateway) TFTP (Trivial File Transfer Protocol). 4011 UDP PXE Client (thin client side) Proy DHCP service (third-party software) Proy DHCP service (an alternative to port 67 if port 67 is not available). 6
Receiver Port Protocol Sender Receiver Purpose 40000 UDP HPDM Server HPDM Agent HPDM Gateway Server/Agent polls Gateway. 40003 TCP HPDM Server HPDM Agent HPDM Gateway Server sends task to Gateway; Agent sends report to Gateway. 40008 TCP HPDM Gateway HPDM Gateway Controller Gateway notifies Gateway Controller there are other gateways running in the same subnet. Table 4: HPDM Agent Receiver Port Protocol Sender Receiver Purpose 22 TCP OpenSSH Client (bundled with HPDM Console) OpenSSH Server (bundled with HPDM WES Agent) OpenSSH port for secure VNC connection (only for WES Agent). 67 UDP HPDM Agent DHCP Server Agent sends DHCP option requests (Note: The receiver for this port is not on HPDM Agent side). 68 UDP DHCP Server HPDM Agent Agent receives replies of DHCP options. 68 UDP HPDM PXE Server (bundled with HPDM Gateway) HPDM Imaging Mini Linu Tool(thin client side) PXE Bootstrap. 5900 TCP VNC Viewer (bundled with HPDM Console) VNC Server (thin client side) VNC Server. 40001 TCP HPDM Gateway HPDM Agent Gateway sends task to Agent 40001 UDP HPDM Gateway HPDM Agent Agent receives replies of broadcasting Gateway 40004 TCP VNC SSL Proy on Console side VNC SSL Proy on Agent side VNC SSL Proy in Listen Mode on Agent side Table 5: HPDM Repositories (Master Repository and Child Repositories): Receiver Port Protocol Sender Receiver Purpose 20 & 21 TCP HPDM Console HPDM Gateway HPDM Agent FTP server (third-party software) The default ports for FTP (used for HPDM Repository). Port 20 is for data transfer and port 21 listens to commands. FTP port can be configured on HPDM Console. If you do not use the default ports for your FTP, please configure the firewall as it is. 7
Receiver Port Protocol Sender Receiver Purpose 22 TCP HPDM Console HPDM Gateway HPDM Agent SFTP server (thirdparty software) The default port for SFTP (used for HPDM Repository). SFTP port can be configured on HPDM Console. If you do not use the default port for your SFTP, please configure the firewall as it is. 137 UDP HPDM Console HPDM Gateway HPDM Agent NetBIOS Name Service For File and Printer Sharing to allow NetBIOS Name Resolution 138 UDP HPDM Console HPDM Gateway HPDM Agent NetBIOS Datagram Service For File and Printer Sharing to allow NetBIOS Datagram transmission and reception 139 TCP HPDM Console HPDM Gateway HPDM Agent NetBIOS Session Service For File and Printer Sharing to allow NetBIOS Session Service connections 445 TCP HPDM Console HPDM Gateway HPDM Agent Microsoft Directory Services For File and Printer Sharing to allow Server Message Block transmission and reception via Named Pipes 989 & 990 TCP HPDM Console HPDM Gateway HPDM Agent FTPS server (thirdparty software) The default ports for FTPS (used for HPDM Repository). Port 989 is for data transfer and port 990 listens to commands. FTPS port can be configured on HPDM Console. If you do not use the default ports for your FTPS, please configure the firewall as it is. 40012 TCP HPDM Server Master Repository Controller Server talks to Master Repository Controller to manage Master Repository (this port is for Master Repository only). 8
Installation Procedure Console, Server, Gateway, and Master Repository Controller HP Device Manager 4.5 Service Pack can only be installed onto a machine which has HP Device Manager 4.5 installed. If there is only one component (e.g. HPDM Console) of HP Device Manager 4.5 installed on a machine, installing HP Device Manager 4.5 Service Pack on this machine will upgrade only the installed component. 1) Double click HPDM Service Pack setup file to run the service pack installer package, the following dialog will pop up to etract the installation files. 2) After finishing preparation step, the setup checks whether HP Device Manager 4.5 is installed on this machine. a. If HP Device Manager 4.5 is not installed on this machine, the following message bo will pop up. The setup process will eit after clicked OK. b. If HP Device Manager 4.5 is already installed on this machine, the following message bo will pop up. Click Yes to go to net step. Or click No to eit this setup process. 9
3) If HP Device Manager 4.5 is installed on this machine, the installation will check which revision of HPDM is installed on this machine. a. If the revision is lower than the revision of this Service Pack, this setup will begin to install the Service Pack on this machine. b. If the revision is the same as the version of this Service Pack, the following message bo will pop up. The setup process will eit after clicked OK. c. If the revision is higher than the revision of this Service Pack, the following message bo will pop up. The setup process will eit after clicked OK. 4) After installation finished, it will pop up a complete dialog, click Finish button. 10
5) You can find the product name changes in control panel Program and Features after the service pack is installed. For instance, in below screenshot, after the service pack 1 is installed, the product name is changed to HP Device Manager 4.5 Service Pack 1. Installation Language By default, the installer is launched in the target system s language. For eample, if the target system s language is German, the installer s UI language is German automatically. If the user wants to launch the installer in a different language from the target system s language, they can specify a language identifier when launching the installer as below: setup.ee l<language ID> For eample, to launch the installer in German: setup.ee -l00407 The following table lists the available language IDs: Table 6: Language ID s 11
Language ID Language Name 00804 Chinese (Simplified) 00404 Chinese (Traditional) 00409 English (United States) 0040c French (France) 00407 German (Germany) 00411 Japanese (Japan) 00412 Korean (Korea) 0040a Spanish (International) Note: The user can specify the language for the HPDM UI language, which is different from the installer s UI language. For eample, the installer is launched in German, and the user can specify Simplified Chinese as HPDM UI language. The HPDM language setting is present in the Installation Configuration Wizard upon installation. Management Agent HP thin clients will ship with a HP Device Management Agent pre-installed. To update the Agent, from the HPDM Console, send an Update Agent task to all thin clients. 12
Imaging Notes Imaging Support Matri The following is the matri for which OS/Model is supported for each imaging task template ( means supported): Table 7: Imaging Support OS / Model _Capture Image (File Based 1 ) _Capture Image (Disk Based) _Deploy Image (File Based 1 ) _Deploy Image (Disk Based) _PXE Imaging 2 WES7 3 t610, t510, t5740e, t5570e, 6360t, mt40, 4320t WES09 t610, t510, t5740, t5570, gt7720 6360t 4, t5400 XPe t5740 HP ThinPro 4 t610, t510, t5745, t5565 HP ThinPro 3 (86) t5745, t5565, t5545, gt7725 5 HP ThinPro 3 (ARM) t5325 6 HP Smart Zero Core (86) t610, t510, t5565z HP Smart Zero Core (ARM) t410 t5335z Notes: 1 File Based Imaging is a new imaging method introduced for WES7 and WES09 since 4.4.3. The original imaging method in 4.4.2 and previous versions is Disk Based Imaging (dd method). 2 PXE imaging: Full image version checking is not available (e.g. XPe version 5.1.502 is compatible with BIOS version 786A1 but not with other BIOS). 3 Drivers will be missing when deploying a WES 7 image captured from a different HP thin client. For eample, an image captured from a t610 will not work if deployed to a t5570e. 4 PXE imaging task is not supported for mobile thin clients because boot order change tools are unavailable. 13
5 PXE imaging cannot work with the Agent in the HP ThinPro image due to some folder name changes. Please update the ThinPro Agent to the latest version (equal to or newer than 3.9.3665.4266) or the one in this release folder before you want to do PXE imaging. 6 PXE imaging task is not supported for T5325 because ARM does not support PXE boot. Preserved Settings during Imaging Source Device: The device from which the image will be captured. Target Device: The device to which the captured image will be deployed. Capture Image WES7: Since 4.4.3, for WES7, WES7E, and WES7P thin clients, the following settings and connections are preserved on both the source device and the captured image when capturing an image. These settings and connections will then be migrated when deploying the image to other devices. Settings Auto Logon setting IE Homepage setting Local User Accounts, including the Administrator account, default user account, and other accounts System Locale User Locale Input Locale UI Language Locale Time Zone Region Format Location Keyboard Layout Notification Area setting Taskbar setting Desktop Wallpaper setting Connections Citri ICA RDP TeemTalk In HPDM 4.4.2 and previous versions, there were two known issues: After capturing a WES7 image, the above settings and connections on the source device may be lost and reset to default settings. When cloning a WES7 image, the above settings could not be captured into the image. The settings are reset to the default setting when deploying this image to other devices. WES09: All settings from the source device are preserved on both the source device and the captured image ecept hostname, network settings, domain settings, and Write Filter status. Note: For WES7E, WES7P, and WES09, if the source thin client was joined to a domain prior to a capture image task, then domain membership will be lost after cloning the image. It is recommended to remove the source device from any domain prior to a capture image task. There is also a known issue where the group policy that controls the domain password compleity will affect local user accounts resulting in the user requirement to change the password to meet a more strict criteria. 14
ThinPro: All settings from the source device are preserved on both of the source device and the captured image ecept hostname and network settings. Deploy Image When deploying an image, the following settings on the target device will be preserved and restored after the image deployment. WES7/WES09: Writer Filter status Hostname Network Terminal Service License ThinPro: Hostname Network Checks before Imaging The following is the matri for what items are checked before imaging in different HP Device Manager versions ( means supported): Table 8: Checks before Imaging OS (HPDM Version) OS Type BIOS Family Flash Size Hardware Architecture WES (4.4 and before) Linu (4.4 and before) WES (4.4.1-4.4.2) Linu (4.4.1-4.4.2) WES (4.4.3 & 4.5 File Based Image) 1 WES (4.4.3 & 4.5 Disk Based image) Linu (4.4.3 & 4.5) Notes: 1 For File Based Image, check the Partition Size instead of Flash Size. 15
What s New in 4.5 Service Pack 1 This release includes the following enhancements: Adds support for the HP 4320t mobile thin client. Adds support to do imaging for the HP t410 thin client. Enhances template importing to allow import of templates created in previous HPDM versions including templates with payload: File & Registry, Imaging, PXE Imaging, Easy Tools Configuration, and Easy Tools Settings. Adds proy option for HP FTP Software Component Browser. Adds new task template to enable joining supported thin clients to a domain. Adds new task template to manage printer settings for ThinPro. Enhances copy file task to allow files with the same name to be captured from multiple devices to the Master Repository. Enhances VNC shadowing of WES thin clients by changing the security protocol from SSH to SSL and encrypting both forward and reverse shadow sessions. Enhances VNC shadowing of ThinPro thin clients by adding the SSL security protocol for encrypted communication. Issues Fied in 4.5 Service Pack 1 Fies an issue where the display settings for multiple monitors could not be correctly set on the t610 thin client. Fies an issue where a capture image task would halt due to a wrong sysprep_unattend.ml created when using WES7E Dutch image. Fies an issue where a deploy image task template created by user would show status as transferring indefinitely in the HP Device Manager 4.5 console and cannot be deleted. Known Issues The privilege of the Administrator account will change to User after cloning an image from the device if the administrator account has never been logged on and the administrator's password has been changed by Device Manager remotely. HPCE: OS has been found to intermittently freeze after reboot during the task processing for several tasks types. This has been found to occur with versions 6.02.625 and 6.05.655 of the HPCE thin client operating system, but it has not been found to occur with version 6.00.612.10. The probability of occurrence for this issue has been greatly reduced by postponing HP Device Manager Agent startup 30 seconds and disabling Easy Tools HPOBL and Deploy Service, but there is still the possibility that the issue can occur. Some FTP servers do not support Unicode. For this case, the users need to set the proper system language settings for all components to make the file name readable. Sometimes IIS will use the dynamic port "4XXXX" instead of the default FTP ports 20 and 21. So on HP XPe/WES, it will not be allowed to pass the Sygate firewall. If a localized character set other than English is used in DHCP tags such as grouping information, the information will be shown as unrecognizable codes on HPDM. If a localized character set other than English is used in LDAP, the information will be shown as unrecognizable codes on HPDM. Wake on LAN (WOL) tasks will fail on HP XPe\WES devices that are in a S3 power state (sleep): To allow this functionality, change the setting in the Power Management tab of the network adapter properties in the Device Manager of the thin client OS to enable "Allow this device to wake the computer", then commit changes and reboot. Please note that the display on the device will remain off until local input (keyboard\mouse) is received, but it can be pinged and otherwise managed. Also note that HPDM does not show indication of suspended devices. On Linu platforms, only the settings of network card eth0 can be set. If eth0 is disabled or does not eist, the task to apply network settings (change hostname and other network information) will fail. 16
When deploying device settings and configurations captured using HP Easy Tools, the target thin clients must have the EWF disabled and be logged on as Administrator. This is because HPDM calls the HP Easy Tools utility to apply the changes, and this is a requirement of HP Easy Tools. 17
License All the license information of open source software used in HPDM can be found in the HPDM installation directory at Doc\licenses. Portions of Device Manager are licensed under the terms of the GNU Public License, version 2, or the GNU Lesser Public License, version 2.1. Source code for these components may be found at ftp.hp.com/pub/device_manager or by contacting HP Support. For more information To read more about HP Device Manager, go to hp.com/go/hpdm 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 epress 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. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Intel and Pentium are trademarks of Intel Corporation in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates. 18 Created November 2013