![]() This switch was new to me and i’ve found a good blog about it Ĭaspan. I advise you to always double check if you are on the right server: : cmd –> hostname. But if you use mstsc /admin, it will ignore all the loadbalancing stuff and get you to that server you want to administer. This can be very annoying and might even result in problems if you don’t check the server name. But you probably have very good reasons to go to a specific server. The problem starts when you as an admin want to connect to a specific server, you still will be redirected to the best suitable server in the silo to handle the next logon (probably the least busy server). The RD Connection Broker orchestrates this. If users connect to a Silo (a collection of RDSH servers with a Connection Broker in place), they will get redirected to a RDSH server that is the most appropriate. This switch ignores the load balancing that might be in place. I dont have any experience with compiling from source but i could give it a try.Most of you know the command line options that exist within MSTSC.exe. I connect against 3 windows machines one with windows 10, windows server 2016 and server 2018. I just cant figure out whats the "correct" order the monitors have to be in.Īre you suggesting that its a "guest" issue. I forgot to mention that i have had it to work as expected in the past but with a reboot later it stops working with the only thing that has changed is monitor numbering when you check with xrandr. No gaps, you notice right away with xrandr if its not aligned. Right now it works with 2 monitors, like 0, 2 or 1, 3 but the other variants results in black screens and maybe 1 monitor that shows the rdp session. ![]() Yes, if i only use multimon all the monitors are being used. Check for gaps between monitor layouts, windows requires the monitors to be next to each other without any pixel left empty in between.Log the layout sent in gcc_write_client_data_blocks and disp_send_display_control_monitor_layout_pdu.If you are able to compile a test version: Could you answer the follwing:įirst, with just /multimon does the session use all monitors successfully? Hard to tell, it is highly dependent on your remote os. I have tried to move the DP cables around the back of the graphics card with limited success, sometimes it will make it better and some times it will make selections that used to work not work anymore. If i select monitor 1, 3 and 5 it can show the remote session on monitor 3,5 but all the other monitors is black. It may work and monitor 0 and 2 will display the remote session.īut if i run /monitors:1,3 it could show the remote session on 1 and 3 but monitor 0 and 2 will be black. Where x is only one monitor i always run fullscreen on the selected monitor.īut if i run xfreerdp /multimon /monitors:0,2 Click Use all monitors for the remote session in the client (mstsc.exe) window. I am trying to run RDP on a selected number of monitors but i cant get a grip on what order RDP wants the monitors. Your current method is correct, including: a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |