Migrate from 32 bit to 64 bit

Agent packages in 64 bit format are available, which you can deploy to nodes that have 64 bit architectures and operating systems. You can also deploy agent packages in 32 bit format to some 64 bit nodes. For more information, see the support matrix at HP Software Support Online.

If you have 32 bit agent packages installed on nodes that have 64 bit architectures and operating systems, you can migrate to the 64 bit packages. When you do this, the management server removes all existing policies, instrumentation and packages from that node. After it deploys the 64 bit agent packages, it then redeploys the policies, and the packages and instrumentation that the policies require.

To migrate from a 32 bit agent to a 64 bit agent

1. In the console tree, right-click Nodes, and then click ConfigureNodes.... The Configure Managed Nodes dialog appears.
2. Right-click the node and then click Change agent. The Change Agent dialog appears.
3. Click Binary Format and then select an option. Agent packages in 64 bit format may not be available for all platforms.
4. Optional. Select the Auto Grant check box if you want the management server to automatically grant the certificate for this node. (This only happens if you also configure the management server to grant certificate requests automatically.)
5. Optional. Specify the credentials that the management server uses to deploy the agent. Right-click a node in the list, and then click Set Credentials. Click one of the following commands:

   • PMAD user. The management server attempts to deploy the agent as the user under which the policy management and deployment (PMAD) service runs (called HP-OVE-Deleg-User by default).

     You can only use this for nodes with a Windows operating system. The nodes can belong to the same domain as the management server, a trusted domain, or a workgroup.

     NOTE:
     The PMAD user does not by default have administrative access to the node. For more information, see Start Windows node security setup.

   • Impersonate user. The management server attempts to deploy the agent using the credentials that you are currently logged in to Windows with.

     You cannot use impersonation for nodes in untrusted domains or workgroups.

     You can use impersonation only if the PMAD user is trusted for delegation in Active Directory, unless your console runs directly on the management server. For more details on delegation, refer to the Active Directory documentation that Microsoft provides.

   • User/Password. The Credentials dialog box appears. Type the Username of a user who has permission to install software on the node and their Password. Click OK. This automatically selects the Deploy check box.

     For nodes with a UNIX or Linux operating system, this is the only command available. You can also use this command to install the HTTPS agent to Windows nodes that belong to the same domain as the management server, a trusted domain, or a workgroup.

6. Optional. Select or clear the Run prerequisites check automatically during job execution check box. You can clear this check box to save time if you are sure that the nodes meet all system requirements. (This check box is dimmed if an administrator disables all prerequisite checking using the Server Configuration dialog.)
7. Click OK. The management server creates all the necessary deployment jobs.

Related Topics:

• Configuring Certificates
• Generic server configuration
• Restart job with new options