Installing and upgrading to HP Insight Software 6.0 on Windows Server 2003 R2 MSCS for high availability
19
Figure 7: HP Insight Control Management problem message
If this occurs, click “Close” and go back and restart from the above Step 5, “Run Integrated
Installer…”. The error should not occur on the second pass.
10. [ICG Steps 11–15] Continue to follow the Insight software installation instructions.
11. [ICG: Step 16] When prompted for the path to local data storage for HP Insight Dynamics
configuration management, capacity planning, and workload management applications, be sure
to specify a directory that is on the Insight software shared disk, V:\ in this paper.
12. [ICG: Steps 17–19] Continue to follow the Insight software installation instructions.
13. [ICG: Step 20] Verify that the items to install are correct and click Install. The installation of
Insight Software components is initiated.
REMINDER: The installation of Insight Software components will cause a reboot. Be sure the other
node of the cluster remains shutdown; otherwise, physical resources such as shared disks, SQL server,
etc., will failover to the other node resulting in a failed Insight Software installation.
14. [ICG: Steps 21–22] Follow the Insight software installation instructions to complete the
installation.
Install Insight software components on the secondary system
To have a clustered installation of HP Insight Software, you must complete the installation process on
the second system as well, with a few differences in the procedure to account for the existing program
files on the cluster disk.
IMPORTANT:
Be sure to specify the same user credentials and path information that you used on the primary
system.
1. Shutdown the primary node.
2. [ICG: Step 1] Start the secondary system and log into Microsoft Windows as a user with
administrator privileges.
Note: Be sure to log in with the same account used to install the Microsoft SQL Server 2005
Enterprise Edition instance.
3. Start the Cluster Administrator and ensure that the secondary system owns all of the clustered disks
and that the primary system is shut down.