Device Refresh Schedule - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

System planning, deployment, and best practices guide
Hide thumbs Also See for ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010:
Table of Contents

Advertisement

Log Settings in ZENworks Control Center
Figure 4-7
For more information, see
"Device Management
Settings" in the
ZENworks 10 Configuration
Management System Administration
Reference.

Device Refresh Schedule

Use the default schedule as a starting point. Discuss the schedules with your customer and adjust
according to their needs. This information should have been collected during the assessment phase
of your project. Remember, shorter refresh schedules means more frequent ZENworks
Configuration Management traffic on the network. This could cause issues with over-utilization of
available bandwidth. Make sure you involve the network management team when you decide on this
setting.
Short refresh times for a large number of devices can also cause extensive server load, which might
cause distribution failures or failures at the server side (uploading inventory and so forth).
Use random refresh rates to future prevent server overload during peak periods. This setting can be
instrumental in increasing the scalability of the infrastructure components. Remember, the tests
Novell performs in the SuperLab are designed to test the breaking point of the components. In the
real world, thousands of devices should not regularly contact a server in the Management Zone.
Performing Design Activities
53

Advertisement

Table of Contents
loading

This manual is also suitable for:

Zenworks 10 configuration management sp3

Table of Contents