Client for Open Enterprise Server 2 SP4
Novell Client 2 SP4 for Windows
Windows 10 (Build 10240, July 2015, Threshold 1, TH1)
Windows 10 Enterprise 2015 LTSB (Build 10240, July 2015, Threshold 1, TH1, Long Term Servicing Branch)
UEFI Secure Boot enabled (Unified Extensible Firmware Interface)
On some Windows 10 machines, after installing Client for Open Enterprise Server the machine immediately boots into "Automatic Repair" mode. The "Startup Repair" option is unable to fix the boot issue.
This behavior can happen on Windows 10 July 2015 (build 10240) installations where no Windows Updates have been applied yet, and where the UEFI Secure Boot feature is enabled. A related behavior will happen on Windows 10 July 2016 (build 14393) and later releases, but for a different reason explained in TID 7017720
Fixed in Client for Open Enterprise Server 2 SP4 (IR4) or later.
Client for Open Enterprise Server 2 SP4 (IR4) is shipped as a Microsoft-signed driver set for Windows 10. So the Secure Boot concerns for Build 10240 (July 2015) and Build 14393 (July 2016) are resolved by the fact the boot-mode drivers have a Microsoft signature embedded in them.
On Windows 8 and above, Microsoft Secure Boot uses the Unified Extensible Firmware Interface (UEFI) during the system start-up to ensure that unauthorized software cannot be loaded on the machine. Part of this process involves verifying that system drivers are signed by an approved digital signature. See "Secure Boot Overview" https://technet.microsoft.com/en-us/library/hh824987.aspx