Some ZCM System Requirements May Not Work as Expected

  • 7017885
  • 26-Jul-2016
  • 26-Jul-2016

Environment


Novell ZENworks Configuration Management 11.4

Situation

You've assigned a system requirement checking a variable with a policy and you've found that it doesn't work as expected, it may be pulling the incorrect variable in for comparison.

Example from zmd-messages.log (pulling in device name instead of username):
[DEBUG] [04/15/2016 09:05:18.887] [1340] [ZenworksWindowsService] [30] [] [EnvironmentUtil] [] [GetUserEnviromentDictionary:Reading Volatile Env subkeys value using the key:S-1-5-18\Volatile Environment\0] [] [] [] [ZENworks Agent] 
[DEBUG] [04/15/2016 09:05:18.887] [1340] [ZenworksWindowsService] [30] [] [Requirement Handler] [] [Comparing actualValue: sjohnson-pc$ with expectedValue: strj500 for ContainmentType: DoesNotEqual returned True] [] [] [] [ZENworks Agent] 
[DEBUG] [04/15/2016 09:05:18.887] [1340] [ZenworksWindowsService] [30] [] [Requirements Module] [] [First requirement returned True] [] [] [] [ZENworks Agent] 
[DEBUG] [04/15/2016 09:05:18.887] [1340] [ZenworksWindowsService] [30] [] [Requirements Module] [] [First requirement returned True] [] [] [] [ZENworks Agent] 
[DEBUG] [04/15/2016 09:05:18.887] [1340] [ZenworksWindowsService] [30] [] [PolicyManager] [] [ Advanced system requirement success for policy Name = TESTBOOKM, Guid = 47f4ee3af66a9a11beb0bfad3ff65175, Type = browserbookmarkspolicy, Version = 3] [] [] [] [ZENworks Agent]


Resolution

Configure the assignment type differently (if user-assigned, use device-assigned, or vice versa) or use a different variable.

Cause

Depending on policy type and/or assignment type, certain variables will only be available in certain sessions associated with that type.