Release Notes

HP Device Manager 5.0

Release (5.0.5.38754)
Build Date: October 28, 2020

Table of contents
Overview .................................................................................................................................................................................2
Component version information .........................................................................................................................................3
Third-party software version information .........................................................................................................................3
New features in HPDM 5.0.5 ................................................................................................................................................4
Issues fixed in HPDM 5.0.5 ...................................................................................................................................................4
Known issues .........................................................................................................................................................................4
System requirements ...........................................................................................................................................................6
HPDM Server requirements .............................................................................................................................................6
HPDM Gateway requirements .........................................................................................................................................6
HPDM Master Repository Controller requirements ......................................................................................................6
HPDM HTTPS Repository requirements .........................................................................................................................6
HPDM Console requirements...........................................................................................................................................7
HPDM Console Web Bridge requirements .....................................................................................................................7
HPDM Configuration Center requirements ....................................................................................................................7
HPDM Agent requirements ..............................................................................................................................................8
Network requirements .....................................................................................................................................................8
Port requirements.............................................................................................................................................................9
Installation procedure ....................................................................................................................................................... 10
HPDM Agent .................................................................................................................................................................... 10
Imaging notes ..................................................................................................................................................................... 11
Imaging support matrix ................................................................................................................................................. 11
Preserved settings during imaging .............................................................................................................................. 11
Checks before imaging .................................................................................................................................................. 11
License ................................................................................................................................................................................. 12
For more information ........................................................................................................................................................ 12
 Overview
This document describes the release of HP Device Manager 5.0.5.

HP Device Manager (HPDM) is an enterprise-class application for managing and administrating thin client devices on large-
and small-scale networks. The system consists of the following major components:

• HPDM Server—The central management service, which monitors all state and controls all device management activities.
• HPDM Gateway—The software component that links the HPDM Server and HPDM Agents on each thin client.
• HPDM Master Repository Controller—The software component that manages the software payloads and package
content in the Master Repository and synchronizes that content to other child repositories as requested by the HPDM
Server.
• HPDM HTTPS Repository—The software component that provides the ability to set up an HPDM repository using the
HTTPS protocol.
• HPDM Console—The software component that is the primary GUI for administrators, allowing the inventory and
management of devices and other administrative activities.
• HPDM Console Web Bridge— This component provides access to HPDM Console content through a web browser.

• HPDM Configuration Center—The graphical application used to configure settings of various HPDM components.
• HPDM Agent—The software component installed on each device to enable device management capabilities.

For more detailed instructions on how to use HP Device Manager, see the HP Device Manager Administrator Guide.

2
Component version information
This release provides the following versions of these components (* are new versions since HPDM 5.0.4, build revision
5.0.4.38693):

Component Version

HPDM installer 5.0.5.38754*

HPDM Server Installer 5.0.3620.38748*

HPDM Gateway for Windows® Installer 5.0.3630.38524

HPDM Master Repository Controller Installer 5.0.3680.38754*

HPDM HTTPS Repository Installer 5.0.3690.38662

HPDM Console Installer 5.0.3610.38748*

HPDM Console Web Bridge Installer 5.0.3700.38626

HPDM Configuration Center Installer 5.0.3710.38480

HPDM Agent
• Windows 10 IoT Enterprise (64-bit) 5.0.3669.38740*
• Windows Embedded Standard 7P (64-bit) 5.0.3669.38740*
• Windows Embedded Standard 7E (32-bit) 5.0.3660.38740*
• HP PC Converter for Windows (64-bit) 5.0.3673.38740*
• HP PC Converter for Windows (32-bit) 5.0.3672.38740*
• HP ThinPro 7 5.0.3674.38740*
• HP ThinPro 6 5.0.3671.38740*
• HP ThinPro 5 5.0.3670.38740*

Third-party software version information

This release includes the following versions of third-party software:

Component Version

Apache HTTP Server 2.4.46

PHP 7.3.22

OpenSSL 1.1.1h

OpenJDK 11.0.8

PostgreSQL 10.4.1

3
 New features in HPDM 5.0.5

Issues fixed in HPDM 5.0.5

• Fixed an issue where the memory of ThinPro would be used up by repeatedly created dmscheduler and
dmupdatemanager processes
• Fixed an issue where HPDM Server might not start when upgrading from HPDM 4.7.x to HPDM 5.0.4 with PostgreSQL
• Fixed an issue where PostgreSQL database failed to restore when upgrading from 4.7.x
• Fixed an issue where AD user cannot logon Console after upgrading from 4.7.x until the local admin get key from AD
server again
• Fixed an issue where imaging tasks would be stuck on 33% on Window 10 IoT image with certain KBs installed

Known issues
• In HPDM Configuration Center, some components show old version as they are not changed since last release.
• After upgrading the HPDM Console on HP Device Manager server, the HPDM Console will fail to launch with and error
“Failed to create/update rmiclient.jks. Please use “Run as Administrator” to start the HPDM Console. To rectify this
issue, Right Click on the “HP Device Manager Console” desktop shortcut and select “Run as Administrator”. This
operation is required only once. This issue will be rectified in a future release.
• After upgrading the HPDM Console on a remote workstation, the console connection will fail with a “Certificate Error”. To
rectify the issue, copy the file “rmiclient.jks” from “..\HP\HP Device Manager\Server\bin” folder on the HPDM Server to
the to the folder “..\HP\HP Device Manager\Console\lib” on the console workstation. This issue will be rectified in a
future release.
• PXE imaging can fail when BIOS option "Host Based MAC Address" is not set to "Disabled". This has been observed on
mt46 and mt32. To resolve this, set the BIOS option "Host Based MAC Address" to "Disabled".
• If you apply region settings with an unsupported value, the task will not fail, but the region list will be empty at device side
(on Windows RS5), or it will choose the first one in the region list (on Windows RS1). Clone region settings will return
the unsupported value. Re-applying region settings with a supported value can fix the problem.
• If a task requires payload is running via the batch control, devices of later batches may execute new incoming immediate
tasks before the currently waiting task. In the case that tasks are independent of each other, the execution results are
not affected. For tasks with dependencies, use a Template Sequence to ensure the order.
• The Deploy File template cannot be created successfully when the file name has Unicode characters.
• The UTF-8 characters returned by scripts of PowerShell version 5.0 or below in task logs or device properties dialog
cannot be displayed correctly.
• The listening TigerVNC Viewer occasionally does not pop up windows when HPDM Agent connects to it via Reverse
Shadow task.
• Occasionally an error dialog displays when opening the _Manage dynamic properties template while HPDM Server is
busy running _Get Asset task reports. The error dialog does not block any processing and can be ignored.
• On HP ThinPro 7.1, after applying screensaver settings via _Apply Settings, the profile captured from the device cannot
be deployed. Also, the profile cannot be restored after imaging, even if the Retain Profile option is enabled. As an
interim solution, HP provides a File & Registry template and instructions to allow the device profile to be retained.
• Due to the HP ThinPro 5.2 OpenSSL limitation, HPDM Agent for HP ThinPro 5.2 does not support TLS1.2. However, HPDM
Gateway enables TLS1.2 for TLS connection by default. To manage HPDM Agent for HP ThinPro 5.2, enable the
SSL/TLS 1.0 Support option for HPDM Gateway. You can find this option in HPDM Configuration Center, under the
Advanced Options of the HPDM Gateway page.
• HP ThinPro 7.1 introduces a new dynamic display management architecture that does not support remote editing of the
display settings configuration of a device.
• Due to a security exposure, HPDM fails to capture or deploy files via the HTTPS protocol on HP ThinPro 5.x. HPDM
automatically disables support for TLSv1.0 and TLSv1.1 connections to the HPDM HTTPS repository and requires the
use of TLS 1.2 or greater; however, HP ThinPro 5.x does not support TLS protocol 1.2 or greater. To capture or deploy
files over HTTPS on HP ThinPro 5.x, modify the configuration of the HPDM HTTPS repository to enable TLS 1.0 support.
• The image file cannot be imported successfully by HTTPS protocol when the file size is greater than the free space size of
the volume that HPDM HTTPS Repository is installed on and the repository is located on another volume that has
enough free space.

4
• Capture Image does not support resume upload. Capture Image might fail due to customer network stability issues and
because the FTPS agent transfer protocol does not support TLS session resumption on data connections. If you are
using FTP servers that does support this, disable this option. For example, on a FileZilla Server, select General
settings, select FTP over TLS settings, and then be sure the Require TLS session resumption on data connection
when using PROT P checkbox is cleared.
• Enabling the Universal Write Filter (UWF) task returns a false success when the UWF module is not installed on the device
side. If the original write filter status is disabled, the HP Write Filter is enabled. If the original write filter status is set to
HP Write Filter enabled, this task does not change the write filter status.
• Remotely installing Windows Security Updates can fail without logging the reason because Microsoft did not include all
explanations for silent installation failure in a standard output form.
• Using HTTPS to deploy an HP ThinPro 5.2 image is not supported, although using HTTPS to capture an HP ThinPro 5.2
image is supported.
• When capturing or deploying images on the HP mt42 mobile thin client, a fatal system error might occur after the
imaging process, resulting in a blue error screen being displayed. The error does not impact the imaging process, and
the system restarts automatically, clearing the error.
• If an HPDM repository is configured to use HTTPS only, and an Update Agent task or Deploy Files subtask (in a File and
Registry task) using that repository is sent to a device that has HPDM Agent version 4.7 SP2 or older, the task is falsely
reported as successful. The workaround is to update the device’s HPDM Agent using a different protocol before
sending it any tasks that uses HTTPS.
• Cached-image capture over wireless networking is not supported for HP ThinPro 5.2, HP ThinPro 6, or HP ThinPro 7. You
must use a wired connection to prepare and capture the image.
• The content of customized File and Registry templates is removed from repositories if the Deploy Files subtask is
removed from the customized template while sending a task that relies on the customized template. This issue can be
avoided by not modifying template content while sending tasks.
• Devices might disappear from the device table during task execution. The devices can be displayed again by refreshing
the device table or switching to another device folder and then reverting to the original view.
• The Deploy Profile task does not finish when the profile has a large file attached.
• The privileges of an administrator account for a Windows Embedded Standard 7 image change to the same privileges of a
user account after capturing an image, if the administrator account has never been logged in and the administrator
password has been remotely changed via HPDM.
• Some FTP servers do not support Unicode. In this case, you must set the proper system language settings for all
components to ensure file names on these FTP servers readable.
• If a localized character other than UTF-Latin-1(Western Europe) is used in DHCP tags, such as grouping information, the
information is shown as unrecognizable characters in HPDM.
• If a localized character set other than UTF-Latin-1(Western Europe) is used in LDAP, the information is shown as
unrecognizable characters in HPDM.
• On HP ThinPro devices, network settings can be set only for network card eth0. If eth0 is disabled or does not exist, the
task to apply network settings (such as changing the hostname and other network information) fails.
• When deploying device settings and configurations captured using HP Easy Tools, the target devices must have EWF
disabled and be signed in as an administrator. This is because HPDM calls HP Easy Tools to apply the changes (a
requirement of HP Easy Tools).

5
 System requirements
HPDM Server requirements
Component Requirements

Operating system Windows Server 2012 R2

Windows Server 2016
Windows Server 2019

Third-party software OpenJDK (bundled with installer)

One of the following database management systems (DBMS):
Microsoft® SQL Server 2016 or later
PostgreSQL (bundled with installer)

Hardware Intel® compatible 64-bit processor supporting 2 or more CPU cores

1 GB RAM
2 GB free disk space

HPDM Gateway requirements

Component Requirements

Operating system Windows Server 2012 R2

Windows Server 2016
Windows Server 2019

Hardware Intel® compatible 64-bit processor supporting 2 or more CPU cores

1 GB RAM
2 GB free disk space

HPDM Master Repository Controller requirements

Component Requirements

Operating system Windows Server 2012 R2

Windows Server 2016
Windows Server 2019

Hardware Intel® compatible 64-bit processor supporting 2 or more CPU cores

1GB RAM
4 GB free disk space
NOTE: The above hardware is the minimum required for the Master Repository. If there will be
a large number of imaging or file-copying operations, then HP recommends using a more
powerful system with additional free disk space.

Protocol HTTPS, FTP, FTPS, SFTP, or SMB

Recommended third-party Apache HTTP Server (An embedded version of Apache HTTP Server is bundled with the
FTP servers installer.)
FileZilla
Microsoft Internet Information Server (IIS)
freeSSHd

HPDM HTTPS Repository requirements

Component Requirements

Operating system Windows Server 2012 R2

Windows Server 2016
Windows Server 2019

Hardware Intel® compatible 64-bit processor supporting 2 or more CPU cores

6
 2 GB RAM
2 GB free disk space
7200 RPM disk
NOTE: The above hardware is the minimum required for HPDM Embedded HTTPS Server. If
there will be a large number of imaging or file transfer-operations, then HP recommends using
a more powerful system with additional free disk space.

Protocol HTTPS

HPDM Console requirements

Component Requirements

Operating system Windows Server 2012 R2

Windows Server 2016
Windows Server 2019
Windows 10

Third-party software OpenJDK (bundled with installer)

Hardware Intel® compatible 64-bit processor supporting 2 or more CPU cores

1 GB RAM
1 GB free disk space

HPDM Console Web Bridge requirements

Component Requirements

Operating system Windows Server 2012 R2

Windows Server 2016
Windows Server 2019

Hardware Intel® compatible 64-bit processor supporting 2 or more CPU cores

1 GB RAM
2 GB free disk space

HPDM Configuration Center requirements

Component Requirements

Operating system Windows Server 2012 R2

Windows Server 2016
Windows Server 2019
Windows 10

Hardware Intel® compatible 64-bit processor supporting 2 or more CPU cores

2 GB RAM (For 1 Console instance and Console Web Bridge server. Add 1 GB for each additional
Console)
1 GB free disk space

7
 HPDM Agent requirements
HPDM provides full support for all HP thin clients within EOL (end-of-life) + 3 years and partial support for all HP thin clients
within EOL + 5 years. Each thin client should have a minimum of 10 MB of free disk space.
In the following matrix, full support (F) indicates that all existing and new features in HPDM 5.0 are supported. Partial
support (P) indicates that not all task templates are available for a given device platform and operating system.

Windows Embedded Standard 7P (64-bit)

Windows Embedded Standard 7E (32-bit)

Windows 10 IoT Enterprise (64-bit)

HP ThinPro 7

HP ThinPro 6

HP ThinPro 5
Thin client model

t740 F F
t730 F F F P P
t640 F F
t638 F F
t630 F F F P
t628 F F F P
t620/t620 PLUS F F F F P P
t540 F F
t530 F F F P
t520 F F F F P P
t430 F F P
t420 F F P P
t240 F
mt46 F F
mt45 F F
mt44 F
mt43 F
mt42 F F
mt32 F F
mt31 F F
mt22 F F
mt21 F F P
mt20 F F P
HP ThinPro PC Converter P
HP PC Converter for Windows P

Network requirements
Component Requirements

Network HPDM supports only IPv4 networks.

HPDM can image thin clients using either PXE or non-PXE (preferred) methods. If PXE imaging
is desired, make sure that there are no other PXE services running on the network.
If you are using an ISC DHCP server, it must be running at least version 3.0.

8
Port requirements
See the HP Device Manager Administrator Guide – Port Usage section for a list of standard and custom ports required.

9
 Installation procedure
Each HPDM minor release is cumulative and includes the latest updates, as well as all updates from any earlier minor
releases. For example, you only need to install HPDM 5.0.3 to get the full functions of HPDM 5.0, and all updates of 5.0 SP1
and 5.0 SP2.
The HPDM 5.0 minor release installer supports direct installation. You do not have to first install the base version of HPDM
5.0.
The HPDM 5.0 minor release installer can upgrade HPDM 4.7 or an HPDM 4.7 service pack.
To install HPDM, double-click the setup file and follow the on-screen instructions. See the HP Device Manager Administrator
Guide for more details about the installation and upgrade.

HPDM Agent
HP thin clients will ship with an HPDM Agent preinstalled. To update HPDM Agent, from HPDM Console, send an Update
Agent task to all thin clients.

10
Imaging notes
Imaging support matrix
The following matrix shows which operating systems and HP thin clients are supported for each imaging method.

File-based Disk-based File-based Disk-based

PXE deployment
Operating system capture capture deployment deployment
and thin client models

Windows* √ √ √

HP ThinPro √ √ √
* Drivers will be missing when deploying a Windows image captured from a different HP thin client.

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
Operating system Preserved settings
Windows All settings from the source device are preserved on both the source device and the captured
image except hostname, network settings, domain settings, and Write Filter status.

HP ThinPro All settings in ThinPro profile (so for 7.1 no display settings) from the source device are
preserved on both the source device and the captured image, except hostname and network
settings.
Note: For Windows operating systems, 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 this
task. 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 more strict criteria.

_Deploy Image
Operating system Preserved settings
Windows • Write filter status
• Hostname
• Network settings
• Terminal Service license
• Windows activation license (select operating systems only)
HP ThinPro • Hostname
• Network settings

Checks before imaging

The following matrix describes which items are checked before imaging.

BIOS family Flash size Hardware architecture

Operating system type
Windows √ √

HP ThinPro √ √

11
 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 HPDM 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 http://www.hp.com/go/hpdm.

Sign up for updates

hp.com/go/getupdated

© Copyright 2016-2017， HP Development Company, L.P.

ARM is a registered trademark of ARM Limited. Java is a registered trademark of Oracle and/or its affiliates. Linux® is the registered trademark of Linus
Torvalds in the U.S. and other countries. Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries. Pentium is a trademark of Intel Corporation in the U.S. and other countries.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's
standard commercial license.

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.