Imaging; Configuring A Layer 4 Switch - 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

Advantages to Assigning Group Policies through ZENworks Configuration
Management
With ZENworks Configuration Management, you can use plural group policies, meaning you can
layer multiple group policies on top of each other, applying what is referred to as effective policies
at the endpoint level. Using ZENworks Configuration Management to do this allows you to handle
roaming users effectively, making policies available to end users no matter where they are logging in
from. Most organizations use group policies to manage the look and feel of the user's desktop
experience. There are two choices when it comes to using Group Policies in your environment:
Import your policy files into ZENworks Configuration Management and replicate them across
your infrastructure.
Deliver your policies though Microsoft Active Directory.

4.2.12 Imaging

We highly recommend that you adopt a methodology for creating and delivering Universal Images
to your endpoints. By this we mean a base image for Windows XP and Windows Vista. After you
have established the Universal Images, you can deliver core applications and line-of-business
applications as add-on images during the imaging process. This method can be further extended to
also provide hardware-specific drivers during the imaging process. Tools such as ENGL's Imaging
Toolkit for ZENworks Configuration Management can be used to make the process of creating a
Universal Image very easy to manage.
For more information, see the
Imaging
Reference.

4.2.13 Configuring a Layer 4 Switch

ZENworks Configuration Management supports achieving load balancing and fault tolerance for
your infrastructure services though using a Layer 4 (L4) switch. An L4 Switch can front either
Primary Servers, Satellite devices, or both. This allows the organization to achieve guaranteed
results when directing traffic to the devices behind the switch. Most importantly, this allows
organizations to ensure that services are always available to their end user community.
L4 switches are expensive and not affordable for many smaller organizations. Smaller organizations
often turn to other forms of load balancing and fault tolerance solutions that are readily available to
them. These include solutions such as DNS Round Robin, Microsoft Load Balancing Services, and
other open source solutions on the market.
When you do use an L4 switch, you need to ensure that it is properly configured. If the switch is not
configured properly, the traffic is not directed properly and there might be issues with connections,
responses, and so forth.
The following sections explain the general requirements for properly configuring an L4 switch to be
used in front of ZENworks Primary Servers and Satellite devices:
"Foundry Networks ServerIronXL Configuration" on page 77
"Summary of Configuration Settings" on page 78
"Configuring the Closest Server Default Rule" on page 78
76
System Planning, Deployment, and Best Practices Guide
ZENworks 10 Configuration Management Preboot Services and

Advertisement

Table of Contents
loading

This manual is also suitable for:

Zenworks 10 configuration management sp3

Table of Contents