New
#1010
Happens to me occasionally and is an annoyance. Basically there doesn't seem to be anything amiss when I open settings. I have shared experiences limited to my devices.
Since there has been no post from anybody but me on this Sunday I thought I'd just post the image below.
What you see is, from left to right, winveron my Windows 10 host, running a dual boot Hyper-V which has booted into Windows Server 2016, which in turn was remotely connected to my HP Proliant running Windows Server 2016 Essentials with a VMware WS Windows 10 VM.
Makes me wonder if Microsoft is planning a 2017 update to Windows Server 2016. I'll try to suss it out.
Hello Kari,
It happened to one of my desktops after an upgrade from 1607 to 1703, one time only and as Marty mentioned I to had no problems as you mentioned. Glitch didn't occur on three other upgrades. At least not yet. The machine it did happen on was after the update was applied to 15063.11. Updating the other machines did not produce the error.
DISM is the thorn in my side now. You've hit the nail on the head imho. By the way, Happy belated Birthday. Noticed it on another group!
Having too much time on my hands I'm posting another screenshot of Nested Winvers. Again on the left is my physical machine running Windows Server 2016 Standard. On this I've made a VMware WS Dual Boot VM which is a VM created by VMware Converter virtualizing the physical. So that Windows 2016 Server VM is connected again to HP Proliant Windows Server 2016 Business Essentials running a VMwaRe VM of Windows 10. The innermost VM is the same as I posted earlier using the Hyper-V Dual Boot VM on the physical Windows 10. Now that I have this I will turn to most problematic situation where I am running openSUSE Leap 42.3 Alpha with a copy of the VMwaRe Dual Boot. However the RDP program may very well timeout,
Marty, am I getting it wrong or you are emulating an emulator in an emulator ? In other words running VM in a VM ?
It was a confusing post, but as I understand it, hes cloned his Physical Server, running that clone in a VM on the same server. Then he has another computer, that has a Windows 10 VM that also has been virtualized from a physical computer and he is remote virtualizing Windows 10 from within the Server VM.
That remote Virtualization could be thought as a Remote Desktop connection, though being a virtual machine. In the end he's virtualizing only once on each hardware.
Ok, now I see my post isn't much less complicated than Marty's
EDIT: Essentially he has cloned his physical hardware and is virtualizing it for testing. If something breaks, he knows what NOT to do on the physical/real computers.
Actually no. I can be done but performance is lousy.
Let's take the first example. Keep in mind that I have a dual boot Windows system (we can leave out the openSUSE OS here).
1. Physical machine running Windows 10 Build 15063. Installed Hyper-V feature
2. Create, using disk2vhd.exe a Hyper-V VM of the physical machine. Kari posted a tutorial on this awhile back but I've used that program before.
3. Inside the Hyper-V VM I boot into Windows Server 2016.
4. I use the Microsoft Remote Desktop Connection program to log into a HP Server running Windows 2016 Essentials on which I've installed VMware WS 12.5 and created a Windows 10 VM. I open that VM from my Windows 10 Desktop a whole 4 feet away. Just using a Netgear router my wife has see up to share an Ethernet connection.
On the second example
1. Booted into Windows Server 2016 from my desktop machine. I've installed VMware WS 12.5 and created a dual boot VMware VM of my physical machine using VMware. From there I boot again to the the virtualized Windows Server 2016 and use Remote Desktop Connection to bring up the same VM running Windows 10 on the HP Server.
In otherwords the same VM winver is the screenshot on the right.
I've never been able to connect to the Windows Server on the HP from openSUSE (or an Linux for that matter) so that just shows (and many of us nerds know this) -- the difficult we do right away - the impossible takes a little longer :)
Hope this clarifies. I now realize it would help if besides showing winver I should have a command prompt session running ipconfig to show the ip addresses.