tacc_adams Posted July 8, 2008 Report Share Posted July 8, 2008 (edited) ***This is for those of you administering Retrospect through terminal services*** The latest update to RDC Client (6.1 as of this posting) deprecated the /console switch when calling it via "mstsc" on the command line. This has been changed to /admin. So, in plain speak, if you have updated to version 6.1 (or higher) of the RDC Client, instead of running: mstsc /console you would now run: mstsc /admin Hopefully this prevents some of you from losing several hours of lost productivity from a seemingly unrelated software upgrade. Edited July 8, 2008 by Guest Clarified reason for the post Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 8, 2008 Report Share Posted July 8, 2008 I am confused. Was this a Retrospect question? Quote Link to comment Share on other sites More sharing options...
tacc_adams Posted July 8, 2008 Author Report Share Posted July 8, 2008 I am confused. Was this a Retrospect question? If you're trying to run Retrospect through a Remote Desktop Connection client, have version 6.1 or higher of the RDC client, the /console switch no longer works, does not provide an error, and will not allow you to use Retrospect. If you change "mstsc /console" to "mstsc /admin", then you will be able to continue using Retrospect through RDC as before. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 8, 2008 Report Share Posted July 8, 2008 I understand. Retrospect for Windows users can now also use the Retrospect Activity Monitor to see the current backup status when the application GUI is in a different user session. 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.