WKPG Deployment Tool

From Research
Revision as of 20:31, 22 February 2018 by Lars (talk | contribs) (→‎Manual Client-side Operation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Overview

WPKG is an automated software deployment, upgrade and removal program for Windows.

It can be used to push/pull software packages, such as Service Packs, hotfixes, or program installations from a central server (for example, Samba or Active Directory) to a number of workstations.

It can run as a service to install software in the background (silent install), without user interaction.

It can install MSI, InstallShield, PackagefortheWeb, Inno Setup, Nullsoft, other software installers or .exe packages, .bat and .cmd scripts and similar: no more repackaging to perform software installation.

WPKG is open source software.

How It Works / Documentation

Information on how WPKG works can be found at their website: wpkg.org

Files

The configuration files are located at \\sr-hurricane.iat.sfu.ca\software\wpkg

Manual Client-side Operation

The synchronization process can be manually triggered on the client workstation using the following steps:

  • Open a command window in Run as Administrator mode.
  • Connect to the software share on sr-hurricane by using this command:
    net use /user:username \\sr-hurricane.iat.sfu.ca\software password
  • Execute this command:
    cscript.exe \\sr-hurricane.iat.sfu.ca\software\wpkg\wpkg.js /synchronize /debug

Specifying a Profile to use

You can create custom profiles irrespective of the current machine's name by using the /profile:<profile> command.
For instance, if you have a profile for installing only SolidWorks, type this:
cscript.exe \\sr-hurricane.iat.sfu.ca\software\wpkg\wpkg.js /synchronize /debug /profile:profile-solidworks

Useful Tips and Tricks

  • The package-id name in the profiles.xml appears to be case-sensitive. It must precisely match the package id used in the package.xml file. Failure to do so will result in the package not being recognized, or even showing up during the client script execution.

Sources