Environment
Client for Open Enterprise Server 2 SP4
ZENworks Patch Management 2017 Update 2 17.2
Situation
When using ZPM to install Client for OES, the process fails and the Client is not successfully installed.
Examining the Client properties > Client tab shows the Product Name as "Failed Install of Client for Open Enterprise Server 2SP4 (IR8a)".
- The error in the ZPM log may resemble:
[WARN] [05/23/2018 22:19:17.299] [1676] [ZenworksWindowsService] [19] [] [ActionManager] [ActionMan.ActionContinueOnFailure] [The action Client for Open Enterprise Server 2 SP4 (IR8a) (5.-1012354706 (ID:Client for Open Enterprise Server 2 SP4 (IR8a) (5.-1012354706) failed due to the reason : Failed to launch C:\Program Files (x86)\Novell\ZENworks/zpm/Remediate.exe. Exit code: 144, however the action is set to continue on failure.] [] [] [] [ZENworks Agent]
- The error in Client for OES installation debug log (\%ProgramData%\Novell\Client\Log\NCIDebug.log) may resemble:
[SETUPNCI.DLL] ERROR: SetupInstallFromInfSection(NVClient.Ndi.ntamd64,SPINST_ALL,C:\Windows\TEMP\7zSF02B.tmp) failed
Windows Error: 1459 - This operation requires an interactive window station.
[SETUPNCI.DLL] ERROR: NV_NVCLIENT upgrade failed with error 1
[SETUPNC.EXE] ERROR: Install(NV_NVCLIENT, C:\Windows\TEMP\7zSF02B.tmp\netnvcli.inf) failed
[SETUP] ERROR: ""C:\Windows\TEMP\7zSF02B.tmp\Install\amd64\SetupNC.exe" /I NV_NVCLIENT "C:\Windows\TEMP\7zSF02B.tmp\netnvcli.inf"" returned 1
[SETUP] ERROR: Installation of the Client failed.
Resolution
The log indicates that Client is being installed with ZENworks on a non-Windows 10 machine using a non-interactive mode to "run with system rights." The ZENworks action needs to be run while interactive with the desktop, rather than "as a service / from a service" which by definition will be non-interactive.
Windows 8.1 and earlier do not allow drivers (any drivers, not just Micro Focus) to be installed non-interactively unless they are signed by Microsoft. Client for OES drivers are signed by Microsoft on Windows 10, but not for Windows 8.1 and earlier. The fix was documented as "Run as unsecure system user" (as opposed to "secure system user") in TID 10094891.