Terminal services and reboot

[somedave]

Hi - I seem to have a problem with my configuration in regards to terminal services and Retrospect. The problem is that after the server reboots (power outage, software install, etc) no scheduled executions will start. I have Retrospect configured to use a specific account (with admin privledges) and I've checked the "Run Retrospect in the Terminal Services session" box. In order to get the backup scripts to run after a reboot, I have to open a new terminal services session, launch the Retrospect client, and then close out of the session without terminating it. the launcher service is running. I'm assuming that the root cause is that Retrospect won't start itself if there is no active terminal services session for the user Retrospect is configured to run as.

 

So the question is: Is there ANY way to get Retrospect to start itself for scheduled jobs when no terminal services session is started? If not, is there a way to auto-start a terminal services session for a given user after a reboot? My concern is that I'll be away or on vacation, the server reboots, and no jobs get run until I come back and recreate the terminal services session for the backup user.

 

Thanks.

[randallrash]

I also launch in a terminal server session. I don't keep a terminal server session open though. Maybe check that Configure->Preferences->Startup has both "Enable Retrospect Launcher" and "Automatically launch Retrospect" are checked. I don't boot my server often enough to know if I may have the same problem.

[randallrash]

Duh, I stand 100% corrected. If a terminal server session is not open then it launches in the main console screen.

[somedave]

My problem is that it doesn't launch at all if I don't manually start it in a terminal services session. It's a big problem for when the server goes down because someone has to first know that it went down and then start Retrospect in the proper TS session.