Client Management Suite

I am using Symantec Client Management Suite version 7.5

I have been searching throught the forum discussions looking for a solution for the package I am deploying in our enterprise.

I have an MSI package with 10 license keys for the 10 assigned users.  Currently I have created 10 seperate package command lines to pass the license key to the MSI during deployment.

This means 10 seperate tasks to deploy the package.  I am wondering if a solution has been figured out how to handle this delema with one command line and using a license key list to compare logged on user to the username in the authorized list and pulling the license key.

I was able to do this using DS 6.9 by creating an exe in wise scripting to get the username from the environment and pull a value from an INI file.

I would like to have a central table that all three admins can look at here and modify if needed.

I know many of us are up against this same scenario, but has anyone figured out a way to make this work.

Appreciate any input on this

Greg Williams

Richmond VA.

 

 

Hi,

We tackled this using a simple batch script and used the %COMPUTERNAME% environment variable. This was useful to us as our software licenses are from a legal point of view provisioned to computers not users.

The  batch scripts we have are along these lines,

if "%COMPUTERNAME%"=="MACHINE_NAME1" ( SET KEY=DD-DD-DD-DD )
if "%COMPUTERNAME%"=="MACHINE_NAME2" ( SET KEY=XX-DD-DD-DD )
if "%COMPUTERNAME%"=="MACHINE_NAME3" ( SET KEY=YY-DD-DD-DD )
if "%COMPUTERNAME%"=="MACHINE_NAME4" ( SET KEY=ZZ-DD-DD-DD )
if "%COMPUTERNAME%"=="MACHINE_NAME5" ( SET KEY=AA-DD-DD-DD )

msiexec /i application.msi /key %KEY%

So in essense we check the computer name against a list with these if statements and set a key as appropriate.

If you really, really need to install the software based on the logged in user (rather than the computer), you'll need to conjur something up which looks at the user associated with the explorer process and then go from there. 

Some clever forum members here might have something a bit more elegant! 

I'd maybe run a pre req task which runs echo %username%>c:\temp\appuser\%username% and run it in the user's context. Then have a batch file for the main install which does a dir c:\temp\appuser /b to read the username.

I've knocked up a vbScript based on one we use to poke user reg-keys into the HKCU of logged on users when executing a package as SYSTEM.  Among a couple of methods I've used to get the logged users, this is quite simple and robust.  It is a sample and you'll need to edit it to fit your requirement.  I'm happy to help you do that if you need it after you've had a look.

The script will return 0 (zero = success) if there is no-one logged on or if no qualifying user is logged on.

It will return the exit code of the called installation command if it gets that far.

It will return the error code of any catastrophic script error, and log the error in the local application event log.

Let me know if this is any way close to what you need - remove "_.txt" from the attachment name to use.

When calling the script use:

Testing: just double-click it.
Executing from CMS:

WScript.exe //B "path\to\script.vbs"

The //B (batch mode) means that on error it will not display an error in the background, but it will exit and still return the error code and log to the local Application event-log.

Regards Darren.

 

HI Greg,

It's been a month -do you need any further help on this?

Kind Regards,
Ian./