We use SCVMM and have been experimenting with the semi-annual 17263 build as well as prior builds. With 17093 and earlier versions, we could add the system as a VMM Host resource. After loading 17263, adding the hosts fail with the error below. SCVMM is the latest roll up. Anyone else having similar issues? Our next thought is to backup to 17093 and do an upgrade of that revision - after adding the hosts to SCVMM - vs. doing a clean install.
----------------------------------------------------
------------------- Error Report -------------------
----------------------------------------------------
Error report created 3/21/2018 2:32:57 PM
CLR is not terminating
----------------------------------------------------
--------------- Bucketing Parameters ---------------
----------------------------------------------------
EventType=VMM20
P1(appName)=vmmservice.exe
P2(appVersion)=4.0.2244.0
P3(assemblyName)=ImgLibEngine.dll
P4(assemblyVer)=4.0.2244.0
P5(methodName)=Microsoft.VirtualManager.Engine.ImageLibrary.Storage.StrgNodeToDisk.ValidateIsFunctionLevelWindowsThresholdAndAbove
P6(exceptionType)=System.ArgumentNullException
P7(callstackHash)=92be
SCVMM Version=4.0.2244.0
SCVMM flavor=C-buddy-RTL-AMD64
Default Assembly Version=4.0.2244.0
Executable Name=vmmservice.exe
Executable Version=4.0.2244.0
Base Exception Target Site=140715892519728
Base Exception Assembly name=mscorlib.dll
Base Exception Method Name=System.Version.Parse
Exception Message=Value cannot be null.
Parameter name: input
EIP=0x00007ffb0b843c58
Build bit-size=64
