Client for Open Enterprise Server 25.3 is an update to Client for Open Enterprise Server 24.4.
In this release, we addressed customer-reported defects.
For information on installing the Client on a single workstation, see Client for Open Enterprise Server Installation Quick Start.
For advanced installation options and procedures, see Client for Open Enterprise Server Administration Guide.
After updating to Client for OES 25.2 on Windows 10 or Windows 11, RDP logins would fail by returning to the login screen after entering correct credentials. No error messages were displayed, and access was not granted.
Resolution:
The Client for OES 25.3 has been updated to support successful RDP logins in all scenarios:
With or without NLA
Whether a session is active or not
With TSClientAutoAdminLogon enabled
The Client for OES now supports Windows AutoAdminLogon with empty passwords in two scenarios:
Windows Default Login: Supports automatic login using eDirectory and Windows default login for accounts without passwords, configured using registry settings.
Non-Default Scenario: Requires eDirectory credentials but allows Windows passwords to be empty for automatic login.
This update enables seamless automatic login on systems that do not require Windows passwords at startup.
After upgrading to Windows 11 24H2, the Client for Open Enterprise Server (OES) fails to authenticate to eDirectory when using third-party credentials.
This issue occurs when:
Login With Third-Party Credential Provider is set to On, and
Client Logon is set to Off on a Windows 11 Enterprise workstation updated to LTSC 2024 and joined to an Active Directory domain.
In this configuration, Windows domain authentication is successful, but authentication to eDirectory fails. However, manually logging in to eDirectory with the same credentials still works, indicating that the credentials themselves are valid.
Reason for the issue:
This issue is due to a change in the EnableMPRNotifications policy in Windows 11 24H2.
Workaround:
The policy must be explicitly enabled to allow Winlogon to pass user credentials to the OES client provider in SSO mode.
There are two ways to enable this policy:
Option 1: Using Group Policy Editor (gpedit.msc)
Press Windows key + R, type gpedit.msc, and press Enter.
Go to Computer Configuration > Administrative Templates > Windows Components > Windows Logon Options.
Double-click Configure the transmission of the user's password in the content of MPR notifications sent by winlogon.
Set the policy to Enabled.
Apply the changes and restart the system.
Option 2: Using the Windows Registry
Create or modify the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "EnableMPR"=dword:00000001
Apply the changes and reboot the system.
This will re-enable SSO functionality to eDirectory using the OES client.
For Client for Open Enterprise Server documentation, see Client for Open Enterprise Server website.
For information on Login Scripts, see Novell Login Scripts Guide.
Copyright 2022 - 2025 Open Text.
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
“OpenSLP” is copyrighted to Caldera systems. OpenText ships a modified version of OpenSLP for the Client for Open Enterprise Servers. OpenText supports the modified OpenSLP software shipped with the Client for Open Enterprise Server.
Copyright © 2000 Caldera Systems, IncAll rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Caldera Systems nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CALDERA SYSTEMS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.