Hello readers and viewers!
I realize it has been a LONG time since I published an “8-Minute-Demo”, but I figured it was time. I was going to wait until my voice was back to normal, but I didn’t know how long you would have to wait. So, please excuse the hoarseness of my voice.
Today’s Video Topic: Have you recently upgraded your Windows Server 2008 R2 machine with Hyper-V to Service Pack 1? Well, some unique changes to Hyper-V come along with that upgrade. One of these is the need to upgrade the Integration Services (Components) for each of the VMs on your Hyper-V Server. This video shows how you can automate the upgrade of all your VMs utilizing OIS and the available VMM Integration Pack.
That said, here is the video!
So that you can draw from the same raw materials I did in the demonstration, the following table contains the PowerShell I used in the OIS workflow:
|PowerShell for Querying the IntegrationServicesVersion values for VMs on the Hyper-V Host (requires http://pshyperv.codeplex.com/). Appears at timestamp 00:01:47 in video.||
|PowerShell for Querying the Registry on the target VMs for their IntegrationServicesVersion value. Appears at timestamps 00:04:12 and 00:07:29 in video.||
$password = ConvertTo-SecureString -String "##PASSWORD VARIABLE##" -AsPlainText -Force;
Also, the other blog post that I mentioned in the video (timestamp 00:04:33) is the “8 Minute Demo – OIS-SCVMM PowerShell Execution Options”. This is where I introduced the syntax for using PowerShell to access information on remote machines from OIS installed on a Windows Server 2008 x64 machine.
Finally, attached to this blog post, I have included the OIS_EXPORT of a version of the workflow in the demonstration. This can be used as a guide to recreate this process in your own OIS environment. The version of the workflow included here has a bit more error checking and includes a loop on the “Verify IC Version on VM” object, which will ensure success of the verification check PowerShell command before the workflow continues to the comparison object.
Keep in mind, this process will do exactly what you have configured it to do. If your DC (or any VM that is a network dependency for other VMs) is in the automated upgrade list, it will be shutdown, updated and restarted. In fact, if it applies, you will want to manually upgrade your OIS and VMM m virtual machines’ ICs for Hyper-V so that they is off the list. 😉
NOTE: As this is simply an example of what you *could* do, only a sample of options are covered in this video and workflow example. Your specific experience will vary based on your environment and process. You may want to add some “intelligent branching” after the “Get VMs” object to handle cases where the published data in the “Computer Name” field from that object will not work in the “Check IC Version on VM”. This would include non-Windows and old-Windows hosts where the PowerShell would not be able to connect and retrieve the IC version information. It may also be a good idea to add a filter to the “Get VMs” object to only return “Running” VMs, as the PowerShell commands will not work on “Stopped” or “Paused” VMs (or ensure all your VMs are “Running” before executing this workflow).
Same workflow, this time without verification steps (minimalistic approach):
You can use the “Get VMs” object in this example to filter out the machines you do not want to run through the process. See the following image of the “Get VMs” object properties:
You would still reference the “VM ID” in each of the subsequent objects, and of course, the “Update VM” object would still contain “True” for the “Install Virtualization Guest Services” field (see image below):
Whichever way you do it…