![]() Installing or Upgrading to Client for Open Enterprise Server 2 SP4 (IR7) or later by default disables this feature by setting the group policy for Automatic Restart Sign On. The feature can be disabled by creating a registry key DisableAutomaticRestartsSignOn of type DWORD under and set the value to 0x1. To resolve this issue and perform eDirectory login along with Windows logon, disable the existing Windows Update group policy for ‘Automatic Restart Sign On’. This feature creates a Windows-only logon session automatically on behalf of previously logged-on user and you are reconnected to this Windows-only logon session even after you provide your credentials to login to eDirectory and Windows again through the interactive credential provider. This is because of a new feature introduced in Windows 10 RS3 to automatically reboot the device using the logon information of the user who had logged in last on the device. But the issue of eDirectory login scripts failing to run and missing NCP connections is observed on the second and subsequent logins with the same credentials used for first login. When you upgrade a device to Windows 10 RS3 without Client for Open Enterprise Server, the first login after installing Client for Open Enterprise Server on the upgraded device logs into both eDirectory and Windows successfully. When you upgrade a device to Windows 10 RS3 (Fall Creators Update) with Client for Open Enterprise Server 2 SP4 (IR6) or earlier already installed, the eDirectory login scripts fail to run and NCP connections fail to establish after Windows logon. To uninstall a later version of NICI and re-install NICI 2.76 on Windows 圆4, in addition to uninstalling the NICI product, you will need to rename or delete the CCSWX64.DLL from the Windows SYSTEM32 directory.Ħ.5 eDirectory Login Fails After Windows Upgrade to Windows 10 RS3 Due to an issue in the NICI 2.76 for Windows 圆4 installer, re-installing NICI 2.76 on Windows 圆4 is unable to overwrite the CCSWX64.DLL file left behind by the NICI 2.77 or later installers. The Novell NICI installer intentionally leaves behind certain NICI files, including CCSW32.DLL and CCSWX64.DLL. If you are intending to uninstall NICI 2.77 or later and re-install NICI 2.76, an additional step is necessary. Earlier versions of Client for Open Enterprise Server contains NICI 2.77.3. The Client for Open Enterprise Server 2 SP4 (IR9) and later contains NICI 3.0.3. Subsequent attempts to use NICI can report -1471 0xFFFFFA41 NICI_E_SELF_VERIFICATION errors due to the damaged NICI installation. For example, attempting to install NICI 2.7.3 or NICI 2.7.4 when NICI 3.0.3 is already present. The NICI installer of the older NICI version can damage the existing newer NICI installation. When starting up, the Windows welcome screen on Windows 圆4 displays an error, such as The procedure entry point CCSX_Authenticate could not be located in the dynamic link library ccsw圆4.dll. This is because the NMAS client included in the initial release cannot resolve its required dependencies using the newer version of NICI still present on the machine. Now, the eDirectory password expiration is handled during the login of the user and changing the passwords during the grace login period.ĭuring installation of the Client on Windows 7 圆4, the NMAS Challenge/Response method will report a 1603 error. Previously, the eDirectory password expiry was handled after the execution of the eDirectory login scripts on the user’s desktop. Enhanced eDirectory Password Expiration Handling The Client for Open Enterprise Server 2 SP5 supports the Open Enterprise Server (OES) 2018 SP2 release. For more information on the NCP server side configuration for MFA, see Managing NCP Security Configurations in the OES 2018 SP2: NCP Server for Linux Administration Guide. The Advanced Authentication capability on the Client for Open Enterprise Server 2 SP5 is enhanced to support the Multi Factor Authentication (MFA) on the OES 2018 SP2 server. For more information on the parameters, see Advanced Settings in the Client for Open Enterprise Server Administration Guide.įor information on the NCP server side configuration for NCP Encryption, see Managing NCP Security Configurations in the OES 2018 SP2: NCP Server for Linux Administration Guide.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |