Knowledge Base

Our dedicated Product Specialist team is always ready to help you when you need it the most. Contact Support

Specops Password Sync

Password does not synchronize for admin account

Specops Password Sync by default will not synchronize password changes for privileged accounts. This default behavior is good security practice. You may see the following message in the Windows Application event logs on domain controllers when attempting to sync admin account passwords: Password will not be synchronized for user ‘username’ because the user is member...

Unable to remove Sync Servers

When removing a Sync Server from the Sync Scopes list, you may encounter the following error: The selected server(s) cannot be removed from the sync scope because they are being used in one or more sync points. Remove the references to the servers from the sync points first Edit each sync point under the sync...

Troubleshooting Specops Password Sync syncing issues.

First to start let’s take a look at the required installed pieces that make up Specops Password Sync: Required Installs: Specops Password Sync Server This should be installed on a Windows Server. Handles the syncing over to your destination sync point. Specops Password Sync Notifier This is required to be installed on all writeable Domain...

Updating the Specops Password Sync Server Certificate

Specops Password Sync Server service uses a self-signed certificate to encrypt traffic sent to it by the Password Sync Notifier Filter Service on your domain controllers. This certificate should be renewed prior to expiration in order to prevent communication issues between the domain controller notifiers and the sync server. Identify the Certificate Currently In Use...

Referral Error When Adding a Password Sync Server

When adding a new Password Sync server (either manually or via the Password Sync setup wizard) you may encounter the following error: This error indicates an issue writing an SPN for the server’s computer account in Active Directory. Administrators can work around this issue by manually creating the SPNs in Active Directory. Run the following...