Difference between revisions of "User contributed software"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
m (→‎Generic Library for scripted checks)
(→‎wpkg-tools)
 
(32 intermediate revisions by 15 users not shown)
Line 1: Line 1:
 +
== wpkg-tools ==
 +
 +
Info: CLI to interact with wpkg clients in debian (written in Perl).<br />
 +
Author: [https://github.com/Link2Twenty Andrew Bone]<br />
 +
URL: [https://wpkg.org/Wpkg-tools wpkg-tools], https://github.com/Link2Twenty/wpkg-tools<br />
 +
Screenshots: https://image.ibb.co/kPfsJy/wpkg_tools_help.png , https://image.ibb.co/gGzmdy/wpkg_tools_service.png
 +
<br />
 +
 +
<br />
 +
 
== InfoMessage ==
 
== InfoMessage ==
  
Line 9: Line 19:
 
<br />
 
<br />
  
−
== wpkgmessage ==
+
== wpkgMessage ==
  
 
Info: Shows little window which can be used to tell the user what WPKG does at the moment.<br />
 
Info: Shows little window which can be used to tell the user what WPKG does at the moment.<br />
 
Author: grubi<br />
 
Author: grubi<br />
−
URL: ftp://ftp.gig-mbh.de/software/wpkgMessage.zip<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:
 
Mailing list discussion:
 
* http://lists.wpkg.org/pipermail/wpkg-users/2008-February/thread.html#2628 ("wpkg via Group Policies" thread)
 
* http://lists.wpkg.org/pipermail/wpkg-users/2008-February/thread.html#2628 ("wpkg via Group Policies" thread)
  
 +
 +
== wpkgPackageStates ==
 +
 +
Info: Generates an Excel or HTML report out of the computer's wpkg.xml files showing which packages are installed on which computers. It can also check for compliance against the wpkg package 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-mbh.de/edv/software/wpkgtools/wpkg-package-states-english.htm<br />
 +
Download URL: ftp://ftp.gig-mbh.de/software/wpkg-package-states.zip<br /><br />
 +
 +
== wpkgPackageList ==
 +
 +
Info: Command line script creating a list of all packages which are part of a wpkg installation in HTML or Excel format. The HTML list is a dynamic report which can be sorted by clicking on the column header.<br />
 +
Author: grubi<br />
 +
Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-package-list-english.htm<br />
 +
Download URL: ftp://ftp.gig-mbh.de/software/wpkg-package-list.zip<br /><br />
  
 
== "Ugly perl script to check if packages are installed on a set of workstations" ==
 
== "Ugly perl script to check if packages are installed on a set of workstations" ==
Line 44: Line 69:
 
* some software (like certain browser plugins) won't install if some other software is running (i.e., a browser).
 
* 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]]
 
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 ==
 
== Generic Library for scripted checks ==
 
Author: Keith Jones<br />
 
Author: Keith Jones<br />
−
Mailing list discussion:
+
Mailing list discussion: http://lists.wpkg.org/swish.cgi?query=ideas+for+features&metaname=swishtitle
−
* Coming soon
+
−
Info: Tired of writing scripts to support custom 'checks' in WPKG and then 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 can be included into your script files to simplify the process.
+
Info: '''WPKG.Utility''', a COM-based utility library to support scripted 'Execute' checks.
  
−
It provides a skeletal framework to consolidate and collect useful functions for administrators. You can trim down the code you have to write and write your tests to a simple standard for re-usability and sharing.
+
Tired of writing scripts to support custom 'checks' in WPKG ?<br>
 +
Tired of writing parameter parsers for each and every one of them?<br>
  
−
The WSC file contains a rough-and-ready command-line parser and semi-automated parameter checks with options to debug code, trap errors 'in-the-field' and build up a unified library of WPKG checks.
+
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!
  
−
It's a work in progress.
 
  
 
Features include;
 
Features include;
  
 
* Simple parsing of command-lines to validate custom parameters.
 
* Simple parsing of command-lines to validate custom parameters.
−
* A growing collection of inbuilt routines. (I'm adding things slowly!)
+
* A growing collection of built-in helper routines.
 
* A simplified approach for less experienced admins.
 
* A simplified approach for less experienced admins.
−
* All code is written in JScript to allow you to customise WPKG if you wish.
+
* All code is written in JScript to maintain compatibility with WPKG.js.
−
* Examples of 'less used' techniques.
+
* Illustrations of 'less used' techniques.
−
* ... being optimised as we write :-)
+
 
 +
 
 +
'''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.
 +
 
 +
 
 +
== PC inventory and reporting script ==
 +
 
 +
Info: Command line script made with Autoit producing a per client pc csv file of installed WPKG programs with the option to email someone a list of machines whose installed packages are out of sync with the 'master' xml config files.  Example of output csv =
 +
 
 +
<pre>
 +
PC NAME,DATE OF XML FILE,DESCRIPTION,PACKAGE ID NAME,PRIORITY,INSTALLED REVISION,MASTER XML REVISION,UPGRADE/DOWNGRADE/BLANK=NOTHING REQUIRED
 +
RECOVERY,09/05/2011_15:37,7-Zip,7zip,10,920,920,
 +
RECOVERY,09/05/2011_15:37,Activation MS Office 2010,msoffice2010-activation,71,1,1,
 +
RECOVERY,09/05/2011_15:37,Adobe Acrobat 9,acrobat9,17,944,944,
 +
RECOVERY,09/05/2011_15:37,Adobe Shockwave Player 11,shockwave,50,11.5.7.601,11.5.7.609,Upgrade required
 +
</pre>
 +
 
 +
This script can be scheduled to run and report back any possible issues before the user realises.
  
 +
priority setting.<br />
 +
Author: cbm214<br />
 +
Info URL: http://wpkg.org/Inventory_script<br />
  
−
URL: [Instructions] http://dev.bus.brighton.ac.uk/kej/WPKG/Utilities/readme.txt<br>
+
[[category:Utility Scripts]]
−
URL: [Utility.WSC] http://dev.bus.brighton.ac.uk/kej//WPKG/Utilities/utility.wsc<br>
+
−
URL: [Example, Diskpace Checker] http://dev.bus.brighton.ac.uk/kej//WPKG/Utilities/diskspace.js<BR>
+

Latest revision as of 08:22, 17 May 2018

wpkg-tools

Info: CLI to interact with wpkg clients in debian (written in Perl).
Author: Andrew Bone
URL: wpkg-tools, https://github.com/Link2Twenty/wpkg-tools
Screenshots: https://image.ibb.co/kPfsJy/wpkg_tools_help.png , https://image.ibb.co/gGzmdy/wpkg_tools_service.png


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:


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:


wpkgPackageStates

Info: Generates an Excel or HTML report out of the computer's wpkg.xml files showing which packages are installed on which computers. It can also check for compliance against the wpkg package 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.
Author: grubi
Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-package-states-english.htm
Download URL: ftp://ftp.gig-mbh.de/software/wpkg-package-states.zip

wpkgPackageList

Info: Command line script creating a list of all packages which are part of a wpkg installation in HTML or Excel format. The HTML list is a dynamic report which can be sorted by clicking on the column header.
Author: grubi
Info URL: http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-package-list-english.htm
Download URL: ftp://ftp.gig-mbh.de/software/wpkg-package-list.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:


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.


PC inventory and reporting script

Info: Command line script made with Autoit producing a per client pc csv file of installed WPKG programs with the option to email someone a list of machines whose installed packages are out of sync with the 'master' xml config files. Example of output csv = 

PC NAME,DATE OF XML FILE,DESCRIPTION,PACKAGE ID NAME,PRIORITY,INSTALLED REVISION,MASTER XML REVISION,UPGRADE/DOWNGRADE/BLANK=NOTHING REQUIRED
RECOVERY,09/05/2011_15:37,7-Zip,7zip,10,920,920,
RECOVERY,09/05/2011_15:37,Activation MS Office 2010,msoffice2010-activation,71,1,1,
RECOVERY,09/05/2011_15:37,Adobe Acrobat 9,acrobat9,17,944,944,
RECOVERY,09/05/2011_15:37,Adobe Shockwave Player 11,shockwave,50,11.5.7.601,11.5.7.609,Upgrade required

This script can be scheduled to run and report back any possible issues before the user realises.

priority setting.
Author: cbm214
Info URL: http://wpkg.org/Inventory_script

Retrieved from "https://wpkg.org/index.php?title=User_contributed_software&oldid=13309"