Hyper V: Get All The Guest VM IP Addresses
KB ID 0001386 Problem Getting the IP address for an individual guest VM is easy enough, but if you have a lot of guest VM’s then you need some PowerShell. Solution To get the IP’s of all the Guest VM’s on an individual Hyper-V host, use the following syntax; Get-VM | Select-Object -ExpandProperty NetworkAdapters | Select-Object VMName,IPAddresses | Format-Table -Auto Note: The entries with no IP, are either powered...
Finding Out Your Microsoft Office Licence Version
KB ID 0001385 Problem While doing some upgrades on a clients RDS farm this week, I needed to find out what version of Microsoft Office they were running. I’m not talking about Office 2013, Office 2016, etc, that’s easy to find out, (run appwiz.cpl and look in Add/Remove Programs). I’m taking about are you running a retail copy, or a volume licensed copy, or an Office 365 Office subscriptions copy. Solution For some...
Hyper-V Creating a NAT Network and vSwitch
KB ID 0001384 Problem I’m without access to all my test equipment at the moment, so when I needed to do some testing, I thought I’d use Hyper-V on my new work laptop. I needed to ‘knock up’ a quick vSwitch that would NAT my test machines, to my laptops connected NIC. Solution Open an administrative PowerShell window, and execute the following three commands. Note: You can change the values in RED to suit your...
VMware: Depreciated VFMS Volume(s) Found On This Host
KB ID 0001383 Problem Well there is a bug on ESX version 6.0.0 that causes this error message, in my case the client had VFMS3 volumes. Depreciated VFMS volume(s) found on the host. Please consider upgrading volumes(s) to the latest version. That’s what was causing the error in my case! Solution I chose to simply update the VFMS3 volumes to VFMS5 > Right click the volume > Upgrade to VFMS5. Select the volume(s) > OK....
Hyper-V 2016 – Missing VM Hardware Versions?
KB ID 0001382 Problem I was helping a colleague with a Hyper-V upgrade this week, he asked if I would upgrade the hardware versions on the guest VM’s Get-VMHostSupportedVersionl However I could not get the cluster to accept a hardware version above version 5 (Server 2012 R2) Solution As it turns out the cluster had had all its nodes upgraded to 2016, but the cluster functional level was still at version 8 (Server 2012)...