I know, that in the era of IaC, OS templates should be gone, but still they’re alive. During my work I faced the situation, that I had to patch monthly about 30 VM Windows Server VMWare templates with only specified patches, whch were previously approved by the relevant team. Patches were defined in the SCCM – for the I wrote another script to gather all needed patches and create an ISO which will be the entry point for the patching script – but this is a different story. Continue reading
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