Hi,
I hope I've come to the right place with my question. The text is translated from German by Deepl. Hope it is understandable for you.

The following scenario is causing headaches: Windows 11 24H2 Enterprise tested today (2024-12-06) without Windows update and also with a complete Windows update run. Also cross-tested with the Open Enterprise Client 24.1 and 24.4.

There is a local user in Windows, which also exists in NetIQ. Passwords are identical.

If I log on to the Windows device with this user via the OES client, the local profile is loaded correctly and the login script is processed correctly.
If I set the client to work “in the background” (Client login: Off, third party login: On, contextless LDAP login configured accordingly, password synchronization activated in the client), it unfortunately happens that after a successful local login the OES client reports that the connection information is incorrect and that I should check the user name and password. The normal OES client screen then appears. If I enter the identical password here, everything runs smoothly.

Under Windows 11 23H2 we also have machines with exactly the same setup (and the OES Client 24.1) and there are no problems. So I log in there locally, the credentials are forwarded to OES, which looks through the tree for the user if necessary and executes a login including script in the background.

I have already tried using ChatGPT to run through GPOs and registry keys in all shapes and colors that Microsoft could have changed in 24H2 ... without success. Now I hope that maybe someone else here has an idea. It seems as if the password transfer or the access to the cached credentials has changed in 24H2 and the OES client cannot cope with it.

Straws are enough for my research ;)

Thanks already!