Annoying Novell Client Isnt Quite Gone

By Cameron Sturdevant  |  Posted 2004-08-09 Print this article Print

The chief difference between the Novell Client of old and Novell Inc.'s new Desktop Management Agent is significant: DMA isn't a network redirector.

The chief difference between the Novell Client of old and Novell Inc.s new Desktop Management Agent is significant: DMA isnt a network redirector.

That distinction is important because Novell Client (often referred to in the field as Client 32) was a general nuisance and often a time-intensive bother for IT staff to install and maintain. DMA, which Novell has used for the last couple of years instead of Client 32, acts as a proxy service in the HTTP stack. DMA is what ZENworks 6.5 administrators will care most about.

Click here to read eWEEK Labs review of ZENworks 6.5.
IT managers should be aware, however, that there is another nettlesome component of ZENworks 6.5 of which IT managers should be aware. DMA is actually functionality the ZENworks team hooks on top of Novells NetIdentity Agent—a piece of Novell code used across product lines to provide secure access. ZENworks 6.5 rides on top of NetIdentity Agent to provide log-in policies to workstations. This proved to be annoying during our tests, particularly because it looked so much like the problematic Client 32.

The only way Novell can provide policy actions is to insert Novell technology in the Windows Graphical Identification and Authentication process at log-in or boot-up, company officials said. Thus, when NetIdentity Agent is modified by the ZENworks DMA code, the Windows log-in changes to show the Novell invitation to access the computer.

IT managers who introduce ZENworks 6.5 to new users will immediately be confronted with the problem of a new user log-in screen. This likely wont work that well for IT staff members who are trying to support all the advanced features that ZENworks 6.5 provides.

Our only advice is to prepare new users for a change in the way their log-in screen works and reassure IT staff that the new method shouldnt introduce the problems they may be familiar with from their Client 32 experience.

ZENworks 6.5 requires that any server or workstation that is still using an older version of Novell Client must upgrade to the latest version of Novell Client, as well as install DMA. IT administrators should factor this requirement into their estimates of the time needed to upgrade.

During our tests, upgrading the client turned out to be a painless process. Organizations that are already using a previous version of ZENworks for Desktops should be able to use that system to deploy the new client.

Check out eWEEK.coms Enterprise Applications Center at for the latest news, reviews and analysis about productivity and business solutions.

Be sure to add our enterprise applications news feed to your RSS newsreader or My Yahoo page

Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at

Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel