The Options dialog for a program updates a particular Registry key see Using the Options dialog below. Parameters specified using policy override parameters specified at the command line, which in turn override parameters specified manually in the Registry. The following table lists the Registry keys to create or edit for each program, and the order in which parameters are applied. Under Windows, if you have permission to edit the Windows Registry, you can specify parameters as values for particular Registry keys. Right-click on the RDP-Tcp connection and go to Properties.Populating the Windows Registry with parameters In the right-side pane, you’ll see below. Expand Terminal Services Configuration and double-click on the Connections folder to open it. You should now see the Terminal Services Configuration listed. Click the ‘Add’ button and then click ‘Close’. Scroll down to find ‘Terminal Services Configuration’. *You only need to do this if you are going to want to interact with console sessions of a different user name logged into the machine than your own, or what user name you’re logging into with Remote Desktop.* + For Windows Server 2003, you can only interact with your own sessions by default, like above, but you can change this behavior. If you continue this user’s Windows Session will end and any un-saved data will be lost. The user is currently logged on to this computer. If you try logging in as another user, it will give you the following error message: + For Windows XP, you can only interact with your own sessions. Video mirror drivers? TCP ports conflicting? + An odd little quirk I’ve noticed is that you can’t have both an interactive session of Remote Desktop running and a VNC session running. + Whether you’re connecting to XP or Server 2003, the machine you’re connecting to will lock and hide what you’re doing from anyone that might be watching the local machine. Or change the target field in a shortcut to be mstsc.exe /console Remote Desktop shortcut properties Or change the target field in a shortcut to be mstsc.exe /adminįrom Windows Server 2003: At Start, Run… enter mstsc /console The switch depends on what operating system you are connecting from, and is independent of which operating system you’re connecting to.įrom Windows XP Pro: At Start, Run… enter: mstsc /admin Real solution: Using Windows Remote Desktop there are switches that allow you to interact with the console session rather than starting a new one. This requires a VNC viewer installed on all the machines I might be connecting from and another process on my machine to secure and be running at all times. Possible solution: Install a VNC server on the machine and use that to connect. To open a new window, you must first close the existing Firefox process, or restart your system.” (or substitute ‘Thunderbird’ in for ‘Firefox’ in that error message). (If it were just a saved file, I could get to it through a file share.) Further more, if I have Firefox and Thunderbird open in my console session, I can’t start them up remotely because of the error: “Firefox is already running, but is not responding. If I use Remote Desktop, I just get another session on my Windows Server 2003 machine and still don’t get access to what I need. Problem: I am logged into my machine in my office and have something open I want to get to from another computer in the building, on the network, or VPN’d in from off the network. If you want to use Remote Desktop to control a session already logged in at the console (physically at and logged into the machine) instead of starting a new session (Windows Server 2003 default) or kicking off the current user (Windows XP default), use the following commands to achieve this. This is for Windows XP Professional and Windows Server 2003.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |