Contact Me

AlanRenouf3 Do you have a script that needs writing ?

Do you want to employ someone to do scripting for you ?

Do you have some additions to an already existing script which you would like to share ?

Contact me at the following email address:  contact@virtu-al.net or chat to me if im online:

  • #1 written by billy somers
    about 1 year ago
    Quote

    Hi,

    I saw your DailyReport script and it looks great but did not see any instructions on what is required to run it? Do you perhaps have some detail installation instructions for this, I’m sorry but I’m new to powershell.

    Thanks

  • #2 written by Joakim
    about 1 year ago
    Quote

    Hi!

    Very Nice Script!
    A very nice to have feature in the script would be if it showed the last 10-20 created machines. Is that possible? Something you allready thought of?

    Regards,
    Joakim

  • #3 written by Amer
    about 1 year ago
    Quote

    Hi I am looking at your nice Health check script, Can we download it is it free to use?

    Regards

    Amer

  • #4 written by Virtu-Al
    about 1 year ago
    Quote

    @Amer
    Absolutely, Free to all !

  • #5 written by Virtu-Al
    about 1 year ago
    Quote

    @Joakim
    Do you think that would be more useful than the vm’s created in the previous x days ? Its easily done but I think I will keep it as it is, Don’t worry though I will do a seperate post showing how to get this info so you can add it easily.

  • #6 written by Virtu-Al
    about 1 year ago
    Quote

    @billy somers
    Ok all you need to do is this…..
    1. Install Powershell
    2. Install PowerCLI (Basic instructions here.. http://www.virtu-al.net/2008/08/13/getting-started-with-the-vi-toolkit/)
    3. Download my script and save it somewhere like c:\temp\dailyreport.ps1
    4. Launch PowerCLI, cd into c:\temp
    5. Type .\DailyReport.ps1 myviserver

    That should be about it, if you get stuck or need any more info please let me know.

  • #7 written by Charlie Lonergan
    about 11 months ago
    Quote

    Al,

    I ran across your “Audit Script” on poshcode.com. There is a parser error that keeps coming up near the end and it looks like the file got cut off. Do you have any thoughts so I could try this?

    Thanks,

    Charlie

  • #8 written by Virtu-Al
    about 11 months ago
    Quote

    @Charlie Lonergan
    Yeah I guess it was too long, you can find it on the Script List above or follow this link:

    http://www.virtu-al.net/2009/01/09/powershell-workstationserver-audit-script-update/

  • #9 written by UnclePhil
    about 11 months ago
    Quote

    Hi Al,

    I use your script regularly, but i hate flat file and i love wiki. so i change some bits to fit my needs and know i can automatically integrate my Vm Environment in my (self wiki made) CMDB

    Many thanks’ for your base script , and try mine if you have time

    Ph Koenig
    Aka UnclePhil

  • #10 written by Aaron
    about 11 months ago
    Quote

    UnclePhil, what CMDB are you integrating with? I would love to see the results you get with your script.

  • #11 written by Rurik
    about 10 months ago
    Quote

    I bumped into your site by accident and I seem to have stumbled on a pot of gold. I’m a PowerShell beginner and wanted to know how to properly run your Audit.PS1 script. When I run it on my test machine (right click and Run with PowerShell), the PowerShell windows comes up and then disappears about 10 seconds later. Is there something I’m doing wrong? Thanks for your time.

  • #12 written by Virtu-Al
    about 10 months ago
    Quote

    @Rurik
    Welcome and thanks for the comment, Have you set your execution policy yet ? see here: http://www.microsoft.com/technet/scriptcenter/topics/msh/cmdlets/set-executionpolicy.mspx – I normaly use remotesigned

  • #13 written by Rurik
    about 10 months ago
    Quote

    Man that was quick!! Silly me…..I have “Set-ExecutionPolicy Restricted” at the tail end of a script that runs daily to query some basic Exchange information. That must have blocked it. Thanks a bunch for pointing me in the right direction. I’ll continue to be an avid reader of your blog.

  • #14 written by Virtu-Al
    about 10 months ago
    Quote

    @Rurik
    Glad it worked out and I will try and keep you interested !

  • #15 written by Tom
    about 10 months ago
    Quote

    Suggestion for a script, may not be easy.
    Basic idea is that VMotion can screw up the auto-start for VMs (turn it off), why not have a script that runs daily and resets the desired auto-start of one’s important VMs??
    There is I know a best practice for restarting VMs, it’s something like: AD/DNS virtual server if there is one (we also have a physical one), Virtual Center server, then other servers as desired.
    One might or might not have DRS enabled, one likely has HA started.
    Perhaps the user must create a text file with a list of VM names and a note about what is the VM’s function.
    The script could look at this list, compare it to the existing list of VMs on the host, then do what is necessary to ensure the VMs are correctly set to auto-start, plus send a message to someone about this too.
    It could become an adjunct to vCheck Daily Report??
    Thank you for reading this, Tom

  • #16 written by Patrik
    about 9 months ago
    Quote

    Hi

    I new on poweshell, but it seem to be great tool.
    I tryed dailyreport with the folowing problem.

    Please specify a VI Server name eg….
    powershell.exe DailyReport.ps1

    What have i missed?
    BR
    Patrik

  • #17 written by Marc
    about 9 months ago
    Quote

    Awesome work all around!!! Really appreciate your scripts. Thank you.

    I have noticed a new problem cropping up in vSphere 4. It seems that they added NUMA verification to the lastest code. So if your hosts do not have the correct memory layout then you will get errors on your ESX host. Is it possible to add a VESI script to check for memory layout? Maybe a best practice query?

    Thanks,
    Marc

  • #18 written by Marvin Blackburn
    about 9 months ago
    Quote

    I saw a webinar today that showed your powerpack for the virtualization echoshell.
    Where can I download this?

  • #19 written by Virtu-Al
    about 9 months ago
    Quote

    @Marvin Blackburn
    Sorry, I must update my script list, the link is here:

    http://www.virtu-al.net/2009/11/14/vesi-powergui-powerpack-v2/

    V3 will be released very soon.

  • #20 written by Graham Kemp
    about 6 months ago
    Quote

    Hi Alan,

    I’ve been using your daily checks scripts for sometime now and can honestly say it helps me immeasurably.

    We’ve recently upgraded our backup solution to a product that fully integrates with the new change block tracking features in the vStorage API. However, to get this fully working i need to add and set the ctkEnabled=true value in the configuration paraments as well as adding and setting the scsi0:0.ctkEnabled = true value for each virtual disk.

    Is there an easy we to do this with powershell other than updating each VM indiviually?

    Thanks

    Graham

  • #21 written by virtualsj
    about 5 months ago
    Quote

    Hi Alan,

    Could you please help. I have just patched all my hosts and I need to upgrade the tools on the guests. Is it possible to pass the update-tools cmdlet a parameter such as remove=hgfs. from what I can see this has been deprecated in PowerCli 4.0U1

    Thanks
    Simon

  • #22 written by Rusty
    about 3 months ago
    Quote

    Hey there, Like the scripts you have obvious.ly put in a lot of time on this! I did note one omission, a script to shutdown multiple VMs in the event you need to power down a cluster or the entire infrastructure. So if you have one handy or know where to point me I would appreciate it….

  • #23 written by PDUK
    about 2 months ago
    Quote

    @Rusty
    Hi,
    Try somehting like
    get-cluster | get-vm | Where-Object {$_.powerstate -eq “PoweredOn”} | shutdown-VMGuest

    You would have to be connected to the VC, that should be a good place to start.

  • #24 written by PDUK
    about 2 months ago
    Quote

    Something happened to the code then….not sure what.

    Put the Cluster Name after the get-cluster cmdlet. Like get-cluster MyCluster | …..

    Omit the get-cluster cmdlet to shut down every VM on the VC.

  • #25 written by Steven Baert
    about 2 months ago
    Quote

    Could you add the extra features of this healt check script? http://www.ivobeerens.nl/?p=256

    Especially the “vmware tools old” section?
    This way we keep in mind to update to the latest version.
    —

    Note that I have “Unable to populate snapshot size due to unsufficient permissions”, however the user I run the script with should have enough priviliges.

    Cheers,
    S.

  • #26 written by tien lam nguyen
    about 1 month ago
    Quote

    Hi there,

    Thanks for your vcheck script. I am very new to powershell and I wad wondering if in the snapshots category, in addition of having that total size of the vm under “sizeMB”, could we also have the size taking by the snapshots.

    I am interested in the amount of data space that is taken by the actual snapshot.

  • #27 written by USMCSE
    about 1 month ago
    Quote

    Al,
    I love the vCheck script and use it regularly for server auditing. However, I’d like to understand how to change three aspects of the script:
    1. Report in excel vice html
    2. Report on multiple servers in one report
    3. Report on any combination of characteristics: ie hotfixes and printers for the multiple servers.

    Thanks in advance for your help.

No trackbacks yet.