If you are unable to connect to a remote machine either through SSH or RDP, log in to the Safeguard for Privileged Passwords desktop client as an Appliance Administrator and check the Activity Center and logs for additional information.
If you are using the embedded sessions module, you may also check:
- Ensure that the Network Interface X1 is configured correctly (Administrative Tools | Settings | Appliance | Networking). If one or more Safeguard Sessions Appliances are joined to Safeguard for Privileged Passwords, X1 is not available in Safeguard for Privileged Passwords.
- Ensure that you have installed the Privileged Sessions module license. (Administrative Tools | Settings | Appliance | Licensing).
If you are unable to delete an account, review the considerations below.
Wrong account name:
As an Asset Administrator, you may receive this error if you attempt to delete an account : This entity has access requests which have not yet expired or have to be reviewed. It cannot be deleted now. This error could indicate that Safeguard for Privileged Passwords is trying to change the password on an account that does not exist on the asset.
One reason for this error message is that the wrong account name was used when adding the account to Safeguard. So now when someone requests the password for this account, Safeguard displays the password that was manually set. However, when the requester attempts to log in to the asset using the bad account and password, it will fail. If the access request policy specified Change password after check-in, the above error message appears when the administrator tries to delete the account from Safeguard for Privileged Passwords.
Workaround: To delete the account with the misspelled name, first manually set the password on the account. Once the account password is reset, Safeguard for Privileged Passwords will allow you to delete the account.
If you receive a message that says Cannot play session... The specified executable is not a valid application for this OS platform, you are most likely attempting to run the Desktop Player on a 32-bit platform, which is not supported.
If you add a directory user who has the User must change password at next logon option enabled in Active Directory, Safeguard for Privileged Passwords prevents that user from logging in. There are two ways to allow the directory user to log in to Safeguard for Privileged Passwords successfully:
- Have the directory user use his domain account to log in to an asset joined to Active Directory. When prompted he can change his password. This fulfills the User must change password at next logon requirement.
- Have the domain administrator disable the option in Active Directory for the directory user.