ZENworks Performance and Database Ideas

  • 7007088
  • 21-Oct-2010
  • 01-Aug-2019


ZENworks Configuration Management 2017
ZENworks Configuration Management 11
ZENworks Configuration Management 10


What are some helpful tips for ZENworks server and database performance issues?
Note: Depending on the ZCM version some aspect may not be applicable.

Additional Information

  1. Novell does not recommend database on virtual server.  We'll work with you certainly, but remember that responsive database is essential.
  2. If physical device is not possible, at least ensure you are using a physical disk system.
  3. For primaries on VMware be sure to set the allocated memory to the same as the "reserved" memory. 
    Setting large page sizes may also help.
  4. Recommend that you split the configuration functionality in closest server rules to load balance among your primaries.  Don't have all devices using same primary for configuration requests.
  5. If all your managed devices come from the same IP segment/DNS zone, you should use layer 4 switching to distribute load among primary servers.
    Use local satellites for content/rollup etc functionality. 
  6. Do not locate Primary servers across WAN from Database (see minimum requirements documentation).
  7. Ensure that satellites have a mixture of parent primaries as they will communicate to parent primary first for some functionality.  For content satellites, try a content schedule greater than default of every hour and increase duration to allow all the downloads.
  8. Recommend if you don't use it - disable Primary User calculation (ZCC/Configuration/Device Management/Primary Workstation/set to None (do not calculate-- affects both PrimaryWorkstation and PrimaryUser).
  9. Change inventory scan settings Configuration/Inventory/Inventory Schedule.  Set to something other than device refresh, depending on your needs such as days of the week.  Randomize when schedule allows.
  10. Configure satellite server rollup, content synch settings appropriately. 
    Content synch during some time after hours, select the random option.  For important content, use a separate schedule per content type.
    The more satellites that are configured, the greater length should be set for synch time.
    Try to randomize or set different start times for synchchronization.  The sync will all start on absolute clock time so have offsets for start times.
    NOTE:  Imaging satellites also synch content so check their configuration regarding content in the same way.
  11. If using Patch Management set download schedule for after hours.
  12. Eliminate unnecessary message processing.  Set Configuration/Local Device Logging/Send message to local system log if severity is" Set to Error.
  13. Ensure regular message purging to keep db size down:  Set Configuration/Event and Messaging/Centralized Message Logging/Automatic Message Cleanup to reduce the cleanup times and frequency.  Should be after hours, and default frequency is likely more than desired.
    Check queue (zman ql --status=N and zman ql --status=I )
    If too many queue jobs for quicktasks, be prudent with using "now" schedule. 
  14. Check ZCC/Configuration/Device Refresh Schedule for reasonable settings.  If overly agressive refersh schedules are set, determine why refresh is necessary and whether alternative scheduling of bundles can help avoid overloading the server.
    Enable Random Time to Wait unless needed (See KB 3026086 for more information if using user assigned policies).
  15. ZCC settings for times to retry busy server etc. should not be set too low.  Otherwise agents may retry server requests prematurely which will drive up traffic to the server.
  16. If ZRS is used:
    Check Configuration / Reporting Folder Synch Schedule to confirm that it is set to default (one day) or greater.  Less can cause deadlocks on the database. 
    Schedule ZRS InfoView report refresh queries for after hours.

Database specifics:
See documentation for 2017 Database Best Practices Guide and  Database Requirements.