Retrospect and Terminal services problem

[chadh]

I have a customer with a Win2003 SP2 SBS running the latest patch for retrospect 7.5 (2/15). I created a domain account called "Retrospect" member of Domain Admins and Backup operators. This account is set to be used by retrospect in the terminal services session. Yes, I followed the guide for configuring the account and Terminal services so the session does not disconnect. I also verified the permissions on the Retrospect directory that may have been changed by SP2. However, when I connect to the server through Terminal services with my Retrospect account and try to open Retrospect I get the error that the program is in use by another user already and asks if I want to quit that instance. If I say OK, it will hang the system and usually require a reboot to clear. Why is this happening? I have used other server level backups before and have never needed to jump through such hoops just to check the status of the program. The way I understand this, I need to login to the server, open retrospect and never close or logoff, if I want to avoid this. As this server has no local login ability, everything is done through Terminal services.

 

How can this problem be fixed?

 

Chad

[MRIS]

simple.

 

connect to the "console" of the terminal server using the /console command line option of the RDP client like so. On your XP client, Start --> Run... --> mstsc /console /v:yourserver

 

When prompted for credentials, login as the retrospect user. There should be a red-box tray icon (the retrospect logo), which you can double-click to open the full GUI. When finished simply close the GUI.

 

The GUI must remain open permanently if you are using proactive backup. Otherwise close the GUI and logout.

[kavsko]

I have exactly the same problem.

The option console is set but still whem I open Retrospect it happens the same error.

[MRIS]

ok, what you guys are saying is that you are trying to reconnect to a disconnected terminal session, but rather than reconnect to that session, a second session is created.

 

One possible explanation for this is that the session you THOUGHT was disconnected wasn't. This could be because someone else is connected to it.

 

For example, if you have the RDP window to the retrospect session open on your work computer and later go home and want to check on status, when you connect to the server you get given a second session (erroneously), because the actual session is still in use (on your work computer). The secret is to disconnect from the retrospect session when not in use. This will allow you to reconnect it it later (eg from home). This also means that only one person can be connected to the session at a time, unless you use TSADMIN's remote session control capabilities.

 

None of this is specific to Retrospect, it is just the way that plain normal terminal sessions, either for a terminal sever in application mode, or a regular server in remote administration mode operate.

 

Windows Server 2003 introduced the capability to connect to the Console of the server with the RDP client. This means if you originally launched retrospect while standing in front of the computer's screen and keyboard, then you are simply logged into the console and are running retrospect there. If you later connect to this server with RDP you will get given the first terminal session (a new session) in which you CANNOT use retrospect because it is already running on the console. In this situation, logout of the terminal session and connect to the console of the server instead. This is where the switch "mstsc /console" comes in.

 

Edited April 12, 2008 by Guest

[Mayoff]

please see

 

http://kb.dantz.com/article.asp?article=7891&p=2