by Jess Males | Technical Consultant at Taos There’s a long list of technologies operations staff have to know. Networking, storage, web-servers, email, DNS, kernels, monitoring: this list is far from complete. This is a formidable list, and enough to keep anyone busy, but, let’s take a moment to look in some other corners; there, […]
I recently had a situation where I needed to change the hostname, IP, and domain of around 200 VMs. No problem, I can just script that out, right? Well, the problem with scripting in this case was that the VMs were in an offline state (more on that below). I also couldn’t use VMware customization specs because those are only available during cloning or deployment operations. The answer came in the form of a clever cmdlet called Invoke-VMScript that let me execute code using VMware tools as the delivery mechanism. In this blog I’ll talk about how VMScript saved me countless hours and I’ll give you some tips on using the command, but first a little background…
A whole lot, that’s what!
First, let us take a look at the name. Normally, I would say “What’s in a name?” but Powershell’s name actually holds some meaning. The first word, ‘Power,’ adequately describes the language, which is quite powerful. It was clearly designed from the ground-up to be a purebred full-throttle administration tool. And ‘Shell’ simply means it is a command-line user interface. Think of Powershell as a powerful command-line administration interface, and you know why they call it that.”