Windows Software Distribution problem

(imported topic written by aruelos91)

I’m trying to create a software distribution for a particular application and running into a problem. It looks as if BigFix is cutting off the install before it has a chance to complete.

The software I’m trying to install is SecureCRT from VanDyke Software (www.vandyke.com)

Here’s the Action Script I’m Using:

wait “{pathname of system folder & “\msiexec.exe”}” /i “{(pathname of client folder of current site) & “__Download\VanDyke Software SecureCRT 6.1.msi”}” /qn /norestart

The files get installed to the “C:\Program Files” path, but none of the shortcuts are created and the application doesn’t get added to “Add and Remove Programs”.

I can run the silent install manually, but I’m unable to get the application to install from BigFix.

(imported comment written by BenKus)

Hi aruelos,

The BigFix Agent launches the application and lets it run so I don’t think it is cutting off the install in any way… Instead, I am guessing that the shortcuts are probably only put in the current user’s desktop and since the agent runs as SYSTEM, you won’t see the icons when you log in. See if you can find the msi option to install for “All Users”.

Ben

(imported comment written by SystemAdmin)

Hi Ben,

Im facing the issue as mentioned, exactly the same issue, the shortcut icon is not installed and also does not see the apps at the Add and Remove Programs.

The question is, if BigFix did not cut the install, the program should be found on the Add and Remove Programs right?

Please advise.

Thanks.

Jeremy

(imported comment written by MattBoyd)

Hey Jeremy,

Perhaps you’re not seeing it because it’s only being installed for the current user (in this case, SYSTEM). You could try something like this:

wait "{pathname of system folder & "\msiexec.exe"}" /i "{(pathname of client folder of current site) & "\__Download\VanDyke Software SecureCRT 6.1.msi"}" ALLUSERS=2 /qn /norestart

Note the ALLUSERS=2 property in the command above.

(imported comment written by SystemAdmin)

Hi Jeremy,

You can take another approach to see what’s going on. After installing, you should see the simple windows installer log file sitting in the system’s temp folder (e.g. c:\windows\temp). Sort by date modified, and look for a file called MSI*.log. You may see something in there as to what’s going on.

You can also create a verbose Windows installer, and put the logfile whereever you want. To the end of, just add: /l*v c:\windows\temp\MyLogFile.txt

e.g.:

wait “{pathname of system folder & “\msiexec.exe”}” /i “{(pathname of client folder of current site) & “__Download\VanDyke Software SecureCRT 6.1.msi”}” /qn /norestart /l*v “{pathname of folder “temp” of windows folder & “\MyLogFile.txt”}”

That might point you in the direction of what’s going on from the point of view of the Windows installer.

(imported comment written by SystemAdmin)

thanks guys, its work, i did tried with ALLUSERS at the first attempt but failed. After reading the post from boyd, tried with ALLUSERS=2… and its works…

May i know why we need to put it =2 ???

Thanks lot…

(imported comment written by MattBoyd)

Jeremy,

I’m not exactly sure why you need the “=2” but I’m guessing that MSI parameters must have accompanying values. Here’s an appdeploy.com FAQ that may be useful: http://www.appdeploy.com/faq/detail.asp?id=69

I’m happy to hear that you got it working :slight_smile: