Scripts > Application Deploy

Application Deploy is a wizard tool to automatically create a script to distribute vendor installation packages (typically setup.exe). The wizard walks you through a step by step process resulting in a script you can schedule to deploy an application to any managed machine.

Step 1: How do you want to deploy the application?

The application needs to execute on the managed machine to install. The wizard generated script tells the remote machine where to get the patch file to execute. The Patch Deploy Wizard asks you in step 4 if you want to "Send the installer from the VSA server to the remote machine and execute it locally" or "Execute the installer from a file share on the same LAN as the remote machine."

Pushing the patch down to each machine from the VSA may be bandwidth intensive. If you are patching a multiple machines on a LAN no internet bandwidth is used to push out the patch. Each machine on the LAN can execute the patch file directly from a common file share.

Step 2: Select the application install file or Specify the UNC path to the installer stored on the same LAN as the remote machine.

If "Send the installer from the VSA server to the remote machine and execute it locally" was selected, then the installer file must be on the VSA server. Select the file from the drop down list.

If the installer file does not appear in the list then it is not on the VSA server. Click the here link to upload the file to the server.

If "Execute the installer from a file share on the same LAN as the remote machine" was selected, then the installer file must be on the remote file share prior to running the application deploy script. The specified path to the file must be in UNC format such as \\computername\dir\.

If the file is not already on the remote file share, you can put it there via FTP. Click the here link to start FTP.

Step 3: What kind of installer is this?

The wizard need to know what kind of installer was used by your software vendor to create the install package. The VSA provides a small utility to automatically identify all supported installer types. Download and run kInstId.exe to automatically identifies the installer type. Supported installer types are:

Step 4: Name the script

The new script appears under the Install Tab. Master administrators can specify a shared script or private script. Standard Administrators can only create private scripts.

Step 5: Reboot the machine after installing the application.

Check this box to automatically reboot the managed machine after running the install. The default setting is to not reboot.