Changes
no edit summary
=Overview=WPKG keeps its configuration in three XML files, is a script-driven installation engine for applications. Its main logic is contained within the wpkg.js file which can is to be changed easily run on each client in an editor like ''vi'' or ''mcedit''a priveleged user context. It can run a number of checks (i.e. check against file versions, file existence, uninstall entries, registry entries or even automaticallythe return value of an arbitrary command) and trigger arbitrary installation commands depending on the result.
* [[hosts.xml]] - defines the hosts and associated profiles, which these hosts will use,
* [[profiles.xml]] - defines the software packages or scripts, which will be installed/executed on hosts,
* [[packages.xml]] - defines how to install and uninstall software packages. In other words, it is a list of all applications and scripts that can be deployed or executed on workstations.
* [[config.xml]] - global WPKG configuration options
'''Note:''' Make sure that your server is not providing any SMB-based services (eg, DC, shared printer or shared folder other
CNAME or IP address to refer to the server in the WPKG Client.
<code>cscript \\server\wpkg\wpkg.js /synchronize /quiet</code>
When WPKG is called on a Windows workstation with these options, it will do the following:
Of course, WPKG has many more options. See [[WPKG flags]] for details.
You will likely run it manually as a local or domain Administrator when you would be still testing WPKG<br>
When WPKG is installed, it runs and installs software automatically in the background, whenever the workstation boots up, even when no one has logged on to that PC.
=Missing functions=
WPKG cannot do everything (yet). Among the things it does not do are the following:
=== Installation of the Operating System ===
WPKG comes into play after the O/S is installed and running. For everything before that use approaches like [http://technet.microsoft.com/en-us/library/cc766320(WS.10).aspx RIS/WDS] or [http://unattended.sf.net Unattended] for automated network-based installation of the O/S)
=== "Software push" functionality ===
WPKG is a client-centred approach to software installation, so it does not support "pushing" software. However, you are free to issue Remote Procedure Calls to clients in order to trigger the start of the WPKG service or even directly the start of the WPKG command
===Software repackaging===
WPKG is about scripted, unattended installations. In our experience, repackaged software while running fine most of the time, might cause obscure problems in rare cases and leaves the admin standing without any reasonable support from the software companies creating the packages. [http://unattended.sourceforge.net/installers.php#repackaging This article at unattended.com] elaborates some more on this matter.
===Integrity or signature checking of installation packages===
This is a security feature and while surely a valuable gain, nobody has yet been found to implement it.
===Multicast deployments===
Multicast transfers would be very valuable in narrow-bandwidth environments with shared media and a large number of clients - typically large wireless networks or networks connected through a narrow link (e.g. a 10 Mbps laser link). WPKG uses file services and installs software packages synchronously, using multicast would necessarily mean a different approach to file transfers and asynchronous installations. Anyway, a lot can be done using a local caching directory, a multicast transfer daemon like [http://www.tcnj.edu/~bush/uftp.html uftp] and some intelligent scripting combined with WPKG.
[[category:Documentation]]