Enzoic for Active Directory

Client Setup Instructions (new in 3.0)


Starting with version 3.0, Enzoic for Active Directory includes an optional Windows client application that can be deployed to domain-joined Windows workstations in your organization to provide users with better feedback and assistance when selecting a new password. The Windows client application augments the built-in Windows password change screen by adding text to indicate what your password requirements are and in the case of a rejected password change, additional details as to the reasons. For example, if a user’s password is rejected due to being a known compromised password, they will be informed of this fact and asked to select a different password.


NOTE: If you are running a 3rd party credential provider on your Windows workstations (to support multi-factor or biometric authentication, for example) the Enzoic Client will typically NOT work. These types of credential providers generally must make themselves the default and disable other credential providers on the system.

Download the Client Installer


The installer is available as an MSI to ease deployment via GPO. Microsoft .NET Framework 4.5 is required.

Links to download the most current version (Domain Controllers must all run the same version):

https://cdn.enzoic.com/files/EnzoicForADClient.msi (MD5: 10dd79b9f4cd9af06ed7e8fab9e0fc0d)

Read the current release notes.

Automated Deployment to Multiple Workstations via GPO


You can use GPO push installs to easily install the Enzoic for Active Directory Client to multiple user workstations.  Note that the Enzoic Client requires .NET Framework 4.5, which does not get installed automatically when running the MSI installer.

Steps for Pushing the Enzoic Client via GPO

Create a distribution point:

  1. Log on to the server you wish to use as a distribution host as an administrator.
  2. Create a shared network folder to distribute the files from.
  3. Give the “Domain Computers” security group read access to the share, and limit write access to authorized personnel only.
  4. Copy EnzoicForADClient.msi into the distribution point
  5. Give the “Domain Computers” security group read access to the EnzoicForADClient.msi
    file in the distribution point.
  6. Click Finish.

Create a Group Policy Object:

  1. Start the Group Policy Management Console (gpmc.msc).
  2. Expand the forest and domain items in the left pane.
  3. Right-click your domain in the left pane, and then click Create a GPO in this domain, and Link it here…. Note that by default this will deploy the Enzoic Client to all workstations in your domain. If you wish to deploy to a subset, you should apply the GPO to the desired OU or Group.
  4. Type “Enzoic Client Distribution” or a name of your choosing, leave Source Starter GPO set to (none), and then click OK.

Prepare the Group Policy Object:

  1. Right-click the newly created “Enzoic Client Distribution” GPO, and then click Edit…
  2. Expand the Computer Configuration, then Policies, then Software Settings nodes in the left pane.
  3. Right-click the Software installation item, and then select New > Package…
  4. Type the full UNC path to EnzoicForADClient.msi in the Open dialog box. You must enter a UNC path so that other computers can access this file over the network. For example, \\server\distribution point share\EnzoicForADClient.msi. Do not just navigate to the file and select it.
  5. Click Open.
  6. Select the Assigned deployment method, and then click OK.
  7. Close the Group Policy Management Editor.

Complete the Installation:

Windows will now install the Enzoic for Active Directory Client on the targeted systems the next time they are restarted.

Troubleshooting GPO Deployments


If the client is failing to deploy via GPO, check the following:

Does the GPO apply to the affected system?
Check the Scope tab on the GPO in the Group Policy Management Console to ensure the affected workstation(s) are covered by the GPO.

Have the affected workstation(s) been restarted?
In some cases it may take two reboot cycles before the GPO gets deployed.

Is the distribution point share and MSI accessible by the affected system(s)?
Check that they can access the share and MSI.

Do the affected system(s) have at least .NET Framework 4.5 installed?
The MSI will not handle installing this, so you will need to ensure that all target systems have at least .NET Framework 4.5 before pushing the Enzoic Client.

Check the Event Log on the affected system for GPO or install failures occurring after the reboot.
If the installer is failing, there should be some indication here.