Recovering Old Templates in HP Device Manager 4.5 Demonstrates how to recover old templates after upgrading HPDM to version 4.
© 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 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.
Table of contents Overview ............................................................................................................................................ 4 Background......................................................................................................................................... 4 Recovering “File and Registry” templates ................................................................................................ 4 Recovering “Update Image” templates .............
Overview This document discusses how to make old templates work in HPDM 4.5. The steps in this document are based on these assumptions: • You have the Master Repository properly configured. • You have templates to recover exported with payload. • You have old repositories backed up. Background The repository system was changed significantly in HPDM 4.5: • All templates with payload have been modified. • Some templates have been deprecated and replaced by new ones.
3. Select a “Deploy Files” subtask and click Edit to open the subtask editor dialog. 4. Click Add from local to insert the same payload as the existing one because the old one will not work.
5. Copy the Path On Device from the old record and paste it onto the newly added one. 6. Delete the old record. 7. Repeat steps 4–6 if you have multiple files or folders to deploy in this subtask. 8. Click OK to accept the modified subtask. 9. Repeat steps 3–8 if you have multiple Deploy Files subtasks in this template. 10. Click Save as to save the template as a new File and Registry template. 11.
12. Enter information about the payload, and click Generate to save. 13. The new template will be available after the transfer is finished. 14. Delete the old template to clean up.
Recovering “Update Image” templates This type of template uses a single file as the payload. It has been changed to the Deploy Image template in HPDM 4.5. Please follow these steps to rebuild these templates with their payload files: 1. From the Template menu, select Import > Image Files > to deploy without PXE. The Import Image File dialog will appear. 2. Click Browse to choose the payload files.
3. Click Import to accept the payload file. 4. Select the operating system using the Select OS type drop-down box. 5. Enter a new template name (the payload filename is entered automatically as the default value). 6. Click Import to start importing. A template with a status of “Transferring” will be generated to avoid other users adding templates of the same name, and then the Package Description Editor will be displayed. 7.
Recovering “PXE Image” templates This type of template uses a single file as the payload. It has been changed to the PXE Deploy template in HPDM 4.5. Please follow these steps to rebuild these templates with their payload files: 1. From the Template menu, select Import > Image Files > to deploy using PXE. The Import Image File dialog will appear. 2. Click Browse to choose the payload files.
3. Click Import to accept the payload file. 4. Select the operating system using the Select OS type drop-down box. 5. Enter a new template name (the payload filename is entered automatically as the default value). 6. Click Import to start importing. A template with a status of “Transferring” will be generated to avoid other users adding templates of the same name, and then the Package Description Editor will be displayed. 7.
Recovering “Apply Easy Tools Configurations” templates This type of template uses a single file as the payload. Please follow these steps to rebuild these templates with their payload files: 1. From the Template menu, select Import > Easy Tools Configuration. The Import Easy Tools Configurations dialog will appear. 2. Select the operating system using the Select OS type drop-down box. 3. Click Browse to choose the payload files.
4. Click Import to accept the payload file. The template name is automatically generated with name of the payload file. 5. Click OK to start importing. A template with a status of “Transferring” will be generated to avoid other users adding templates of the same name, and then the Package Description Editor will be displayed. 6. Enter information for the payload, and then click Generate to accept the descriptions.
Recovering “Apply Easy Tools Settings” templates This type of template uses a single file as the payload. Please follow these steps to rebuild these templates with their payload files: 1. From the Template menu, select Import > Easy Tools Settings. The Import Easy Tools Settings dialog will appear. 2. Select the operating system using the Select OS type drop-down box. 3. Click Browse to choose the payload files.
4. Click Import to accept the payload file. The template name is automatically generated with name of the payload file. 5. Click OK to start importing. A template with a status of “Transferring” will be generated to avoid other users adding templates of the same name, and then the Package Description Editor will be displayed. 6. Enter information for the payload, and then click Generate to accept the descriptions.
Recovering sequence templates Sequence templates with payload (except for Update Agent templates) will not work after upgrading to HPDM 4.5. Some of them have been removed, and in others, the logic of the whole sequence might have become invalid. You will need to rebuild the whole sequence. However, good preparation before upgrading could help you save time on rebuilding them. First, you can export the sequence templates with payload so that you can find the payload files easier.