Difference between revisions of "User contributed software"

Revision as of 18:14, 3 August 2009

InfoMessage

Info: Displays a simple, configurable, centered message box on the screen using HTML (IE5-IE7). See .js source header for more information.
Author: Brian White
URL: http://www.megaupload.com/?d=RQUSZPFS
Screenshots: Screenshot #1 | Screenshot #2
Mailing list discussion:

• http://lists.wpkg.org/pipermail/wpkg-users/2008-June/003513.html

wpkgMessage

Info: Shows little window which can be used to tell the user what WPKG does at the moment.
Author: grubi
Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-message-english.htm
Download URL: ftp://ftp.gig-mbh.de/software/wpkg-message.zip
Mailing list discussion:

• http://lists.wpkg.org/pipermail/wpkg-users/2008-February/thread.html#2628 ("wpkg via Group Policies" thread)

wpkgCreateReport

Info: Generates an Excel sheet out of the computer's wpkg.xml files showing which packages are installed on which computers.
Author: grubi
Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-create-report-english.htm
Download URL: ftp://ftp.gig-mbh.de/software/wpkg-create-report.zip

wpkgListPackages

Info: Command line script displaying all packages sorted according to the package's priority setting.
Author: grubi
Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-list-packages-english.htm
Download URL: ftp://ftp.gig-mbh.de/software/wpkg-list-packages.zip

"Ugly perl script to check if packages are installed on a set of workstations"

Info: When you run the script, it will evaluate the list of packages that should be installed with the packages that are installed on each computer in the status directory. It then prints the differences. If the program gives no output, then everything is up to date. I use this program to send a list to our desktop techs about which computer are out of compliance.

Author: Chris Crow
Script source: http://lists.wpkg.org/pipermail/wpkg-users/2008-March/002820.html
Mailing list discussion:

• http://lists.wpkg.org/pipermail/wpkg-users/2008-March/thread.html#2823 ("Ugly perl script to check if packages are installed on a set of workstations." thread)
• http://lists.wpkg.org/pipermail/wpkg-users/2008-April/002863.html
• http://lists.wpkg.org/pipermail/wpkg-users/2008-April/002876.html
• http://lists.wpkg.org/pipermail/wpkg-users/2008-June/003514.html

Scripts for generating hosts.xml from Active Directory

Info: Scripts written in different languages (Perl, bash, vbScript) which pull hosts.xml from Active Directory OUs automatically
URL: http://wpkg.org/WPKG_with_Active_Directory

Script for checking if a process is already running

Info: Sometimes, you don't want to make an upgrade or installation if a user has already started a given process, because:

• upgrade could fail, as the files are in use,
• if the installer is "smart", it could kill the running process, without asking the user to save (precious) work,
• some software (like certain browser plugins) won't install if some other software is running (i.e., a browser).

URL: http://wpkg.org/Script_for_checking_if_a_process_is_already_running

Generic Library for scripted checks

Author: Keith Jones
Mailing list discussion: http://lists.wpkg.org/swish.cgi?query=ideas+for+features&metaname=swishtitle

Info: WPKG.Utility, a COM-based utility library to support scripted 'Execute' checks.

Tired of writing scripts to support custom 'checks' in WPKG ?
Tired of writing parameter parsers for each and every one of them?

This is a prototype script library based in a .wsc (Windows Scripting Component) file that aims to reduce your typing to the minimum.

It provides 2 resources;

• A way to consolidate and collect useful functions for administrators.
• A simple parser framework to develop reusable 'scriptlets'.

...and only takes one line in your scripts to implement!

Features include;

• Simple parsing of command-lines to validate custom parameters.
• A growing collection of built-in helper routines.
• A simplified approach for less experienced admins.
• All code is written in JScript to maintain compatibility with WPKG.js.
• Illustrations of 'less used' techniques.

Documentation:
gettingstarted.txt - A quick guide to using WPKG.Utility.
integrating.txt - A guide to using scriptlets with WPKG.
parser.txt - A rough guide to using the parser to make scriptlets.
advanced.txt - A guide to more advanced techniques.
history.txt - About the origins of WPKG.Utility.
changes.txt - The changelog for WPKG.Utility.
aboutWSC.txt - A rough guide to Windows Scripting Components.
thoughts.txt - General thoughts.
comingsoon.txt - A rough guide to things that I'm thinking about.

Examples
DiskSpace.js - A documented version of the DiskTotal.js script

Code:

WPKG.Utility - The WPKG.Utility component library.

 Versions : V110,V110-01

Scriptlet Library:

Please note: These scripts need amendments made to them to locate the WPKG.Utility .wsc file.
The WPKG.Utility component can be detected, if you place it into the same folder as the scripts.
You will have to replace the two lines setting utilityPath and utility at the top of the scripts with the following.

var fso		= new ActiveXObject("Scripting.FileSystemObject");
var path		= WScript.ScriptFullName;
var base		= fso.GetParentFolderName(path);
var utilityPath	= fso.BuildPath(base,  "Utility-V110-01.wsc");
var utility		= GetObject("script:" + utilityPath);

DiskTotal.js - Checks a drive for a given total space.

Versions : V101

Usage: [cscript.exe] DiskTotalVxxx.js <Drive|Path> <lessthan|lessthanorequalto|etc> <Megabytes>

Returns: 0, if the test succeeded, 1 if the test failed.

DiskFree.js -  Checks a drive for a given free space.

Versions : V101

Usage: [cscript.exe]DiskFreeVxxx.js <Drive|Path> <lessthan|lessthanorequalto|etc> <Megabytes>

Returns: 0, if the test succeeded, 1 if the test failed.

DiskExists - Checks to see if a drive physically exists.

Versions : V101

Usage: [cscript.exe]DiskExistsV101.js <Drive|Path>

Returns: 0, if the test succeeded, 1 if the test failed.