Terminal Services - Reconnect?

[Barnacle]

I started a Terminal Services session with a Windows 2000 server in our network. I ran Windows Update on that server through the session. Then I closed Terminal Services while the update ran. When I reconnected I expected to see my Windows Updates screen, but it wasn't there!

Should I just ASSUME that it finished properly and reboot the server, or is there a way to get back to where I was when I disconnected the session?

 

[Stevehewitt]

Very nearly.

Logon to the server locally (ideally, although not necessary) and open Terminal Services Manager from the Administrative Tools menu.

Ensure that your server is selected in the list from the left hand explorer style tree and you should see in the right hand side of the Window all users that currently have a session. The "Console" is the local user, and anyone else is a remote Terminal Services user. If you want to reconnect to a session that is disconected, right click and take control. If not try a reset.

If you are still not sure what happened after you disconnected try having a look in the Event Viewer.

One last thing, MS do not recommend doing updates or installing software using Terminal Services - and you can see one of the reasons why!

Good Luck, and if there are anymore problems post back.


Steve.
If this post was helpful, don't forget to star it!

Steve Hewitt

 

[Barnacle]

Thank you for the reply Steve. The Terminal Services session that I disconnected from was one that I disconnected from "normally". It wasn't an accident. I wanted to start it and let it run while I drove about 80 miles home from the remote office I was working at.

Whenever I connect to this server using Terminal Services I always get a message from and application asking me if I want to register. It doesn't come up when I'm sitting in front of the server though. That was why I thought that I would see the Windows update results when I logged back on. Oops! I didn't see anything about the updates in the Event log. I hope the server comes back when I reboot it!

 

[Stevehewitt]

I agree, and I bend the rules for that as well when needs be - but Windows works differently when running under TS which is why Microsoft don't recommend it.

If you have a peek in Event viewer you should be able to see if the the server got restarted.

What application are you gettting a message from?


Steve.
If this post was helpful, don't forget to star it!

 

[Barnacle]

It's some Acuprint application. I don't know what it is. It was on the server before I started working on it.

I get 2 messages...one says "Error, Server setup values corrupted, contact Technical Support for server reinitialization".

The other says "Server not registered, do you wish to register now".

 

[Barnacle]

When I said YES to register it took me to a box that says the program is Securecheck Server. That program is running fine on the server and you don't get the messages when you start it normally.

 

[Stevehewitt]

Thats just a dodgey application that probably works fine,
locally, but is not designed for Terminal Services.