Internal HPDM Repository for External Clients

ManualsBrandsHP ManualsDesktopsHP t520 Flexible Thin Client

Best Practices Whitepaper

Internal HPDM Repository for

External Clients

Table of contents

Introduction .............................................................................................................................................................................. 2

Overview .................................................................................................................................................................................... 3

Prework ..................................................................................................................................................................................... 4

Configuring HPDM Repository Server .................................................................................................................................... 6

Infrastructure Firewall Rules .................................................................................................................................................. 9

This guide was developed around HP Device Manager V5.0.3 but the concepts and configuration can be applied to previous

versions back to HP Device Manager back to V4.7 SP10.

Summary of content (9 pages)

PAGE 1
Best Practices Whitepaper Internal HPDM Repository for External Clients Table of contents Introduction ..............................................................................................................................................................................2 Overview....................................................................................................................................................................................3 Prework .................................
PAGE 2
Introduction To configure a HP Device Manager Repository to service Thin Clients that are separated by a NAT firewall takes some behind the scenes magic. The HPDM Server and the HPDM Repository are separate pieces of HPDM infrastructure. In the scenario where all components are installed together, the MRC and Console refers to the same hosts file. The MRC and Console need to “see” the HPDM Repository using the same name as external clients use to access the HPDM Repository.
PAGE 3
Overview For this document, the HPDM Server Service, HPDM Gateway Service and HPDM Master Repository Service are all installed on a single Windows® Server. While the concepts are transferable, multi-server configurations are beyond the scope of this document. Figure 1 below represents the end state of a HPDM environment configured to support external or Internet Connected thin clients. Figure 1. HPDM Traffic Diagram HPDM G/way HPDM Repos Sign up for updates hp.
PAGE 4
Prework One commonly used option is to change the HPDM Repository HTTPS access port from the default of 443 to 8443. This frees up port 443 to be used by the HPDM Console Web Bridge which makes access to the HPDM Web Console via a web browser simpler. Note: The port 8443 has been chosen for this example but a different port could be chosen to suit the customer requirements. Figure 2.
PAGE 5
Once HPDM Web Console has been changed to use port 443, it is possible to logon to HPDM Web Console using as browser without specifying a port as per Figure 4 below. Figure 4. HPDM Web Console Logon Page Sign up for updates hp.
PAGE 6
Configuring HPDM Repository Server 1. Test the Internet resolvable FQDN name of your HPDM Repository Server. If the FQDN cannot be resolved, you cannot use it. Figure 5 below shows “hpdm2.australiasoutheast.cloudapp.azure.com” as an internet resolvable FQDN of the HPDM Repository Server. In this example, it is also the HPDM Server. Figure 5. Checking External HPDM Repository Name to IP Address 2. Update the Hosts file (c:\Windows\Sysem32\Drivers\etc\hosts) on the MRC and console.
PAGE 7
3. Using the HPDM Console, update the HPDM Master Repository configuration to replace the IP address of the internal HPDM Repository Server with the Internet resolvable name of the HPDM Repository Server. The name must be the Fully Qualified Domain Name, not just the hostname. Figure 7. Repository Configuration Server Address 4. The only HPDM Repository Server file transport protocol required to service external thin clients is HTTPS.
PAGE 8
5. Ensure the HTTPS Protocol Settings are configured for the previously chosen port number (Figure 2). Also check the HPDM Repository Server URL is the Internet resolvable FQDN of HPDM Repository Server (Figure 5). Figure 9. Repository Configuration HTTPS Port 6. Ensure the test of the HPDM Repository is successful. If the test is unsuccessful, go back and check all steps above. Also check server firewall is configured to allow the HTTPS port.
PAGE 9
Infrastructure Firewall Rules To support the HPDM configuration described in this document, there are a few firewall and NAT rules required to allow traffic to pass between internal server infrastructure and external placed thin clients. 1. Port 40001 - Outbound - HPDM Gateway Server to the internet 2. Port 40003 – Inbound Firewall and NAT – Internet based thin clients to the HPDM Gateway Server 3. Port 8443 – Inbound Firewall and NAT – Internet based thin clients to the HPDM Repository Server.