A quick video on the plugin utility commands found in vCheck 6! For more info, be sure to visit the vCheck 6 release page, and visit the vCheck Plugins page to browse the available plugins. Don’t forget to thank Alan for all of his hard work on vCheck!
If you are not the video watching type, here are some helpful tips:
1. In order to access the vCheck Utility Commands. You must ‘dot-source’ the file:
. .\vCheckUtils.ps1
That’s dot[space]dot, for those reading this on a mobile device. 
2. The list of commands will display. The basic functionality is as follows:
Get-vCheckCommand # Get commands found in vCheckUtils.ps1 Get-vCheckPlugin # Retrieve list of plugins Add-vCheckPlugin # Add plugin from Virtu-Al.net Remove-vCheckPlugin # Remove an installed plugin
3. Some common uses:
List Plugins not installed(available from Virtu-al.net repository):
Get-VCheckPlugin -notinstalled
Get a plugin by name:
Get-VCheckPlugin -name "Plugin Name"
Get a plugin by name and install it from the Virtu-Al.net repository:
Get-VCheckPlugin -name "Plugin Name | Add-VCheckPlugin
Get a plugin by name and UNINSTALL it:
Get-VCheckPlugin -name "Plugin Name | Add-VCheckPlugin
Get all plugins that are NOT installed, and install them (warning, lots of plugins!):
Get-VCheckPlugin -notinstalled | Add-VCheckPlugin
Need more help?
Get-Help Get-VCheckPlugin
February 8th, 2012 at 5:05 pm
[...] Alan a aussi intégrer des cmdlet (pour l’instant juste des scripts sourcés mais un petit module PowerShell pourrait peut être voir le jour ^^) pour gérer les plugin (ie récupérer automatiquement les plugin à jour et/ou les nouveaux plugin), @jakerobinson a fait un billet dessus d’ailleurs, vous devriez aller voir la vidéo pour plus d’informations : vCheck6 Utility Commands [...]
February 8th, 2012 at 5:17 pm
[...] Alan also developp some cmdlet (for now it’s just sourced scripts but there’ll may be a PowerShell module someday ^^) in order to manage plugin (ie download automatically updated plugin and/or new ones), @jakerobinson already posted about this functionnality, you can look at the video in order to get more information: vCheck6 Utility Commands [...]
February 9th, 2012 at 11:02 am
Hi,
Thanks for the info, however when i try to run any of the commands I get “is not recognised as the name of a cmdlet” etc, etc, any help would be greatly appreciated.
February 9th, 2012 at 4:34 pm
Hi Adam,
You will need to `dot-source` the file by running:
. .\vcheckUtils.ps1or
. C:\whatever\vCheck\vcheckUtils.ps1February 10th, 2012 at 5:07 am
Hi Jake,
I’ve done that but still get the same problem. I’m new to powershell so I presume its something pretty simple that I’m doing wrong.
This is what i get:
PS C:\VCheck> ls
Directory: C:\VCheck
Mode LastWriteTime Length Name
—- ————- —— —-
d—- 09/02/2012 10:30 Headers
d—- 09/02/2012 10:30 Plugins
-a— 03/02/2012 10:52 890 Changelog.txt
-a— 30/01/2012 11:36 115 EndScript.ps1
-a— 09/02/2012 10:34 6972 GlobalVariables.ps1
-a— 05/02/2012 14:59 16847 Header.jpg
-a— 05/02/2012 16:20 11243 vCheck.ps1
-a— 07/02/2012 23:42 17718 vCheckUtils.ps1
PS C:\VCheck> .\vCheckUtils.ps1
CommandType Name Definition
———– —- ———-
Function Add-VCheckPlugin …
Function Get-vCheckCommand …
Function Get-VCheckPlugin …
Function Remove-VCheckPlugin …
PS C:\VCheck> Get-VCheckPlugin
The term ‘Get-VCheckPlugin’ is not recognized as the name of a cmdlet, function, script file, or operable program. Chec
k the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:17
+ Get-VCheckPlugin <<<
Any help would be really appreciated (again)
February 10th, 2012 at 5:18 am
Scratch that, was being a complete dimwit, I didn’t put a . infront of the .\
Apologies for wasting your time.
Ta,
Adam
February 10th, 2012 at 4:48 pm
February 20th, 2012 at 5:44 pm
Not getting the Security Warning prompt to run this once, etc..???
February 20th, 2012 at 10:52 pm
You’ll only get the security warning if your Execution Policy is set to restricted, or if you are running as Administrator, like I was.
February 29th, 2012 at 3:00 am
Hi jake,
How do I modify this script if I’m behind a proxy server?
February 29th, 2012 at 5:24 pm
Great question. You can add proxy support with code from the following link: http://mohundro.com/blog/2007/06/28/a-simple-function-to-get-a-webclient-with-proxy-in-powershell/
Let me know if you need help implementing!
Cheers,
Jake
March 5th, 2012 at 8:29 am
Getting through authenticating proxy:
Add the indented extra code to vCheckUtils.ps1 around line 91.
$webClient = new-object system.net.webclient
$Credentials = new-object System.Net.NetworkCredential(“ProxyAuthUser”, “ProxyAuthPassword”, “YourDomain.local”)
$proxy = New-Object System.Net.WebProxy(“YourProxyServer.local”, “ProxyPort”)
$proxy.Credentials = $Credentials
$webClient.Proxy = $proxy
$response = $webClient.openread(“http://www.virtu-al.net/vcheck/plugins/plugins.xml”)