Changes

User contributed software

7,798 bytes added, 20:23, 3 October 2010
Undo revision 8429 by 174.54.240.129 (Talk)
==Contributions by the Main DeveloperInfoMessage ==
Shutdown Info: Displays a simple, configurable, centered message box on the screen using HTML (IE5-IE7). See .js source header for more information.<br />Author: Brian White<br />URL: http://www.megaupload.com/?d=RQUSZPFS<br />Screenshots: [http://i269.photobucket.com/albums/jj78/mscdexdotexe/developerstuff/message_ss2.png Screenshot #1] | [http://i269.photobucket.com/albums/jj78/mscdexdotexe/developerstuff/message_ss.png Screenshot #2]<br />Mailing list discussion:* http://lists.wpkg.org/pipermail/wpkg-users/2008-June/003513.html<br /> == wpkgMessage == Info: Shows little window which can be used to tell the user what WPKG does at the moment.<br />Author: grubi<br />Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-message-english.htm<br />Download URL: ftp://ftp.gig-mbh.de/software/wpkg-message.zip<br />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 or HTML report out of the projectcomputer's wpkg. xml files showing which packages are installed on which computers. It can also check for compliance against the wpkg database and post the result in an additional state column. There it is shown if a package needs to be installed, removed, downgraded or upgraded to meet the requirements.<br />Author: grubi<br />Info URL: http://www.gig-5mbh.de/10edv/04software/wpkgtools/wpkg-create-report-english.htm<br />Download URL: ftp://ftp.gig-mbh.de/software/wpkg-create-report.zip<br />  == wpkgListPackages == Info: Command line script displaying all packages sorted according to the package's priority setting.<br />Author: grubi<br />Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-list-packages-english.htm<br />Download URL: ftp://ftp.gig-mbh.de/software/wpkg-list-packages.zip<br />  == "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<br />Script source: http://lists.wpkg.org/pipermail/wpkg-users/2008-March/002820.html<br />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<br />URL: [[WPKG_with_Active_Directory|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: [[Script for checking if a process is already running|http://wpkg.org/Script_for_checking_if_a_process_is_already_running]]  == Generic Library for scripted checks ==Author: Keith Jones<br />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 ?<br>Tired of writing parameter parsers for each and every one of them?<br> 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:'''<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/gettingstarted.txt gettingstarted.txt] - A quick guide to using WPKG.Utility.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/integrating.txt integrating.txt] - A guide to using scriptlets with WPKG.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/parser.txt parser.txt] - A rough guide to using the parser to make scriptlets.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/advanced.txt advanced.txt] - A guide to more advanced techniques.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/history.txt history.txt] - About the origins of WPKG.Utility.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/changes.txt changes.txt] - The changelog for WPKG.Utility.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/aboutWSC.txt aboutWSC.txt] - A rough guide to Windows Scripting Components.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/thoughts.txt thoughts.txt] - General thoughts.<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/comingsoon.txt comingsoon.txt] - A rough guide to things that I'm thinking about.<br> '''Examples'''<br>[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/DiskSpace.js DiskSpace.js] - A documented version of the DiskTotal.js script<br>  '''Code:'''<br> '''WPKG.Utility''' - The WPKG.Utility component library.<br> Versions : [http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/Utility-V110.wsc V110],[http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/Utility-V110-01.wsc V110-01]  '''Scriptlet Library:'''<br> Please note: These scripts need amendments made to them to locate the WPKG.Utility .wsc file.<br>The WPKG.Utility component can be detected, if you place it into the same folder as the scripts.<br>You will have to replace the two lines setting ''utilityPath'' and ''utility'' at the top of the scripts with the following.<source lang="javascript">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);</source>  '''DiskTotal.js''' - Checks a drive for a given total space.<br> Versions : [http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/DiskTotalV101.js V101]<br> Usage: [cscript.exe] DiskTotalVxxx.js <Drive|Path> <lessthan|lessthanorequalto|etc> <Megabytes><br> Returns: 0, if the test succeeded, 1 if the test failed.  '''DiskFree.js''' - Checks a drive for a given free space.<br> Versions : [http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/DiskFreeV101.js V101]<br> Usage: [cscript.exe]DiskFreeVxxx.js <Drive|Path> <lessthan|lessthanorequalto|etc> <Megabytes><br> Returns: 0, if the test succeeded, 1 if the test failed.  '''DiskExists''' - Checks to see if a drive physically exists.<br> Versions : [http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/DiskExistsV101.js V101]<br> Usage: [cscript.exe]DiskExistsV101.js <Drive|Path><br> Returns: 0, if the test succeeded, 1 if the test failed. [[category:Utility Scripts]]