Applicable to Entuity v19.0 upwards. If you are running an earlier version of Entuity, please see this article.
Existing devices that had configuration management enabled pre-upgrade
New uncertified devices failing to be taken under management
Windows bug affecting patch installs (ENA v17.0/v18.0 on Windows Server 2016/2019)
EMS rule failure - 'Discard Events From Recently Added Devices':
In Entuity v19.0, the EMS rule 'Discard Events From Recently Added Devices' fails. This causes events from recently added devices to not be filtered out.
Note, this rule is disabled by default, and so this issue only affects installations where an administrator has manually enabled the rule.
This issue will also affect users who have deployed custom event rules that access object attributes via Groovy using the ‘dot’ syntax, for example:
def src = source;
src != null && src.pollDefnForPort.statusEventsEnabled == "0"
Please contact Entuity Support for a hotfix for this issue until Entuity v19.0 P01 is released.
Existing devices that had configuration management enabled pre-upgrade:
Existing devices that had configuration management enabled before upgrade to Entuity v19.0 are no longer enabled for configuration management after upgrade.
Note, this only effects users who have an unlimited license in Entuity v19.0 for configuration management.
This issue will be fixed in Entuity v19.0 P01. Until then, users will either need to navigate to Asset Management and re-enable devices for configuration management, or contact Entuity Support for a hotfix.
New uncertified devices failing to be taken under management:
New devices, if not certified, are failing to be taken under management. This does not affect devices that are already under management, and uncertified devices that are already under management are not removed from management after upgrade to Entuity v19.0.
This issue will be fixed in Entuity v19.0 P01. Until then, please contact Entuity Support for a hotfix.
Windows bug affecting patch installs (ENA v17.0/v18.0 and Entuity v19.0 on Windows Server 2016/2019):
There is a bug in Windows, as of December 2018, affecting any version of Entuity that is using Windows Server 2016 or Windows Server 2019, that can remove a temp directory that installPatch requires to run.
In Windows, user sessions are given their own temporary storage location, which is stored in the temp or tmp environment variables. This location is: C:\Users\Username\AppData\Local\Temp\session_id.
The bug, however, can remove the folder under temp for that session. The symptom of this issue is the following error:
"ERROR: Unable to install patch. The system cannot find the path specified."
This occurs even though the patch file supplied does exist.
The solution is to update the environment variable. There are two ways to do this:
- find the temp directory by running echo %TEMP% in cmd, and then create the folder manually.
- set a custom temp directory using the following commands in cmdset: