Environment
ZENworks Configuration Management 2017 Update 3
Situation
Note: This TID applies only to zones that use Microsoft SQL (MSSQL) server for the database. This TID applies only to zones being updated from ZENworks 2017 or 2017 Update 1 to 2017 Update 3. Zones at 2017 Update 2 moving to Update 3 do not see the problem.
After updating to ZENworks 2017 Update 3 from 2017 or Update 1, for MSSQL only, System variables on bundle or device and folder levels are overwritten with zone system variables.
Resolution
This is fixed in ZENworks Configuration Management 2017 Update 3a. For more information see KB 7023221 "ZENworks Configuration Management 2017 Update 3a and 3 update information and list of fixes" at https://support.microfocus.com/kb/doc.php?id=7023221
Note: Aside from the issue described in this TID, ZENworks 2017 Update 3 and ZENworks 2017 Update 3a builds are functionally identical.
This problem will impact zones where system variables have been set at levels below zone. To determine whether variables are set run this sql query:
select * from zZENObject where zuid in (select ObjectUID from zSystemSetting where name = 'zenworks.system.variables' and ObjectUID is not NULL)
If ZENworks 2017 Update 3 is downloaded but not yet applied to the primaries, delete the system update and apply ZENworks 2017 Update 3a when it becomes available.
If ZENworks 2017 Update 3 has already been applied to the primaries, and the query above returns no results, then there is no change necessary, no need to do anything and can continue with ZENworks 2017 Update 3.
If ZENworks 2017 Update 3 was already applied to the primaries, and the query above returns values, if the number is excessive, contact Micro Focus Customer Care ZENworks support. The query will return a list of bundles or folders impacted. Do not increment the bundle versions of the bundles listed in the query until fixing them. If there aren't too many, it can be fixed by manually modifying in ZCC and re-adding the variables to the settings.
Cause
A one time only system update global action mistakenly overwrites system variables set below zone level setting them to zone level and losing the custom variables. The problem was due to a preglobal action and will not reoccur for new bundles created after the update.