It may occur that the Active Directory-Lightweight Directory Services (AD-LDS) configurations performed in the editor are not considered in the 7.11 runtime.

• Related Articles

• It may occur that the Active Directory login takes a long time to be executed in the runtime.

  Summary Under not specified circumstances the active directory user data takes a long time to be read slowing down the active directory login in the runtime. Description Under not specified circumstances the active directory user data takes a long ...

• Login with cached domain credentials in the runtime using Active Directory users is not available

  Summary When the option to use Active Directory users is enabled in the project, a login is only successful when one of the domain controllers can be reached. When the domain controller is offline, a login with domain credentials is not possible. ...

• FAQ: Will the functionality of using Active Directory users in Service Engine be affected by the Windows Update in March 2020 for the Microsoft Advisory ADV190023?

  Tests have demonstrated that the functionality of using Active Directory users in Service Engine is not affected by the changes that are introduced with the update for the advisory. Service Engine uses Windows API functionality for the LDAP ...

• A user in AD ADS with the option "user must change password on next logon" cannot login in the runtime

  Summary A user created in AD LDS (Active Directory Lightweight Directory Services) cannot login in the zenon runtime when the user has the checkbox "user must change password at next logon" set. A message "wrong password" is displayed when attempting ...

• Memory is not correctly released after closing the Active Directory user administration screen in runtime.

  Summary The Active Directory user administration screen allocates memory when loading the AD structure but does not release it after causing a large memory usage increase. Description The Active Directory user administration screen allocates memory ...