Installing the NSL Client without local Administrative Rights
(Last modified: 31Jan2006)
This document (10100347) is provided subject to the disclaimer at the end of this document.
fact
Novell ZENworks 6.5 Desktop Management - ZfD6.5
Novell ZENworks 7 Desktop Management - ZfD7
Novell Application Launcher (NAL)
Novell SecureLogin version 3.5
Novell SecureLogin version 3.51 SP3
Novell Nsure SecureLogin 3.51.3
goal
Installing the NSL Client without local Administrative Rights
How to install the SecureLogin Client with ZENworks
Installing the SecureLogin Client with elevated rights through ZENworks
symptom
Error: "Unable to instantiate ScriptBroker module: 80040154" when installing the NSL Client
fix
Two other TID's talk about how to do a silent install of the NSL Client so that it doesn't prompt for any information (through a "setup.exe -s command), and then issuing the commands to register the relavant .DLLs afterwards. Those TID's are: 10096072 and 10095116.
note
Running the actual Service and .DLL registration commands through the ZENworks workstation object, or local system account doesn't work successfully because the SLBROKER.EXE does some user and registry hive checking on registration, and will fail if the real user logged into the box isn't part of the local Administrators group. But, doing it through a snAppShot has the correct effect because all of the proper registry keys are created without any code checking by SLBROKER.EXE to verify the user's group memberships.
document
Document Title: | Installing the NSL Client without local Administrative Rights |
Document ID: | 10100347 |
Solution ID: | NOVL105000 |
Creation Date: | 31Jan2006 |
Modified Date: | 31Jan2006 |
Novell Product Class: | Management Products |
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.