Hi,
I have recently set up a number of new Server 2016 Remote Desktop Servers. I have a timed script which runs at 6am to reboot them all, as we have some Excel add-ins which have tendency to crash and require a reboot, and a scheduled reboot means the servers don't have to be checked regularly for this.
I've always done this with the previous Remote Desktop Server (2012 R2), and never had any issues. With the new ones, most of them are fine but on two of them there is an intermittent problem (at least 1 in every 2 days) of them being inaccessible by RDP after the reboot. When I go into thm via VMWare, I can see that the Remote Desktop Connection Broker (Tssdis) service is stopped. If I manually start the service, or reboot the server again, it's then fine.
I can't replicate the problem manually - if I copy the line from the batch file which reboots all the Remote Desktop Servers and use it to reboot one of the problem ones from a command prompt, they are fine.
I've checked the event log, and on both of them there's a information item saying that the service has started after the reboot, as would be expected - but then another one saying it has stopped a few seconds later.
Anyone able to suggest anything? At the moment I'm checking these two servers before most of our staff start work, and starting the service if it's stopped - but this isn't a long-term solution!
Thanks
David