MSTSC - Terminal Server Connection
Creates connections to terminal servers or other remote computers, edits an existing Remote Desktop Connection (.rdp) configuration file, and migrates legacy connection files that were created with Client Connection Manager to new .rdp connection files.
How to connect to the windows console on a Win2k3 machine via remote desktop:
mstsc -v:servername /F -console
mstsc.exe {ConnectionFile | /v:ServerName[:Port]} [/console] [/f] [/w:Width/h:Height]
mstsc.exe/edit“ConnectionFile“
mstsc.exe/migrate
Parameters
ConnectionFile
Specifies the name of an .rdp file for the connection.
/v:ServerName[ :Port]
Specifies the remote computer and, optionally, the port number to which you want to connect.
/console
Connects to the console session of the specified Windows Server 2003 family operating system.
/f
Starts Remote Desktop connection in full-screen mode.
/w:Width/h:Height
Specifies the dimensions of the Remote Desktop screen.
/edit“ConnectionFile“
Opens the specified .rdp file for editing.
/migrate
Migrates legacy connection files that were created with Client Connection Manager to new .rdp connection files.
Remarks
•
You must be an administrator on the server to which you are connecting to create a remote console connection.
•
default.rdp is stored for each user as a hidden file in My Documents. User created .rdp files are stored by default in My Documents but can be moved anywhere.
Examples
To connect to the console session of a server, type:
mstsc /console
To open a file called filename.rdp for editing, type:
mstsc /edit filename.rdp
Shadow
Enables you to remotely control an active session of another user.
shadow{SessionName | SessionID} [/server:ServerName] [/v]
Examples
To shadow session 93, type:
shadow 93
To shadow the session ACCTG01, type:
shadow ACCTG01
MSTSC
Terminal Server Connection, RDP (Remote Desktop Protocol)
Syntax MSTSC option MSTSC /Edit”ConnectionFile” MSTSC /migrate Options ConnectionFile The name of an RDP file for connection /v:<server[:port]> Terminal server (or PC) to connect to /console Connect to the console of a server /f Start in Full Screen mode /w:width Width of the RDP screen /h:height Height of the RDP screen /edit Open the RDP file for editing /migrate Migrate a Client connection file to RDP
The /console option only works when connecting to an Windows XP Professional or Windows Server 2003 computer.
When connected to a remote desktop, the key combination Ctrl-Alt-END will send Ctrl-Alt-Del to the remote client.
Examples:
MSTSC /v:MyServer /f /console
MSTSC /v:127.0.0.1 /w:1024 /h:768
MSTSC /v:MyServer /w:800 /h:600
MSTSC /edit filename.rdp
On the Windows XP CD, under \SUPPORT\TOOLS you’ll find MSRDPCLI.exe. This is the setup for use with 9.x/2000 machines.
Terminal Services
Windows Server 2008 features major upgrades to Terminal Services. Terminal Services now supports Remote Desktop Protocol 6.0. The most notable improvement is the ability to share a single application over a Remote Desktop connection, instead of the entire desktop. This feature is called Terminal Services Remote Programs. Other features new to Terminal Services include Terminal Services Gateway and Terminal Services Web Access (full web interface). With Terminal Services Gateway, authorized computers are able to connect securely to a Terminal Server or Remote Desktop from the Internet using RDP via HTTPS without implementing a VPN session first. Additional ports do not need to be opened in the firewall, RDP is tunneled through HTTPS. Terminal Services Web Access enables administrators to provide access to the Terminal Services Sessions via a Web interface. TS Web Access comes with an adjustable Webpart for IIS and Sharepoint, which advertises the possible applications and connections to the user. Using TS Gateway and TS Remote Programs, the whole communication is via HTTP(S) and the remote applications appear transparent to the user as if they are running locally. Multiple applications run in the same session to ensure that there is no need for additional licenses per user. Terminal Services Easy Print does not require administrators to install any printer drivers on the server, but guarantees successful client printer redirection and availability of all printer UI and properties for use in remote sessions. Terminal Services sessions are created in parallel, instead of a serial operation - the new session model can initiate at least four sessions in parallel, or more if a server has more than four processors.
http://en.wikipedia.org/wiki/Windows_Server_2008
http://www.microsoft.com/windowsserver2008/default.mspx
Terminal Services in Windows Server 2008
http://www.microsoft.com/windowsserver2008/terminal-services/default.mspx
http://www.msterminalservices.org/articles/Terminal-Services-Remote-Programs-Part1.html
Terminal Services - commands
http://technet2.microsoft.com/windowsserver/en/library/f47ce263-f72e-469d-bf14-6605b7f4cce51033.mspx?mfr=true
Windows 2003 Terminal Services (Part 2)
http://www.windowsnetworking.com/articles_tutorials/Windows_2003_Terminal_Services_Part2.html
Windows Terminal Services & SBC Resource Site: Articles & Tutorials
http://www.msterminalservices.org/
Leave a Reply
You must be logged in to post a comment.