Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010 Migration Manual page 14

It is scalable: No other systems management product on the market scales to the level of
ZENworks (in fact, there are no known limits to how many users a single ZENworks system
can manage).
You will want your new infrastructure to be as flexible, simple, and scalable as your existing
environment. Thus, it's helpful to have a solid understanding of the architectural differences
between existing versions of ZENworks 10 Configuration Management and earlier versions of
Novell ZENworks.
Novell ZENworks 7.x is the final release patterned after traditional ZENworks architecture.
Traditional ZENworks architecture is two-tiered and relies on direct access to the object store
(Novell eDirectory
Client32
TM
object information, or logic, stored in the directory.
In traditional ZENworks, it is important to note that the bulk of the logic and processing is done on
the client side in the form of policy searching, launcher refreshing, and so on. In other words, the
client does most of the work. This setup has a dramatic effect on the scalability of the product.
Instead of one server doing all of the work for 100 clients, the total workload is spread across all 100
clients.
Figure 2-1
Figure 2-1
Back-End Servers
eDirectory Replication
and Tiered Electronic
Distribution
Traditional ZENworks architecture is characterized as follows:
The ZENworks Management Agent is installed on every workstation
Client32 is required in a NetWare
The use of the middle-tier server is required when the Novell Client
the managed devices
14 ZENworks 10 Configuration Management ZENworks Migration Guide
) for configuration information. Every workstation was required to have Novell
TM
installed or Middle tier configured in order to access ZENworks services—specifically
illustrates the traditional architecture for Novell ZENworks Desktop Management:
ZENworks Desktop Management Architecture
Within the Firewall
Outside
the Firewall
Middle-Tier Servers
Managed Devices
®
environment
is not installed on
TM