Can anyone rip a Windows Server Backup as a CAB file, so I may install on Win10 x64? Like SystemState backups.
Do you mind elaborating on this? When you say "upgrade existing VM's" do you mean upgrading to server 2016? If so, care to fill us in on what roles your existing servers have and how did you upgrade them? Did you upgrade the hyper-v host?
Anyone had any luck installing this as a Server 2008R2 Hyper-V guest? When I attempt to install to a fresh virtual machine, I get a bluescreen and the message "MACHINE CHECK EXCEPTION". Windows 10 1607 appears to do the same - I'm running a previous version of Windows 10 as a guest without problems. Are 1607 builds incompatible with Hyper-V on Server 2008R2?
According to MS HV functionality is guaranteed for one subsequent OS generation. So 2008r2's HV guests are supposed to work correctly until Win8/Srv2012. Practically it works correctly also with W8.1/Srv2012 R2. W10, depending on how you count the various major releases is from three to five generations ahead, and it doesn't work. Maybe there is a workaround figured out by someone, somewhere, but I'm nothing I'm aware of. (nor I searched thoroughly for it)
I had several VM's which were upgraded from Server 2012R2 to Server 2016 TP2 or TP3, I forget which. I originally installed with the desktop interface, and after upgrading to 2016 they included Store and Edge. When I upgraded to 10586, the ones which were hosted on a 2008R2 Hyper-V would crash at first boot and undo the upgrade. Moving the VHD files to a 2012R2 Hyper-V and building a new VM with identical configuration solved that issue. At 14393, I still have Store but Edge is a blank nonfunctional tile. Does that answer your question?
just upgraded a TP5 machine and let it check for updates during install, it finished install on 14393.187
Yes, Cumulative updates do not change build version, it will be always 14393.0 those WSUS packs are for completely different build 14393.82 i remember they did this odd mix in one of insider builds