home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.morenci.k12.mi.us
/
ftp.morenci.k12.mi.us.tar
/
ftp.morenci.k12.mi.us
/
Clients
/
w2kxpv492
/
49sp2e.exe
/
English
/
WINNT
/
i386
/
49SP2.txt
next >
Wrap
Text File
|
2004-06-24
|
18KB
|
465 lines
Novell Client v4.90 Support Pack 2 for Windows NT/2000/XP
June 2004
Overview
This Support Pack contains updates for Novell Client v4.90
Windows NT/2000/XP only.
The purpose of this Support Pack is to provide a bundle of
fixes that have all been tested together. These files have
undergone component testing, core OS testing, and
integration testing with other Novell products.
Do not install individual files from the Support Pack.
For information on the latest Support Pack issues, see TID
10091736
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/1
0091736 .htm).
1.0 Support Pack Installation
1.1 Prerequisites
1.1.1 NDPS
1.1.2 Installing NetWare 4.11 or 4.2 Server
Patch Prior to Installing the Client
Solves File Open Issue
1.2 Install Option 1 - setupsp.exe
1.3 Install Option 2 - ACU Install
1.4 Install Option 3 - Installing the Novell Client
with the Support Pack Integrated
1.5 Setupsp.exe Functionality
1.6 Acu.exe Functionality
2.0 Known Issues
2.1 Additional Issues
2.2 SLP v2 Versus SLP v1
2.3 Update Agent
2.3.1 Client Update Service for Novell
2.3.2 Administrator Rights limitations
2.4 SHELL_VERSION login script variable
2.5 ZENworks 6.5 Middle Tier fails to authenticate
3.0 Legal Notices
1.0 Support Pack Installation
1.1 Prerequisites
1.1.1 NDPS
An update to NDPS is required to solve a
client hang. Install the dprpcnlm.nlm
file, dated 22Nov2000 or later. This
update is included in NetWare 5.1 Support
Pack 3 or later. For more information, see
TID 10062546
(http://support.novell.com/cgi-bin/search/
searchtid.cgi?/10062546.htm).
1.1.2 Installing NetWare 4.11 or 4.2 Server
Patch Prior to Installing the Client
Solves File Open Issue
A server patch update addresses an issue
in which a file that is opened once by
different threads (one open in each
thread) in an application and then closed,
leaves an instance of the file open, even
after you exit the application. This
problem could cause the server to run out
of memory or hang. The server update is
located in TID 2952441
(http://support.novell.com/cgi-bin/search/
searchtid.cgi?/2952441.htm).
You do not have to update the server
product version to install and use the
latest client software.
1.2 Install Option 1 - setupsp.exe
To install the updates on a workstation with the
Novell Client v4.90 for Windows NT/2000/XP
already installed, run the setupsp.exe located in
products\winnt\i386.
Available options for configuring setupsp.exe are
described in 1.5 Setupsp.exe Functionality.
Setupsp.exe can be launched automatically as part
of the NetWare login script. The following is an
example of the code you would add to the login
script:
@\\%<aserver>\sys\public\client.sp3\products\winnt
\i386\setupsp.exe
1.3 Install Option 2 - ACU Install
Automatic Client Upgrade (acu.exe) checks the
Novell Client major, minor, and Support Pack
versions previously installed on the workstation.
If the workstation requires only the Support Pack
updates, setupsp.exe will be launched instead of
the full Client Install to update the software on
the workstation.
For example, when acu.exe runs on a workstation
with the Novell Client 4.90 for Windows
NT/2000/XP installed, the setupsp.exe program is
executed. A workstation with an old client
version or no client installed will run the full
Novell Client install.
Available options for configuring the acu.exe are
described in 1.6 Acu.exe Functionality.
1.4 Install Option 3 - Installing the Novell Client
with the Support Pack Integrated
Update the Novell Client 4.90 for Windows
NT/2000/XP source files located in the
sys:public\client\winnt\i386 by copying the
Support Pack files from products\winnt\i386 to
sys:public\client\winnt\i386\. This copy will
overwrite the corresponding files in the full
Novell Client source directory.
The Support Pack download file contains files in
all languages. To avoid issues, remove the
language directories that do not correspond to
directories in the full client 4.90 installation
already on the workstation. There are NLS-related
directories within the Support Pack extracted
directory structure: winnt\i386\nls\language,
winnt\i386\admin\nls\language,
winnt\i386\nal\nls\language, and
\winnt\i386\rm\nls\language. Delete the unneeded
language directories from both locations.
Run the setupnw.exe program to install the
integrated Novell Client and Support Pack.
In cases where both compressed and uncompressed
versions of a file end up in the same directory,
the installation will automatically install the
uncompressed file. It is not necessary to delete
the compressed files.
1.5 Setupsp.exe Functionality
The setupsp.inf file contains a
[ServicePackOptions] section through which
additional setupsp.exe behavior can be
controlled. The default values for the option
section have changed and are as follows:
[ServicePackOptions]
Reinstall = NO
DisplayInstallPrompts = YES
UpdateNICI = YES
UpdateNMAS = YES
UpdateNetIdentity = YES
RebootOnCompletion = PROMPT
PromptUserOnCompletion = YES
Reinstall
Setting the value Reinstall = NO disables the
ability to reinstall the Support Pack, if the
current Support Pack has already been installed
on the workstation. For example, once the Support
Pack has been installed successfully, running
setupsp.exe will not install the Support Pack
again. When the value is set to YES it allows the
Support Pack installation to re-apply the updates
even though the current Support Pack may have
already been installed.
DisplayInstallPrompts
Setting the value DisplayInstallPrompts = YES
displays all dialogs regarding the installation
of the Support Pack. When the value is set to NO,
no dialogs will be displayed during the Support
Pack installation.
DisplayInstallPrompts has no affect on the
RebootOnCompletion or PromptUserOnCompletion
values.
productupdate
The UpdateNICI, UpdateNMAS, UpdateNetIdentity
parameters indicate whether SETUPSP.EXE is to
install updates to the optional products included
with the Novell Client. The product will only be
updated if is has been detected on the
workstation prior to the Support Pack
installation.
RebootOnCompletion
Setting the value RebootOnCompletion = PROMPT
prompts the user to decide whether the
workstation should be shut down and restarted
after the Support Pack installation completes.
The PromptUserOnCompletion setting has no effect
when RebootOnCompletion is set to PROMPT.
Setting the value RebootOnCompletion = YES
restarts the workstation after the Support Pack
installation completes without waiting for the
user to acknowledge any prompts.
RebootOnCompletion = NO exits the Support Pack
installation without restarting the workstation.
PromptUserOnCompletion
The PromptUserOnCompletion setting controls
whether the user is advised that the Support
Pack install completed prior to exiting the
installation program. Setting the value
PromptUserOnCompletion = NO exits the Support
Pack installation without waiting for the user to
acknowledge any prompts.
Setting PromptUserOnCompletion = YES displays an
informational prompt upon completion of the
installation process. The user must simply press
OK and does not have a choice to override or
force a reboot. This prompt only confirms that
installation completed prior to whichever
post-install action will take place (whether
setupsp.exe will just exit or will reboot the
workstation, depending on whether
RebootOnCompletion is set to YES or NO).
1.6 Acu.exe Functionality
In addition to providing all the functionality
Automatic Client Upgrade (acu.exe) has previously
provided, it also provides administrators with an
additional method for executing setupsp.exe on
workstations that already have client software
installed. An administrator can choose to use
acu.exe to launch setupsp.exe to provide
additional prompting or logging during the client
update process.
Normally the acu.exe application checks only the
workstation's major and minor client version (and
the administrator's major and minor internal
version, if defined) to determine whether acu.exe
should attempt to launch the full setupsp.inf
install.
If the workstation major and minor client version
checks show that the workstation already has the
same major and minor client version that is
available for install, acu.exe will now also
check the workstation ServicePack value (as
setupsp.exe does) to determine whether the local
workstation has the Support Pack installed. If
the workstation is in need of only the Support
Pack updates, acu.exe then launches only
setupsp.exe instead the full client
upgrade/install process.
The acu.ini file contains a [ServicePack] section
through which this new behavior can be further
controlled. The default values for the
[ServicePack] section are as follows:
[ServicePack]
Check = Yes
Setting the value Check = Yes causes acu.exe to
take the [ServicePack] into account, as described
previously.
Setting the value Check = No causes acu.exe to
ignore the workstation [ServicePack] value and
will not run setupsp.exe instead of a full client
upgrade/install. This behavior can also be forced
by launching acu.exe with an /NSP command line
switch. For example:
ACU.EXE /NSP
2.0 Known Issues
2.1 Additional Issues
For a list of additional changes made since the
last Support Pack, see TID 10090516
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10090516.htm).
2.2 SLP v2 Versus SLP v1
SLPv2 is now provided with the Novell Client 4.9
Support Pack 2. This release includes an advanced
setting to select the SLP protocol version to be
used (automatic, SLPv2 only, and SLPv1). The
default is automatic which means that the client
will try to determine the protocol version
supported by Directory Agents (DA) that are
contacted. The bias is for SLPv2. This means that
the client will first attempt to contact a DA
with an SLPv2 DA service request and if the DA
responds the SLPv2 will be used exclusively with
that DA. If no response is received, then the
client will send an SLPv1 service request and if
a response is then received SLPv1 will be used
exclusively with that DA.
The <unscoped> scope is only supported with
SLPv1. This means that certain unscoped features
are not available when running in SLPv2 mode. For
example if a scope is configured with the static
option then only that scope will be used and
other scopes advertised by DA will be ignored.
With SLPv1 if a scope does not match any known
DA, it can be sent to an SLPv1 DA that supports
<unscoped>. In a network where DAs are capable of
supporting both SLPv1 and SLPv2, SLPv2 will
always be selected and <unscoped> scopes with the
capability described above will not be available.
Thus, if a configured scope is not supported by
any SLPv2 DA, the client has no other option but
to multicast.
For additional information, see TID 10092523
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10092523.htm).
2.3 Update Agent
2.3.1 Client Update Service for Novell
The loading of the "Client Update Service
for Novell" can be configured from the
Update Agent property page. To load the
Client Update Service for Novell, select
both the "Enable Update Agent" checkbox
and the "Administrator Rights" checkbox.
Deselecting either of these two check
boxes will result in the Client Update
Service for Novell not being loaded during
the workstation boot process.
2.3.2 Administrator Rights limitations
The "Administrator Rights" option works
only if the "Update Location" and/or
"Previous Install Location" is a URL or if
the Update Location and/or Previous
Install Location is a UNC path connected
using NCP. The Administrator Rights option
does not work if the Update Location
and/or Previous Install Location is a
mapped drive connected using NCP, or if
the Update Location and/or Previous
Install Location is either a mapped drive
or a UNC path connected using CIFS.
2.4 SHELL_VERSION login script variable
Starting in the Novell Client 4.9 SP2, the
SHELL_VERSION login script variable returns the
version displayed in the Novell Client Properties
to provide more effective Novell Client version
testing from within the login script.
Any existing uses of SHELL_VERSION which are not
enhanced by the additional data returned in
Novell Client 4.9 SP2 can be changed to reference
REQUESTER_VERSION instead.
For additional information, see TID 10092676
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10092676.htm).
2.5 ZENworks 6.5 Middle Tier fails to authenticate
Users and workstations can no longer authenticate
through the middle tier after installing the Novell
Client 4.9 SP2. For more information, see
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10093371.htm
3.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.
U.S. Patent Nos. 5,157,663; 5,349,642; 5,455,932;
5,553,139; 5,553,143; 5,594,863; 5,608,903; 5,633,931;
5,652,854; 5,671,414; 5,677,851; 5,692,129. U.S. and
Foreign Patents Pending.
NDPS, NetWare, Novell, and Novell Client are a
registered trademarks of Novell, Inc. in the United
States and other countries.
All third-party products are the property of their
respective owners.