Dns And Dhcp Services - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

0.5 Mbps
In a one-hour period, it is possible to transmit 11.25 MB to every device at SITE 2 if you use all of
the bandwidth available to ZENworks Configuration Management. In this situation, you might not
choose to place a Satellite device at this site because the level of bandwidth per device is relatively
high.
When you take this all into account, the main requirements for choosing which sites should host a
Satellite device vary from one installation to the next. For example, some customers, even though
the available bandwidth with SITE 2 is high, might still want to have a device locally designated as
a Satellite device. In this case, a workstation-class machine should be more than sufficient to
manage the devices at that site.
The suggested placement of Satellite devices should be based on simple rules. Some examples of
sites that are good candidates for Satellite devices are as follows:
Sites with more than 200 devices.
Sites that have high cost or limited access links between the MD and Primary Servers.
Sites where the bandwidth per device per hour is less than x. In the examples above, 5 MB was
chosen because this is the average size of a patch.
Sites that have secure locations to store devices. Customers might not want to place dedicated
Satellite devices in locations where they cannot be secured. In other words, you want to avoid a
situation where a user turns off the Satellite device or physically removes it from the network.
Sites with limited or charged access to WAN Infastructure.

3.7.2 DNS and DHCP Services

You should ensure that your network environment is well designed for ZENworks Configuration
Management. You need to ensure the following:
DNS forward and reverse lookup is properly configured so that you can resolve servers by
using their DNS names and IP addresses. VNC, for example, relies on the DNS infrastructure.
For this reason, it is important that the DNS service is well designed and implemented. If it is
not, the problem needs to be addressed during the design phase, properly documented, and
resolved before deployment begins.
We recommend that you register all of your managed devices in DNS, which makes it easy to
resolve by name. This is possible only if Dynamic DNS is in place and properly configured.
DHCP must be properly configured for imaging purposes, and your network team should work
with you to ensure that you can image across multiple subnets if necessary.
PXE must be enabled on your workstations if you choose to leverage the automated imaging
functionalities.
42 System Planning, Deployment, and Best Practices Guide
x 3600
8
20
= 11.25 MB per device per hour