Remote Desktop Connection uses display IDs, not the local Windows “main display” setting, when selecting monitors for a remote session. In the supported RDP properties, the selected displays are a comma-separated list of machine-specific display IDs, and the first ID in that list becomes the primary display in the remote session.
To control which monitor is primary in the remote session:
- Find the local display IDs by running:
mstsc.exe /l - Note the IDs for the monitors to use.
- Configure the RDP session to use multiple monitors:
use multimon:i:1 - Specify the monitors in the order wanted:
selectedmonitors:s:<primaryID>,<otherID>,<otherID>
Important details:
- The first ID in
selectedmonitorsis set as the primary display in the remote session. -
selectedmonitorsrequiresuse multimonset to1. - The selected displays must be contiguous.
- By default, if
selectedmonitorsisn’t set, all displays are used. - If exiting full screen is part of the workflow,
singlemoninwindowedmode:i:1makes a multi-display remote session switch to a single display when exiting full screen. The default is0, which retains all displays when exiting full screen. -
smart sizing:i:1scales the remote session content to fit the window size when resized.
This means the practical fix is to save or edit the .rdp file so the external monitor intended as the remote primary is listed first in selectedmonitors, instead of relying on the laptop panel being display 1 in local Windows.
References: