Too bad the Citrix Receiver remaps the keyboard shortcuts in a way that keyboards without a numeric keypad is a pain.
First of all, it was a bit tough to find the shortcuts, and I have not found a way to modify them.
Here is what I did find:
Posted by jpluimers on 2015/09/07
Too bad the Citrix Receiver remaps the keyboard shortcuts in a way that keyboards without a numeric keypad is a pain.
First of all, it was a bit tough to find the shortcuts, and I have not found a way to modify them.
Here is what I did find:
Posted in Keyboards and Keyboard Shortcuts, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | Leave a Comment »
Posted by jpluimers on 2015/09/04
Posted in Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | Leave a Comment »
Posted by jpluimers on 2014/02/24
Before I forget:
Got there because I lost the “Connection Bar” of MSTSC, and this solved it:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
"PinConnectionBar" = REG_DWORD:1Will make the connection bar pinned.
–jeroen
Posted in Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | Leave a Comment »
Posted by jpluimers on 2014/02/10
Every now and then my Mac RDP program will suddenly turn on the CAPS LOCK on the connected Windows terminal.
It happens on different OS X versions, and different Windows versions. I haven’t figured out the steps to reproduce yet. I will amend this post when I have (:
I also have it occasionally fail when I RDP from a physical Windows system to another Windows system, but far less than from Mac OS X.
You work around it using the On Screen Keyboard tool in Windows like Josh Adams explains:
- launch the On-screen Keyboard application (generally this can be done by choosing Start ==> All Programs ==> Accessories ==> Accessibility ==> On-screen Keyboard; as noted by DrFooMod2 in a comment below, you can also bring up the On-screen Keyboard by typing “osk” without the quotes in the Windows Run… box) and
- toggle Caps Lock by clicking on the virtual “lock” button in the application.
- The On-screen Keyboard application shows–and can change–the state of Caps Lock
The easiest way to start the On Screen Keyboard is to create a shortcut to this:
%windir%\system32\osk.exe
–jeroen
via: Josh Adams’s Blog: Fixing Inverted Caps Lock on VMWare Fusion, Parallels, or Remote Desktop.
Posted in Apple, Keyboards and Keyboard Shortcuts, Mac, Mac OS X / OS X / MacOS, Mac OS X 10.4 Tiger, Mac OS X 10.5 Leopard, Mac OS X 10.6 Snow Leopard, Mac OS X 10.7 Lion, MacBook, MacBook-Air, MacBook-Pro, OS X 10.8 Mountain Lion, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | 1 Comment »
Posted by jpluimers on 2014/01/24
The F keys on a Mac still perform the Mac OS X specific function, even in a full screen RDP session, but you can get their Windows functionality back with ease as MacRumors user blindzombie shows:
I got it to work with fn – command – F9
or just command – F9 if you set your keyboard preferences to use F1, F2, etc as standard function key
–jeroen
via function keys (F1-F12) in remote desktop – MacRumors Forums.
Posted in Apple, Keyboards and Keyboard Shortcuts, Mac, Mac OS X / OS X / MacOS, Mac OS X 10.4 Tiger, Mac OS X 10.5 Leopard, Mac OS X 10.6 Snow Leopard, Mac OS X 10.7 Lion, MacBook, MacBook-Air, OS X 10.8 Mountain Lion, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | Leave a Comment »
Posted by jpluimers on 2014/01/03
All software and protocols has weak points, so it is good to know about the weak points on MSTSC and the RDP protocol: Hacking Microsoft Remote Desktop Services for Fun and Profit.
–jeroen
Posted in Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | Leave a Comment »
Posted by jpluimers on 2014/01/02
Very interesting, especially since rdesktop.org works with Windows Server 2008 R2 and Windows 7 as well, and is stable on x64.
It provides three tools: rdesktop, rdpproxy and seamlessrdp.
Researching this, I also found about TSWindowClipper which allows you to seamlessly integrates remote apps on your client by integrating a DLL inside the MSTSC software using the official virtual channels.
Back to rdesktop: I really wish the documentation was better, but it contains some very interesting source code.
rdesktop is an open source client for Windows Remote Desktop Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user’s Windows desktop. rdesktop is known to work with Windows versions such as NT 4 Terminal Server, 2000, XP, 2003, 2003 R2, Vista, 2008, 7, and 2008 R2.
rdesktop currently runs on most UNIX based platforms with the X Window System, and other ports should be fairly straightforward.
rdesktop is released under the GNU Public Licence (GPL), version 3. Please send feedback, bug reports and patches to the appropriate mailing list. Patches can also be submitted to the SF patch tracker.
rdesktop is a project. See the Sourceforge rdesktop project info and the Wiki for more information.
Status
The latest stable version of rdesktop is 1.7.1 (edit: this was at the time of writing, for the current latest, check here). This versions solves major issues with 64bit version and smartcard support among a few minor fixes.
–jeroen
Posted in *nix, Development, Linux, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Software Development, SuSE Linux, Windows, Windows 7, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2013/10/07
Interesting Q/A thread because it mentions quite a few alternatives next to the well known TeamViewer, RDP, VNC combo.
--jeroen
via: performance – How is TeamViewer so fast? – Stack Overflow.
Posted in Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | Leave a Comment »
Posted by jpluimers on 2013/05/24
Enable Remote Desktop Connection on Vista Home Premium | frans goes blog.
Great as it has steps both for Windows Vista SP1 and SP2, and steps for Vista RTM.
–jeroen
Posted in Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows, Windows Vista | Leave a Comment »
Posted by jpluimers on 2013/03/18
Thanks to Joe Klemencic, TSListUsers is a great little console tool that shows you the currently logged on users and which session they use:
List Terminal Services Users
TSListUsers is a command line utility to list both the currently connected and disconnected users, hostname, IP address and RDP session number on either the local or a remote Windows Terminal Server/RDP Server
To list the users, you need to have the following abilities:
- NetBios access to the server
- Permissions allowing you to Query RDP session information (if you can log into the TS, you should have this by default)
- Terminal Services/RDP should be running on the target host
Usage:
TSListUsers.exe /? to get the Help text
TSListUsers.exe to query a target Terminal Server
TSListUsers.exe with no paramters to query the local hostYou can download TSListUsers from here.
Example output of remote session:
C:\Windows>TSListUsers.exe Active Connections: Username, HostName(IP), SessID, RDP-Port ---------------------------------------- jeroenp, W701UJPL (192.168.71.34), 2, RDP-Tcp#92 Disconnected Connections: Username, HostName, SessID --------------------------
Example output of local session:
C:\Windows>TSListUsers.exe Active Connections: Username, HostName(IP), SessID, RDP-Port ---------------------------------------- jeroenp, 1, Console Disconnected Connections: Username, HostName, SessID --------------------------
–jeroen
Posted in Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows, Windows 7, Windows 8, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »