Hello.

We have 6 servers for software acces with terminal service. We need to restart the servers each day to questions of stability and server uptime. There are 3 months, we started having problems following the server reboot. Those are no longer available to connect to TS. A simple reboot does not work, the TS service remains unabalable. For it working again, we must put the Terminal Server service by "disabled", reboot the server, restore the service to "Manual" and the start

We had a task to restart the server, "shutdown.exe -r -f". If we use this exe, most of the time, after the reboot, the service is not available, even if it is started. If we do this manually reboot, everything works. We tried the PsShutdown, it worked well 2 weeks, but at some point, it began to stop working as shudown.exe.

We even made a powershell script that disable the service before the reboot and restart after startup. This script is the sequence that we are doing manually for it working. But even with this script, we got the same problem after reboot. I even made it a condition that if 3389 is not available, the server reboot after 15 minutes. It reboot all the last weekend...

These are physical servers Windows 2003 with 24 core and 16 gig RAM. (They will eventually be migrated to 2012, but not before the end of the year). We also look to the teaming network cards, but it does not seem to resolve anything either.

We are now being out of idea for the problem. We have another 4 servers sluster that have the same symptom.

Is there someone who has had this problem? Anyone knows how to solve this problem ???

Tx

Hi,

Please check event logs on terminal servers to find the cause why terminal services didn't start automatically after reboot.

Best Regards,
Amy