HP Device Manager 4.6 - Deployment Guide

Appendix
Use cases
HPDM is used by thousands of customers throughout the world in deployments ranging in size from 30 units to 50,000
units. HPDM is modular, which allows customers to structure HPDM to fit into their existing corporate network architecture.
Like any tool, the components of HPDM can be optimally configured to make the best use of system and network
performance. The use of multiple HPDM Servers is highly recommended to ensure fast testing, validation, and delivery in
production environments. HPDM allows you to easily export and import created templates from one system to another to
reduce the burden of using multiple HPDM Servers. Strategically place the HPDM Gateways and repositories, based on
existing network architecture, to maximize the use of LAN traffic versus WAN traffic. HPDM is included in the cost of HP thin
clients, so there is no additional cost or limitation on using multiple installations.
Customer 1
Industy: US retail
Units managed: 50,000 HP ThinPro
Environment: 1 HPDM Server, MS-SQL Database, 10 HPDM Gateways (regional), 1 repository per store (500+)
Usage: Asset management, patch deployment, and distribured administration—entire Help Desk (300+ admins) run
through HPDM.
Customer 2
Industy: Global telecom
Units Managed: 45,000 WES, Windows CE, and HP ThinPro
Environment: 1 HPDM Server, MS-SQL Database, 13 HPDM Gateways, 13 repositories
Usage: Asset management, patch deployment, imaging and OS updates, reporting, automation and distributed
administration.
Customer 3
Industy: Global banking
Units Managed: 15,000 WES
Environment: 5 HPDM Servers (one per country), MS-SQL Database, 5 HPDM Gateways, 5 repositories
Usage: Asset management, patch deployment, imaging and OS updates, reporting, automation and distributed
administration. The customer creates and tests templates in the US instance. After it is validated, the template with
payload is exported from the local HPDM Server and sent to remote HPDM installations. The local HPDM adminstrator
receives the template, validates it on the local test HPDM Server, and then imports it into local production for the HPDM
Server to use.
Performance testing data
HPDM 4.6 is performance optimized and was subjected to performance testing. The testing results are based on 50,000
units with a single HPDM Server, single HPDM Gateway, and database is MS SQL Server 2008. All components are distributed
in different machines.
Table 1. Testing environment
13