HP Client Automation Starter and Standard Editions Migration Guide

HP Client Automation Starter and Standard
Edition
For the Windows® operating system
Software Version: 8.10
Migration Guide
Document Release Date: March 2012
Software Release Date: February 2012
Migration Guide
Legal Notices
Warranty
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.
The information contained herein is subject to change without notice.
Restricted Rights Legend
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.
Copyright Notice
© Copyright 1993 - 2011 Hewlett-Packard Development Company, L.P.
Trademark Notices
Microsoft®, Windows®, Windows® XP, and Windows Vista® are U.S. registered trademarks of
Microsoft Corporation.
Oracle is registered trademark of Oracle Corporation and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Acknowledgements
This product includes software developed by the Apache Software Foundation
(http://www.apache.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Page 2 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Documentation Updates
The title page of this document contains the following identifying information:
l
Software Version number, which indicates the software version.
l
Document Release Date, which changes each time the document is updated.
l
Software Release Date, which indicates the release date of this version of the software.
To check for recent updates or to verify that you are using the most recent edition of a document, go
to:
http://h20230.www2.hp.com/selfsolve/manuals
This site requires that you register for an HP Passport and log on. To register for an HP Passport
ID, go to:
http://h20229.www2.hp.com/passport-registration.html
Or click the New users - please register link on the HP Passport log on page.
You will also receive updated or new editions if you subscribe to the appropriate product support
service. Contact your HP sales representative for details.
Page 3 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Support
Visit the HP Software Support Online web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support
that HP Software offers.
HP Software online support provides customer self-solve capabilities. It provides a fast and
efficient way to access interactive technical support tools needed to manage your business. As a
valued support customer, you can benefit by using the support web site to:
l
Search for knowledge documents of interest
l
Submit and track support cases and enhancement requests
l
Download software patches
l
Manage support contracts
l
Look up HP support contacts
l
Review information about available services
l
Enter into discussions with other software customers
l
Research and register for software training
Most of the support areas require that you register as an HP Passport user and sign in. Many also
require a support contract. To register for an HP Passport ID, go to:
http://h20229.www2.hp.com/passport-registration.html
To find more information about access levels, go to:
http://h20230.www2.hp.com/new_access_levels.jsp
Page 4 of 32
HP Client Automation Starter and Standard Edition (8.10)
Contents
Migration Guide
1
Contents
5
Introduction
7
System Requirements
9
Abbreviations and Variables
10
Upgrading HPCA Core Server
11
Step 1: Backup the Existing HPCA Core Server Installation
11
Step 2: Upgrade to the Latest Version
12
Step 3: Restore HPCA Data
13
Step 4: Migrate the HPCA SQL/Oracle Database
14
Step 5: Log in to the Core Console
16
Step 6: Update Core Configuration and Content
16
Update HP Live Network Content
Upgrading Deployed Components
16
17
Upgrading HPCA Agent
17
Upgrading HPCA Administrator
18
Upgrading Satellite Servers
18
Upgrading Satellite Server Manually
19
Step 1: Backup the Existing Satellite Server Installation
19
Step 2: Upgrade to the Latest Version
19
Step 3: Restore HPCA Data
21
Step 4: Synchronize Satellite
21
Upgrading Satellite Server through HPCA Console
Upgrading Proxy Servers
21
23
Upgrading Proxy Server to Satellite Server Manually
23
Upgrading Proxy Server to Satellite Server through HPCA Console
24
SQL Database Tables that must be Migrated
Page 5 of 32
25
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Contents
Migrating the HPCA SQL/Oracle Database Manually
30
We appreciate your feedback!
31
Page 6 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 1: Introduction
Introduction
This document explains how to upgrade your HP Client Automation (HPCA) Standard or Starter
Edition environment to HPCA version 8.10 while preserving your data.
Note: This document applies only to HPCA Standard or Starter Edition Core and Satellite
installations; it does not apply to HPCA “classic” (component-based) installations.
To upgrade an HPCA Enterprise Edition environment, see the HPCA Enterprise Edition Migration
Guidefor details.
Use these instructions to upgrade the following products to the latest version of HPCA Core and
Satellite:
l
HPCA Standard and Starter Edition Core and Satellite version 7.50
l
HPCA Standard and Starter Edition Core and Satellite version 7.80
l
HPCA Standard and Starter Edition Core and Satellite version 7.90
Caution: HP recommends to apply the latest patch available to your current HPCA version before
starting the migration process.
Page 7 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 1: Introduction
Page 8 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 2: System Requirements
System Requirements
HP Client Automation (HPCA) Standard and Starter Edition version 8.10 supports those database
servers listed in the HPCA Standard Edition Release Notes and HPCA Starter Edition Release
Notes.
If your HPCA environment uses Microsoft SQL Server, you must use either Microsoft SQL Server
2005 or Microsoft SQL Server 2008 with HPCA version 8.10.
If you are using an older version of Microsoft SQL Server, be sure to upgrade your database to
either Microsoft SQL Server 2005 or Microsoft SQL Server 2008 before you begin the HPCA
migration process described in this document. Refer to your Microsoft SQL Server documentation
for instructions.
Page 9 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 2: Abbreviations and Variables
Abbreviations and Variables
Abbreviations Used in this Guide
Abbreviation Definition
HPCA
HP Client Automation
Core and
Satellite
HPCA Enterprise environment consisting of one Core server and one or more
Satellite servers. All features are installed as part of the Core or Satellite server
installation.
CSDB
Configuration Server Database
Portal
HPCA Portal
Variables Used in this Guide
Variable
Description
Default Values
InstallDir
Location where the HPCA server
is installed
For a 32-bit OS: C:\Program
Files\Hewlett-Packard\HPCA
For a 64-bit OS: C:\Program
Files(x86)\Hewlett-Packard\HPCA
SystemDrive Drive label for the drive where the
HPCA server is installed
Page 10 of 32
C:
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 3: Upgrading HPCA Core Server
Upgrading HPCA Core Server
Caution: Be sure that your environment meets the "System Requirements" (on page 9) before you
begin the HPCA migration process.
The upgrade process includes four steps:
"Step 1: Backup the Existing HPCA Core Server Installation" (on page 11)
"Step 2: Upgrade to the Latest Version" (on page 12)
"Step 3: Restore HPCA Data" (on page 13)
"Step 4: Migrate the HPCA SQL/Oracle Database" (on page 14)
Caution: Migration processes might result in data loss. Ensure that you fully backup your
environment before you start the migration process.
Caution: It is important to prevent agent and satellite connections to the Core during the upgrade
process. Such connections can result in duplicate device entries and other problems.
Ensure that access to the Core’s Web Server and Configuration Server ports (3466 and
3464, respectively by default) is blocked until the upgrade and restoration of the Core is
complete.
Note: During migration, the admin password is reset to secret. Be sure to change this after you
have completed the migration process.
Step 1: Backup the Existing HPCA Core Server Installation
Backup the existing Core Server installation and database to prepare for the upgrade.
To back up the existing installation:
1. From the HPCA media, copy the \Setup-Core\migrate folder to a temporary location (for
example, C:\migrate).
You must copy this folder to a temporary location since the migration scripts cannot be run
directly from the HPCA media.
2. Open command prompt and change the directory to the newly copied migrate folder.
3. Enter the following command:
hpcabackup drive
where, drive is the drive label for the drive where you want to store the backup files. Ensure
that the drive contains free space to store the backup files. The script detects the space
available when it runs and estimates the required space. This is a personality extraction utility
and the space required is roughly as much as the currently installed size.
For example, to store the files on C: drive, enter the following command:
hpcabackup C
The currently installed version is detected and, if adequate space is available, the upgrade
process begins to store the backup files in C:\HPCABackup\HPCABackup directory.
Page 11 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 3: Upgrading HPCA Core Server
4. After the migration scripts identify the tasks that are to be completed to initiate the backup, the
HPCA-preview-report.html opens in the default web browser. On the command prompt,
press y to start the backup process.
5. After the backup tasks are completed, the command prompt displays the following message:
Info: Action completed
Info: Backup Completed Successfully
Press [ENTER] to end
Caution: Do NOT move the HPCABackup folder to another drive. If you move this folder, the
restore operation will not work.
Note: If the backup script is run again, a new backup folder is created. The
C:\HPCABackup\HPCABackup folder is renamed to a timestamp folder (for example,
C:\HPCABackup\HPCABackup-1263495101) and a new
C:\HPCABackup\HPCABackup folder is created.
6. The hpca-backup-report.html file opens in the default browser. Verify this file to
determine the tasks that were completed during the backup process. This file also directs you
to the respective logs that you must refer to, for an error or a warning message.
You must review all error and warning messages in this file, as these may indicate the need for
manual intervention to ensure that settings are migrated properly.
Step 2: Upgrade to the Latest Version
Note: The upgrade process will update the existing HPCA database. You should not remove the
existing database.
Note: The DSN information used to connect to MS SQL Server or Oracle databases must be the
same as that used in the previous installation for the migration to work correctly.
To upgrade to the latest version:
1. Run HPCACore.msi available in the Setup-Core directory on HP Client Automation 8.10
media. The HP Client Automation Core Installer window opens.
When the MSI runs, the installer detects an upgrade and prompts to confirm that you have read
the migration guide and completed the prerequisite backup steps before continuing.
Caution: Failure to complete the prerequisite backup steps before running the upgrade results
in data loss.
2. Click Next. The installer detects an upgrade and prompts you to confirm that you have read the
migration guide and completed the prerequisite backup steps before continuing.
3. Click Yes to continue with the upgrade. The HP Client Automation Core Installer window
opens.
4. Click Next. The HP Client Automation Software License Agreement page opens.
5. Review the HP Client Automation Core license terms, select I accept the license
agreement, and then click Next. The HP Client Automation Installation Folder page opens.
6. The Installation Folder page displays the default installation directory for the HPCA Core
server.
Accept the default location, or click Browse to select a different location, and then click Next.
The HP Client Automation Data Folder page opens.
Page 12 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 3: Upgrading HPCA Core Server
7. The Data Folder page displays the default directory for the HPCA Core server data files.
Accept the default location, or click Browse to select a different location, and then click Next.
The HP Client Automation Host Name page opens.
8. Select a name for this HPCA server and click Next. The HP Client Automation Server Ports
page opens.
9. Accept the default ports, or specify Web Server and Configuration Server ports, and then click
Next. The HP Client Automation Installation Confirmation page opens.
Caution: The installer provides an option to configure Windows Firewall to enable access to
the Web Server and Configuration Server ports (3466 and 3464, respectively). You
should clear this option during the install and then manually configure your firewall to
allow communication through these ports after the upgrade and restoration of the Core
is complete.
10. Click Next to start the installation.The existing installation is removed, and the new version is
installed.
11. Click Finish to complete the HP Client Automation Core server installation. The HPCA
Console automatically opens, and the login window is displayed in your default browser.
12. On the login window, specify the default user name, password, and directory source. The
default user name is admin and the password is secret.
13. Click Sign In. The First Time Setup Wizard opens, and prompts you for initial configuration
settings for your HPCA environment.
14. Close this browser window.
Caution: Do not run the First Time Setup Wizard. Your settings are automatically applied
during the upgrade process.
15. If you are prompted to reboot the server, click Yes to reboot.
Caution: If you do not reboot when prompted, files marked for deletion will not be handled
properly. It is imperative that you reboot immediately when prompted before
continuing any further.
Note: The HPCA Administrator is automatically installed with the 8.10 Core Server. If an existing
HPCA Administrator was installed, it will be upgraded to the latest version. To upgrade an
HPCA Administrator on another device, see the "Upgrading HPCA Administrator" (on page
18).
Step 3: Restore HPCA Data
After you have upgraded to the latest version, restore your existing data into the new environment.
To restore HPCA data:
1. From the migrate folder that you created in "Step 1: Backup the Existing HPCA Core Server
Installation" (on page 11), run hpcarestore.cmd followed by the drive letter on which you
stored the backup files in Step 1, above. For example, to restore the files from C:, type:
hpcarestore C
2. After the script identifies the restore tasks to be completed, the file HPCA-previewreport.html opens in the default web browser. Review this preview report. Do not continue
with the restore operation unless you carefully review any actionrequired messages in the
preview report.
Page 13 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 3: Upgrading HPCA Core Server
n
You must review the changes required for the rcs module. The rcs migration logic detects
any customizations you have made to the CSDB class schema and attempts to merge
these forward. If CSDB class schema customizations are identified, an actionrequired
message is generated for the rcs module. The ZEDMAMS script is generated to migrate
these CSDB customizations forward. The scripts can be located in the
\HPCABackup\HPCABackup\rcs\database\CLIENT\ directory. Each such script
should be manually reviewed and, if necessary, modified before continuing with the restore
operation.
n
The preview report contains an actionrequired message for the Policy Server with the
description "Policy Server processing and configuration settings has
been changed since the version you are migrating from, please
refer to the migration documentation for additional information
on new policy server operation".
The directory services configured in HPCA environment for policy management are
automatically mounted on Policy Server for policy resolution. During this process, a .cfg
file is created for each directory service. These configuration files include parameters used
to connect to the directory services and to perform policy resolution.
If you have not applied any customization to these configuration files in your environment,
ignore this message. However, if you have applied any manual changes to the default
Policy Server configurations, complete the following steps:
i. Compare the configuration files in the <InstallDir>\PolicyServer\etc\ldap
directory to the configuration files backed up from the previous installation to identify
the additional parameters for policy resolution on a specific directory service.
ii. Manually add the additional parameters in the overrides section of the individual
configuration file.
Note: Before continuing with the restore operation, you must review the SUBNET_CREATE_
INSTANCES.txt file located at
C:\HPCABackup\HPCABackup\rcs\database\CLIENT\ for all the connections to
the newly created subnets to ensure that the correct subnets are created after successful
migration.
3. After reviewing the preview report, type y to continue with the restore operation.
The data stored in the HPCABackup folder is migrated into the new HPCA environment.
If a failure occurs during restore, a subsequent restore attempts to start where it left off. To
perform a fresh restore, you must remove the HPCA-restore* files from the HPCABackup
folder.
4. The hpca-restore-report.html file opens in the default web browser. Review the file to
determine what occurred during the restore process.
It is important to review all warning messages that occur, as these may indicate the need for
manual intervention to ensure that settings are properly migrated.
It is common to receive warnings during execution of the “rms” component when migrating from
version 7.50 – the problems indicated by these warnings will be corrected when you run
sqlmigrate in "Step 4: Migrate the HPCA SQL/Oracle Database" (on page 14).
Step 4: Migrate the HPCA SQL/Oracle Database
Caution: This step is not required when migrating from version 7.80 or 7.90. It is required when
migrating from version 7.50. If you already have a FOREIGN KEY CONSTRAINT set to
Page 14 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 3: Upgrading HPCA Core Server
the DEVICECONFIG.DEVICE_ID column on Inventory database tables, you can skip
this step.
Caution: This step should only be performed by an experienced HPCA database administrator.
After you have upgraded your HPCA Core Server to the latest version and restored your data, you
must migrate the HPCA database. This involves the following steps:
l
Export the contents of specific database tables
l
Drop these tables
l
Re-create these tables
l
Import the data into the updated table structure
You can use the sqlmigrate script to perform these steps, or they can be performed manually (see
"Migrating the HPCA SQL/Oracle Database Manually" (on page 30)).
To migrate the HPCA database:
1. Stop the HPCA Core service.
2. In your local copy of the migrate folder, change to the sql folder. For example: cd
C:\migrate\sql
3. Run the following command:
sqlmigrate DriveLetter
Here, DriveLetter is the drive where the script will store exported data and any error information
generated during the subsequent import. Data is stored here:
DriveLetter:\HPCABackup\SQLMigrate
Note: Be sure that ample free space is available on this drive
Note: For large databases, this migration step can take many hours.
Note: If the sqlmigrate script is run again, a new data folder is created:
DriveLetter:\HPCABackup\SQLMigrate-timestamp
where timestamp indicates when the data folder was created.
4. Examine the contents of the C:\HPCABackup\SQLMigrate\errors folder to ensure that
the migration was successful. If errors occurred during the migration of a particular table, the
following files are created in this folder.
n tablename.log contains the insert statement and any errors that occurred
n
tablename.tsv contains the rows (if any) that failed to import
n
tablename.sql is a SQL Script of any insert statements that failed
where tablename corresponds to the name of the pertinent database table.
Examine these files to determine if you need to perform any manual restoration of data.
See "SQL Database Tables that must be Migrated" (on page 25) for a list of the tables migrated
by the sqlmigrate script.
5. Restart the HPCA Core service.
Page 15 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 3: Upgrading HPCA Core Server
Step 5: Log in to the Core Console
To log in to the updated console, use a browser and go to:
http://HPCA_host:3466
Where HPCA_host is the server’s host name.
You can now enable remote access to the Core’s Web Server and Configuration Server ports.
After the Core has been upgraded, you will need to upgrade any deployed components. See
"Upgrading Deployed Components" (on page 17) for details.
Step 6: Update Core Configuration and Content
Following the restore of the Core, perform the following actions prior to upgrading the deployed
components.
Update HP Live Network Content
Perform a full HP Live Network update to ensure that all of your service content is current.
Since the services offered through HP Live Network may have changed since you last configured it
through the HPCA Console, it is highly recommended that you validate your configuration before
performing an update.
To configure your HP Live Network connection, in the HPCA Console, go to Configuration >
Infrastructure Management > Live Network.
Unless directed otherwise by a support engineer, use the version of the Live Network Connector
that is installed with HPCA.
To update your HP Live Network content, go to Operations > Infrastructure Management > Live
Network
Note: After migration, you might receive script exception error when accessing the Connections
tab under Core Console > Configuration > Infrastructure Management > Satellite
Management > Satellite Server > Locations > Location Details. To resolve this issue,
contact HP Technical Support.
Page 16 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 4: Upgrading Deployed Components
Upgrading Deployed Components
Use these instructions to upgrade HPCA Standard or Starter components that were deployed to
devices in your environment.
The following sections describe how to upgrade Enterprise deployed components:
l
"Upgrading HPCA Agent" (on page 17)
l
"Upgrading HPCA Administrator" (on page 18)
l
"Upgrading Satellite Servers" (on page 18)
Note: Upgrading deployed components requires that you first upgrade the HPCA Server, as
described in "Upgrading HPCA Core Server" (on page 11).
These sections also contain pointers to any appropriate component-specific migration guides. All
migration guides are stored on the HPCA media.
Upgrading HPCA Agent
To upgrade the HPCA Agent:
1. Use the Agent Deployment Wizard to deploy the latest HPCA Agent to all managed devices.
The new HPCA Agent installation will upgrade the existing agent to the latest version.
2. Use the Reporting tab to verify that the HPCA Agent was upgraded. The version 8.10 HPCA
Server deploys a version 8.10 Agent.
A filter is available in Search Options > Data Filters > Inventory Management Filters >
Operational Filters > HPCA Agent Version
If you upgraded an HPCA Agent without using the HPCA console to deploy the latest version, you
will need to enable self-maintenance for upgraded HPCA Agents to receive the latest rma.tkd.
To enable self-maintenance for upgraded agents:
1. Create the following directory:
<InstallDir>\Media\extended_infrastructure\management_agent\rma
In this case, InstallDir is the location where you originally installed HPCA. By default, this is
C:\Program Files\Hewlett-Packard\HPCA.
2. Copy the following file into the directory that you just created:
<InstallDir>\Media\client\default\win32\rma\rma.tkd
3. Obtain the build number for rma.tkd by running the following command:
C:\Program Files\Hewlett-Packard\HPCA\ManagementPortal\nvdkit-hpcarmp.exe version rma.tkd
4. Create a text file called selfmaintenance with the following parameters and values:
criticalRMABuildNum rma_build
expectedRMABuildNum rma_build
proactiveupgrade 0
where rma_build is the build number that you found in step 3.
Page 17 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 4: Upgrading Deployed Components
Do not use tab characters to separate parameters and values. Also, the filename should not
contain an extension (for example .txt).
5. Place the selfmaintenance file in the following HPCA installation directory:
InstallDir\Media\extended_infrastructure\management_agent\
Upgrading HPCA Administrator
Caution: The HPCA Agent upgrade will remove a previous version of the HPCA Administrator if
one is installed on the device.
The HPCA Administrator is automatically installed during the 8.10 HPCA Core installation. If an
existing HPCA Administrator is present during the HPCA Core installation, it is updated during the
installation process.
To upgrade the HPCA Administrator on a device other than the Core server, first remove the
existing version of the HPCA Administrator installed on the device. You can upgrade to the latest
version of the HPCA Administrator in the following two ways:
l
l
Use the HPCA Administrator installation files for Windows, Linux, and Macintosh operating
systems to upgrade the HPCA Administrator.
n For Windows: Run setup.exe, the HPCA Administrator installation command located in
the \Setup-Core\Media\admin\default\win32 directory on the HPCA installation
media.
n
For Linux: Remove the existing HPCA Administrator and run the ./install command
from the \Setup-Core\Media\admin\default\linux directory.
n
For Macintosh: Remove the existing HPCA Administrator and run the sudo ./install
command from the \Setup-Core\Media\admin\default\macx86 directory.
Deploy the HPCA_ADMINTOOLS service to the managed device from the HPCA Core
Console. You must upgrade the HPCA Agent installed on the device before deploying the
HPCA_ADMINTOOLS service.
Caution: If you are migrating from a version prior to 7.90, do not deploy the legacy CCM_
PUBLISHER service in a 8.10 environment. This service could be deleted from the
CSDB as it is no longer needed.
Upgrading Satellite Servers
HPCA Satellite Server 8.10 consists of Apache Server Data Cache and Integration Server-based
Proxy Server components. The Apache Server Data Cache is used to store Patch Manager
Gateway (Patch MGR) binaries. The Integration Server-based Proxy Server Data Cache is used to
store CSDB resource data. Example, Software, OS Manager, Audit, and Security data. You can
upgrade the Satellite Servers manually or through HPCA Console.
l
Upgrading Satellite Server Manually
l
Upgrading Satellite Server through HPCA Console
Note: Before synchronizing the Satellite server with its Core server, you must restart the
Messaging service on the Satellite server.
Page 18 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 4: Upgrading Deployed Components
Upgrading Satellite Server Manually
Step 1: Backup the Existing Satellite Server Installation
Backup the existing HPCA Satellite installation to prepare for the upgrade.
To back up the existing HPCA Satellite installation:
1. From the HPCA media, copy the \Setup-Satellite\migrate folder to a temporary
location on the HPCA Satellite Server (for example, C:\migrate).
You must copy this folder to a temporary location since the migration scripts cannot be run
directly from the HPCA media.
2. Open command prompt and change the directory to the newly copied migrate folder.
3. Enter the following command:
hpcabackup drive
where, drive is the drive label for the drive where you want to store the backup files. Ensure
that the drive contains free space to store the backup.
For example, to store the files on C: drive, enter the following command:
hpcabackup C
The currently installed version is detected and, if adequate space is available, the upgrade
process begins to store the backup files in C:\HPCABackup\HPCABackup
4. After the migration scripts identify the tasks that are to be completed to initiate the backup, the
HPCA-preview-report.html opens in the default web browser. On the command prompt,
press y to start the backup tasks.
5. After the backup tasks are completed, the command prompt displays the following message:
Info: Action completed
Info: Backup Completed Successfully
Press [ENTER] to end
Caution: Do NOT move the HPCABackup folder to another drive. If you move this folder, the
restore operation will not work.
Note: If the backup script is run again, a new backup folder is created. The
C:\HPCABackup\HPCABackup folder is renamed to a timestamp folder (for example,
C:\HPCABackup\HPCABackup-1263495101) and a new
C:\HPCABackup\HPCABackup folder is created.
6. The hpca-backup-report.html file opens in the default browser. Verify this file to
determine the tasks that were completed during the backup process.
It is important to review all warning messages in this file, as these may indicate the need for
manual intervention to ensure that settings are migrated properly.
Step 2: Upgrade to the Latest Version
Run the latest HPCA Satellite MSI installer to upgrade to the latest version.
To upgrade to the latest version:
Page 19 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 4: Upgrading Deployed Components
1. Run HPCASatellite.msi available in the Setup-Satellite directory on HP Client
Automation 8.10 media. The HP Client Automation Satellite Installer window opens.
2. Click Next. The installer detects an upgrade and prompts you to confirm that you have read the
migration guide and completed the prerequisite backup steps before continuing.
3. Click Yes to continue with the upgrade. The HP Client Automation Satellite Installer window
opens.
4. Click Next. The HP Client Automation Software License Agreement page opens.
5. Review the HP Client Automation Satellite license terms, select I accept the license
agreement, and then click Next. The HP Client Automation Installation Folder page opens.
6. The Installation Folder page displays the default installation directory for the HPCA Satellite
server.
Accept the default location, or click Browse to select a different location, and then click Next.
The HP Client Automation Data Folder page opens.
7. The Data Folder page displays the default directory for the HPCA Satellite server data files.
Accept the default location, or click Browse to select a different location, and then click Next.
The HP Client Automation Host Name page opens.
8. Select a name for this HPCA server and click Next. The HP Client Automation Server Ports
page opens.
9. Accept the default ports, or specify Web Server and Configuration Server ports, and then click
Next. The HP Client Automation Installation Confirmation page opens.
Caution: The installer provides an option to configure Windows Firewall to enable access to
the Web Server and Configuration Server ports (3466 and 3464, respectively). You
should clear this option during the install and then manually configure your firewall to
allow communication through these ports after the upgrade and restoration of the
Satellite is complete.
10. Click Next to start the installation.The existing installation is removed, and the new version is
installed.
11. Click Finish to complete the HP Client Automation Satellite server installation.The Windows
Security login window opens in your default browser.
12. On the login window, specify the default user name, password, and directory source. The
default user name is admin and the password is secret.
13. Click OK. The First Time Setup Wizard opens, and prompts you for initial configuration
settings for your HPCA environment.
14. Close this browser window.
Caution: Do not run the First Time Setup Wizard. Your settings are automatically applied
during the upgrade process.
15. If you are prompted to reboot the server, click Yes to reboot.
Caution: If you do not reboot when prompted, files marked for deletion will not be handled
properly. It is imperative that you reboot immediately when prompted before
continuing any further.
Page 20 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 4: Upgrading Deployed Components
Step 3: Restore HPCA Data
After you have upgraded to the latest version of the Satellite, restore your existing data into the new
environment.
To restore HPCA data:
1. From the migrate folder that you created in "Step 1: Backup the Existing Satellite Server
Installation" (on page 19), run hpcarestore.cmd followed by the drive letter on which you
stored the backup files in Step 1, above. For example, to restore the files from C:, type:
hpcarestore C
2. After the script identifies the restore tasks to be completed, the file HPCA-previewreport.html opens in the default web browser. Review this preview report.
3. After reviewing the preview report, type y to continue with the restore operation.
The data stored in the HPCABackup folder is migrated into the new HPCA environment.
If a failure occurs during restore, a subsequent restore attempts to start where it left off. To
perform a fresh restore, you must remove the HPCA-restore* files from the HPCABackup
folder.
4. The hpca-restore-report.html file opens in the default web browser. Review the file to
determine what occurred during the restore process.
It is important to review all warning messages that occur, as these may indicate the need for
manual intervention to ensure that settings are properly migrated.
Note: HPCA resource data is converted from Apache format to the classic Proxy Server
format and moved to the Proxy Server Data location during the restore process. For
example, after restore process is complete, the converted HPCA resource data is copied
to the following directory:
C:\Program Files\Hewlett-Packard\HPCA\Data\ProxyServer\static
Step 4: Synchronize Satellite
Note: Before synchronizing the Satellite server with its Core server, you must restart the
Messaging service on the Satellite server.
After you migrate a Satellite server, you must synchronize it with its Core server.
To synchronize a Satellite server:
1. On the Satellite server, open a browser, and go to the following URL to open the HPCA user
interface:
http://localhost:3466
2. Login as admin.
3. On the Operations tab, click Server Status.
4. Click Synchronize satellite now.
You have now successfully migrated your Satellite Server.
Upgrading Satellite Server through HPCA Console
To upgrade your existing Satellite Server:
Page 21 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 4: Upgrading Deployed Components
1. On the Configuration tab in HPCA Console, go to the Infrastructure Management, Satellite
Management area.
2. Click the Servers tab.
3. Select the device on which you want to upgrade the Satellite Server in the Satellite Servers list.
4. Click the Install the Satellite Server toolbar button to launch the wizard.
5. Enter the User ID and Password to be used for deployment. This account must have
administrator-level access on the target device.
6. Click Next. The Properties window opens.
7. Select the Installation Drive, and Data Drive, and Deployment Mode. For HPCA Standard and
Starter Editions, only Streamlined (Standard) deployment mode is available. This mode offers
only data caching services to the Client Automation agents that the satellite serves.
8. Click Next. The Schedule window opens.
9. Specify the run schedule for the deployment job. Select Run: Now to deploy the Satellite
Server right away, or select Run: Later to schedule a date and time for deployment.
10. Click Next. The Summary window opens.
11. Review the summary information
12. Click Submit.
13. A Satellite Server Deployment job is created.
The Satellite Server download file is large. The deployment may take a long time if network
traffic is heavy. You can check the status of the job in the Jobs Management area on the
Management tab.
14. Click Close to exit the wizard.
Note: After a successful Satellite Server upgrade, HPCA resource data is converted from Apache
format to classic Proxy Server format and moved to the Proxy Server Data location. For
Example,
C:\Program Files\Hewlett-Packard\HPCA\Data\ProxyServer\static
Page 22 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 5: Upgrading Proxy Servers
Upgrading Proxy Servers
In classic versions of HPCA, a Integration Server-based Proxy Server was employed. In HPCA
Core-Satellite 7.xx versions, an Apache-based Proxy Server is used as a part of Satellite Server.
HPCA Satellite Server 8.10 consists of Apache Server Data Cache and Integration Server-based
Proxy Server components. The Apache Server Data Cache is used to store Patch Manager
Gateway (Patch MGR) binaries. The Integration Server-based Proxy Server Data Cache is used to
store CSDB resource data. Example, Software, OS Manager, Audit, and Security data. You can
upgrade a classic Proxy Server to Satellite Server manually or through HPCA Console.
l
Upgrading Proxy Server to Satellite Server Manually
l
Upgrading Proxy Server to Satellite Server through HPCA Console
Upgrading Proxy Server to Satellite Server Manually
To upgrade the classic Proxy Server (RPS) to the Satellite Server:
1. Copy the \Setup-Satellite\Media\satellite\win32 folder from HP Client
Automation 8.10 media to a temporary location on RPS system. Example C:\Temp
2. Navigate to the media\satellite\ folder in the temporary location.
3. Run the following command:
migrate-satellite-unattended.cmd [-proxyserver-cache-dir] [logfile] -install-satellite true
where
- proxyserver-cache-dir: is the target Proxy Server cache directory. This parameter is
required. Example: C:\Program Files\HewlettPackard\HPCA\Data\ProxyServer
- logfile: is full path and file name of the log to which messages will be written. This
parameter is optional. Example: C:\temp\proxy-migration.log
-install-satellite [true|false]: specifies if the Satellite Installer should be
launched after any necessary cache migration is completed. Default is True.
A sample command
migrate-satellite-unattended.cmd -proxyserver-cache-dir "C:\Program
Files\Hewlett-Packard\HPCA\Data\ProxyServer" -logfile
"C:\temp\proxy-migration.log" -install-satellite true
4. After you upgrade to the Satellite server, you must synchronize it with its Core server. Before
synchronizing the Satellite Server, you must run the First Time Setup Wizard to apply settings
for the Satellite Server.See the Synchronize Satellite section for more details.
Note: After a successful upgrade from Proxy Server to Satellite Server, HPCA resource data is
moved to the Proxy Server Data location. For Example,
C:\Program Files\Hewlett-Packard\HPCA\Data\ProxyServer\static
C:\Program Files\Hewlett-Packard\HPCA\Data\ProxyServer\dynamic
Page 23 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 5: Upgrading Proxy Servers
Upgrading Proxy Server to Satellite Server through HPCA
Console
Use the Satellite Server Deployment Wizard to upgrade the Classic Proxy Server (RPS) and
enable remote services, such as data caching.
To upgrade the Proxy Server:
Task 1: Add the Proxy Server to the Core and Satellite Servers group.
For information on how to add a device to the Core and Satellite group, see the Add a Satellite
Server section in the HP Client Automation Core and Satellite Standard Edition User Guide or the
HP Client Automation Core and Satellite Starter Edition User Guide.
Task 2: Upgrade the Proxy Server
1. On the Configuration tab, go to the Infrastructure Management, and then click Satellite
Management.
2. Click the Servers tab.
3. Select the Proxy Server system that you added to the Core and Satellite Servers group in Task
1.
4. Click the Install the Satellite Server toolbar button to launch the wizard.
5. Enter the User ID and Password to be used for deployment. This account must have
administrator-level access on the target device.
6. Click Next. The Properties window opens.
7. Select the Installation Drive, and Data Drive, and Deployment Mode. For HPCA Standard and
Starter Editions, only Streamlined (Standard) deployment mode is available. This mode offers
only data caching services to the Client Automation agents that the satellite serves.
8. Click Next. The Schedule window opens.
9. Specify the run schedule for the deployment job. Select Run: Now to deploy the Satellite
Server right away, or select Run: Later to schedule a date and time for deployment.
10. Click Next. The Summary window opens.
11. Review the summary information
12. Click Submit.
13. A Satellite Server Deployment job is created.
The Satellite Server download file is large. The deployment may take a long time if network
traffic is heavy. You can check the status of the job in the Jobs Management area on the
Management tab.
14. Click Close to exit the wizard.
Note: After a successful upgrade from Proxy Server to Satellite Server, HPCA resource data is
moved to the Proxy Server Data location. For Example,
<InstallDir>\Data\ProxyServer\static
<InstallDir>\Data\ProxyServer\dynamic
Page 24 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 6: SQL Database Tables that must be Migrated
SQL Database Tables that must be Migrated
The following tables have had schema changes that require the tables to be re-created to generate
the correct primary and foreign keys for HPCA version 8.10. This process is performed
automatically by the sqlmigrate.cmd script.
rWin32_WinSAT
rWin32_VideoController
rWin32_UserAccount
rWin32_USBController
rWin32_TimeZone
rWin32_SystemEnclosure
rWin32_SystemDriver
rWin32_StartupCommand
rWin32_SoundDevice
rWin32_SoftwareFeature
rWin32_SoftwareElement
rWin32_Share
rWin32_Service
rWin32_SerialPort
rwin32_quickfixengineering
rWin32_Product
rWin32_Processor
rWin32_Process
rWin32_Printer
rWin32_PortResource
rwin32_portablebattery
rWin32_PointingDevice
rWin32_PnPEntity
rWin32_PhysicalMemory
rWin32_ParallelPort
rWin32_PageFileUsage
rWin32_PageFileSetting
rWin32_PageFile
rWin32_OperatingSystem
Page 25 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 6: SQL Database Tables that must be Migrated
rWin32_NetworkLoginProfile
rWin32_NetworkConnection
rWin32_NetworkAdapterConf
rWin32_NetworkAdapter
rWin32_MotherboardDevice
rWin32_MemoryDevice
rWin32_MemoryArray
rWin32_LogicalProgramGroup
rWin32_LogicalMemoryConf
rWin32_LogicalDisk
rWin32_LoadOrderGroup
rWin32_Keyboard
rWin32_IRQResource
rWin32_IDEController
rWin32_Group
rWin32_FloppyDrive
rWin32_FloppyController
rWin32_Environment
rWin32_DMAChannel
rWin32_DisplayControllerConf
rWin32_DisplayConf
rWin32_DiskPartition
rWin32_DiskDrive
rWin32_DeviceMemoryAddress
rWin32_DesktopMonitor
rWin32_Desktop
rWin32_ComputerSystemProduct
rWin32_ComputerSystem
rWin32_CDROMDrive
rWin32_CacheMemory
rWin32_Bus
rWin32_BootConf
rWin32_BIOS
Page 26 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 6: SQL Database Tables that must be Migrated
rwin32_baseboard
rWiFi_NetworkAdapter
rRegistry
rNVD_WBEMStatus
rNVD_UserAccount
rNVD_SolarisPatch
rNVD_Product
rNVD_PDASystem
rNVD_NISUserAccount
rNVD_NISGroupAccount
rNVD_MulticastStatistics
rNVD_INSTALLED_UNINSTALL
rNVD_INSTALLED_APPS
rNVD_GroupMember
rNVD_GroupAccount
rNVD_DownloadStatistics
rMSSD_FailurePredictStatus
rMSSD_AttributeData
rhp_biosstring
rhp_biossensor
rhp_biospassword
rhp_biosorderedlist
rhp_biosinteger
rhp_biosevent
rhp_biosenumeration
rCIM_UnixOperatingSystem
rCIM_UnixLocalFileSystem
rCIM_UnixComputerSystem
rCIM_StorageVolume
rCIM_SoftwareFeatureElements
rCIM_SoftwareFeature
rCIM_SoftwareElement
rCIM_Service
Page 27 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 6: SQL Database Tables that must be Migrated
rCIM_SCSIInterface
rCIM_SCSIController
rCIM_ResidesOnExtent
rCIM_ProductSoftwareFeatures
rCIM_Product
rCIM_Processor
rCIM_Process
rCIM_ParallelController
rCIM_OperatingSystem
rCIM_NFS
rCIM_MediaPresent
rCIM_LogicalDiskBasedOnVolume
rCIM_LogicalDisk
rCIM_IDEController
rCIM_HPUX_SwBundles
rCIM_Export
rCIM_EthernetAdapter
rCIM_DVDDrive
rCIM_DiskDrive
rCIM_Directory
rCIM_ComputerSystem
rCIM_CDROMDrive
DeviceUserGroup
SMBiosInfo
Query
DeviceNotify
FileAudit
DeviceZRStates
DeviceZRState
DeviceSynopsis
HDeviceStatus
DeviceStatus
HDeviceState
Page 28 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 6: SQL Database Tables that must be Migrated
DeviceState
DeviceServices
DeviceMap
HDeviceErrors
DeviceErrors
Audit_Type
Audit_Attrs
Audit_Event
Audit_Cat
Audit_AttrNames
HAppEvent
AppEvent
HAppRNPEvent
AppRNPEvent
HAppMSIEvent
AppMSIEvent
JOBTASK
HJOBSTAT
JOBSTAT
JOBPARM
ADInfo
HDeviceConfig
DeviceConfig
Page 29 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
Chapter 6: Migrating the HPCA SQL/Oracle Database Manually
Migrating the HPCA SQL/Oracle Database Manually
Caution: This step is not required when migrating from version 7.80 or 7.90. It is required when
migrating from version 7.50. If you already have a FOREIGN KEY CONSTRAINT set to the
DEVICECONFIG.DEVICE_ID column on Inventory database tables, you can skip this step.
Instead of using the sqlmigrate.cmd script, you can migrate the HPCA SQL database manually
after restoring your data.
Caution: This process should be performed only by an experienced HPCA database administrator.
The database tables listed in "SQL Database Tables that must be Migrated" (on page 25) have had
schema changes that require the tables to be re-created to generate the correct primary and foreign
keys. Data from these tables should be exported or stored in temporary tables prior to beginning the
manual migration process. To migrate the HPCA SQL database manually:
1. On the system hosting the HPCA Core, stop the HPCA Core service.
2. Export (or store in temporary tables) the data in the tables listed in "SQL Database Tables that
must be Migrated" (on page 25).
3. Drop the tables listed in "SQL Database Tables that must be Migrated" (on page 25) .
Caution: The order is important – drop the tables in the SAME order shown in "SQL Database
Tables that must be Migrated" (on page 25).
4. Restart the HPCA Messaging Server service (to re-create the table schema).
5. Re-import your data into the tables.
Caution: The order is important – import the data in the REVERSE order shown in "SQL
Database Tables that must be Migrated" (on page 25).
During the import process, data that violates database integrity will not be imported. Be sure to
review this data to determine if it is still valid and still needed.
6. Start the HPCA Core service.
Page 30 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
We appreciate your feedback!
We appreciate your feedback!
If an email client is configured on this system, by default an email window opens when you click
here.
If no email client is available, copy the information below to a new message in a web mail client,
and then send this message to docfeedback@hp.com.
Product name and version: HP Client Automation Starter and Standard Edition, 8.10
Document title: Migration Guide
Feedback:
Page 31 of 32
HP Client Automation Starter and Standard Edition (8.10)
Migration Guide
We appreciate your feedback!
Page 32 of 32
HP Client Automation Starter and Standard Edition (8.10)