Thank you Hetman66.
This is similar to my #3 attempt, other than firing the cmd file from the startup folder rather than as a logon script. The problem that arises is that it ties up the console session. (This server is on an isolated network, so the only outside world connection is the KVM, which of course connects to the console session. Different people with different security priviledges need remote access to the server, so I can't tie up that console session.) I tried putting a logoff in the cmd file, but that just creates an endless loop of logging the console session on and off. Also, when different people log on to the console session, the defaultusername changes, which of course interferes with AutoAdminLogon.
Main Topics
Browse All Topics
by: Netman66Posted on 2009-05-14 at 16:47:20ID: 24391112
You should be able to do this like so:
1) From the Run box, type in mstsc - then ENTER
2) Click the Options arrow (lower left).
3) Setup the connection with username and password
4) Check the box for Allow me to Save credentials.
5) From the first tab, Save As - save it somewhere you can find it.
6) You can create a batch file using the following syntax:
mstsc.exe Connection.rdp
Where Connection.rdp is the full path to the RDP file you saved above.
7) Save the .cmd file above to the Administrator's startup folder. As long as the Administrator logs in this will run. You may need to configure Autologon and include a way to lock the console afterwards (easy enough). Do not do this on a DC because the builtin Administrator is also Domain Admin and Enterprise Admin. You'd rather run this from a member server.
This should launch the TS client using the RDP file for input.
Let us know how you make out.