Repository Management in HP Device Manager 4.5

Transcription

1 Repository Management in HP Device Manager 4.5 Demonstrates how to install, configure, and use the new repository features of HP Device Manager 4.5 Technical white paper

2 2 Copyright 2012 Hewlett-Packard Development Company, L.P. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. First Edition: December 2012 Document Part Number:

3 3 Table of contents Overview... 4 Pre-installation... 5 Setting up an FTP server... 5 Configuring a Share Folder... 5 Installation... 6 Installing the Master Repository Controller... 6 Master Repository Controller configuration Connection configuration between HPDM Server and the Master Repository Controller for a first-time run Connection configuration Connection authentication Repository configuration Configuring repository protocol Configuring the Master Repository Configuring child repositories Configuring repository mapping Repository content management Repository content generation Built-in package Easy Tools Configuration package Easy Tools Settings package Files Captured category Files to Deploy package Image package Repository content deletion Repository synchronization Synchronizing packages when sending tasks Synchronizing all repositories... 34

4 4 Overview This document discusses how to use the new Auto Repository Management feature in HPDM 4.5. It includes environment preparation, component installation and configuration, package management, and repository management. The overall structure of the Auto Repository Management feature is shown in the diagram below. Secure Line Sync/List DM Server Secure Line Sync/List Master Repository DM Console Master Repository Controller Packages 3 DM Agent DM Gateway DM Gateway DM Gateway 2 DM Agent 1 DM Agent Add/Delete/Upload/Download Download Download Download / Upload Download Synchronize from Master to Child Repositories 3 2 ArM Slave Repository 1 ArM Slave Repository Child Repository Payloads Packages Payloads FTP / FTPS / SFTP / ShareFolder

5 5 Pre-installation Setting up an FTP server Here, we assume you have installed an FTP server service on a computer that will serve as the Master Repository and on which the Master Repository Controller will be installed. You can refer to the FTP Server Configuration white paper for details on how to setup an FTP server. 1. Go to the root path of the FTP server. In this document, we assume that your FTP root path is c:\inetpub\ftproot. 2. Make a directory called HPDM in the above folder. Please do not use an existing directory that was created for a version of HPDM prior to 4.5. If you really want to use an old directory, please back up the files in it to another location and then delete them from the old directory. Configuring a Share Folder Configure the directory HPDM created above as an SMB share folder with full control permissions. This step is required only when you will need to access the repositories via SMB protocol, which is one of protocols that HPDM supports for accessing repositories. SMB is not recommended unless you have a good reason. Sometimes, Linux thin clients are not able to work well with Microsoft SMB share folders. A known case where you will have to use SMB is for WES7/WES09 file-based imaging tasks capturing or deploying.ibr images.

6 6 Installation Installing the Master Repository Controller For system requirements for the installation of the Master Repository Controller, you can refer to the HP Device Manager User Guide. 1. Double click the installation package. 2. Click Next. 3. Accept the terms of the license agreement and click Next.

7 7 4. Confirm the system requirements, and click Yes. 5. Select the Custom setup type, browse to the desired destination folder, and then click Next. NOTE: You can install the Master Repository Controller with other components on the same machine by selecting the Complete setup mode. For details, please refer to the HP Device Manager User Guide.

8 8 6. Select only the Master Repository Controller component and click Next. 7. Set the Master Repository root path. You must input the folder that you configured in the Pre-installation section of this document. You should also read the detailed explanation in this dialog. After this, click Next.

9 9 8. Click Install. 9. After the installation is complete, the below configuration dialog box will appear. Select the language and click Next.

10 In the right panel, you will see the port needed by the Master Repository Controller. Check the box next to the port, then click Next. 11. Click Execute to execute the configuration.

11 After the execution is complete, the below dialog box will appear. Click Finish to complete the configuration. 13. Click Finish to complete the entire installation.

12 12 Master Repository Controller configuration 1. After installation, open the Services console in Windows (Start > All Programs > Administrative Tools > Services or run the command services.msc). You will find the HP Device Management Master Repository Controller service. Here, you can start, stop, or restart this service. 2. In the Windows Explorer, go to the folder where you installed the Master Repository Controller. 3. Open the file Controller.conf, located in the folder MasterRepositoryController, and you can see the below configuration: a. ReposSetting:: ReposPath This is the Master Repository root path that you input during the installation. You must change the path manually if you change the Master Repository root path after the installation. b. LogSetting::Loglevel This is the log level setting parameter. 0 is Error, 1 is Warn, and 2 is Info. If you want to see the detailed log information when encountering some problems, set the log level to 2 (Info). Please note that after you change the settings above, you must restart the Master Repository Controller service for the changes to take effect. 4. Go to the Master Repository root path that you set up during installation, and you can find the built-in packages. Please do not modify these files if you are not proficient on this system.

13 13 Connection configuration between HPDM Server and the Master Repository Controller for a first-time run Here, we assume that you have installed all other components of HP Device Manager. You can refer to the HP Device Manager User Guide for detailed information on their installation. Connection configuration 1. Open the HPDM Console. When you first open it after installation, a warning message will appear. Click OK.

14 14 2. In the Repository Wizard dialog box, establish the protocol and port you wish to use. You can select FTP, FTPS, or SFTP according to your FTP server settings. You must select Share Folder if you have a Windows platform and want to capture/deploy images with the.ibr format. You can refer to the HP Device Manager User Guide for more details. Then, click Next. NOTE: The protocol settings will be applied to all repositories, including the Master and Child Repositories, and HPDM will only use that protocol to access the repositories.

15 15 3. Input the Repository Name, Server Address, Username, Password, and Path in the Repository Editor. Then, click Save. NOTE: The Server Address is the address at which the Master Repository Controller has been installed. The Username and Password for each protocol are what you configured during the pre-installation for the FTP server and/or Share Folder settings. The Path specified above must point to the same location that you configure for the Master Repository Controller during installation.

16 16 4. The Repository Configuration dialog box will appear, and it shows that a Master Repository has been configured. 5. If you enter the wrong server address for the Master Repository, an error message will appear after a while to show that HPDM Server cannot connect to the Master Repository Controller. As the error message shows, you can go to the Repository Configuration dialog to correct it. In the Repository Configuration chapter, we will discuss this in more detail.

17 17 Connection authentication In our system, we use SSL to authenticate the connection between HPDM Server and the Master Repository Controller. After you have finished the configuration successfully for the first-time run, the authentication certificate and private key are generated between the Server and the Master Repository Controller. 1. Go to the installation folder of HPDM Server, and you can find the key store file hpdmskey.keystore in the folder InstallerFolder/Server/bin. This file stores the certificate of the Master Repository Controller and the certificate and private key of itself. 2. Go the installation folder of the Master Repository Controller, and you can find these three files: Controller.key Master Repository Controller s private key Controller.crt Master Repository Controller s certificate Client.crt HPDM Server s certificate Once the authentication is set up, a connection request that doesn t have the certificate will be refused by the Master Repository Controller. Also, the Server will refuse the Master Repository Controller if it does not pass the authentication. When the authentication fails, the below message will appear on the Console. HPDM only supports one Server and one Master Repository Controller in the running system. If you use another Server or Master Repository Controller, the above error message will occur. If the authentication files above are deleted or modified, you can recover the authentication via the following steps. Before you do this, you must check that, in your system, there is only one Server and one Master Repository Controller. 1. Stop the Server and Master Repository Controller service. 2. Delete all of the authentication files mentioned above. 3. Start the Server and Master Repository Controller service. 4. Open the Console again, and the error message will not appear.

18 18 Repository configuration Configuring repository protocol Repository protocol was configured by the Repository Wizard when you ran the system for the first time. Here, we discuss how to edit the configuration. 1. Select Tools > Repository Management > Protocol Configuration from the Console menu bar. 2. In the Protocol Configuration dialog, edit the protocol and port you wish to use.

19 19 Configuring the Master Repository The Master Repository was configured by the Repository Wizard when you ran the system for the first time. Here, we discuss how to edit the configuration and do a connection test. 1. Select Tools > Repository Management > Repository Configuration from the Console menu bar. 2. In the Repository Configuration dialog box, select the Master Repository item and click Edit.

20 20 3. In the Repository Editor dialog box, you can edit the Repository Name, Server Address, Username, Password, and Path settings. NOTE: For the Repository Name, you can input any value you want, but for the other values, you must input a valid value as explained in Connection configuration.

21 21 4. Click Connect if you want to test the connection to the Master Repository Controller. If the connection between the HPDM Server and the Master Repository Controller is working well, the below message will appear. If you modify the Server address, the below message will appear. If the Server address is invalid, after a while, the below error message will appear. If the Server address is valid, no message will appear.

22 22 5. You also can click Test if you want to test the connection to the FTP server and/or Share Folder. If the Username, Password, and Path are all valid, the below message will appear. If one of the above values is invalid, the below warning message will appear. 6. After you confirm your configuration, click Save to save the settings. NOTE: The Master Repository cannot be deleted once you have configured it, and you cannot add another one. Configuring child repositories Here, we discuss how to add, edit, and remove a child repository on the Console. Before you add a child repository to the system, you must have configured the FTP server and/or Share Folder on the machine on which the child repository will reside. For more information, refer to Pre-installation. 1. Select Tools > Repository Management > Repository Configuration from the Console menu bar.

23 23 2. In the Repository Configuration dialog box, click Add. The Repository Editor will appear. 3. Fill in the Repository Name, Server Address, Username, Password, and Path settings just like with the Master Repository. 4. Click Test to test the connection to the child repository.

24 24 5. After you confirm your configuration, click Save to save the settings and go back to the Repository Configuration dialog box. 6. Select the child repository. You can click Remove to delete the child repository and Edit to edit it. Configuring repository mapping There are two repository mapping methods in HPDM 4.5: Batch Mapping Per-Device Mapping Refer to the HP Device Manager User Guide for more details.

25 25 Repository content management 1. Select Tools > Repository Management > Content Management from the Console menu bar. In the Content Management dialog, you can view all the content of the Master Repository. 2. Select a category in the left panel, then double-click an item in the right panel. A dialog box will appear detailing the content information. When you first run the system after installation, there are only built-in contents. Next, we will discuss how to generate repository content.

26 26 Repository content generation In general, the content of an HPDM repository consists of HPDM packages and discrete files/folders, typically captured from client devices. An HPDM package contains two parts: payload files and the description file for the package. For example, if you have a package called Test, you should see a folder and a file shown as below, and the folder should contain payload files in it. Folder: Test File: Test-D653B4C263C399E924FF5F70AE5BD9EF.desc The description filename is the combination of the payload name and the MD5 value for the payload separated by -. The content of the description file includes detailed information of the package, such as payload size, OS type, and thin client models that the package can be applied to. The information comes from either UI input or other sources such as imported HP FTP components. For a package, the payload and description file are both required. The following section will discuss each content in detail. Built-in package Built-in packages are generated when installing the Master Repository Controller. You can view them in the Content Management dialog box. Also, you can go to the Master Repository root path, which is configured during installation, to find the files of these packages. Easy Tools Configuration package 1. Select Template > Import > Easy Tools Configuration from the Console menu bar. 2. Select the OS type and browse to select an Easy Tools Configuration file. Then, click OK.

27 27 3. In the Package Description Editor, input the Title, Installation Space, Architecture, OS Type, Thin Client Models, and Description values for this Easy Tools Configuration package. Then, click Generate. 4. After the generation is complete, open the Content Management dialog, and in the Easy Tools Configuration category, you can view the package information.

28 28 Easy Tools Settings package 1. Select Template > Import > Easy Tools Settings from the Console menu bar. 2. The next steps are the same as in Easy Tools Configuration package. Files Captured category The Files Captured category lists all the files and folders captured from client devices. It should be noted that the content in this category is not a package and cannot be deployed to thin clients directly. You should download this content and make a package according to the steps in the next section Files to Deploy package. 1. You can generate a captured file task by dragging a _File and Registry template to the target device.

29 29 2. Edit the File or folder name with full path. 3. When the Capture Files task is complete, the captured files or folders will be listed in the Files Captured category.

30 4. There is no package description information file binded with captured files or folders in the Files Captured category, so the package description dialog will not be shown. If you want to send a task with captured files or folders, click Download, then generate a package according to the next section. 30

31 31 Files to Deploy package The Files to Deploy category lists all the files needed to be deployed to the target client devices. 1. Generate a File and Registry template with available packages for Deploy Files. 2. Add files or folders for this File to Deploy package. If you want to deploy the files or folders that you captured in the section Files Captured category, you can add them here and generate a payload.

32 32 3. Click OK, and the Package Description Editor will appear to ask you to input the necessary information for this package. 4. Click Generate, and the Deploy Files package will be generated. After generation, you can open the Content Management dialog and view it in the Files to Deploy category with detailed package information.

33 33 Image package 1. Send a Capture Image task to a thin client. For details about the Capture Image task, refer to the Imaging with HP Device Manager 4.5 white paper. 2. After the Capture Image task is complete, open the Content Management dialog again, and in the image category, you can view the image package information. NOTES: You can generate an image package by importing a local image file. For details about importing image files, refer to the Imaging with HP Device Manager 4.5 white paper. After generation, all of the content is only uploaded to the Master Repository directly, and you can go to the Master Repository root path to check the existence of the content. If you want to send a task that will deploy packages to a thin client mapped to a child repository, the synchronization will be executed. We will discuss this in the next section. Repository content deletion 1. Open the Content Management dialog box. 2. Select an item in the right panel, then click Delete. A confirmation message will appear. Click Yes, and the package (files or folders in the Files Captured category) will be deleted from the Master Repository. The system will also try to delete the package in the child repositories. Note: The built-in packages cannot be deleted from the Console.

34 34 Repository synchronization Here, we discuss how to synchronize packages from the Master Repository to child repositories. Currently, we provide two methods for synchronization. Synchronizing packages when sending tasks When you send a task that will lead to deploying packages to the thin client, the synchronization will be executed automatically. This process only synchronizes the packages needed by this task to the child repository that is mapped by the target thin client. For example: 1. Configure two child repositories, Child Repository A and Child Repository B. 2. Discover two thin clients, Thin Client A and Thin Client B. 3. Map Thin Client A to Child Repository A, and Map Thin Client B to Child Repository B. 4. Send a Deploy Files task that contains Package1 to Thin Client A. 5. Package1 will be synchronized to Child Repository A and not to Child Repository B. 6. Thin Client A will download Package1 from Child Repository A and execute the task. Synchronizing all repositories Synchronizing all repositories will synchronize all of the content, including image packages in the Master Repository, to all of the child repositories and delete all the files in the child repositories that do not exist in the Master Repository. After synchronization, the content in the child repositories will be exactly the same as the content in the Master Repository. Currently, there are two methods for you to execute this action. From the Repository Configuration dialog: 1. Select Tools > Repository Management > Repository Configuration from the Console menu bar.

35 35 2. In the Repository Configuration dialog, click the Sync All button. 3. A warning message will appear. Click Yes to confirm, then wait for the synchronization to finish. The amount of time spent on the synchronization depends on the number and size of files, specifically image files on the Master Repository and the number of the child repositories. If you do not have any child repositories, the synchronization will do nothing.

36 36 4. After the synchronization is complete, open the Repository Configuration dialog again, and the Last Time Synchronized column of each child repository will be updated. 5. Now, you can go to each child repository s root path that is set when configuring the child repositories for the FTP server and/or Share Folder to see that all the packages are the same as the packages in the Master Repository. From the Content Management dialog: 1. Select Tools > Repository Management > Content Management from the Console menu bar. 2. Click Sync All, and the subsequent process is the same as above.