This post is for a lazy administrators. Recently I had to install vCenter and its components. Part of it is opening the proper firewall ports in Windows firewall. The list of required ports for vCenter Server 5.5 can be found on this VMWare site. However it’s just a table containing all the ports required for the specific vCenter Server component. I run a quick google search for windows netsh commands to create the firewall rules for the specific vCenter role/component, but I didn’t find it, so I decided, to save any other lazy admin some time. Below you can find them in the vCenter Server role/component installation order.
Probably many people had to face such task before me. I had to get information about storage paths in VMWare including the ESX cluster name, hostname, HBA, etc.
I could of course look for a script which was already written, but probably in the same time I was able to write my own script, which was more challanging for me. I’m using PowerCLI cmdlets, so I need at least VMware.VimAutomation.Core pssnapin. So here goes the script. Continue reading
I reckon, that Powershell is one of the best Mictosoft products. It came alive when Vista/Windows Server 2008 (codename Longhorn – who remembers this 🙂 ) were released. I’m great Powershell fan, it allows to manage many Microsoft products, but not only. Once, I had to change few options in VMWare environment: “Memory/CPU Hotplug” and “Check and upgrade Tools during power cycling” as on screen below
I could do that manually, but changing manually settings in over 5 virtual machines is simply waste of time. Continue reading