Summary
Due to certain restrictions in the standard user access, Northern requires some form of Administrator interaction to install the Active X Controls.
More Information
It was intended to run through a GPO, but you can quite possibly run this through other means.
Resolution
1.1 The easiest, and recommended way to deploy the ActiveX controls is by allowing ActiveX downloads in IE. HOWEVER, this only need to be allowed for the local intranet security settings, so as long as they don't feel there is a threat of users for some reason creating and distributing malicious ActiveX controls, this shouldn't be an issue. Also, since our ActiveX package is signed and the ActiveX controls are marked as "Safe" they can disable the download of un-signed and un-safe controls. If this is not an option, see 1.2
1.2 The controls in the .\MyStorage\Controls\NSSEndUserControls.cab, must be manually installed, or deployed using a logon-script (see Creating administrative scripts in the Windows 200x help). To do this:
1.2.1 Un-pack the three ocx-files and the exe-file from said NSSEndUserControls.cab into the MyStorage share of the server
1.2.2 Create a vbs-file with the following code:
|
'Copy the client ActiveX files:
Set fso = WScript.CreateObject("Scripting.FileSystemObject")
Set WSHShell = WScript.CreateObject("WScript.Shell")
sysfolder = fso.GetSpecialFolder(SystemFolder)
fso.CopyFile "\\[SERVER]\NSS\MyStorage\Controls\NSP_user.ocx", sysfolder & "\System32\NSP_user.ocx"
fso.CopyFile "\\[SERVER]\NSS\MyStorage\Controls\NSS_Admn.ocx", sysfolder & "\System32\NSS_Admn.ocx"
fso.CopyFile "\\[SERVER]\NSS\MyStorage\Controls\NSS_Cch.exe", sysfolder & "\System32\NSS_Cch.exe"
fso.CopyFile "\\[SERVER]\NSS\MyStorage\Controls\NSS_Lang.ocx", sysfolder & "\System32\NSS_Lang.ocx"
WshShell.Run "regsvr32 /s " & sysfolder & "\System32\NSP_user.ocx", 1, True
WshShell.Run "regsvr32 /s " & sysfolder & "\System32\NSS_Admn.ocx", 1, True
WshShell.Run "regsvr32 /s " & sysfolder & "\System32\NSS_Lang.ocx", 1, True
Set fso = Nothing
Replacing [SERVER] with the name of your NSS server.
|
Note that this will copy and register the controls every time the user logs in, this can be useful if you want to make sure that they always run the latest version of the controls. You can then update these controls if you install an new version of NSS (of course with option 1.1 this will be done automatically). If you do not wish for the script to run every time, you will need to add a check to see if the files already exist and are registered.
1.2.3 Add the vbs-file as a logon script for the user-group(s) that it applies to.
