Updating the Novell Client using the Client Update Agent fails on some machines

  • 7002896
  • 02-Apr-2009
  • 26-Apr-2012

Environment

Novell Client for Vista 2.0.0 Installation
Novell Client for Vista 1.0.0 Installation

Situation

Attempting to invoke Update Agent operations with "Use Administrator Privileges" selected fails to perform the Update Agent action on some machines.
 
This issue is occurring because the Update Agent feature in the Novell Client 2 for Windows Vista/2008 and earlier releases of the Novell Client for Windows Vista was inappropriately attempting to identify the Windows built-in "Administrators" group using an English name-based reference.  This fails on any machine where the built-in "Administrators" group has been renamed, or where the native Windows language uses something other than the English representation of "Administrators" for this group.

Resolution

This issue is fixed in the "Novell Client 2 for Windows Vista/2008 (IR1a)" and later.  Note that due to the nature of the issue, the Update Agent feature of "Use Administrator Privileges" will not work successfully on some non-English workstations or workstations where the "Administrators" group has been renamed, until after the Novell Client 2 (IR1a) or later is installed.  Meaning that the upgrade to Novell Client 2 (IR1a) or later itself may have to be performed manually, to work around the fact that the Update Agent "Use Administrator Privileges" feature of the existing installed Novell Client cannot be used to perform this update.

Pre-Novell Client 2 for Windows Vista/2008 (IR1a) Workaround:
Do not enable the"Use Administrator Privileges" option in the "Update Agent" tab of the Novell Client Properties.  Users logged on without sufficient permissions to install system applications may still be able to install the Novell Client, if Windows User Account Control (UAC) is enabled to prompt for elevation, and if the interactive user is able to provide credentials of an account that does have permission to install such system software.
 
Other potential workarounds would be to rename the "Administrators" group to the English representation of this name, or to create a separate group named "Administrators" which does have sufficient permission to install Windows system software.