Upgrade Guide › Migrating PMDs to an Advanced Policy Management Environment › How the Migration Process Works › How Policies Are Initially Sent to a Migrated Endpoint

How Policies Are Initially Sent to a Migrated Endpoint

When you migrate from a PMD environment to an advanced policy management environment, CA ControlMinder creates policies from the rules in the PMDB and sends them to the migrated endpoints. Understanding how CA ControlMinder initially sends the policies to the migrated endpoint may help you troubleshoot any errors that occur during the migration process.

The following process explains how policies are initially sent to a migrated endpoint after you start CA ControlMinder on the endpoint:

1. CA ControlMinder starts and invokes policyfetcher, which sends a heartbeat notification to the DMS.
2. The DMS receives the heartbeat notification and checks if a corresponding host (HNODE) object exists on the DMS.
3. One of the following happens:
   • If a corresponding host exists on the DMS, and the host is part of the host group that corresponds to the PMD that you migrated:
     1. CA ControlMinder associates the endpoint and the host.
     2. CA ControlMinder deploys the policies that are assigned to the host group to the endpoint.
   • If a corresponding host does not exist on the DMS:
     1. CA ControlMinder creates the host.
     2. When you create and assign policies, CA ControlMinder joins the host to the host group that corresponds to the PMD that you migrated.
     3. CA ControlMinder deploys the policies that are assigned to the host group to the endpoint.
4. CA ControlMinder modifies the Update Time property for each resource listed in the policy to the time the policy was deployed.

   Note: Because CA ControlMinder changed commands that create objects to commands that modify objects, you should not see any deployment errors for the policy.

Note: For more information about policies and host groups, see the Enterprise Administration Guide.