The settings defined by the earlier Nomad install will be migrated - these may differ from the settings with which the Nomad module was initially configured with.ġE Nomad Branch and 1E Client Health services may be stopped if upgrading to Nomad 7.0 if previous version of Nomad installer is no longer in source folder or the Windows Installer cache. This will disable the Nomad module and remove the Nomad service, then re-enable the Nomad module, which will in turn uninstall the earlier version of Nomad and install the Nomad module. Then run the following command from the 1E Client installation directory on the affected devices.ġE.Client.exe -reconfigure =false -restart & 1E.Client.exe -reconfigure =true -restart To resolve this issue should it occur, first address the Application Supersedence to prevent it from recurring. ![]() To avoid this situation, always define Application Supersedence on the 1E Client Application such that it supersedes any Applications that install previous versions of Nomad (and the 1E Client when introducing new versions of the 1E Client). Nomad may be downgraded by active Application deployments in CM, which may cause issues with behaviour of the 1E Client Nomad module. Nomad is not support on Windows XP therefore when 1E Client is installed with Nomad module, the module is not enabled, and the Nomad Branch service is not installed. Will not install Nomad." however the very next log lists that "Module 'Nomad' has been installed". ![]() On Windows XP, 1E.Client.log displays a warning "Unsupported OS version. This will be fixed in a future release of 1E Client. In such a scenario, we recommend reinstalling the 1E Client with a new set of properties / transform that enables the Nomad module. The installer is currently creating the majority of Nomad registry values because the service doesn’t create them all and Nomad doesn’t tolerate the absence of all the settings that the service doesn’t create. If someone deletes those settings and enables Nomad module later, Nomad won't function right. If someone deletes those registry settings and enables Nomad module later, Nomad won't function right. ![]() 1E Client installer adds Nomad registry settings even when Nomad module is NOT enabled while installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |