Comments on: PowerCLI: Daily Report http://www.virtu-al.net/2009/07/14/powercli-daily-report/ Virtually everything is poshable Fri, 19 Mar 2010 18:00:59 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Virtu-Al http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-4/#comment-1993 Virtu-Al Fri, 19 Mar 2010 14:02:44 +0000 http://www.virtu-al.net/?p=792#comment-1993 Ok, Try this: C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" " & "c:\scripts\DailyReport.psc1 stnsvpvcenter" Note the extra quote. I normally run it from a DOS prompt first to make sure it works. Ok, Try this: C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile “C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1″ ” & “c:\scripts\DailyReport.psc1 stnsvpvcenter”

Note the extra quote. I normally run it from a DOS prompt first to make sure it works.

]]> By: Andrew Allsopp http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-4/#comment-1988 Andrew Allsopp Thu, 18 Mar 2010 17:44:59 +0000 http://www.virtu-al.net/?p=792#comment-1988 On s server 2008 R2 64 bit machine running the latest vcenter I issue the following command at the command line. C:\Users\stn1vmadmin>C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1 " & "c:\scripts\DailyReport.psc1 stnsvpvcenter" and I get this error ... Windows PowerShell console file ""C:\Program" extension is not psc1. Windows PowerShell console file extension must be psc1. On s server 2008 R2 64 bit machine running the latest vcenter I issue the following command at the command line.

C:\Users\stn1vmadmin>C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile “C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1 ” & “c:\scripts\DailyReport.psc1 stnsvpvcenter”

and I get this error …

Windows PowerShell console file “”C:\Program” extension is not psc1. Windows PowerShell console file extension must be psc1.

]]> By: Virtu-Al http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-4/#comment-1976 Virtu-Al Wed, 17 Mar 2010 15:27:21 +0000 http://www.virtu-al.net/?p=792#comment-1976 Thanks for the comment, to be honest I have not tried it in an unmanaged 3.5 environment, you will probably get a bunch of errors but you should get some info back at least, the script only reads information, there is no writes at all so give it a go, the worst that can happen is it will fail ! I would be interested in your results ! Thanks for the comment, to be honest I have not tried it in an unmanaged 3.5 environment, you will probably get a bunch of errors but you should get some info back at least, the script only reads information, there is no writes at all so give it a go, the worst that can happen is it will fail !

I would be interested in your results !

]]> By: VirtualI http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-4/#comment-1969 VirtualI Wed, 17 Mar 2010 04:00:39 +0000 http://www.virtu-al.net/?p=792#comment-1969 Hi Looks like a great script. I would like to know if this script can be used for ESX 3i based environment ? I have 2 ESX 3i based environment and of which one is managed by VC and 2nd one without VC. Please suggest Hi

Looks like a great script.
I would like to know if this script can be used for ESX 3i based environment ?
I have 2 ESX 3i based environment and of which one is managed by VC and 2nd one without VC.

Please suggest

]]> By: Virtu-Al http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-3/#comment-1944 Virtu-Al Tue, 09 Mar 2010 13:10:37 +0000 http://www.virtu-al.net/?p=792#comment-1944 Thanks, Updated now ! Thanks, Updated now !

]]> By: phimic http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-3/#comment-1943 phimic Tue, 09 Mar 2010 12:55:12 +0000 http://www.virtu-al.net/?p=792#comment-1943 Thank you, V3 works! The link on bottom of this page points still to V2. Thank you, V3 works! The link on bottom of this page points still to V2.

]]> By: Virtu-Al http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-3/#comment-1942 Virtu-Al Tue, 09 Mar 2010 09:20:34 +0000 http://www.virtu-al.net/?p=792#comment-1942 Are you using V3 of this ? I think i fixed it there. Are you using V3 of this ? I think i fixed it there.

]]> By: phimic http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-3/#comment-1940 phimic Tue, 09 Mar 2010 09:07:42 +0000 http://www.virtu-al.net/?p=792#comment-1940 Very powerful script, but i miss the output of VMs which has no VMware-Tools installed Very powerful script, but i miss the output of VMs which has no VMware-Tools installed

]]> By: Virtu-Al http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-3/#comment-1908 Virtu-Al Tue, 02 Mar 2010 08:48:05 +0000 http://www.virtu-al.net/?p=792#comment-1908 Suresh, No not as yet but you should be able to with some manipulation of the code. Suresh,

No not as yet but you should be able to with some manipulation of the code.

]]> By: Suresh http://www.virtu-al.net/2009/07/14/powercli-daily-report/comment-page-3/#comment-1906 Suresh Tue, 02 Mar 2010 03:05:13 +0000 http://www.virtu-al.net/?p=792#comment-1906 thanks for the script, how do we point this script to talk to only one datacenter... we have multiple datacenters listed in our environment and it will be good if this can point to only one datacenter.. thanks for the script, how do we point this script to talk to only one datacenter…

we have multiple datacenters listed in our environment and it will be good if this can point to only one datacenter..

]]>