HP Device Manager 4.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Pentium is a trademark of Intel Corporation in the U.S. and other countries. Microsoft and Windows are U.S. registered trademarks of the Microsoft group of companies. Java is a registered trademark of Oracle and/or its affiliates. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.
Table of contents 1 Introduction ....................................................................................................................................................... 1 What is HP Device Manager? .............................................................................................................. 1 Overview .............................................................................................................................................. 2 HPDM Console ..................
Automatic registration (PCoIP zero clients) ........................................................................................ 19 Using a DNS service record .............................................................................................. 19 Using a DHCP vendor class option ................................................................................... 19 Searching for devices .............................................................................................................
Adding a new rule .............................................................................................................. 33 5 Device management ....................................................................................................................................... 34 Viewing devices .................................................................................................................................. 34 Deleting devices ......................................................
Deploying connections ....................................................................................................... 47 Updating firmware .............................................................................................................. 47 6 Imaging operations ......................................................................................................................................... 48 Imaging support matrix ..................................................................
8 Security management ..................................................................................................................................... 60 User management .............................................................................................................................. 60 Adding users ...................................................................................................................... 60 Deleting users .........................................................
12 HPDM Server Backup and Restore Tool ...................................................................................................... 74 Backing up the HPDM Server ............................................................................................................ 75 Restoring the HPDM Server ............................................................................................................... 75 13 HPDM Port Check Tool ...............................................................
1 Introduction What is HP Device Manager? HP Device Manager (HPDM) is a server-based application that provides powerful centralized administration capabilities for thin client devices running HP software.
Overview HPDM is structured as a Console–Server–Gateway system. Figure 1-1 HPDM overview NOTE: The deployment of the HPDM system is very flexible. See the deployment white paper at ftp://ftp.hp.com/pub/hpdm/Documentation/WhitePapers/ for more details.
HPDM Console The HPDM Console is the user interface of HPDM and can be installed on any number of machines. Several HPDM Consoles can interact with an HPDM Server. The HPDM Console allows system administrators to do the following: ● View details for each controlled device ● Organize device trees ● Create and maintain remote job definitions ● Monitor tasks sent out to devices HPDM Server The HPDM Server controls HPDM Agents through the HPDM Gateway.
Repositories Repositories are where task payload files are stored. HPDM Agents download files from or upload files to repositories according to tasks from the HPDM Server. These files can include but are not limited to the following: ● Device images ● Imaging tools ● HPDM Gateway and HPDM Agent files ● Software components (add-ons) The components of the repository system are as follows: ● Master Repository—Holds all payload files. There can only be one Master Repository in the system.
Terms and definitions Table 1-1 Terms and definitions Term Definition Device A device refers to a device managed by HPDM, such as a thin client. Package A package is comprised of a description file and a folder that contains payload files. The package name is identical to the folder name, which can be any legal string. The name of the description file follows the convention PackageNameChecksumString.desc.
2 Getting started with HPDM This chapter discusses the following topics: 6 ● System requirements ● Installing HPDM ● Using the HPDM Console ● Discovering device systems ● Displaying device properties ● Keeping the HPDM Agent updated on device systems Chapter 2 Getting started with HPDM
System requirements The following sections describe the minimum system requirements for HPDM.
HPDM Console requirements Table 2-3 HPDM Console requirements Component Requirements Operating system Windows Server 2003 with Service Pack 2 (64-bit) Windows Server 2003 R2 with Service Pack 2 (32- and 64-bit) Windows Server 2008 with Service Pack 2 (32-bit) Windows Server 2008 R2 with Service Pack 1 (64-bit) Windows Server 2012 (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 Environment version 6 update
HPDM Agent requirements HPDM provides full support to all HP thin clients within EOL + 3 years and partial support to all other HP thin clients. See the following table for support coverage. The following matrix shows the device types and operating systems that are supported in HPDM 4.6. Full support (F) means that all existing and new features in HPDM 4.6 are supported. Partial support (P) means that all existing and new features except settings and connections are supported.
Device type Win XPe WES 2009 t5740e WES 7E (32-bit) WES 7P (32-bit) WES 8 (64-bit) Win CE 6.0 F F F HP Smart Zero Core F F F F F t620 F F F F F t820 F F F NOTE: Client devices should have a minimum of 10 MB of free disk space.
Master Repository Controller requirements Table 2-4 Master Repository Controller requirements Component Requirements Operating system Windows Server 2003 R2 with Service Pack 2 (64-bit) Windows Server 2008 R2 with Service Pack 1 (64-bit) Windows Server 2012 (64-bit) Hardware Pentium III or greater 512 MB RAM 2 GB free disk space NOTE: The above hardware is the minimum required for the Master Repository.
Installing HPDM To install HPDM: ▲ Run the HPDM InstallShield Wizard and follow the on-screen instructions. NOTE: If a previous version of an HPDM component is already installed on the local computer, the installation program will detect it and attempt to perform an update. See the installation white paper at ftp://ftp.hp.com/pub/hpdm/Documentation/WhitePapers/ for more details.
Installing an HPDM 4.6 Service Pack An HPDM 4.6 Service Pack can only be installed onto a system that has an HPDM 4.6 base installation or a previous version of an HPDM 4.6 Service Pack. If there is only one component (for example, the HPDM Console) of HPDM installed on a system, then an HPDM 4.6 Service Pack will only update the installed component. An HPDM Service Pack is cumulative. Each Service Pack includes the latest updates, as well as all of the updates from any earlier Service Packs.
Operating system tabs Each of the operating system tabs produces the following view: Figure 2-2 HPDM Console—Operating system tabs 1 Operating system tabs—These tabs group devices by operating system. Only the tabs for the operating systems currently managed by HPDM will appear.
HPDM Gateway tab Clicking the HPDM Gateway tab will display information specific to the currently selected HPDM Gateway.
Displaying device properties HPDM stores asset information about each device it manages. When a device registers with the HPDM Server, it passes just enough basic asset information so that it can be uniquely identified and HPDM can communicate with it. You can both view and export this information. Basic asset information To display a device’s basic asset information: ▲ Double-click a device in the device pane to open the Device Properties window.
Table 2-7 Basic asset information (Agent) (continued) Agent Pull Interval Indicates how often the HPDM Agent attempts to pull tasks from the HPDM Gateway. First Contact Time The date and time when the device registered with HPDM. Last Time Online The date and time of the last time HPDM communicated with the HPDM Agent on the device. Collecting complete asset information To collect more information about a device, you must execute a Get Asset Information task.
3 Device discovery Devices must be discovered (added to the HPDM asset database) by HPDM before they can be managed.
Automatic registration (PCoIP zero clients) Using a DNS service record HP PCoIP zero clients must have either a static domain name or access to a DHCP server to get the domain name via DHCP option 15 or 12. If the DHCP server only supports DHCP option 12, the hostname string must contain the domain name. To create a DNS service record: 1. Open the DNS console, and select the zone containing PCoIP zero clients. 2.
3. Enter MC Address in the Name field, set the Data type to String, set Code to 1, and then click OK. 4. Set the Value of the MC Address to the IP address of the HPDM Gateway, and then click OK. To enable a vendor class option: 1. Select the Scope Options of the Scope that the PCoIP zero clients are in. 2. Right-click to display the menu, and then select Configure Options to display the Scope Options dialog. 3. Select the Advanced tab. 4.
Configuring an IP scope To configure an IP scope: 1. In the Discover by Range dialog box, select the Use Preset IP Scope checkbox, and then select the Edit option in the IP Search Scope box to display the Edit IP Walking Scope dialog box. 2. Select an existing IP scope from the IP Walking Scopes list or click Add to create a new one. 3. Enter a scope name to be used by HPDM to refer to the new search scope, and then click OK. 4.
Manually registering multiple devices To manually register multiple devices: 1. In the HPDM Console, select File > Import Devices. 2. Click Select, and then choose a folder that contains text files that describe the devices to import. TIP: See the white paper HP Device Manager 4.6 Automated Device Importer for information on how to configure these files. 3. Click Import to register all devices from all text files in that folder.
4 Using tasks Task templates Task templates are displayed in the Task Templates tab of the task pane.
Creating and editing task templates A set of standard ’blank’ task templates belonging to different categories are all listed in the Task Templates tab of the task pane. The names of standard templates begin with the _ (underscore) character, for example: _File and Registry. To create or edit a task template: 1. Double-click an existing template in the Task Templates tab of the task pane, or right-click a template then select Properties from the pop-up menu. 2.
To import task templates: 1. Select Template > Import > Exported Templates from menu. 2. Select the XML file, Zip file, or both to import. Only XML files and ZIP files exported from HPDM will be accepted. HPDM 4.4 and 4.5 templates can be imported. Template versions before 4.4 may not be recognized or be compatible. 3. Click Import. The file will be added as a new template. Payload files in ZIP format will be uploaded to the Master Repository automatically. NOTE: Importing task templates since HPDM 4.
f. iv. Update Image will convert to Deploy Image. v. Update Agent, Apply ET Configurations, and Apply ET Settings will not be converted. For templates requiring payload, the HPDM Console will perform the following tasks. i. Check for missing required payloads (excluding Update Agent). ii. Convert subtasks to new subtasks when necessary. iii. Guide users to generate a package description file if the new template contains payload. iv.
Table 4-1 Template sequence conditions (continued) Icon Condition Description success Execute the template only if the previous template completed successfully. failure Execute the template only if the previous template completed with a failure. To define a new template sequence: ▲ Double-click the standard _Template Sequence template to open the Template Editor. _Template Sequence HPDM supports two types of template sequences: Basic and Advanced.
Each level of templates in an advanced template sequence is called a dependency level. An advanced template sequence can have a maximum depth of 50 dependency levels. Each dependency level can have either one anyway template or one success and one failure template. Tasks All the tasks that have been sent are monitored and the results are displayed in the task pane. The task pane lists all the tasks that have been sent to devices.
Table 4-2 Task status icons (continued) The task is being sending from HPDM Server through HPDM Gateway to the device and is waiting for a reply. Failed / Timeout The task has failed or timed out. (If the task is not complete after finite time, the status of the task will be displayed as Timeout. The error code of the status is 0.) Ready The task is executed and waiting for the user’s operation. Paused The task has been paused. Cancelled The task has been cancelled.
Target Device List The Target Device List tab lists the devices the task will be applied to. You may also add or remove devices to the list using the buttons provided. Schedule & Batch Control The Schedule & Batch Control tab contains the following sections. ● Schedule—This section enables you to specify a date and time for the task to execute. ● Batch Control—This section enables you to specify a batch size. This is used when a task is sent to a large number of devices.
The Valid Time and Timeout options enable you to set the duration HPDM will wait for the execution of tasks. You can also specify the start and end time of working hours during which HPDM will not execute tasks. Clicking in an option field will cause the Description box to display a short description of that option. 1. Select Valid Time and Timeout in the option tree pane of the Configuration Management dialog box. 2.
Resending tasks If a task has finished, you can resend the task to the device. 1. Select the finished task in the task pane. 2. Right-click and select Resend from the pop-up menu. Canceling tasks To cancel a selected ongoing task, right-click the task and select Cancel from the pop-up menu. The system will try to notify the device to cancel the task, and the status of the paused task will be changed to Canceled. NOTE: Only ongoing tasks (tasks in the Sending or Processing state) can be canceled.
Viewing tasks from all users If you have the User Management privilege, you can select the View tasks from all users checkbox in the bottom-right of the task pane to view all tasks sent by all users. You can also resend, pause, continue, cancel, and delete any task sent by any user. Task rules In HPDM rules enable you to automate the execution of tasks, and you can execute the rules in order.
5 Device management ● Viewing devices ● Deleting devices ● Grouping devices ● Checking network connection status ● Printing information about devices ● Shadowing devices ● Power management ● Managing normal thin clients ● Managing PCoIP zero clients Viewing devices To view the currently managed devices in the device pane: ▲ Select a folder in the device tree.
Indicates the device is currently in push mode Indicates the device is currently in push-lock mode (the write filter is on) The following icons are used in the HPDM Gateway tab of the HPDM Console: Represents an HPDM Gateway that is currently active Represents an HPDM Gateway that is currently down or disconnected Deleting devices To delete a device from the device tree: 1. Right-click the folder in the device tree. 2. Select Delete from the menu.
Figure 5-1 Setting group information using a DHCP tag The format that is used by HPDM for tag 203 is as follows. All the parameters are optional but those specified must be assigned a value: P1=“valor”;P2=“valor”;P3=“valor”;P4=“valor”;P5=“valor”;P6=“valor”;MG=“valo r” For example: P1=”Asia”;P2=”China”;P3=”Shanghai”;MG=”Empresa/Departamento/Grupo” Switch to Manual Grouping 1. Click the Group by button. 2. Select Manual Group > _global (system). 3.
Filtering devices Filtering enables you to work with a subset of your devices. It can be combined with User Privileges to divide the management of your devices between different administrators. Creating a new Device Filter 1. Select View on the main menu then Device Filter ... 2. Click Add in the Device Filter Management window. 3. Give your new filter a name. Click OK to accept the name. 4. Click Add… in the Edit Device Filter dialog box to open the Choose Criteria Key dialog box. 5.
1. Display the Tools menu and select User Management. 2. Select the name of the user on the Users tab, then click Edit. 3. Display the Filter tab. 4. Select the filter to use in the Security Filter drop-down list. When you log on as that user, you will see that only the devices allowed by the selected filter are displayed. Checking network connection status You can check the network connection status of a device (i.e. whether it is connected to the network or not). 1.
Shadowing devices Shadowing enables you to connect to a remote device by SSL tunnel and view and control that device from the HPDM Console. This can be achieved either by using the _Shadow Device template available in the Task Templates tab of the task pane, or by selecting from the pop-up menu when you right-click on a device as described below. NOTE: Update the HPDM Agent to the latest version before shadowing a device. Send an Apply Settings task to enable the VNC Server. To shadow a device: 1.
Capturing and deploying connections To capture connections: 1. Double-click the _Pull Connection Configuration template to open the Template Editor. 2. Use the check boxes to indicate which connection settings to capture. 3. In the Save result as template field, enter a name for the result template that will be created to store the captured connections. 4. Click Save as, enter a name for the new template, and then click OK. The template is added to the Task Templates tab of the task pane. 5.
NOTE: When configuring Time Settings, the values available for WES 2009 and XPe devices are unified with those available for WES 7 devices. There are 97 values in all. Some may not be supported by WES 2009 or XPe devices. Also, not all values on WES 2009 and XPe are supported by HPDM templates and tasks. NOTE: Firefox Browser Settings are only available for HP ThinPro 4.1 and earlier versions. NOTE: Printer Settings are only available with HP ThinPro. Only configure printer settings after cloning.
1. Right-click on a _File and Registry template, and select Merge. 2. Click another _File and Registry template, and then click OK. 3. Enter a name for the merged template when prompted. Capturing files To capture files from devices and save them to the Master Repository: 1. Double-click the _File and Registry template to open the Template Editor. 2. Click Add, select the Capture Files subtask, and then click OK. 3. In the Capture Files Editor, specify the path of the file or folder to transfer.
Deleting files To delete files from devices: 1. Double-click the _File and Registry template to open the Template Editor. 2. Click Add, select the Delete Files subtask, and then click OK. 3. Add files or folders to delete. Each line has the following options: ● File or Folder Name—Enter the file or folder name to delete. The wildcards * and ? are also supported. ● Path On Device—Enter the path on the device where the file or folder is located.
Adding, editing, and deleting registry settings To add, edit, or delete registry settings: 1. If you want to use a previously generated result template from a _Get Registry task, double-click that template, and then double-click the Registry subtask. If you want to create a new template, double-click the _File and Registry template to open the Template Editor, and then click Add. Select the Registry subtask, and then click OK. 2.
5. In the Wait column, select Yes if the command has to wait for the previous command to finish before executing. 6. If you want to add more commands, click Add. 7. Click OK when you are finished editing registry settings. 8. Click Save as, enter a name for the new template, and then click OK. The template is added to the Task Templates tab of the task pane. 9. Drag and drop the template onto the desired devices. 10. Click OK to apply the task to the devices.
Running a script To run a script on a device: 1. Double-click the _File and Registry template to open the Template Editor. 2. Click Add, select the Script subtask, and then click OK. 3. In the editor, enter the script content. IMPORTANT: HPDM supports only batch script on Windows and only shell script on Linux. 4. For Windows platforms only, specify the path to start the script in if necessary. 5. For Windows platforms only, specify the user account to run the script for if necessary. 6.
Deploying connections To deploy connections to PCoIP zero clients: 1. Double-click the _Deploy Connections template or the result template of a _Capture Connections task to open the Template Editor. 2. If necessary, select the connection type and set the values. 3. Click Save as, enter a name for the new template, and then click OK. The template is added to the Task Templates tab of the task pane. 4. Drag and drop the template onto the desired devices. 5. Click OK to apply the task to the devices.
6 Imaging operations HPDM can be used to capture an image from a device and deploy it to any number of similar devices. An image is a binary file containing all the data from a device’s flash storage. IMPORTANT: HPDM will not deploy images to devices that are not licensed for the operating system contained in the image. TIP: There is no license check for HP ThinPro or HP Smart Zero Core, so those operating systems can be interchanged as long as there is enough disk space.
Imaging support matrix The following table describes which operating systems and HP thin clients are supported for each imaging method.
IMPORTANT: PXE imaging does not work with the default HPDM Agent in an HP ThinPro 3 image due to some folder name changes. Please update the HPDM Agent to the latest version before attempting PXE imaging. NOTE: File-based imaging is the current method used by HPDM for WES imaging. The original imaging method used by HPDM in version 4.4.2 and prior was disk-based imaging. NOTE: PXE imaging is not supported on the 6360t, t5400, or 4320t because the boot order change tools are unavailable.
The device will then reboot again. 10. The task pane in the HPDM Console will continue to indicate that the task is processing. The captured image is being compressed. After the task is finished and the checksum of the captured image is verified, a new template will appear in the Task Templates tab of the task pane with the name you specified. 11.
5. If you want to deploy an image to a device that is a different hardware platform from the source device, select Allow Cross Platform Imaging. This option only applies to WES, and you need to make sure the image can work well on the target device. 6. Click the Save as button to save the template with a new name. 7. Drag and drop the template onto the devices to which you want to deploy the image.
5. When the task is sent, a result template will be created with the name you designated. Its initial status will be “Transferring”. 6. After the task is finished, the result template is valid and can be used to send tasks. NOTE: An image captured for PXE imaging is always in the .dd.gz format, regardless of the operating system.
These instructions assume the following: ● The network is already configured using DHCP. ● The DHCP server has not been previously configured for a PXE bootstrap. ● There are no other TFTP servers running on the same network. To configure the DHCP server: 1. Make sure that DHCP option 43 is not set. 2. Add DHCP option 60 by doing the following: a. From the Windows Start menu, select Start > Run. TIP: In Windows Server 2012, right-click the lower-left corner of the desktop and select Run. b.
ddns-update-style ad-hoc; Authoritative; Option NDM code 201 =string; Option vendor-class-identifier “PXEClient”; Option NDM “‘’ ‘40003’”; NOTE: The is the address of the server running the HPDM Gateway service. This command must be written exactly as shown above, including the double quotes, single quotes, and single space, as shown in the following example: Option NDM “‘192.168.1.100’ ‘40003’”; 2. Restart dhcpd to use the new configuration.
7 Repository management HPDM uses a Master Repository and one or more Child Repositories to store the files needed for its tasks. The Master Repository holds all files deployed by HPDM, while a Child Repository can hold either all or a subset of the files held in the Master Repository. Each repository is a file server to which HPDM will connect using either standard FTP, the encrypted equivalents SFTP and FTPS, or a Shared Folder.
4. Click Test if you want to test the connections you've configured NOTE: The tests are performed before changes are saved anyway. 5. Click OK. If the address of the Master Repository was changed, the HPDM Server will drop the current connection and try to connect to the Master Repository Controller at the new address. NOTE: The HPDM Server will need time to establish the connection to the Master Repository Controller. Wait for a while before doing repository-related operations such as managing content.
Synchronizing repositories TIP: It is not required to manually synchronize repositories or to schedule an automatic synchronization. The relevant files in the Master Repository are automatically synced to the Child Repositories when a task is started. To manually synchronize all content to all Child Repositories: 1. Select Tools > Repository Management from the HPDM Console menu. 2. In the Repository Management dialog box, click Sync. 3. In the Synchronization dialog box, click Sync. 4.
Downloading contents from the Files Captured category To download contents from the Master Repository: 1. In the Content Management dialog box, select an item in the Files Captured category, then click the Download button. 2. Browse to the location where you want to save it. The content will be downloaded to the local machine. Repository mapping HPDM automatically maps each device to the nearest and most convenient repository.
8 Security management There are two forms of security management in HPDM: User Management and Authentication Management. User management Each user account can have customized permissions, according to their level of need. These are assigned through the user groups system. To view the User Management dialog box: ▲ From the HPDM Console’s menu bar, click Tools > User Management. Adding users 1. In the User Management dialog box, click Add to add a new user. The Create New User dialog box will appear. 2.
3. Enter the New Password for the user, and then re-enter it in the Confirm Password field. 4. Click OK to finish. NOTE: When you log in as root for the first time, it is strongly recommended that you change the password from the default. Assigning Security Filters to Users 1. In the User Management dialog box, double-click a user from the list in the Users tab. 2. Select the Filter tab. 3. Click Add to add the filter to this user, or click Remove to remove the security filter from this user.
Deleting groups 1. In the User Management dialog box, select a group from the list in the Groups tab. 2. Click the Delete button, and then click Yes to confirm. User authentication with LDAP and Active Directory Users and groups in an Active Directory, or other LDAP servers, can be used to log in to HPDM. This allows reuse of existing login accounts and simplifies the management of who has administrative privileges with HPDM. Configuration To configure a connection to a LDAP Server: 1.
● 8. ◦ dc=testnet,dc=com ◦ o=company,c=US Specify the RDN Attribute. The RDN (Relative Distinguished Name) attribute is the LDAP attribute that specifies the login name of the user. Common values for this include sAMAccountName (Active Directory), UID, and CN. Configure a Search User. This Search User will be used in two situations: by the Import Users and Groups dialog box to browse the LDAP Server, and to dynamically determine the members of an imported Group.
4. a. The Attribute, on the left side of the query, offers several common attributes to search on. If the desired search attribute is not present, type the attribute into this field. b. The Search Value, on the right side of the query, is what is being searched for. An asterisk, *, can be used as part of the Search Value. This permits searching when the full Search Value is unknown. Example: Searching Attribute UID with an Equals comparison for Value *.smith@testnet.
Import Users or Groups: 1. Locate the Users or Groups with Browse or Search. 2. Add the User or Group. 3. Click the Import button in the lower right corner. The imported Users and Groups will now be visible in the User Management dialog box. 4. If a Group has been imported, the privileges of the group must be assigned. Please see Assigning permissions to groups on page 61.
3. The system will prompt you to create and confirm the KeyStore password. 4. In the Create KeyStore Password dialog box, enter a KeyStore Password and confirm the password in the Re-enter Password field. 5. Click the OK button. To import Authentication Key(s): 1. Click the Import Key(s) button in the Key Management window to display the Import dialog box. 2. Browse for the exported *.ks file, then click the Import button. 3. The system will prompt you to enter the KeyStore password. 4.
9 Report management Adding a report template To add a report template: 1. Select Tools > Report Management from the HPDM Console’s menu bar to display the Report Management window. 2. Select one report type from the Report Types list, then click the Add button. A Set New Report Template Name dialog box will prompt you to input a report template name. 3. Click OK to open the Edit Report Template window. In the Edit Criteria field, click the ... button to open the Choose Criteria Key window.
1. In the Report Management window, select a report type from the Report Types list and all the report templates belong to the selected type will be displayed in the Report Templates list. 2. Select a template from the list then click Edit, or double-click on the template to view the template's content. 3. Click Generate Report to preview the report. Producing reports HPDM enables you to print information about your devices and the tasks you have sent to them.
Task Status report This report lists information about a task's status. To create a Task Status report: ▲ Select a task from the Device Task View dialog, right-click and select Print Preview > Status .... Task Log report This report lists information about a task's status log. To create a Task Status Log report: ▲ Select a task from the Device Task View dialog, right-click and select Print Preview > Log ....
10 Status Walkers HPDM has two integrated tools that monitor and record the performance of the devices: Status Walker and Status Snapshot. NOTE: The Status Walker has been deprecated and is no longer supported by HP. It is still provided as a tool for your use. Status Walker The Status Walker tool makes a list of all the IPs available and walks to them; it brings back their status information and displays it. This status report is made in real time.
1. Select Tools > Configuration from the HPDM Console’s menu bar to open the Configuration Management window. 2. Select the Status Walker Configuration item in the left-hand tree pane. NOTE: You can display a short description of each option by clicking in the option field. 3. Enter a value for the Walking Group Size. 4. Define a value for Walking Timeout. 5. Click Apply to save the settings. 6. Click OK.
11 HP FTP Software Component Browser The HP FTP Software Component Browser provides a means to automate the process of leveraging software components from the HP public FTP site. IMPORTANT: This features requires Internet access. If the system running the HPDM Console or Master Repository Controller cannot access the Internet directly, you must first configure proxy settings. See Configuring HP FTP proxy settings on page 73 for more information.
Configuring HP FTP proxy settings Proxy settings must be configured to use the HP FTP Software Component Browser if the system running the HPDM Console or Master Repository Controller cannot access the Internet directly. To configure HP FTP proxy settings: 1. Select Tools > Configuration from the HPDM Console menu. 2. In the Configuration Management window, select the HP FTP Proxy page. 3.
12 HPDM Server Backup and Restore Tool The HPDM Server Backup and Restore Tool can back up and restore the HPDM Server files and database, including the following items: ● Database schema and data ● [HPDM Installation Root]\Server\task folder ● [HPDM Installation Root]\Server\template folder ● [HPDM Installation Root]\Server\template_plugins folder Before using the HPDM Server Backup and Restore Tool, note the following: ● This tool requires the credentials of a user account that has the database o
Backing up the HPDM Server To back up the HPDM Server: 1. In the HPDM Server Backup and Restore Tool, select the authentication type and enter the credentials of a user account that has the database owner privilege. 2. Specify an already-existing folder in which the backup will be stored. TIP: Each backup creates a new sub-folder that contains all the backup content, so you can use the same parent folder to store all the backups. 3. Click the Back up button.
NOTE: A backed-up database can only be restored to a database of the same type. For example, if you back up an SQL Server database, you can only restore it to an SQL Server, not another database type.
13 HPDM Port Check Tool The HPDM Port Check Tool is a utility for checking the network and service connectivity and firewall port allowance between different components of HPDM. The tool is located at the following path: \Console\bin\HPDMPortCheck\ Copy the tool (the whole folder) to a connection initiator (a thin client), run the tool, and use it to connect to the target component.
14 HPDM Agent polling and error logging This chapter describes the HPDM Agent polling and error logging capabilities of HPDM. HPDM Agent polling The HPDM Gateway can be set to communicate with the HPDM Agent periodically and update device status (on/off) to the HPDM Server. The default interval is 0, which means this process will not occur to save net traffic. A detailed description of its two parameters can be found in the configuration GUI by hovering the mouse cursor over the text.
Table 14-2 HPDM Gateway logging (continued) Level Description WARN Low-level error; for example, HPDM Gateway failed to connect to Console/Server at this time, maybe Server is not ready, but HPDM Gateway will retry later ERROR Significant errors FATAL High-level error; the error will usually prevent HPDM Gateway from running normally To change the logging level for an HPDM Gateway, use one of the following methods: ● Use the HPDM Gateway configuration dialog, which can be accessed from right-clicki
Master Repository Controller logging Level Description INFORMATION Logs of running information, contains no errors WARNING Low-level error ERROR Significant errors To change the logging level of the Master Repository Controller: ▲ Change the value of LogLevel in the file /MasterRepositoryController/ Controller.conf, which is located in the HPDM installation folder. The log file of the Master Repository Controller is located in /MasterRepositoryController/ log/.
A Template reference HPDM separates templates into the following categories: ● File and Registry ● Agent ● Connections ● Imaging ● Operations ● Settings ● Template Sequence File and Registry Table A-1 File and Registry templates Template Description _File and Registry This template enables you to create a sequence using these sub-templates: _Get Registry ● Set a registry key. ● Capture a file from a device. ● Deploy a file to a device. ● Execute a command on a device.
Table A-2 HPDM Agent templates (continued) Template Description _Configure Task Deferment This template enables you to configure task deferment settings on target devices. _Update Agent This template updates HPDM Agent on the target devices to the version stored in your repository. The payload will be synchronized to the mapped repository automatically before the task is sent to the target devices.
Table A-5 Operation templates (continued) Template Description _Reverse Shadow Device This template causes the HPDM Agent on a targeted device to connect to the VNC viewer bundled with the HPDM Console by SSL tunnel. This template is not available for the HPCE thin clients. _Send Message This template sends a customized message to targeted devices. This template is not available for HP ThinPro thin clients.
Table A-6 Setting templates (continued) Template Description _Take TPM Ownership This template enables/activates TPM and sets the TPM owner password and BIOS setup password to take the TPM ownership of the selected devices. _Write Filter Settings This template enables you to change the Write Filter settings for a device.
B Port reference The following sections list the ports used by HPDM: ● HPDM Console ports ● HPDM Server ports ● HPDM Gateway ports ● HPDM Agent ports ● Repository ports HPDM Console ports Table B-1 HPDM Console ports (inbound) Receiver port Sender Receiver Protocol Purpose 5500 SSL VNC Proxy (bundled with HPDM Console) VNC Viewer (bundled with HPDM Console) TCP (loopback) VNC Viewer in Listen Mode (reverse VNC) 5900 VNC Viewer (bundled with HPDM Console) SSL VNC Proxy (bundled with HP
Table B-2 HPDM Console ports (outbound) (continued) Receiver port Sender Receiver Protocol Purpose 139 HPDM Console NetBIOS Session Service TCP Allows NetBIOS Session Services connections 445 HPDM Console Microsoft Directory Services TCP For File and Printer Sharing to allow Server Message Block transmission and reception through Named Pipes 989 & 990 HPDM Console FTPS server (third-party software) TCP These are the default ports for FTPS (used for repositories).
Table B-4 HPDM Server ports (outbound) Receiver port Sender Receiver Protocol Purpose 40000 HPDM Server HPDM Gateway UDP Allows the HPDM Server to poll the HPDM Gateway 40003 HPDM Server HPDM Server TCP Allows the HPDM Server to send tasks to the HPDM Gateway 40006 HPDM Server PostgreSQL (bundled with HPDM Server) TCP (loopback) The default database PostgreSQL listening port (only needed when PostgreSQL is used) 40012 HPDM Server Master Repository Controller TCP Allows the HPDM Serve
Table B-6 HPDM Gateway ports (outbound) (continued) Receiver port Sender Receiver Protocol Purpose please configure the firewall appropriately. 22 HPDM Gateway SFTP server (third-party software) TCP This is the default port for SFTP (used for repositories). SFTP ports can be configured via the HPDM Console. If you do not use the default port for your SFTP, please configure the firewall appropriately.
Table B-7 HPDM Agent ports (inbound) (continued) Receiver port Sender Receiver Protocol Purpose 68 HPDM PXE Server (bundled with HPDM Gateway) HPDM Imaging Mini Linux Tool (client-side) UDP PXE bootstrap 5500 Windows platform : VNC Server (client-side) Windows platform : SSL VNC Proxy (bundled with HPDM Agent) TCP (loopback) SSL VNC Proxy in Listen Mode (reverse VNC) 5900 SSL VNC Proxy (bundled with HPDM Console) VNC Server (client-side) TCP (loopback) VNC Shadow 40001 HPDM Gateway HPD
Table B-8 HPDM Agent ports (outbound) (continued) Receiver port Sender Receiver Protocol Purpose 139 HPDM Agent NetBIOS Session Service TCP Allows NetBIOS Session Services connections 445 HPDM Agent Microsoft Directory Services TCP For File and Printer Sharing to allow Server Message Block transmission and reception through Named Pipes 5500 Windows platform: VNC Server (client-side) Windows platform : SSL VNC Proxy (bundled with HPDM Agent) TCP (loopback) SSL VNC Viewer in Listen Mode (re
Table B-9 Repository ports (inbound) (continued) Receiver port Sender Receiver Protocol Purpose please configure the firewall appropriately. 22 HPDM Console HPDM Gateway SFTP server (third-party software) TCP This is the default port for SFTP (used for repositories). SFTP ports can be configured via the HPDM Console. If you do not use the default port for your SFTP, please configure the firewall appropriately.
Table B-10 Repository ports (outbound) 92 Receiver port Sender Receiver Protocol Purpose 20 & 21 Master Repository Controller FTP server (third-party software) TCP These are the default ports for FTP (used for repositories). Port 20 is for data transfer and port 21 is for listening to commands. FTP ports can be configured via the HPDM Console. If you do not use the default ports for your FTP server, please configure the firewall appropriately.
Index A Active Directory 62 authentication key exporting 65 importing 66 updating 65 viewing 66 authentication management 65 C Child Repositories configuring 57 deleting 57 description 4 connections capturing 40 deploying 40 D device discovery 18 manual registration 21 walking with IP list 21 walking with IP range 20 device filters creating 37 editing 37 devices definition 5 deleting 35 grouping 35 management 34 network, checking connection status 38 printing information about 38 properties, displaying 16 r
configuring routers 55 deploying 53 on legacy Neoware devices 55 PXE, definition 5 R reports adding template 67 generating using 67 importing plug-in file 67 management 67 repositories 56 content management 58 description 4 exporting 57 importing 57 management 56 synchronizing 58 result template, opening 32 routers, configuring for PXE imaging 55 rules, definition 5 S security authentication management 65 filter 37 HPDM Gateway access control 66 key management 65 management 60 user authentication 62 shadowi
