vksmjones Posted January 27, 2005 Report Share Posted January 27, 2005 Retrospect needs to run as a service (especially on multi-server) so that when I connect to my backup server through terminal services, I can run an instance of Retrospect and see what's running. Right now I have to connect to the server via Netmeeting and that has more limitations than terminal services. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 8, 2005 Report Share Posted February 8, 2005 This should help: http://kb.dantz.com/article.asp?article=7891&p=2 BTW, thanks for the big list of suggestions. Quote Link to comment Share on other sites More sharing options...
vksmjones Posted March 2, 2005 Author Report Share Posted March 2, 2005 Starting a terminal service session into the server is not a problem. The problem is that starting a session without any parameters gives me a terminal service session with not Retrospect. If I want to see Retrospect when I connect via terminal services (or remote desktop connection), I have to connect with the following command: "%windir%\system32\mstsc.exe -v:<servername> /F -console" so I see the programs running in the console session. The first problem here is that I have to TS into this server differently than I do all of the rest of my servers. The second problem is that the physical console goes to a CTRL+ALT+DEL prompt once I TS into the console session and it doesn't return to the console once I logout of the TS session. Because of this, I may get a call from an operator on the weekend when she tries to swap tapes for me because she doesn't have the login info for this server. If there is an easier way to get to Retrospect via TS without specifying the extra command line arguments, let me know. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.