When you make any changes to policies by clicking New, Edit, or Remove on the page where the policies are listed, the Entitlements Service Driver is stopped. The driver is not restarted unless you click the Close button on that page.
This feature prevents the driver from granting or revoking entitlements in your production environment while your changes to policies are incomplete.
Similarly, the Entitlements Service Driver won't start if more than one person appears to be editing Entitlement Policies at the same time.
The Entitlements Service Driver won't start if the driver object is associated with more than one server. This configuration is not supported.
The Entitlement Policy grants entitlements on connected systems through a DirXML driver, and the driver is identified by the GUID of the driver object in eDirectory, not the name of the object. This means that if you replace a driver object with another driver object of the same name, the Entitlement Policy won't work for entitlements on that driver because the object has a new GUID.
Because one Entitlements Service Driver is used per driver set, an Entitlement Policy can manage only users that are in a read/write or master replica on the server that is associated with that driver set.