Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 6.0.10 LTS - Administration Guide

Introduction System requirements and versions Using API and PowerShell tools Using the virtual appliance and web management console Cloud deployment considerations Setting up Safeguard for Privileged Passwords for the first time Using the web client Getting started with the desktop client Using the desktop client Search box Privileged access requests Toolbox Accounts Account Groups Assets Asset Groups Discovery Entitlements Partitions Settings
Access Request settings Appliance settings Asset Management settings Backup and Retention settings Certificate settings Cluster settings External Integration settings Messaging settings Profile settings Safeguard Access settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP 2.7 or later migration guidance Appendix C: SPP and SPS join guidance Appendix D: Regular Expressions SPP glossary

System services did not update or restart after password change

If the system services do not update or restart after an automatic password change, first check your audit logs in the Activity Center.

NOTE: You can also check the Support bundle logs.

If the audit logs do not adequately explain the problem, then check the options on the Change password tab of the profile that governs the service account. For more information, see Creating a profile.

For service accounts that run system services or scheduled system tasks, verify the options on the profile's Change password tab that enable or disable automatic service update, or restart. You must update the Change Password Setting to change these options. For more information, see Change Password.

Test Connection failures

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.For more information, see Connectivity failures.

Disabling User Account Control (UAC) Admin Approval Mode on a remote host can also resolve Test Connection failures. For more information, see Change password fails.

The following topics explain some possible reasons that Test Connection could fail.

Test Connection failures on archive server

There could multiple reasons why you receive an Unexpected copying error... when attempting to run Test Connection on an existing archive server.

When you run Test Connection, Safeguard for Privileged Passwords adds a file named Safeguard_Test_Connection.txt to the Storage Path location of the archive server owned by the Account Name you entered when you created the archive server. To run Test Connection on an existing archive server with a new account name, you must first delete the existing Safeguard_Test_Connection.txt file.

Certificate issue

If you are experiencing Test Connection failures for an asset that uses SSL, these are some possible causes:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating