This is Windows 8.1 only, not 7, not 10. It is not known whether 8.0 is affected.
The current known operative case is Citrix-hosted applications, in a dual-monitor situation. If you see a malfunction, go to Control Panel, All Control Panel Items, Display. If “Let me choose one scaling level for all my displays” is unchecked, check it. It will require logoff/logon. And the problem will be fixed.
Here’s a bash script! Works very nicely. Once run on one side and specifying a destination, one does not need a password to open that SSH link in the future.
echo "setup-autossh by Jonathan E. Brickman, email@example.com"
if [ $# = 0 ]; then
read -p "Please enter the SSH destination in the format user@host : " sshdest
elif [ $# = 1 ]; then
echo "Usage: setup-autossh [user@destination]"
if [ ! -f ~/.ssh/id_rsa ]; then
echo "Creating RSA key for authorization..."
ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa
echo "Copying authorized RSA key to $sshdest ..."
remotecmd="cat > authorized_keys ; mkdir -p .ssh ; cat authorized_keys >> .ssh/authorized_keys ; rm authorized_keys"
cat ~/.ssh/id_rsa.pub | ssh $sshdest $remotecmd
netsh firewall set service remotedesktop enable
netsh firewall set service remoteadmin enable
reg ADD "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0
netsh firewall Set service REMOTEDESKTOP ENABLE
netsh firewall set service REMOTEAdmin ENABLE
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0
Terminal servers require special user modes, for software additions to work correctly, and sometimes, to happen at all.
Before installing anything on a terminal server, do this:
change user /install
And after the installation is complete, do this:
change user /execute
It appears that FreeNX has begotten X2Go:
Use the following as a script wrapper:
ssh -Y -C -c blowfish $1
It turns compression on, and also sets up Blowfish encryption which is much more responsive than the default.
Something new, looks like it might be excellent:
Sometimes the default configuration for Remote Web Workplace does not set up use of the RDP gateway by default. The following documentation:
discusses a group policy setting which fixes this nicely.