ZCM 10.2.2 nalwin patch - TID 7004250
This document (5065660) is provided subject to the disclaimer at the end of this document.
patches this patch supersedes
patches that supersede this patch
| Product | Status | Next Superceded By | Last Superceded By |
|---|---|---|---|
| Novell ZENworks Configuration Management 10.2.2 | Obsolete | ZCM 10.3.0a upgrade manual import file | ZCM 10.3.0a upgrade manual import file |
patch attributes
document
abstract
This patch for ZCM 10.2.2 contains updated NalWin.exe and NalShell.dll files that address the issue of the NAL Window not being able to exit cleanly on logoff. See TID 7004250 "ZENworks Application Window (NALWIN) does not exit on logout unless a bundle has been selected" for details.
This is fixed in version 10.3 - see TID 7005455 "ZENworks Configuration Management SP3 (10.3) - update information and list of fixes" which can be found at http://www.novell.com/support
details
Abstract:
This patch contains updated NalWin.exe and NalShell.dll files that addresses the issue of NAL Window not being able to exit cleanly on logoff, this patch is only for use on systems that have been upgraded to ZCM 10.2.2.
Overview:
The NalWin.exe and NalShell.dll files in this patch replace the NalWin.exe and NalShell.dll on the managed Windows device. The updated NalWin.exe and NalShell.dll allow NAL Window to exit cleanly on logoff.
System Requirements:
ZCM 10.2.2 (there is a separate patch for ZCM 10.2.1 available)
Windows 2000
Windows XP
Windows Vista
Windows 7
Installation:
1. Unzip ZCM_10_2_2_FTF_20091217_532839
This zip file contains:
a. x86 version of
- NalWin.exe (in directory NalWin.exe\Release)
- NaShell.dll (in directory NalShell.dll\Release)
b. x64 version of
- NalWin.exe (in directory NalWin.exe\x64)
- NaShell.dll (in directory NalShell.dll\x64)
c. MSI packages for this FTF
- novell-zenworks-windows-desktop-10.2.2.46883.msi
- novell-zenworks-windows-desktop-langs-client-10.2.2.46825.msi (x86 version)
- novell-zenworks-windows-desktop-langs-client-10.2.2.46825.x86_64.msi (x64 version)
The MSI packages can be used to apply the FTF for new agent installations by modifying the Agent Packages on the server.
d. ZCM_10_2_2_FTF_20091217_532839.md5sum which contains the MD5 hashes for all the files in this patch
2. The NalWin.exe and NalShell.dll files replace the existing NalWin.exe and NalShell.dll in the %ZENWORKS_HOME%\bin directory on a managed device. Before installing the new file, make a backup copy of the original NalWin.exe and NalShell.dll files and rename the original files to be something like NalWin.exe_original and NalShell.dll_original. Since the NalShell.dll file is in use during this operation, the file cannot be deleted, but it can be renamed. NalWin.exe can be modified if the ZENworks Application window is not open.
Manual Installation
1. Copy the relevant (32-bit or 64-bit, see step 1 in "Installation" above for the locations) NalWin.exe and NalShell.dll files from this patch to the %ZENWORKS_HOME%\bin directory (on 64-bit devices, NalWin.exe and NalShell.dll are installed in the "Program Files(x86)" folder). Make sure that the user that copies the files is a local administrator, it is not sufficient to use elevated permissions via UAC.
2. After copying the new files, relogin to the managed device.
Installation through ZCM Bundles:
Since there is a different exe/dll for each architecture, it will be necessary to create 2 bundles using "architecture" as a system requirement. Since the files will be in use, it will be necessary to run the bundle as dynamic administrator so that the files are automatically replaced on the next reboot.
1. Create a File bundle for 32-bit workstations (since the exe/dll files are specific to a particular architecture, x86 or x64, it is necessary to create a bundle for each architecture).
2. Add an install file action and upload the 32-bit (see step 1 in "Installation" above for the locations) NalWin.exe and NalShell.dll. Enter %ZENWORKS_HOME%\bin as the destination directory.
3. Edit the install action: click on "more options" and select 'Run as dynamic administrator'.
4. Add a system requirement "architecture" with the value of x86.
5. Optionally, add a reboot action if a forced reboot is desired.
6. Assign the bundle to the device, choosing the distribution and launch schedules.
7. Install the bundle on the device.
8. Repeat steps 1-7 to create a bundle for 64-bit workstations, selecting the 64-bit files (see step 1 in "Installation" above for the locations) and x64-bit architecture for the system requirement.
Installation by modifying Agent MSI packages:
Below are the steps to repackage the pre-agent install packages on servers with the modified MSI.
1. Move the following files
novell-zenworks-windows-desktop-10.2.2.46407.msi
novell-zenworks-windows-desktop-langs-client-10.2.2.46325.msi
novell-zenworks-windows-desktop-langs-client-10.2.2.46325.x86_64.msi
out of the msi directory
Windows:%ZENWORKS_HOME%\install\downloads\msi
Linux: /opt/novell/zenworks/install/downloads/msi
renaming the files is not sufficient - move them to another directory.
2. copy the following files
novell-zenworks-windows-desktop-10.2.2.46883.msi
novell-zenworks-windows-desktop-langs-client-10.2.2.46825.msi
novell-zenworks-windows-desktop-langs-client-10.2.2.46825.x86_64.msi
to the msi directory
Windows:%ZENWORKS_HOME%\install\downloads\msi
Linux: /opt/novell/zenworks/install/downloads/msi
3. at the server console/command prompt, run
novell-zenworks-configure -c CreateExtractorPacks -Z
Note that option 1 is already checked, select 2 and press enter.
Press enter one more time to start the rebuild process for the default deployment packages. See 8.4 Rebuilding Packages in the "ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference" at http://www.novell.com/documentation/zcm10. This section also contains information on how to rebuild any custom packages that may have been previously created.
This process will need to be repeated for each primary server running ZCM 10.2.2 that is used for agent deployments.
Uninstalling:
Before uninstalling the patch files, make sure that a backup copy of the original files are available. Rename the patched NalWin.exe and NalShell.dll in the %ZENWORKS_HOME%\bin-directory and then re-install the original NalWin.exe and NalShell.dll and relogin to the managed device. For the deployment packages, reverse the steps in "Installation by modifying Agent MSI packages:" above, i.e., delete the new MSI packages copied in step 2 above, and restore the files moved out in step 1 of that section.
Known Problems and Limitations:
N/A
change log
1 April 2010 - updated readme with details of fix
file contents
| Files Included | Size | Date |
|---|---|---|
| ZCM_10_2_2_FTF_20091217_532839.zip | 6.1 MB (6472987) | 2010-01-02 06:39:20 |
| readme_5065660.html | N/A | 2011-07-01 08:37:34 |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
Novell is a registered trademark of Novell, Inc. in the United States and other countries. SUSE is a registered trademark of SUSE Linux AG, a Novell business. *All third-party trademarks are the property of their respective owners.
© 2007 Novell, Inc. All Rights Reserved.