Comments on: Running a PowerCLI Scheduled task

By: vCheck 6.0 released | | Virtu-Al.NetVirtu-Al.Net

vCheck 6.0 released | | Virtu-Al.NetVirtu-Al.Net — Wed, 08 Feb 2012 20:57:32 +0000

[...] is a vCenter checking script, the script is designed to run as a scheduled task before you get into the office to present you with key information via an email directly to your [...]

By: Alan

Alan — Fri, 03 Feb 2012 15:03:21 +0000

The view snapin is called VMware.View.Broker so i would add something like this to the start of your script:

if (!(get-pssnapin -name VMware.View.Broker -erroraction silentlycontinue)) {
add-pssnapin VMware.View.Broker
}

By: Steve

Steve — Fri, 03 Feb 2012 13:34:43 +0000

Hi,
I was wondering how I would run a VIEW PowerCLI script as a scheduled task?
I do not have the VMware PowerCLI installed on my connection server, just the View PowerCLI, so ‘VMware.VimAutomation.Core’ is not available. Any ideas?

Cheers,
Steve

By: vSoluationArchitect

vSoluationArchitect — Tue, 31 Jan 2012 04:04:23 +0000

vCheck worked right away.

The surprise was it find ‘exceptions’ and reports on them. I used it recently as we built a lab prior to a mgiration to later version of vSphere. It was helpful to monitor both production and lab with script (aimed at the different vCenters).

It was easy to adjust limits (such as number of VMs per LUN up from 5 (default), etc).

Nice job.

Larry T.

By: Nigel Snow

Nigel Snow — Fri, 25 Nov 2011 01:26:12 +0000

Trouble running as scheduled task resolved.

I have been playing with this exceptionally helpful script for a few days as I was having trouble triggering it via a scheduled task in Windows 2008R2 and noticed others also had problems.

I needed to change the line in the script that set the appdata environment variable from “C:\Documents and Settings\” + $USER + “\Application Data” to “C:\Users\” + $USER + “\AppData\Roaming”, I also hardcoded the cred file path to $CredFile = “C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\mycred.crd” once created and tested.

The correct syntax is throughout the posts above.
Cheers

By: Dean

Dean — Wed, 14 Sep 2011 18:35:19 +0000

Hello,
Awesome vCheck script! Saves me so much time it is amazing. I do have one issue that maybe you have seen. When the html comes out to IE it looks perfect but when it sends to my email (outlook 2010) the secondary titles and descriptions and any background colors are lost. Is there anything I can do to clean up the look of the email output to match the IE output?

Thanks again for an awesome script.

Dean

By: Matt

Matt — Wed, 24 Aug 2011 23:40:27 +0000

I read all the comments and could not get this to execute on my Win7 x64 PC. I downloaded System Scheduler free, put the commands into a .bat file and it executed with no issue.

By: Eric

Eric — Fri, 19 Aug 2011 18:54:37 +0000

Note on a 64bit server the path to vim.psc1 is different it should be “C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1″

By: Guido

Guido — Wed, 29 Jun 2011 12:41:50 +0000

this is all is says.
[vSphere PowerCLI] C:\> cd scripts
[vSphere PowerCLI] C:\scripts> cd test
[vSphere PowerCLI] C:\scripts\test> .\vcheck5.ps1
2:41:06 PM Connecting to VI Server
[vSphere PowerCLI] C:\scripts\test>

By: Gerard Delgado

Gerard Delgado — Wed, 29 Jun 2011 11:54:06 +0000

Try to run the task from a PowerCLI prompt and see what you get. Make sure the account you specified when creating the XML encrypted file has rights to log onto VCenter.