Windows Logon

Configure Windows Logon

In registry

1. Open Windows Registry Editor.

2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Axidian-ID\SrvLocator2.

3. Modify the ServerUrlBase string parameter and specify the URL of your Core Server, such as http(s)://dc.axidian.local/am/core/.

   Note

   When using the HTTPS protocol connection, you must install a client certificate on each Core Server.

In Group Policy Editor

Important

When configuring with policies, the values are specified in the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Axidian-ID\SrvLocator2 and take priority over the manual configuration.

1. Add the AxidianID.ServerUrl.admx policy to the workstation with Windows Logon installed.

2. In gpedit.msc, go to Computer Configuration→Administrative Templates→Axidian ID→ClientConnection→Server connection settings.

   Enable the policy.

3. In the Core Server URL field, specify the URL of your Core Server, such as http(s)://dc.axidian.local/am/core/.

Configure concurrent operation with RDP Windows Logon

If the scenario implies installing Windows Logon and RDP Windows Logon on the same machine, you must configure the policy for Windows Logon.

In registry

1. Go to the machine with the RDP Windows Logon and Windows Logon modules installed.
2. Open Registry Editor.
3. Go to the Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Axidian-ID\Logon for Windows section.
4. Create a parameter of the DWORD type named CredProvFilter and set it to the value 2.

In Group Policy Editor

1. Go to the machine with the RDP Windows Logon and Windows Logon modules installed.
2. Open Group Policy Editor.
3. Go to the Computer Configuration→Administrative Templates→Axidian ID→Windows Logon section.
4. Enable the Credential Provider settings policy and set the Display of login methods parameter to All except the password.

Core Server availability check

For client computers, you can enable Core Server availability check, as well as to configure the time period after which Core Server becomes unavailable and the client computer starts using cached data.

By default and when the policy is disabled, Core Server availability checks are turned off and not performed, and the time for determining server unavailability is unlimited.

When configuring with policies, the values are specified in the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Axidian-ID\ServerAvailability and take priority over the manual configuration.

To configure the Core Server availability check:

In registry

1. Go to the client machine with Windows Logon installed.

2. Open Registry Editor.

3. Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Axidian-ID\ServerAvailability.

4. Set the values of the following parameters:

   • For the IsEnabled parameter, set the value 1 to enable the check.
   • For the CheckWaitTimeoutMs parameter, set the period during which the client module waits for the server availability check result, after which the server is considered unavailable. The default value is 5000 ms.
   • For the CheckResultTtlMs parameter, set the time during which the result of the previous check remains valid and is used instead of performing new checks. The default value is 6000 ms.

In Group Policy Editor

1. Go to the machine with Core Server and the Windows Logon module installed.

2. Open Group Policy Editor.

3. Go to Computer Configuration→Administrative Templates→Axidian ID→Client Connection.

4. Enable the Axidian EA\ESSO server availability check policy.

5. Set the values of the following parameters:

   • For the Check result waiting timeout parameter, set the period during which the client module waits for the server availability check result, after which the server is considered unavailable. The default value is 5000 ms.

   • For the Check result lifetime parameter, set the time during which the result of the previous check remains valid and is used instead of performing new checks. The default value is 6000 ms.