<div>
Not yet. It's the main file server and PDC. Will try after hours. Just a bit scary - don't have access to the server if anything goes wrong.
</div>


Not yet. It's the main file server and PDC. Will try after hours. Just a bit scary - don't have access to the server if anything goes wrong.

<div>
I understand, cant you just export it out and import the files to a new vm that has no NIC.?
</div>


I understand, cant you just export it out and import the files to a new vm that has no NIC.?

<div>
Thanks Patrick. I can't even do a forced shutdown of the OS - fails. Only option is to 'Turn Off' but haven't tried that yet. Will look into the export / import option.
</div>


Thanks Patrick. I can't even do a forced shutdown of the OS - fails. Only option is to 'Turn Off' but haven't tried that yet. Will look into the export / import option.

<div>
<div class="content wysiwyg-content">
Strange problem with a VM on Hyper-V 2016. I can't log on via RDP, either from Hyper-V Manager nor from another machine on the network. Even TeamViewer doesn't work. I just get a black screen without interaction.<br />
<br />
Has anyone else run into this?<br />
<br />
Thanks!<br />
<br />
Hardware: Lenovo TD350/70DG<br />
<a href="https://filedb.experts-exchange.com/incoming/2017/03_w12/1152768/HyperV_2016_VM_Logon_BlackScreen.jpg" target="_blank" class="file-inline" title="HyperV_2016_VM_Logon_BlackScreen.jpg (100 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>HyperV_2016_VM_Logon_BlackScreen.jpg</a>
</div>
</div>


HyperV_2016_VM_Logon_BlackScreen.jpg

Strange problem with a VM on Hyper-V 2016. I can't log on via RDP, either from Hyper-V Manager nor from another machine on the network. Even TeamViewer doesn't work. I just get a black screen without interaction.

Has anyone else run into this?

Thanks!

Hardware: Lenovo TD350/70DG

Hyper-V 2016 VM RDP login: Black screen

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.