SCVMM 2016 Technical Preview 2 – Operational Notes

If you are testing the SCVMM 2016 Technical Preview 2 I have some operational notes for you. I ran into several issues in the first two days of testing the TP2 release and I want to share the solutions with you.

First issue that you will run into it is an error where the VMM console crashes when you try to add an additional cluster node to an existing cluster. As it is mentioned in the release notes you have to user PowerShell instead.

-> https://technet.microsoft.com/en-US/library/dn966269.aspx

Second issue that you will run into it is an error where the VMM job fails if you try to refresh a Hyper-V host which has a local disk running as dynamic disk instead of basic disk. In my case it was a Hyper-V host in my Hyper-V failover cluster but the behavior can be the same with a standalone Hyper-V host. The error message in the VMM job will be the following one.

Object reference not set to an instance of an object.

But have a look at the report.txt in the mentioned folder. You will see some more specific information.

System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.VirtualManager.Engine.Adhc.HyperVClusterProperties.<>c__DisplayClass1c.<>c__DisplayClass1e.<PopulateClusterSpecificData>b__a(HostDiskData diskData)
at System.Collections.Generic.List`1.Find(Predicate`1 match)
at Microsoft.VirtualManager.Engine.Adhc.HyperVClusterProperties.<>c__DisplayClass1c.<PopulateClusterSpecificData>b__9(HostVolumeData candidate)
at System.Collections.Generic.List`1.Find(Predicate`1 match)

In my case the only solution was to backup all the files on this volume and recreate the disk as basic disk again. Format the volume and restore all the files.

Third issue that you will run into it is a behavior of the VMM console where you cannot really use the VMM console because it freezes and crashes after some time. But with the VMM PowerShell cmdlets it works fine. Make sure you have installed the update KB3061186 on your VMM management server and VMM console workstation. The update will solve this third issue.

-> https://support.microsoft.com/en-us/kb/3061186

Facebooktwittergoogle_pluslinkedinmail

Leave a Reply