I'm connecting (or trying) a Windows 10 N Enterprise VM on a Windows Server 2016 host. All are up to date and the wrapper config / installation looks fine. But as soon as I try to connect another session I get asked to disconnect my current session, as if no wrapper would be active. The screenshot shows it all:
The last time (two weeks ago) I configured the same setup but on 'real' instead of virtual hardware and then all was fine.
My goals is to run a 'rdp wrapped' Windows 10 VM on Azure. Yes I could run session directly on the server instead of on the VM but my use case does not allow me to do so. I other words I really like to have it on a virtualized Windows 10 installation.
The virtualization should have no influence as far as my reasoning goes (Since I'm connecting to the VM's RDP and not the Server)... Any clues what's going on here?
I'm connecting (or trying) a Windows 10 N Enterprise VM on a Windows Server 2016 host. All are up to date and the wrapper config / installation looks fine. But as soon as I try to connect another session I get asked to disconnect my current session, as if no wrapper would be active. The screenshot shows it all:
The last time (two weeks ago) I configured the same setup but on 'real' instead of virtual hardware and then all was fine.
My goals is to run a 'rdp wrapped' Windows 10 VM on Azure. Yes I could run session directly on the server instead of on the VM but my use case does not allow me to do so. I other words I really like to have it on a virtualized Windows 10 installation.
The virtualization should have no influence as far as my reasoning goes (Since I'm connecting to the VM's RDP and not the Server)... Any clues what's going on here?