Restart windows 2003 terminal services

Operating Systems. Anand Sudabattula June 3, 0 Comments. C Butler Posted June 3, 0 Comments. Hank Arnold Posted June 4, 0 Comments.

The command the OP gave is the same as using the Services console. Register or Login. Welcome back! Reset Your Password We'll send an email with a link to reset your password. Stay ahead! Get the latest news, expert insights and market research, tailored to your interests.

Sign in with email Enter the email address associated with your account. You auth link is expired or incorrect, please try again. Sign up with email Get the latest news, expert insights and market research, tailored to your interests. The batch file might look like this:. By saving this command in a batch file, it can save you time if you routinely restart the same remote server.

Check out the Windows Server archive to get even more Windows Server tips. Stay on top of the latest Windows Server tips and tricks with our free Windows Server newsletter, delivered each Wednesday. Automatically sign up today! Derek Schauland has been tinkering with Windows systems since From the command line, you can shut down or reboot any Windows Server computer or even Windows XP or Vista machines with the Shutdown. Note : The exe file extension is optional for the Shutdown command. The Shutdown.

Miss a Windows Server tip? Editor's Picks. Windows Terminal Server not responding after reboots Ask Question. Asked 9 years, 6 months ago. Active 9 years, 6 months ago. Viewed 2k times. All terminal servers show the following errors in the event log after reboots however not all of them arent responding, most work fine post reboot Event ID - Error - Netlogon - This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following: There are no logon servers available.

Thanks for any assistance! Improve this question. Why are you rebooting every night? Unfortunately this is out of my control, I believe it is due to the belief that the servers run out of resources after continued use. Forces all users to disconnect and have all resources opened each business day. You can go into the Computer Management and set timeout limits so that all of the users accounts are logged off automatically after a set amount of time.

But DanBig is right in asking "Why are you rebooting every night" You should fix whatever is wrong, instead. I realize that we shouldnt be rebooting every night. Unfortunately as I mentioned this is out of my control. I think its reasonable to expect an OS to be able to reboot nightly without running into these issues as well. I think its reasonable to expect an OS to be able to go witout rebooting every night :. But as you said it's out of your controll.

My feeling is just that you should avoid these things because in larger networks the reconnecting and reesablishing of all links can be more troublesome. Maybe you should have a word with the people who are in charge of this. To get back to the Problem: It seems like a problem with your Domain Controller. Show 6 more comments. Active Oldest Votes. First thing I'd do is set the TS services to delayed start up, in case it's an OS or machine boot issue.

It'll set the service to start up after most everything else, so any dependencies should be fully started and there won't be any conflicts with it started at the same time as whatever else. Failing that, I'd use a scheduled task to restart the service a couple minutes after the OS boots up. Would take a little bit of guesswork to schedule it right, based on reboot time, machine boot speed and OS load speed.

Investigate the NICs on the machines? Is it possible that the cause is outdated drivers or firmware, and updated software like Windows Updates and any other patches you've [hopefully] applied conflicting with each other from time to time? Failing that and maybe anyway, to try to resolve the root cause, rather than just alleviate the symptom , I'd do a reinstall uninstall, install fresh of the Terminal Services on the impacted servers.

I've had this kind of issue, absent EventID and that usually resolves it, at least when it's a problem with the TS services on the server, and not caused by networking or domain controller issue. Maybe do this before 4 Troubleshoot this from the Domain Controller. There is a reason that the Eventlog is telling you the server can't contact a logon server and the Domain Controller isn't allowing the hostname to be assigned to the indicated interface.

This can be caused by domain or Domain Controller settings. Look on the DC to see if there are any indications of that.