Version 1.2.0 June 19, 2013
Download links and version changes at the bottom of this page.
App-V 5 supports adding a reference to scripts in the Deployment and User Config XML files. While the new capabilities are great, there are things that we need to do in scripting that need some added help, and that is where this tool comes in.
In a recent training class we ran on App-V 5, we found that there are several problems the App-V scripting solution at present. This list was further enhanced by a contract sequencing of an app that we did for a Cloud Service provider:
ScriptLauncher is an executable that you place on the client machine and reference as the scripting program in your config.xml files.
You make Scriptlauncher.exe the primary script program to run, and then place the complete command line of the script you want to run
(including any environment variables) as arguments to the program.
ScriptLauncher will parse and dereference the EnvironmentVariables for you and run the command, even if the App-V Scripting subsystem will not.
ScriptLauncher will create an added environment variable for use in the script called "EffectiveUserName". Use this variable in place of UserName when you run scripts that run in the User Security Context. I love using this to reference C:\Users\%EffectiveUserName%\AppData\Roaming.
ScriptLauncher is a 32-bit console application that produces no output. This means that unless the command you run produces a window, the user will not see anything when the script is run.
Version 1.2 also handles command parameters better than the initial version. Previously, some scripts had problems with path names that included spaces when passed to programs like robocopy. The parameters now preserve any quotation marks you put in the arguments in the config file.
There is no installer. Just copy the file into a folder on the client.
You can place it in any folder contained in the PATH variable and reference it by name alone, or you can place it in a new folder and reference it with the full path.
You may want to add an environment variable to the client system to indicate where the scripts are centrally stored.
The example below uses a variable called SCRIPTHOSTSYSTEM to point to the site-specific name of the server hosting the scripts.
Because some of the App-V scripts run under the user context, and some under the system context, you should make the variable a system environment variable.
Such a variable is easily pushed out via Group Policy.
The TMurgent website contains this Blog Post which provides some information about the
kind of scripts that you can add to the Deployment and User Config files, and the context that they run under.
You may also need to look at this post about environments and contexts to get a better grip on what is going on.
Below are some examples of use of Scriptlauncher:
Some Notes about the Config.xml Path element...
Some Notes about the Config.xml Arguments element...
Some Notes about problems Scriptlauncher doesn't address...
TMurgent believes in giving back to the community. ScriptLauncher is free for for use./p>
Anywhere the App-V Client works.
TMurgent has a bunch of tools on this page. Usually they are free, unless you are a Software Vendor.
Tools for performance have a segregated list here.