Changing a managed system policy’s service ID
Product administrators with the "Maintain servers and Manage managed system policies" administrative privileges can quickly change the service ID for any managed system policy in a replication environment. You might need to do this in a recovery scenario; for example, when a replication node goes offline and its responsibilities need to be moved to another service, but the offline server is unable to release the managed system policy.
Managed accounts (including account sets) and group sets are monitored by the managing node of the managed system policy in which they reside. Each managed system policy is linked to a Service ID of a managing node, which follows the format of <servername> _ <instance name> . Changing the service ID of a managed system policy moves the management responsibility to a new node. This change will affect privileged access currently checked out from that policy or checked out later on.
To change the service linked to a managed system policy :
Click Manage the system > Privileged access > Node assignments > Node assignments.
For the managed system policy you want to change, select its node.
Check the managed system policy you want to change, and click Select.
The page is displayed.
Select a new node using the New Privileged Access service drop-down menu.
Click one of the following:
Update: if the current managing node of the managed system policy is active, and can be contacted to transfer over responsibilities to the new service.
Force update: if the current managing node of the managed system policy is decommissioned and will not be used again. This option will immediately transfer over responsibilities to the new service.
If the managed system policy is already in the “releasing” state when you change the node, it stays in this state momentarily even after you change the node. This is because the “releasing” state is required to set the managed system policy into the “unbound” state so that it can be removed.