Novell DirXML 1.1a for Windows NT/2000

Last updated August 18, 2004
1.0 Documentation
2.0 ZENworks for Desktops Environment and Workstation Manager
3.0 For ZENworks Environment: Installing the Novell Client When Workstation Manager is Required
4.0 Special Instructions
5.0 Known Issues
6.0 Legal Notices

1.0 Documentation

For information about DirXML® and the drivers, refer to the documentation located at the Novell Product Documentation site.

You can view the documentation online in HTML, or download a copy in PDF format.

The latest readme file is also available online at the same location.


2.0 ZENworks for Desktops Environment and Workstation Manager

If the Windows* NT/2000 server is running in a Novell® ZENworks® for Desktops environment, be sure that the Workstation Manager component of the Novell ClientTM is either not installed or is disabled. For information on how to not install or how to disable Workstation Manager or if Workstation Manager is required on the server, see the information below, 3.0 For ZENworks Environment: Installing the Novell Client When Workstation Manager is Required.


3.0 For ZENworks Environment: Installing the Novell Client When Workstation Manager is Required

eDirectory allows only a single system-level authentication from a node at one time. Novell products, such as ZENworks for Desktops, DirXML, or OnDemand/DeFrame run as services on Windows NT/2000. Those services may each do an eDirectory authentication when starting up, and each service can use a different username and password. Generally, these services are started alphabetically, and you cannot control the order. After any service starts, and authenticates to eDirectory, subsequent services trying to log in will fail. (The login behavior of the service depends on the configuration of the service.)

For example, if a machine has been imported using ZENworks for Desktops 3 and a workstation object is created in eDirectory, Workstation Manager will need to authenticate to eDirectory during startup. If a service such as DirXML is then installed, Workstation Manager will no longer be able to authenticate because the DirXML service starts first and performs its own eDirectory authentication. If this conflict in authentication happens, you might experience high CPU utilization as the service tries to authenticate, a growing PAGEFILE.SYS, or failure of the feature controlled by the failing service. In addition, DirXML will stop functioning if this authentication conflict occurs.

To avoid this problem, refer to the appropriate scenario below before installing DirXML.


4.0 Special Instructions


5.0 Known Issues


6.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.


Patents Pending.

ConsoleOne, DirXML, GroupWise, Novell, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.

eDirectory is a trademark of Novell, Inc.

All third-party trademarks are the property of their respective owners.