Policy Guide › How Policy Works › Policy Version Numbers › Reported and Assigned Policy Versions

Reported and Assigned Policy Versions

When rolling out policy changes across your organization, it is important to understand the difference between reported and assigned policy versions.

Reported policy version

The version of a policy reported by a client machine to the CMS when it logs on to CA DataMinder.

Assigned policy version

The latest policy version held on the CMS. This version is automatically replicated to the relevant client machine at intervals determined in the CMS policy.

Why do reported and assigned versions differ?

This can happen if an administrator updates a user's policy while the user is not logged on to CA DataMinder. In this situation, the updated (or assigned) policy is held on the CMS but the old policy remains on the client machine. When the user next logs on to CA DataMinder, their client machine reports that it is using the old policy. Eventually, the discrepancy is eliminated when the assigned version of the policy replicates down from the CMS to the client machine.

Policy version mismatches can also occur if two people are logged on to separate client machines as the same user. In the Administration console, the policy versions shown for that user account are those of the person who connected most recently to the CMS. If an administrator then updates that user’s policy, the assigned policy is replicated down to the client machines. There may be a few seconds delay before the policy versions shown in an Administration console update to the latest version.

Note: You can view the reported and assigned policy versions for individual users in the Administration console. If a user is logged on to CA DataMinder, you can select the user and view their Open Session details in the right-hand pane. These include both policy versions.