VMware has published a new KB (2082132) article outlining the latest versions of PowerCLI that contain fixes for the infamous OpenSSL bugs.
I’ve gotten some great feedback from my original PowerShell/PowerCLI script to deploy multiple VMs asynchronously via a CSV file found here. I decided a minor update was needed to employ these new ideas along with a few I had myself.
One of those ideas was to require the usage of the new PowerCLI 5.5 R2 features which allows the script to run without the need for a 32bit PowerShell console.
- Cleaned up code / Minor bug fixes
- Added CSV field descriptions to notes section
- Removed requirement for 32bit PowerShell
- Added requirement for PowerCLI 5.5 R2 or later
- Added Boot parameter to determine whether or not to power on new VMs
- Added OS Customization Spec to CSV (previously was hard coded in user variables)
- Fixed logic for vSS vs vDS – Added parameter to CSV
- Added ability to use DHCP instead of just static IPs
- Renamed a few CSV fields to better describe parameter
- Added progress bar to indicate status
As a VMware admin there are a plethora of tools to assist you in gaining visibility into your virtual environment. I’ve seen folks layer on three or four tools at a time in an attempt at getting the best insight into what is going on under the virtual covers. Some of these tools excel in different areas though I have rarely found one that fits all needs. Almost all will have some sort of alerting capability to let you know when something has gone south and many of these products cost in the tens of thousands of dollars.
If there was one tool that was an absolute must have for me – vCheck – hands down.
And the best part? It’s free!
Now, vCheck is not going to replace all those shiny, expensive tools but for a single report that gives you an overview of what you are walking into in the morning, it can not be beat.
VMware has rolled out a few updates this week with the release of vSphere 5.5 Update 1. The majority of the products involved all got some sort of bump/patch as well as the addition of VSAN. Not to be outdone, Alan and his team also released PowerCli 5.5 R2 (Build 1649237). It is wonderful to see grand improvements in a product I use everyday.
A full rundown of the new features and download link can be found here.
It just may be time to give a serious look at updating to PowerShell 4.0 as with this update, PowerCli is fully compatible. Time to start looking at other plugins as well and determine what dependencies might have issues.
Another one of the new features that caught my eye was this:
64 bit Support
The New/Set-OSCustomizationSpec cmdlets have been updated to work in 64-bit PowerShell and no longer require running in a 32-bit PowerShell environment.
This will help my VM Deployment script as you will now longer have to run in 32bit mode. I’ll be checking this out and updating shortly.
A few posts back I described how you can document your Veeam backup job settings. This gives a great overview, especially if you have many jobs to keep track of. As I mentioned, I had found a few inconsistencies across jobs and in this post I’ll show how to update all jobs via a small script. You can imagine the time saved by not having to open each and every job, check the settings and update if needed.
Changing passwords is always one of those fun tasks for any admin. It becomes even more challenging when your a Windows admin over hundreds of individual servers that are not part of the same domain. Here’s my take on a PowerShell script to change the password of a local user on a remote system (or many remote systems), regardless of domain status.