<div>
Use <b>Alt+Ins</b><br />
You won't get the graphical selection view in the middle of the screen, but the applications will be put into the foreground one after the other.
</div>


<div>
You could use the following:<br>Alt + PageUp<br>or<br>Alt + PageDown<br><br>This will cycle through the open applications.<br>Keep holding the Alt after pressing PageUp or PageDown will keep the window with applications open which you can select with the mouse.<br><br>
</div>


arnold

<div>
Are you in full screen mode?
</div>


<div>
In full screen mode. Using Windows server 2012 RDS publishing remote desktop. Also Local Resources&gt;Keyboard settings options. No Luck.<br>&nbsp;
</div>


<div>
The functionality is described here.<br><a href="https://docs.microsoft.com/en-us/windows/win32/termserv/terminal-services-shortcut-keys" rel="ugc">https://docs.microsoft.com/en-us/windows/win32/termserv/terminal-services-shortcut-keys</a><br>They also mention the ALT+TAB mapping to ALT+PAGE UP and Local Resources, Apply Windows key combinations<br><br>Does the Windows key work, and if yes, on which computer is the menu opened ?<br>Is this a direct RDP session from a physical computer or do you maybe work with a nested RDP session ?<br>You could try "Shift + Alt + PageUp"<br><br>
</div>


<div>
Zalazar's comment does it not work for you?<br>Do you use another keyboard layout , language that may alter the key combinations.
</div>


<div>
not working. Tried all ALT+Pageup or ALT+Pagedown or Shift+Alt+Pageup or ALT+Ins.<br>I am connecting to the jump box via rd web and the taking remote of the machine. Pressing windows key , opening in local pc.
</div>


<div>
The same is working from the Microsoft Remote desktop App from app store. But that cannot be used in RDS rdweb.&nbsp;
</div>


<div>
You are double passing which seems to be your issue<br>Workstation =&gt; jump box =&gt; RDP final session<br>=&gt; RDP sessions?<br><br>Look at VPN as an access mechanism <br>So you have ==&gt; RDP final session with ==&gt; RDP via VPN
</div>


<div>
it is Workstation==&gt;vpn==&gt;jumb box==&gt; RDP final session
</div>


<div>
If you would set "Local Resources", "Apply Windows key combinations" to "On the remote computer"<br>Is the Windows key then still opening the menu on the local computer ?<br><br>
</div>


<div>
Are you using RDP to jumpbox.<br>What do you need with alt tab, where looking at the task bar will not do?<br><br>
</div>


<div>
Can you try to make sure that the .RDP file that will be run from your "RD Web Access" session to access the remote server, contains the following.<br><pre><code class="code-1 nolinks" id="code-20-43083257-1"><span>keyboardhook:i:1</span>
</code></pre>This will set "Apply Windows key combinations" to "On the remote computer"<br><br>
</div>


<div>
Are you using RDP to jumpbox.<br>Yes<br>What do you need with alt tab,<br>Toggling between applications<br>&nbsp;where looking at the task bar will not do? <br>I dont understand your question
</div>


<div>
@Zalazar<br>Not available. It has only below.<br>redirectclipboard:i:1<br>redirectprinters:i:1<br>redirectcomports:i:0<br>redirectsmartcards:i:1<br>devicestoredirect:s:*<br>drivestoredirect:s:*<br>redirectdrives:i:1<br>session bpp:i:32<br>prompt for credentials on client:i:1<br>span monitors:i:1<br>use multimon:i:1<br>remoteapplicationmode:i:1<br>server port:i:3389<br>allow font smoothing:i:1<br>promptcredentialonce:i:0<br>videoplaybackmode:i:1<br>audiocapturemode:i:1<br>gatewayusagemethod:i:0<br>gatewayprofileusagemethod:i:1<br>gatewaycredentialssource:i:0<br>full address:s:<br>alternate shell:s:||mstsc<br>remoteapplicationprogram:s:||mstsc<br>remoteapplicationname:s:Remote Desktop Connection<br>remoteapplicationcmdline:s:<br>workspace id:<br>use redirection server name:i:1<br>loadbalanceinfo:s:tsv://MS Terminal Services Plugin.<br>alternate full address:<br>signscope:s:Full Address,Alternate Full Address,Use Redirection Server Name,Server Port,GatewayUsageMethod,GatewayProfileUsageMethod,GatewayCredentialsSource,PromptCredentialOnce,Alternate Shell,RemoteApplicationProgram,RemoteApplicationMode,RemoteApplicationName,RemoteApplicationCmdLine,RedirectDrives,RedirectPrinters,RedirectCOMPorts,RedirectSmartCards,RedirectClipboard,DevicesToRedirect,DrivesToRedirect,LoadBalanceInfo<br>signature:s:
</div>


<div>
Usually a jumpbox is an exposed directly to the outside using MFA to gain access.<br>If you have a VPn connection, why are you not going directly to the end system?<br>Not sure you can &nbsp;map different key combos to pass through....
</div>


<div>
To avoid , direct RDP to the end system. I have the jump box. It is not advisable to go directly.<br><br>
</div>


<div>
Not advisable, By whom?<br>The not advisable commonly is exposing multiple systems to the outside.<br>1) is the RDP accessible to the VPN Conncted system?<br>Do not attach local drives to the RDP session if that is the concern.
</div>


<div>
by me.<br>Jumpbox is on a DMZ. <br>Do you have the solution or not?<br><br>
</div>


<div>
Thanks.<br>If you would open a registry editor (regedit) and then go to:<br>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms]<br>Then browse to your Collection name, Applications or RemoteDesktops and try to find the icon you click.<br>There should be a registry entry named: RDPFileContents<br>This contains all the RDP options.<br>Can you copy the line and paste it to a notepad and verify that it contains the same options as posted.<br><strong>Important: You can not edit the line directly as it contains new line characters and binary data so it's not possible to simply add the proposed parameter at the end of the line.</strong><br><br>In addition: The RDP file is also signed so editing is more difficult.<strong><br></strong>And I can't find the setting in the "Session Collection" parameters where you normally define these RDP parameters.<br><br>
</div>


<div>
Does your VPN policy restrict your access to the DMZed system only?<br>You are looking to remap a key-combos on a keyboard connected to the workstation, passed to the jump box and then translated to the end system as alt-page up/down.<br><br>Consider the following question, does the office manager check in with the sevurity guard at the front entrance after entering through the employee entrance and before going to their office?<br><br><br>
</div>


<div>
It's possible to specify custom properties on the Session Collection.<br><a href="https://docs.microsoft.com/en-us/powershell/module/remotedesktop/set-rdsessioncollectionconfiguration?view=win10-ps" rel="ugc">https://docs.microsoft.com/en-us/powershell/module/remotedesktop/set-rdsessioncollectionconfiguration?view=win10-ps</a><br>-CustomRdpProperty<br>Specifies Remote Desktop Protocol (RDP) settings to include in the .rdp files for all Windows Server 2012 RemoteApp programs and remote desktops published in this collection.<br><br><pre><code class="code-1 nolinks" id="code-20-43083291-1"><span>Set-RDSessionCollectionConfiguration –CollectionName QuickSessionCollection -CustomRdpProperty "keyboardhook:i:1"</span>
</code></pre><br>Before setting it you could first check if the parameter already contains a value via:<br><pre><code class="code-1 nolinks" id="code-20-43083291-2"><span>Get-RDSessionCollectionConfiguration -CollectionName QuickSessionCollection | Select -ExpandProperty CustomRdpProperty</span>
</code></pre><br>
</div>


<div>
@zalazar<br>Is keyboardhook:i:1 alone sufficient for lt+tab? I have added this via poweshell as you mentioned. But still no luck.
</div>


<div>
One good news is Ithat I am able to do ALT+TAB by connecting to Jump box using the below RDP file and from there remote to end system. ALT+TAB is working fine.But if I go with RDS rdweb remote only it is not working.<br><br>screen mode id:i:2<br>use multimon:i:0<br>desktopwidth:i:1366<br>desktopheight:i:768<br>session bpp:i:32<br>winposstr:s:0,1,12,45,1366,728<br>compression:i:1<br>keyboardhook:i:1<br>audiocapturemode:i:0<br>videoplaybackmode:i:1<br>connection type:i:7<br>networkautodetect:i:1<br>bandwidthautodetect:i:1<br>displayconnectionbar:i:1<br>enableworkspacereconnect:i:0<br>disable wallpaper:i:0<br>allow font smoothing:i:0<br>allow desktop composition:i:0<br>disable full window drag:i:1<br>disable menu anims:i:1<br>disable themes:i:0<br>disable cursor setting:i:0<br>bitmapcachepersistenable:i:1<br>full address:s:...<br>audiomode:i:0<br>redirectprinters:i:1<br>redirectcomports:i:0<br>redirectsmartcards:i:1<br>redirectclipboard:i:1<br>redirectposdevices:i:0<br>autoreconnection enabled:i:1<br>authentication level:i:2<br>prompt for credentials:i:0<br>negotiate security layer:i:1<br>remoteapplicationmode:i:0<br>alternate shell:s:<br>shell working directory:s:<br>gatewayhostname:s:<br>gatewayusagemethod:i:4<br>gatewaycredentialssource:i:4<br>gatewayprofileusagemethod:i:0<br>promptcredentialonce:i:0<br>gatewaybrokeringtype:i:0<br>use redirection server name:i:0<br>rdgiskdcproxy:i:0<br>kdcproxyname:s:<br>drivestoredirect:s:<br><br><br>
</div>


<div>
Registry content<br><br>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\Server\Applications\mstsc]<br>"Name"="Remote Desktop Connection"<br>"SecurityDescriptor"=""<br>"Path"="C:\\Windows\\system32\\mstsc.exe"<br>"VPath"="%SYSTEMDRIVE%\\Windows\\system32\\mstsc.exe"<br>"CommandLineSetting"=dword:00000000<br>"RequiredCommandLine"=""<br>"ShowInPortal"=dword:00000001<br>"Folders"=hex(7):2f,00,00,00,00,00<br>"RDPFileContents"="redirectclipboard:i:0<br><br>redirectprinters:i:1<br><br>redirectcomports:i:0<br><br>redirectsmartcards:i:1<br><br>devicestoredirect:s:*<br><br>drivestoredirect:s:<br><br>session bpp:i:32<br><br>prompt for credentials on client:i:1<br><br>span monitors:i:1<br><br>use multimon:i:1<br><br>remoteapplicationmode:i:1<br><br>server port:i:3389<br><br>allow font smoothing:i:1<br><br>promptcredentialonce:i:0<br><br>videoplaybackmode:i:1<br><br>audiocapturemode:i:1<br><br>gatewayusagemethod:i:0<br><br>gatewayprofileusagemethod:i:1<br><br>gatewaycredentialssource:i:0<br><br>full address:s:<br><br>alternate shell:s:||mstsc<br><br>remoteapplicationprogram:s:||mstsc<br><br>remoteapplicationname:s:Remote Desktop Connection<br><br>remoteapplicationcmdline:s:<br><br>screen mode id:i:2<br><br>workspace id:s:....<br><br>use redirection server name:i:1<br><br>loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1......<br><br>alternate full address:s:...<br><br>signscope:s:Full Address,Alternate Full Address,Use Redirection Server Name,Server Port,GatewayUsageMethod,GatewayProfileUsageMethod,GatewayCredentialsSource,PromptCredentialOnce,Alternate Shell,RemoteApplicationProgram,RemoteApplicationMode,RemoteApplicationName,RemoteApplicationCmdLine,RedirectPrinters,RedirectCOMPorts,RedirectSmartCards,RedirectClipboard,DevicesToRedirect,DrivesToRedirect,LoadBalanceInfo<br><br>signature:s:AQABAAEAAAD4EAAAMIIQ9AYJKoZIhvcNAQcCoIIQ5TCCEOECAQExCzAJBgUrDgMC &nbsp;0dHA6Ly9jZXJ0cy5n
</div>


<div>
What you are trying to achieve is<br>Key-combo on workstation<br>Through RDP session<br>The key-combo has to be ignored, and passed on<br>Through second RDP session<br>Interpreted as alt-tab<br>The issue is whether you when you establish the first RDP you declare/define a session key map translation<br>Establish the second RDP and do the same to handle the keystrokes being passed from the original key board.<br>If you make registry changes, you will run into issues when there are internal direct access to the RDP.
</div>


<div>
I dont understand.<br><br>Establish the second RDP and do the same to handle the keystrokes being passed from the original key board.
</div>


<div>
Is it possible to use the same commands in second RDP with session key mappping?
</div>


<div>
Keystrokes are received and interpreted on a session by session basis.<br>The RDP session to the jumpbox is effectively have to pass the keystrokes from the keyboard on the workstation amd not interpret it,<br>I.e. If you establish an RDP session to the jumpbox.<br>You the. Establish an RDP session from tHe jumpbox To the end system.<br>When you hit ctrl-alt-end is seen by the jumpbox and acted accordingly by presenting the options on the jumpbox RDP <br>You are trying to pass a key-combo from the workstation all the way through the two RDP sessions and have the last system act on that key combo.<br><br>There is a powershell cmdlet taht deals with setting session parameters.<br><br>My prior statement dealing with the existence of the VPN connection which effectively places the workstation wihtin the most secure &nbsp;limit.<br>Having passed the security barrier, going through seemingly unnecessary step of going through a jump box to then RDP again to the final destination.<br><br>The same way you are trying to translate the keystrokes through RDP session from the workstation through the jumpbox to the end system, you can translate and attach the local harddrive and resources through the RDP session to the jumpbox to the end system via that RDP session.<br><br>Registry changes are commonly permanent..
</div>


<div>
What is the issue with direct access once the vpn is setup?<br><br>Is the jumbos runs as RDS? Does the end system res? Or remote administration ?
</div>


<div>
An approach you refuse to use is not the same as no resolution. You are requiring a specific option.<br>and the only way to achieve what you want is to handle keystroke remaping through each RDP session.<br><br><a href="https://www.nextofwindows.com/how-to-use-the-same-win-key-combinations-on-remote-desktop" rel="ugc">https://www.nextofwindows.com/how-to-use-the-same-win-key-combinations-on-remote-desktop</a><br><br>note you need to try to pass this from workstaion to jump box and then from the jumpbox to the end system<br><br><br>
</div>


<div>
@Arnold. Have some wide thinking when you look at a problem.<br>I already conveyed that I am able to achieve Alt+Tab successfully via RDP to Jumpb box and then the end machine. Only when I go via RDWEB , the problem arises. Now tell me the reason.&nbsp;
</div>


<div>
Note the last link to see whether you can use the options displayed where you would setup the respective connection, potentially when full screen mode is used, that the keystrokes from the workstations will pass through the intermediate RDP session, to the end session.<br><br>I am uncertain I understand the circumstances that your setup is making you so rigid. <br><br>A jumpbox is a system with an MFA that is Internet facing. Once accessed provides access to other internal systems.<br><br>A VPN with or without an X-user and an MFA is providing access to the Office LAN.<br><br>You are insisting even though you are already on the LAN to use the JUMPBOX which is situated in a more restrictive zone that the system on which your keyboard/screen interface is.<br><br>I can not understand the scenario under which conditions you are envisioning a one to one access.<br>Anything you can attach directly, you can pass through the jumpbox <br>A GPO can restrict what resources can be attached to the individual server on LAN as applied to the JUMPBOX if any. I.e. You are currently applying a GPO to the JUMOBOX to deny users attachment of local DRIVES, printers, etc.<br>This same restriction can be imposed on all servers.<br><br>Are you familiar with ssh tunnels?<br><br>what it seems from here.<br>1) you have a highly secured environment<br>2) you have a secure number which you can use to call for the outside and then connect, make other choices to contact different individuals.<br>3) the phone system was upgraded such that it made it possible for your phine to register with the phine system after an establishment of a VPN connection.<br>4) even with your phone being directly connected to the phone system you are still insisting on calling the external number through which you dial other people.<br><br>This is what I do not understand.
</div>


<div>
There is no need of a VPN to have access to entire LAN. It can be restricted only to the jump box. There is no rule to have a jump box to face the internet directly. A jump box can be accessed via a secure VPN. You are keep on deviating from my question.&nbsp;
</div>


<div>
I am trying to get a picture of the environment.<br><br>In your setup, VPN required to access a jumpbox from which other things are accessiblle.<br><br>Over the VPN are you connecting to the jump box in full screen mode, or used the option as illustrated in the link while not connecting the RDP session in full screen mode?<br>The RDP session from the jumpbox to the end system, which mode of the options are you using, full screen mode to try and see whether that will create a passthrough of the keystrokes from the workstation to the final destination system?<br><br>
</div>


<div>
Does the jumpbox agave ssh server options?<br>Ssh tunnel through the jumpbox to the final destination?
</div>


Abdul Raheem

<div>
@Zalazar<br><br>You are great man. Your first method works. But I could use only ALT+Pageup or Pagedown.<br>Any chance of using ALT_TAB?
</div>


<div>
Thanks and great to hear it's working !<br />
I could not find a way to use ALT-TAB unfortunately.<br />
Only the alternative key combinations work.<br />
<br />
There is a possibility but you would need an external RDP program named Royal TS for this.<br />
By saving and importing the RDP file and setting the option &quot;Advanced |Input |Windows Keys Passthrough: Enabled&quot; for the connection.<br />
Then ALT-TAB within the RDP session works fine.
</div>


<div>
Thanks Zalazar. Its a great help from you. Please suggest any open source of RDS if you aware of.
</div>


<div>
mRemoteNG is open source and has a possiblity to set<br />
Redirect |Key Combinations: Yes<br />
but the software is not capable to run the RDP session via the published application.<br />
I couldn't find any other open source or free RDP program which is capable to run the session via the published application and passthrough ALT-TAB in combination with this setup.
</div>


<div>
<div class="content wysiwyg-content">
Alt+Tab not working in windows Remote desktop. How to resolve it?
</div>
</div>


Alt+Tab not working in windows Remote desktop. How to resolve it?

Remote Desktop Alt+Tab

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.