Preparing ZENworks for the Windows Environment


Minimum Network Requirements

ZENworks requires the following in this sample Windows network:


Expected Network Setup

The following Windows network setup is assumed for this sample Windows environment:


ZENworks Desktop Management User Workstation Configuration Options

ZENworks Desktop Management can run on user workstations using either the Novell Client or by using two other non-client modes:

It is assumed that in a Windows network environment, the Novell Client is not used; therefore, you need to decide on the features you need in your network and configure ZENworks Desktop Management for your users in one of the non-client modes.


Application Browser View Mode

In this mode, a single Application Browser View is delivered when a user connects to IIS and opens the application page (myapps.html) provided by ZENworks Desktop Management. The Web view is automatically installed on the workstation if the user has rights to install applications locally.

The Application Browser mode can deliver applications to the workstation only when the user connects to a personalized application Web page. Dynamic local user account creation, hardware and software inventory, automated imaging services, and remote management capabilities are not included in this mode.


Full Desktop Management Agent Mode

In Full Desktop Management Agent mode, all of the Desktop Management components are installed on the workstation by an administrator, as part of an image, or by the user. By including all of the Desktop Management components in the Desktop Management Agent installation, you provide your users all of the capabilities that ZENworks Desktop Management has to offer.

If you want to create a Dynamic Local User account on the workstation, you can configure the Desktop Management Agent to prompt the user to log in to eDirectory prior to the local login to Windows. When the agent has this configuration, the user is prompted for an eDirectory user name and password (which should be the same as the Active Directory account, because the two accounts are being synchronized by DirXML), then ZENworks Desktop Management creates a local account on the workstation if one is not present and logs the user into Windows with the provided username and password.

If you do not require Dynamic Local User account creation, ZENworks silently passes Novell user credentials to Windows when the user logs into the workstation (the user must already have an account on the workstation; the user will not need an account on the workstation if logging in to Active Directory---the workstation must be part of the Active Directory domain). The Desktop Management Agent then connects to eDirectory using the provided username and password in order to distribute applications to the user.

NOTE:  With the Desktop Management Agent installed on the workstation, you might still choose to deliver applications through the browser view only.


DirXML Engine and Drivers

The DirXML engine provides the ability to synchronize eDirectory data with any outside data service. The DirXML engine has several drivers running that describe how output and input should be sent between data sources.

The DirXML Driver for Active Directory (included on the Novell ZENworks 6.5 Companion 2 CD in the Novell DirXML Starter Pack folder) is specifically designed to synchronize data between Novell eDirectory and Microsoft Active Directory. The synchronization is bidirectional; you determine whether information should flow to and from both directories, or whether information should flow only from one directory to the other.

Many DirXML Drivers are available for installation on Windows 2000 Servers for synchronization with other data sources such as PeopleSoft, JDBC, any LDAP directory, Lotus Notes, SAP HR, and WebSphere MQ. For information about other drivers, see the Novell DirXML Web site.

DirXML architecture uses a publisher/subscriber model. In this model, the publisher's responsibility is to place information into eDirectory while the subscriber places changes from eDirectory into the external, synchronized data source. The behavior of the publisher and subscriber and the attribute mapping are determined by a set of rules that are part of the DirXML driver. DirXML drivers can be customized through XML rules to deliver nearly any data configuration you want.

For more details about how DirXML can be configured, see the DirXML documentation Web site.

For more information about Novell solutions for customizing your DirXML installation, see the Novell DirXML Web site.