Release Notes. Revision: ( ) Build Date: November 10, 2011

(1)

Release Notes

Software:

HP Device Manager

Revision:

4.4.1 (4.4.12793)

Build Date: November 10, 2011

Table of Contents

Introduction 2

Component Version Information 2

System Requirements 3 Management Console 3 Management Server 3 Management Gateway 4 Management Agent 4 Additional Requirements 5 Third-Party Software 5 Network Requirements 6 Ports 6 Installation Procedure 7

Console, Server and Gateway 7

Installation Language 10

Management Agent 11

Standalone Agent Installer 11

What’s New in Release 4.4.1 12

Issues Fixed in 4.4.1 12

Known Issues 12

(2)

Introduction

This document describes the development release of HP Device Manager 4.4, the next 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 four 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 Management Server. • Management Agent – Client side software required for managing devices.

For more detailed instructions on how to use HP Device Manager please refer to the User Manual.

Component Version Information

This release provides the following versions of these components (* are new versions since 4.4.12440): • Installer (HPDM.exe): 4.4.12793*

• Console and Server: 4.4.3610.12785* • Gateway for Windows: 4.4.3630.12293* • Agents

 HP WES7 & WES09 & XPe Agent Build: 4.4.3660.12652*  HP ThinPro (x86, ARM) Agent Build: 4.4.3665.12652*  HP ThinPro Zero (x86, ARM) Agent Build: 4.4.3667.12652*  HP Debian 4 Agent Build: 4.4.3661.12138  HP CE 5 & 6 Agent Build: 4.4.3662.12138  HP ThinConnect Agent Build: 4.4.3663.12138  HP Debian 3.1 Agent Build: 4.4.3664.12138  HP Blade OS (dc73) Agent Build: 4.2.3666.8689  Neoware NL4 Agent Build: 4.2.3640.8980  Neoware CE Agent Build: 4.2.3641.8980  Neoware XPe Agent Build: 4.2.3642.8980  Neoware NL3 Agent Build: 4.2.3643.8980  Maxspeed XPe Agent Build: 3.7.3650.2332  Maxspeed CE Agent Build: 3.7.3651.2332

(3)

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 (SP2) (32 & 64 bit) • Windows Server 2003 R2 (32 bit)

• Windows Server 2003 R2 (SP2) (64 bit) • Windows Server 2008 (SP2) (32 & 64 bit) • Windows Server 2008 R2 (64 bit)

• Windows XP Professional (SP3) (32 & 64 bit) • Windows 7 Pro (32 & 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

The Management Server should be installed on a single machine. The following environments is the minimal hardware and required software for running the Management Server:

Operating Systems:

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 2000 or later

(4)

Hardware:

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.

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:

Hardware:

• 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 & WES09 & WES7 • HP CE 5 & 6

• HP ThinPro • HP ThinPro Zero • HP ThinConnect • HP Linux Debian 4/3.1

(5)

• HP Blade OS • NeoLinux 3 • NeoLinux 4.0.1 • Neoware CE 8.1

• Neoware XPe 1.4.2 or later • Maxspeed CE

• Maxspeed XPe

Hardware:

• Thin-Client device supporting one of the above operating systems. • 2 MB free disk space

Supported Devices:

• HP XPe/WES09/WES7  t5740, t5740e, t5730, t5730w, t5720, t5630, t5630w, t5570, t5570e, t5400, gt7720, vc4820T, 6360t, 4410t, 4320t • HP CE  t5550, t5540, t5530, t5520 • HP ThinPro  t5745, t5735, t5565, t5545, t5325, t5145, gt7725 • HP ThinPro Zero  t5565z, t5335z • HP Linux Debian  t5735 • HP ThinConnect  t5145, t5135 • HP Blade PC  dc73

Additional Requirements

To support communication between the different components of the system the network must provide open access on certain ports. In addition to transfer large files between components, FTP servers must be accessible by the system. The following are additional requirements for running the management system:

Third-Party Software

• FTP Server – The following servers are recommended for use with HP Device Manager:  Microsoft Internet Information Server (IIS)

(6)

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).

Ports

The following tables list the standard and customer ports used by HP Device Manager:

Table 1: Standard Ports Required

Receiver

Port Sender Receiver Protocol Purpose

20 & 21 HPDM Console HPDM Server HPDM Gateway HPDM Agent

FTP Server (Third

Party Software) TCP The default port for FTP (used for HPDM Repository). Port 20 for data transfer and port 21 to listen to commands. FTP port can be configured on HPDM Console. 22 HPDM Console /HPDM Server /HPDM Gateway /HPDM Agent SFTP Server (Third

Party Software) TCP The default port for SFTP (used for HPDM Repository). SFTP port can be configured on HPDM Console. 22 OpenSSH Client (bundled with HPDM Console) OpenSSH Server (bundled with HPDM WES Agent)

TCP OpenSSH port for secure VNC connection (Only for WES Agent for now).

67 PXE Client (Thin Client side) HPDM Agent HPDM PXE Server (bundled with HPDM Gateway) DHCP Server

UDP PXE – Bootstrap.

68 HPDM PXE Server (bundled with HPDM Gateway) DHCP Server

PXE Client (Thin Client side) HPDM Agent

UDP PXE – Bootstrap.

69 PXE Client (Thin

Client side) HPDM PXE Server (bundled with HPDM Gateway)

UDP TFTP (Trivial File Transfer Protocol). 989 & 990 HPDM Console /HPDM Server /HPDM Gateway /HPDM Agent FTPS Server (Third

Party Software) TCP The default ports for FTPS (used for HPDM Repository). Port 989 for data transfer and port 990 to listen to commands. FTPS port can be configured on HPDM Console.

1099 HPDM Console HPDM Server TCP Console queries the RMI Registry. 4011 PXE Client (Thin

Client side) Proxy DHCP Service (Third Party Software)

UDP Proxy DHCP Service (It is an alternative to port 67 if port 67 is not available).

5500 VNC Server (Thin

Client side) VNC Viewer (bundled with HPDM Console)

TCP VNC Viewer in Listen Mode (Reverse VNC).

(7)

Receiver

5900 VNC Viewer (bundled with HPDM Console)

VNC Server (Thin

Client side) TCP VNC Server.

Table 2: Custom HPDM Ports Required

Receiver

40000 HPDM Server HPDM Agent

HPDM Gateway UDP Server/Agent polls Gateway. 40001 HPDM Gateway HPDM Agent TCP Gateway sends task to Agent 40002 HPDM Console HPDM Server TCP Console calls the remote objects

on Server by RMI. 40003 HPDM Server

HPDM Agent

HPDM Gateway TCP Server sends task to Gateway; Agent sends report to Gateway. 40005 HPDM Gateway HPDM Server TCP Gateway sends report to Server. 40006 HPDM Server PostgreSQL

(bundled) TCP The default database PostgreSQL listening port (the port is only needed when PostgreSQL is used).

40008 HPDM Gateway HPDM Gateway

Controller TCP Gateway notifies Gateway Controller there are other gateways running in the same subnet.

Installation Procedure

Console, Server and Gateway

The server-side components of the system are installed using the HP Device Manager installer (setup.exe). There are a number of options during the installation:

Complete: The Management Console, Server and Gateway will be installed with their default configurations. If you choose to install the Server you will be required to configure a database for it.

Custom: Select which components to install and specify the configuration of each one. • Console: Does not require any configuration.

• Server: The administrator can choose which database will be used for the Server. The optional databases are PostgreSQL and Microsoft SQL Server.

• Gateway: The administrator should configure DHCP settings and Gateway settings. The DHCP server is used by the PXE boot ROM to get an IP address as well as other basic networking information (subnet mask, default gateway, etc.).

(8)

Note 1:

HP Device Manager will create some necessary configuration and log files in installation folder. Please make sure you have the write permission of installation folder and its subfolders when you install and run HP Device Manager.

Note 2:

For Microsoft SQL Server users only: If you want to use Microsoft SQL Server with Windows Authentication mode to connect to database, please notice the following prerequisites:

1) You should have already set up the demanded Windows user account (Local Windows user or Windows domain user) as a valid Windows Authentication account in Microsoft SQL Server.

2) You’re running HPDM installer and DBSetup application as the demanded Windows user.

3) After installation is done and services are created, please manually change the HPDM Server Service’s account to the demanded Windows user

(Windows Start menu -> Control Panel -> Administrative Tools -> Services -> “HP Device Management Server Service” -> “Log on” tab -> Change “Log on as:” from “Local System account” to “This account:” and input the demanded Windows user name and password).

3) The demanded Windows user or Windows domain user should have the privilege to log on as a service.

Ignoring any of the above prerequisites may result in HPDM Server Service not able to start (Please check Microsoft Windows and Microsoft SQL Server Help to know more details about relative settings and knowledge).

Note 3:

For Microsoft SQL Server users only: If you uninstall Microsoft SQL Server which has earlier version of HPDM database and reinstall Microsoft SQL Server on the same installation path of uninstalled Microsoft SQL Server, please backup and remove the database directory files (like C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\) before reinstallation. Not removing the data files may result in HPDM not able to create database during database setup phase.

Silent: Silently install any combinations of Console, Server, and Gateway with command-line parameter combinations. Command line options can be specified when running the installer with the following format:

setup.exe /z"options"

Please note, the double quotation marks after /z are necessary. For Example:

HPDM.exe /z"--silent --language=en_US --component=CSG --destination=C:\Program Files\HP\HP Device Manager user=root password=secret serveraddr=192.168.1.2 --gatewayconfig=C:\Documents and Settings\Administrator\Desktop\Gateway.cfg"

(9)

A result log file “C:\hpdm-install.log” will be generated after silent installation, the user can check the log file if the installation is failed.

The following table lists the available command line options and their parameters:

Table 3: Silent Install Command Line Options

Command Line Option Default Parameter Description

--silent n/a This option runs the installer silently.

--component=[C][S][G] CSG This option determines which of

HPDM components will be installed. Use one or more of the following arguments with this option: C – Installs the Console S – Installs the Server G – Installs the Gateway --language=<language> en_US _{This option determines which}

language will be installed. Use one of the following arguments for the desired <language>:

zh_TW - Chinese (Taiwan) zh_CN - Chinese (Simplified) en_US - English (United States) fr_FR - French (France) de_DE - German (Germany) ja_JP - Japanese (Japan) ko_KR - Korean (Korea) es_ES - Spanish (International) --destination=<path> “C:\Program

Files\HP\HP Device Manager”.

This option determines the

destination installation path of HPDM. --user=<username> root This option determines the HPDM

administrator account name. This option is only applicable and is required if the Server component is being installed.

--password=<password> n/a This option determines the HPDM administrator account password. The parameter value for the <password> must be provided. This option is only applicable and is required if the Server component is being installed. --serveraddr=<address> n/a This option determines the IP address

of HPDM Server. This option is only applicable and is required if the Console component is being installed. The IP address must be provided as the <address> parameter.

(10)

Command Line Option Default Parameter Description

--gatewayconfig=<filespec> n/a This option determines the path of the predefined Gateway configuration file. Please note the <filespec> parameter provided must be an absolute path. For example, you cannot set

--gatewayconfig=.\gateway.cfg you must set

--gatewayconfig=C:\Program Files\gateway.cfg.

This option is only applicable and is required if the Gateway component is being installed.

Installation Language

By default, the installer is launched in the target system’s language. For example, if the target system’s language is German, the installer’s UI language is German automatically.

If the user wants to launch installer in a different language from the target system’s language, they can specify a language identifier when launch the installer as below:

setup.exe –l<Language ID>

For example, to launch installer in German:

setup.exe -l0x0407

The following table lists the available language IDs:

Table 4: Silent Install Command Line Options

Language ID Language Name

0x0804 Chinese (Simplified)

0x0404 Chinese (Traditional)

0x0409 English (United States)

0x040c French (France)

0x0407 German (Germany)

0x0411 Japanese (Japan)

0x0412 Korean (Korea)

(11)

Note:

The user can specify the language for HPDM UI language which is different from the installer’s UI language. For example, the installer is launched in German, and the user can specify Simplified Chinese as HPDM UI language. The HPDM language setting is present in Installation Configuration Wizard on 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.

Standalone Agent Installer

The Agents for some platforms can be installed using the standalone Agent Installer. There are some important notices for specific Agent Installer:

• HP WES/XPe:

 Please log on with Administrator account to install Agent.

 Make sure you have disabled Write Filter before installation, or commit Write Filter after installation if Write Filter is enabled.

 You can select to upgrade Agent if a previous version of Agent has been installed, however, you cannot roll back to the previous version if upgrade is done.

 There might be a dialog to ask you to input the Administrator credentials to finish the installation when rebooting after installation. (If Write Filter is enabled, please commit again.)  Symantec Endpoint Protection Agent needs to be running when installing HPDM Agent. Silent: Silently install the Agent with the command-line option --silent. This command line option can be specified when running the installer with the following format:

HPDMAgent_HPXPe.exe /z"options"

Please note, the double quotation marks after /z are necessary. For Example:

HPDMAgent_HPXPe.exe /z"--silent"

A result log file “C:\ hpdmagent-install.log” will be generated after silent installation, the user can check the log file if the installation is failed.

The installer is launched in the target system’s language. For example, if the target system’s language is German, the installer’s UI language is German automatically.

(12)

What’s New in Release 4.4.1

This release includes the following enhancements: • Adds support for the following OS Refreshes:

 Windows Embedded Standard 7 Fall 2011 Refresh  Windows Embedded Standard 2009 Fall 2011 Refresh  HP ThinPro 3.3 Fall 2011 Refresh

• Adds support for the following hardware:  Support Adrenaline

• Enhances the option to import and deploy OS images captured using HP Easy Tools to include images captured from the Windows Embedded Standard 7 Fall 2011 Refresh.

• Enhances Task Deferment

 Reverses the direction of the client side progress bar to make it more intuitive.  Changes the client side control for postpone time from a drop down box to a slider.  Adds a new task template to configure the task deferment settings on thin clients.  Adds a new option in the Configuration Management dialog of the console to globally

enable or disable task deferment.

• Enables cross OS imaging by simplifying the imaging tool logic checks.

Issues Fixed in 4.4.1

• Fixes an issue where ThinPro Desktop icons do not get cloned with session.

• Fixes an issue where the CTRL+ALT+DEL key combination is required on Windows Embedded Standard thin clients when cloning devices which are joined to a domain.

• Fixes an issue where some users from imported AD group could not log in to HPDM console. • Fixes an issue where the wrong HPDM agent version is reported in ThinPro System Information/Software

information.

• Fixes an issue where imaging tasks would fail if the ftp repository user account password contained the ‘@’ character.

Known Issues

• 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 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 still occur.

• 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).

• 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.

(13)

• PXEless imaging task does not work with image T3X31012 on T5145 because there is not enough space on the flash, only PXE imaging task is support for this platform.

• PXE imaging task is not supported for mobile thin clients (except the 6720t) because boot order change tools are unavailable.

• PXE imaging task is not supported for T5325 because ARM does not support PXE boot. • Some FTP Servers do not support Unicode. For this case, the users need to set proper system

language settings for all components to let the file name readable.

• Sometimes IIS will use the dynamic port "4XXXX" instead of the default ftp port 20, 21. So on HP XPe/WES, it will not be allowed to pass the Sygate firewall.

• If 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 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 to 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 display on device will remain off until local input (keyboard\mouse) received but can ping and other wise manage device. Also note that HPDM does not show indication of suspended devices. • In Linux platforms, only the settings of network card eth0 can be set. If eth0 is disabled or does

not exist, the task to apply network settings (change hostname and other network information) will fail.

• When deploying device settings and configurations captured using HP Easy Tools, the target thin client(s) 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.

(14)

License

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://ftp.hp.com/pub/device_manager or by contacting HP Support.

© Copyright 2011 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.