Terminal Server not responding? Black Screen!

[abillybob]

Morning All

 

This has been happening every day since Thursday night and I'm really confused as to why.

 

Basically we have an old terminal server here that everyone uses for day to day tasks but for some strange reason every day when staff try to login it just sits there saying "Configuring Desktop". It's a Hyper-V Machine and when I try to connect on from the Hyper-V Console the screen is just black and I have to reboot it.

 

Once rebooted it works fine for a while and then it happens all over again in a couple of hours. I've looked through event viewer but couldn't find much apart from hundreds of these this morning, I've checked on AD and it is a member of the terminal license group.

 

 

It will also still ping perfectly fine so it's reachable although some other events are saying: Drivers failed to load VBoxNetAdp and cdrom. I also have two others complaining about the NTP server being out of sync and a problem with it that it can't find AD to login users?

 

I'm sorry to bother you all but I've been working on this all weekend and I can't understand what's wrong could really do with some help!!

[3s-gtech]

Some sort of time drift, possibly due to host time sync conflicting with AD?

[abillybob]

Some sort of time drift, possibly due to host time sync conflicting with AD?

The NTP server is pointing to the AD anyway so I don't understand, it's almost like it can't connect to the NTP server during a random time and then after a restart it can again?

[3s-gtech]

Hyper-V has a time sync feature (under each VM's settings) that links the VM to the host to sync the clock. In an AD environment, this should be switched off - check that first.

[abillybob]

Hyper-V has a time sync feature (under each VM's settings) that links the VM to the host to sync the clock. In an AD environment, this should be switched off - check that first.

Cheers mate, have done, not sure why I left this checked! Surely though that wouldn't cause the screen to go black when connecting to it via HyperV? I have to force turn it off and then restart it for me to be able to use it again?

[3s-gtech]

That wouldn't directly cause that issue, no, but it can cause some very odd behaviour. Have a look to see if there are any scheduled tasks running (server or host) around that time too, as some of these can take the VM to a totally unresponsive state (e.g. snapshots).

[abillybob]

I think I may have found the issue.. I've recently installed MalwareBytes EndPoint on all the servers. When I told the client on this particular server to manually update it completed the update then froze the whole machine. I had to turn it off again and restart it so I've removed it for now. Very strange as the other servers don't seem to have the same issue! Any ideas for a remedy?

[3s-gtech]

https://forums.malwarebytes.com/topic/200378-malware-bytes-for-business-and-rds-2016/