Migrate from HTTPS to DCE

Where possible you should deploy the HTTPS agent on your managed nodes. Nevertheless, you can migrate from the HTTPS agent to the DCE agent if necessary.

When you migrate from the HTTPS agent to the DCE agent, the management server removes all existing policies, instrumentation and packages from that node. After it deploys the DCE agent packages, the management server then redeploys the policies, and the packages and instrumentation that the policies require. However, if any of the policies require the HTTPS agent, the deployment jobs for those policies will fail.

It is not possible to deploy the DCE agent to nodes with a UNIX or Linux operating system using the console. You must install the DCE agent manually on these nodes.

Caution:
When you migrate from an HTTPS agent to a DCE agent, you lose all data that the DCE agent stores locally, including performance data and custom configuration settings. If appropriate, back up this data and reconfigure it after you migrate to the DCE agent.

NOTE:
The HTTPS agent enables multiple management servers to configure the same node. This is not possible with the DCE agent. If other management servers are currently managing the node, they do not receive a notification when you migrate to the DCE agent. If deployment jobs exist on other management servers for this node, they will fail. Ensure that the node is removed from other management servers before or after migrating to the DCE agent. You can then add the node again with the communication type set to DCE.

To migrate from an HTTPS agent to a DCE 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 Comm Type and then select DCE.
4. 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).

     The node 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.

5. Optional. Select or clear the Run prerequisites check automatically during job execution check box. If you are sure that the nodes meet all prerequisites, you can clear this check box so that the agent installation jobs complete more quickly. (This check box is dimmed if an administrator disables all prerequisite checking using the Server Configuration dialog.)
6. Click OK. The management server creates all the necessary deployment jobs.

Related Topics:

• Manual installation of DCE agents
• Generic server configuration
• Restart job with new options