Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Suggested Answer
  • Replies replies
    5
  • Answers answer
    1
  • Subscribers subscribers
    24
  • Views views
    1001
  • Users 0 members are here
Related
Options

New Windows10 lockscreen/OES client/AutoAdminLogin problem

bbsm

This week we encountered a problem when unlocking locked Windows 10 workstations where AutoAdminLogin is enabled for the Windows user. After entering the eDirectory credentials the unlock screen gets stuck and the workstation has to be rebooted. Normal Login is not affected.

The workaround we found to solve this problem is changing the "Unlock Workstation Credentials" in the Advanced Login Settings of the Client to "eDirectory only".

The affected workstations are Windows 10 Pro (64-Bit) version 22H2. Client for Open Enterprise Server 2 SP7 (both IR2 and IR3) is installed.
AutoAdminLogin is enabled (eDirectory prompt, Autologon to Workstation) for use with a generic local Windows user account.
This configuration has worked flawlessly for over a decade. Before the problem occurred both the cumulative Windows update for 22H2 KB5031356 and the current version of Avast Business Security were installed as part of routine maintenance.

I suspect that something in KB5031356 breaks the unlock credential mechanism in the OES client, but did not have the time to investigate further.

Parents
  • 0  

    I believe the key may be the "eDirectory prompt, Autologon to Workstation" you mentioned.  Meaning in addition to the Microsoft AutoAdminLogon policy being configured, the Client for Open Enterprise Server's option for "Prompt for network logon during Windows AutoAdminLogon" is also enabled.  (Also known as the Client for Open Enterprise Server "AutoAdminQueryNDS" registry policy.)

    We are currently investigating a hang that occurs in the current client releases when both AutoAdminLogon and AutoAdminQueryNDS are both enabled. There is no known workaround for this issue at this time, other than to temporarily disable at least the "AutoAdminQueryNDS" policy which seemed to avoid the failure in our investigation thus far.  But the actual root cause has not yet been identified yet, nor is there a proposed fix at this time.

Reply
  • 0  

    I believe the key may be the "eDirectory prompt, Autologon to Workstation" you mentioned.  Meaning in addition to the Microsoft AutoAdminLogon policy being configured, the Client for Open Enterprise Server's option for "Prompt for network logon during Windows AutoAdminLogon" is also enabled.  (Also known as the Client for Open Enterprise Server "AutoAdminQueryNDS" registry policy.)

    We are currently investigating a hang that occurs in the current client releases when both AutoAdminLogon and AutoAdminQueryNDS are both enabled. There is no known workaround for this issue at this time, other than to temporarily disable at least the "AutoAdminQueryNDS" policy which seemed to avoid the failure in our investigation thus far.  But the actual root cause has not yet been identified yet, nor is there a proposed fix at this time.

Children

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.