The following minimum permissions are required for Windows assets to perform directory password management and sessions management tasks using Windows Management Instrumentation (WMI).
Asset password management
Using a local account or domain account:
- (Only applies to Windows Desktop and Windows Server) Test connection, Check connection, Password check, and Account discovery tasks require the following permissions:
- Remote Enable permission on WMI's CIMV2 Namespace
- Enable Account permission on WMI's CIMV2 Namespace
-
Remote Activation permission on computer via DCOM.
To set Remote Enable and Enable Account permissions
- Open wmimgmt.msc.
- Right-click WMI Control (Local) and select Properties.
- Select the Security tab.
- Expand the Root node.
- Select the CIMV2 node.
- Click the Security button.
- Add user/group and select Remote Enable and Enable Account.
- Click OK.
To set Remote Activation permissions
- Open dcomcnfg.
- Expand Component Services | Computers.
- Right-click My Computer and select Properties.
- Open the COM Security tab.
- Under Launch and Activation Permissions, select Edit Limits.
- Add user/group and select Allow for Remote Activation.
- Click OK.
- Password change task requires the following permission:
- Member of Local Administrators group
Domain password management
Using a Domain account:
- Test connection, Check connection, Password check, and Account discovery tasks require the following permissions:
- Password change task requires that the Service account has the following delegated permissions:
Asset session access
Using a local account:
- Member of Remote Desktop Users group
- Defined in the "Allow log on through Remote Desktop Services" policy (directly or via group membership)
- Not defined in the "Deny log on through Remote Desktop Services" policy (directly or via group membership)
Using a Domain account:
- Defined in the Remote Desktop Users group or be a member of a domain security group by a group policy update to the Remote Desktop Users group for that asset
- Defined in the "Allow log on through Remote Desktop Services" policy (directly or via group membership)
- Not defined in the "Deny log on through Remote Desktop Services" policy (directly or via group membership)
There are so many possible root causes for a sick appliance. If you receive an error that the appliance is sick take the following steps.
- Check network connectivity between nodes.
- Wait (up to 30m) to see if the error resolves automatically.
- If the error persists, create a support bundle and contact support. For more information, see Support bundle.
Categories of appliance sick events by error message prefix
There are 6 categories for appliance sick events which can be distinguished by the error message prefix.
Audit Log is sick : <reason>
There is an error in the underlying audit log database. The reason will provide more details about the exact issue. Typically this is due to loss of consensus as a result of network connectivity. This may be the result of temporary network conditions and, if so, it will resolve automatically after a few minutes. If not, check network connectivity between Safeguard nodes. After ruling out network connectivity, generate a support bundle and contact Support. Do not reboot the appliance until consulting with Support. In some cases, rebooting the appliance can make the condition worse.
Access Request Workflow is sick : <reason>
There is an error in the underlying password workflow database. The reason will provide more details about the exact issue. Typically this is due to loss of consensus as a result of network connectivity. This may be the result of temporary network conditions and, if so, it will resolve automatically after a few minutes. If not, check network connectivity between Safeguard nodes. After ruling out network connectivity, generate a support bundle and contact Support.
Policy Data is sick : <reason>
There is an error in the underlying policy database. The reason will provide more details about the exact issue. Typically this occurs when a replica has lost network connectivity to the primary. This may be the result of temporary network conditions and, if so, it will resolve automatically after a few minutes. If not, check network connectivity between Safeguard nodes. After ruling out network connectivity, generate a support bundle and contact Support.
Cluster Connectivity is sick : <reason>
There is an error in the VPN connection between Safeguard nodes. The reason will provide more details about the exact issue. This may be the result of temporary network conditions and, if so, it will resolve automatically after a few minutes. If not, check network connectivity between Safeguard nodes on the public IP address since the VPN is tunneled over the public IP. After ruling out network connectivity, generate a support bundle and contact Support.
Appliance Resource Usage is sick : <reason>
A Safeguard process or underlying database is exhibiting unexpectedly high OS resource usage (CPU, Memory, Disk). The reason will provide more details about the exact issue. Restarting the appliance may resolve this issue. If the problem persists or recurs frequently, generate a support bundle and contact Support.
The most common causes of failure in
Safeguard for Privileged Passwords are either connectivity issues between the appliance and the managed system, or problems with service accounts.
Always verify network connectivity and asset power before troubleshooting.
The following topics explain some possible reasons that Check Password, Change Password, and Set Password may fail, and gives you some corrective steps you can take.