Authors: Shashikala BV
This AppNote describes how to deploy the NSL 7.0.1 64-bit client along with dependent components (like NICI or .Net 3.0) on a pool of systems through ZCM in larger deployments.
Table of Contents
1. Problem Statement
2. NICI dependency
2.1 Step 1 - Creating Bundles
2.2 Creating NICI 32-bit Bundle
2.3 Creating NICI 64-bit Bundle
2.4 Create Bundle for Responsefile.ini
2.5 Create NSL Client Bundle
2.6 Adding the Dependency bundles to the Primary bundle
2.7 Deployment at Client with ZCM Agent
3. .Net Dependency
SecureLogin or NSL can be deployed through ZCM agent in the larger deployments. Users can install them manually if the deployments are small in numbers. What if an administrator wants to install NSL on pool machines from a remote location? Though administrator can use ZCM for the same, there is a prerequisite for NSL 7.0.1 64bit client installation which looks for both NICI 32 and 64-bit client. (Refer to Section 3.2 in NSL 7.0.1 Readme document.
The following screen shot shows the same.
Install 32 and 64bit NICI first and then install NSL 64bit client.
It has been assumed that NICI 32 and 64bit clients are already installed before the NSL 64bit client is installed successfully. Now that a system is ready, we can create the bundles using ZCM agent which can be used for larger deployments. We need the bundles for the following files to perform a silent install through NSL using the responsefile.ini.
Usually the responsefile.ini which got generated while installing NSL will be available at C:/NSLFiles/responsefile.ini
The following screen shots will help in creating the required bundles.
Open a browser and enter the url of the ZCM server - E.g.: http://<IP address of ZCM server>/Zenworks. You should see the screen as shown below. Login to the ZCM server by giving the admin credentials.
On the left panel select Bundles.
Click on New -> Bundle
Select File Bundle and click Next
Select Install File(s) and click Next
Enter bundle name and click Next
Add NICI 32bit client and click Next
Before clicking on Finish, select Define Additional Properties
Select Launch and click on Add to select Launch Executable
Enter NICI 32bit file as shown below under command.
Click on Apply.
Now lets create the NICI 64bit bundle. NICI 64bit is a msi file. Here there is a slight difference in creating the bundle for .msi file. Repeat the same step of Bundles -> New Bundles and select Windows Bundle form the Bundle Type since it is a .msi file.
Click on Next.
Select MSI Application from Bundle Category and click on Next.
Enter Bundle Name and click on Next.
Under .msi file click on the browse icon and select 64bit NICI. Accept the default values for rest of the options and proceed.
Click on Next.
Click on Next
Click on Finish.
Now create the bundle for responsefile.ini. This is a file bundle. Follow the same steps you used to create the 32bit NICI. At the following screen, don't select Define Additional Properties. Finish the bundle creation
Once the responsefile bundle is created. Create the bundle for the NSL 64bit client. Since this is a .msi file, follow the same steps you used to create the 64bit NICI until the following screen.
Select Novell SecureLogin.msi by browsing through the folders. Note that under Install Parameters you need to add PATHTOISS=<path where responsefile.ini is copied> needs to be added after " and before /qn as shown in the screen. In this E.g: it is entered as PATHTOISS=c:/responsefile.ini.
Click on Next and accept the default values in the next screens and finish the bundle creation.
We have now created File bundles for NICI 32bit, responsefile.ini and Windows MSI bundles for NICI 64bit and NSL 64bit client. The NSL 64bit client is the main bundle that needs to be deployed using ZCM which has dependencies on NICI 32bit, NICI 64bit and responsefile.ini. Now let's add the dependency bundles to the NSL 64bit client bundle.
Goto Bundles -> select NSL 64bit client bundle -> Actions -> Install – Add -> Install Bundle as shown below:
Now select the bundle from the list, and add all three dependent bundles in similar manner. After this step go back to the Summary tab and click on the URL of the Dependency Bundles. The following screen will be displayed:
Once this is done, if prompted, increment the version.
Once the Primary bundle is configured it can be assigned to either Hosts or Users. For illustration purpose in this document we are assigning it to device.
Now add a device / devices to the NSL 701 64bit bundle. Under Device Assignments select Add.
A list of devices which are registered with the ZCM servers gets displayed. Select the device / devices to which you want to deploy the bundles and click OK.
Select the locations to place the shortcuts for the bundle. By default the Application Windows will be enabled. Select the other preferences. Click on Next.
From the Schedules screen select the schedules. Distribution and Launch schedules are must. Click on Next.
From the Distribution Schedule select Install Immediately after Distribution and Launch immediately after installation (if required) and click on Next.
From the Launch Schedule screen modify the fields only if needed else accept the default values.
Click on Next and finish the installation.
Now we are done with assigning the bundles to devices.
On the client systems, right click on the ZENworks icon and select refresh. ZENworks refresh starts and the NSL 701 64bit client bundle gets copied on to the desktop and starts the installation according to the dependencies added in the bundles.
Once the installation completes, the system automatically gets rebooted and prompts for NSL login.
We are now done with deploying NSL 701 64bit bundles through the ZCM client.
NSL gets installed without any problems on a system where .Net applications are not running. If there are .Net applications like iFolder installed before or after NSL installation, it also installed .Net framework. When tried to access iFolder it gives an error "Novell iFolder Windows Client has encountered a problem and needs to close. We are sorry for the inconvenience." and it crashes. This is because iFolder installs .Net framework version 2.0 whereas for Uto support .Net SSO NSL requires .Net framework 3.0 or above.
Install .Net 3.0 or above where ever there are .Net applications running.