![]() ![]() Mac is what it is at the moment unless I buy the HOB client (which I likely won't get approval for from management - not to mention it will look really bad when I ask for more money to do something we already have working in the environment with the solution we're replacing ). ![]() so I'd really like to get this to work at least on Windows. Not sure if that's the root of my problems or not - and I'm not really interested in upgrading to. Our SE says that Mac will have an official RDP launch client (non-Java) and the mstsc launcher has some updates in version 13 that's coming out soon. I hadn't configured it, one of my colleagues did and I may have been mistaking what I saw (he may have been connecting directly to a windows box, not through the F5).ĭoes he just not feel like helping people today? If that was my answer to one of my customers I'd be getting some heat from my boss. I only saw it work in a lab environment when I was testing against a previous bug with the active x control RDP module. I don't recall off hand if it was using an access portal or the client itself. I am certain I have seen the mstsc monitor span successful with the *span monitors:i:1*. When asking about RDP spanning with the native (Windows) client: then from the other computer, run command prompt CMD, type in this: mstsc multimon. This has been brought up as an RFE on multiple occasions and is a limitation of the underlying Java RDP implementation that PD has said they won't change. It is possible to configure the MSTSC.exe client to support span however if you absolutely need it. The short answer is no, Span support isn't available for the Java RDP client. I opened a support case with F5 - but the engineer was not entirely helpful. Neither of these parameters appear to work: You may wish to use DSC or a GPP to ensure they remain set how you like them.Has anybody been able to get monitor spanning to work with an RDP access resource? Note that much like the ShowInPortal key if you make amendments to your session collection via the GUI these keys can get reset back to their default. The REG_SZ key is very long but a little way in you will find the following:Īnd then you will no longer get sessions spanning multiple screens. To disable this edit the RDPFileContents key which can be found in the same node as the ShowInPortal key which you already edited. I would to configure it directly in the RDP file. Is there an option in the GUI settings dialog of the RDP file to have the span effect I dont always want to type the command 7 run a batch script in order to fill the screen. However, even if you have set relevant GPO on your session hosts to not allow multi-monitor you will find that it still spans two displays, which is particularly annoying if you need to view content on both your local machine and the remote machine. It is possible to fill the screen with an RDP session using the following command: mstsc myconnection.rdp /span. The full remote desktop session will now be published to the session collection. BeyondTrust supports remote desktops configured to use multiple. One can also display a full RDP desktop session by changing the registry value ShowInPortal to a value of 1: How to use dual monitors with remote desktop. I have attempted to use the multimon, but I get the display of both monitors as 1 view. mstsc /v:computername /shadow:1 /control /noconsentprompt /f. There are a few settings associated with the Remote Desktop Multimon feature. I have a need to rdp to a machine and only use the 2nd monitor. By default RDWeb in Windows Server 2012 R2 only displays published RemoteApp programs. I can also use mstsc /multimon as a command line to use multiple monitors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |