KACE Product Support

Install.bat


start /wait msiexec.exe /qb /norestart /i vpnclient_setup.msi
copy xxxxx.pcf "C:\Program Files\Cisco\Profiles"
start /wait CreateShortCut.vbs
shutdown /r /t 15


CreateShortCut.vbs


Option Explicit
Dim objShell, objDesktop, objLink
Dim strAppPath, strWorkDir, strIconPath

strWorkDir ="C:\Program Files\Cisco Systems\VPN Client"
strAppPath = "C:\Program Files\Cisco Systems\VPN Client\ipsecdialer.exe"
strIconPath = "C:\Program Files\Cisco Systems\VPN Client\ipsecdialer.exe,0"

Set objShell = CreateObject("WScript.Shell")
objDesktop = objShell.SpecialFolders("AllUsersDesktop") 'this is where you assign where shortcut goes
Set objLink = objShell.CreateShortcut(objDesktop & "\Cisco VPN.lnk") 'this changes per install

' ---------------------------------------------------
' Section which adds the shortcut's key properties

objLink.Description = "Cisco VPN"
'objLink.HotKey = "CTRL+SHIFT+X"
objLink.IconLocation = strIconPath
objLink.TargetPath = strAppPath
objLink.WindowStyle = 3
objLink.WorkingDirectory = strWorkDir
objLink.Save

WScript.Quit


you can also use the .arguments property to have the shortcut automatically launch the vpn connection, but if you use multiple vpn connections this might not be advisable.

Thank you DyeHardFan,

I'm going over to work with the contractor I sub for tonight and we'll try doing it this way.

One question though -- what is to keep the script from installing over and over? Should there be an "if exist c:\xxxxx\VPN Client...." goto END or something like that?

Thanks dyehardfan - that's nearly verbatim how I did my Cisco VPN client as well.

RoverDrover - Do this as an MI, and if the software is present it doesn't run again.
Otherwise you could run it in the scripting tab and give it some litmus test like a smart label that is removed if a condition is true (like a custom inventory rule that looks for your config file). Add a verify stage to your script as well as a double check. You could certainly use "if exist c:\xxxxx\VPN Client...." goto END or something like that the problem there is that the script has to actually run to evaluate that statement; to be more efficient have something that only runs the script on machines that still need it.

Thank you, Christopher. You guys are helping me with two issues right now, and I appreciate it. Things changed, and I'm not going to get to work on the Kbox till this weekend, so don't think I'm just blowing off the good advice. I'll let you know how it goes and if I have more problems.

Both of you have a good week, and I appreciate your time,

Bob

Where would I set this up in KACE? Under a managed install or a script? If someone could provide a little more detail on how to get the install.bat configured in KACE.

You could set this up under either, it just becomes a matter of preference at the point.

Have you gone through your jump-start training yet?

Your trainer will go over distribution with you.