Migrate from DCE to HTTPS


If you have DCE agents installed on nodes in your environment, you can migrate to the HTTPS agent. For example, you may need to deploy a new policy that requires the HTTPS agent.

When you migrate a node from the DCE agent to the HTTPS agent, the management server removes all existing policies, instrumentation and packages from that node. After it deploys the HTTPS agent packages, it then redeploys the policies, and the packages and instrumentation that the policies require. If the node's policy inventory contains policies that are not available on the management server, the management server cannot redeploy these policies to the HTTPS agent. This can happen, for example, if the policy exists only on a different management server, or if the policy exists on the node but has been deleted from the management server.

When you migrate a DCE agent to an HTTPS agent, the installer migrates the following data:

NoteCaution:
When you migrate from a DCE agent to an HTTPS agent, you lose the following data from the DCE agent: If appropriate, back up this data and reconfigure it after you migrate to the HTTPS agent.

To migrate from a DCE agent to an HTTPS agent

  1. In the console tree, right-click Nodes, and then click ConfigurearrowNodes.... 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 HTTPS.
  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:
  6. 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.)
  7. Click OK. The management server creates all the necessary deployment jobs.
  8. While the change agent deployment job is in progress, the node requests a certificate. Policy and package deployment jobs start for each node only after this request is granted. If you did not configure automatic granting of certificates, you must grant the certificates manually. Otherwise, the policy and package deployment jobs fail.

Related Topics: