Comments |
|
Aug 27, 2008 1:15 AM
sTyLeR_1 says:
Hi Alan,
Sep 4, 2008 4:46 PM
halr9000 says:
Running it against my 250 VM VI now. It better be good, it's been running forever. Author of the upcoming book: Managing VMware Infrastructure with PowerShell Co-Host, PowerScripting Podcast (http://powerscripting.net)
Sep 5, 2008 6:23 AM
halr9000 says:
in response to: halr9000
Sorry for not commenting back--I barely finished my judging work in time to drive to @jonwalz for the podcast show last night.
Dec 15, 2008 6:27 PM
dlm1975 says:
Great report. Worked out of the box. I have 265 VMs. No issues.
Dec 16, 2008 12:57 AM
alanrenouf says:
in response to: dlm1975
Thanks for the comment, glad it worked fine in your environment, I will be creating a newer and hopefully faster version when I get time, you can follow my blog for updates and other scripts I have written...
Dec 16, 2008 10:24 AM
ServerDude says:
Can't get this to work for me. I'm running ESX 3.5 Update 2 and VI 2.5 Update 3. Start Date: 12/16/2008 12:14:57 End Date: 12/16/2008 12:15:05 Argument: '1' should not be a System.Management.Automation.PSReference. Do not use ref. At C:\Scripts\Report.ps1:460 char:16 + $wordDoc.SaveAs( <<<< ref$filename) The term 'Disconnect-VIServer' is not recognized as a cmdlet, function, operable program, or script file. Verify the te rm and try again. At C:\Scripts\Report.ps1:485 char:20 + Disconnect-VIServer <<<< -Confirm:$False PS C:\Scripts>
Dec 16, 2008 12:19 PM
alanrenouf says:
in response to: ServerDude
Hi, Sorry you are having problems, from the looks of it you dont have the VI toolkit (http://www.vmware.com/sdk/vitk_win/index.html) installed as the first cmdlet 'connect-viserver' is not working. If you havent yet installed it you will need to download and install on the same machine as powershell.
Dec 16, 2008 2:55 PM
jmedd says:
in response to: alanrenouf
Might also be the version of the VI Toolkit. I think the connect-viserver cmdlet was named differently in an earlier version.......
Dec 17, 2008 12:46 AM
alanrenouf says:
in response to: jmedd
jmedd, true, in the Beta version it was 'get-viserver' but hopefully he will be using the current version which has lots of fixes and major performance tweaks
Dec 17, 2008 4:04 PM
SetClear says:
in response to: alanrenouf
Please help, installed Word and excell oto the virtualcenter server where this report would be scheduled and run. but I get a tom of errors and when the reports finished it have no charting. Start Date: 12/17/2008 18:38:40 End Date: 12/17/2008 18:51:50
Dec 18, 2008 1:04 AM
alanrenouf says:
in response to: SetClear
Hi,
Dec 18, 2008 10:33 AM
SetClear says:
in response to: alanrenouf
Alan,
Dec 19, 2008 1:02 AM
alanrenouf says:
in response to: SetClear
Thats very strange, I have tried it with Word 2007 before and its worked fine, to test the office web components can you try this please.....
Dec 19, 2008 7:44 AM
rmarche says:
in response to: jmedd
Sweet script. In case anyone is having a similar problem, I had to run the following prior to running the ps1.
Dec 19, 2008 11:25 AM
alanrenouf says:
in response to: rmarche
Correct, If your running this as a scheduled task you need to add that to tell powershell to add the VI Toolkit snapin. Thanks for the comments rmarche.
Dec 19, 2008 11:28 AM
alanrenouf says:
in response to: SetClear
Some people have managed to fix the non showing graph issues by doing the following: by the following lines: $chartsEntry = (array $chart.charts)[0] $chartEntry = $chartsEntry.Add(0) $series = $chartEntry.SeriesCollection.Add(0)
Dec 23, 2008 8:35 AM
BasicVirtu says:
in response to: alanrenouf
Ran great against our Test VI host! I was wondering if this can be run against the Virtual Center Server so it collects all the VI servers in the cluster into one word document. I was a little scurrred to try it as we have alot of them and didn't want to have a chance of crashing it. Great post!
Dec 23, 2008 11:01 AM
alanrenouf says:
in response to: BasicVirtu
I have not known any instance of it crashing any servers yet, go for it, it may take a while if you have a large environment but shouldn't cause stress on your VI
Dec 23, 2008 2:03 PM
BasicVirtu says:
in response to: alanrenouf
Thanks it worked great except for some empty graphs... I will try to use your code in the above post to see if it changes the results.
Jan 6, 2009 1:51 PM
BasicVirtu says:
in response to: alanrenouf
These lines are difficult to read for some reason, I think the html is messing them up; I tries this but it doesn't seem to work. The graph displays fine with individual esx hosts but when I run it against our virtual center the esx hosts do not display the graphs. Any suggestions?
Jan 23, 2009 11:34 AM
Sandhya94 says:
I love this script! Thank you Thank you Thank you!! I can't believe how easy it was to use and the info that it provided is so valuable.
Mar 5, 2009 6:07 AM
pkratz says:
I have problems to get it running
Mar 5, 2009 7:04 AM
pkratz says:
in response to: SetClear
Thanks, that helped but now I stuck with that message:
May 18, 2009 10:50 AM
max2479 says:
having problems : vc1 is my virtual center debug message: Microsoft Word Detected Office Web Components Detected Connecting to VI Server The argument cannot be null or empty.
May 18, 2009 2:30 PM
alanrenouf says:
in response to: max2479
Max, Alan Renouf http://virtu-al.net
Jun 25, 2009 2:37 PM
foxy1977 says:
in response to: alanrenouf
Hi Alan,
Jun 25, 2009 4:19 PM
max2479 says:
in response to: foxy1977
Foxy1977, if you found this or any other answer useful please consider allocating points for helpful or correct answers <
Oct 20, 2009 8:21 AM
vancod says:
in response to: alanrenouf
I've scoured your blog in search of an updated version of this script, and there appears to be none. Is that correct? |
This is awesome! We are now using this to contribute to our monthly reporting to management.
Very useful indeed, no modification was required to run in our environment.