Active Directory (AD) group <> zenon group association fails, despite correct naming

A customer reported the following solution:

Use the Active Directory Screen (Service Engine) to display the groups, existing in AD.
Copy the groups name from the Service Engines "Edit Object" dialogue.
Paste the groups name, in the Engineering Studios group naming (ruling out eventual character set discrepancies)

Make sure the User Administration file "password.cmp" is being generated and transferred (generate all files).

The customer restarted the Service Engine, instead of only reloading.

Related Articles
Password change at first user logon works via operating system but not via zenon SE ; no AD login possible
Description In the Edge Gateway frontend, the user password can no longer be changed in MS Active Directory, when the zenon system is not a member of the domain. Despite correctly entering the previous password and the new password including password ...
The user rights for active directory users are not taken over correctly in the runtime from the active directory group name and group description
Summary When user rights for active directory users are specified using special naming conventions for the active directory group name and group description, the user rights are not taken over correctly after a successfull login of an active ...
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 ...
Acknowledgement of alarms limited to equipment groups does not work if the user data comes from an external identity provider (AD, Identity Service)
Summary The acknowledgement of alarms that are restricted to system groups does not work if the user data originates from an external identity provider such as Active Directory or Identity Service. This error has been fixed. Description In AML, the ...
Active Directory: zenon logon screen does not adopt the configured policies from the AD user group policy
Summary Under specific circumstances locked out users are treated as locked out for longer than configured Description Under specific circumstances locked out users are treated as locked out for longer than configured Information 1- Wait more than 3 ...

Active Directory (AD) group <> zenon group association fails, despite correct naming

Active Directory (AD) group <> zenon group association fails, despite correct naming

Related Articles

Password change at first user logon works via operating system but not via zenon SE ; no AD login possible

The user rights for active directory users are not taken over correctly in the runtime from the active directory group name and group description

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?

Acknowledgement of alarms limited to equipment groups does not work if the user data comes from an external identity provider (AD, Identity Service)

Active Directory: zenon logon screen does not adopt the configured policies from the AD user group policy