![]() ![]() Server: xxx Event Xml: 168 0 4 4 11 0x4000000000000000 9433 Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational 1440 1920 0 xxx Log Name: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational Source: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS Date: 7:42:36 PM Event ID: 168 Task Category: RemoteFX module Level: Information Keywords: User: NETWORK SERVICE Computer: xxx Description: The resolution requested by the client: Monitor 1: (1920, 1080), origin: (0, 240). Log Name: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational Source: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS Date: 7:42:36 PM Event ID: 168 Task Category: RemoteFX module Level: Information Keywords: User: NETWORK SERVICE Computer: xxx Description: The resolution requested by the client: Monitor 0: (2560, 1440), origin: (1920, 0). I'm not sure what does "origin" refers too though. The event log on the Windows VMs shows that the host session requested two virtual monitors and selected their sizes correctly based on the physical available monitors. Session is showing two VM monitors, but the restore was done on a single host monitor, both the VM monitors are cramed into a single host monitor. Windows Server 2019: session mode was enabled by default, I have installed all updates on the VM and connected to it in full screen mode, minimized the session and restored it again, and this behaved exactly like Windows 10 VM, where the.Ubuntu 19.4: after installing and configuring XRDP, enhanced session mode was enabled, I was able to login to the VM in full screen mode, minimize the session and restore it again in full screen, no problems here. ![]() I have installed 2 additional VMs to test different OSes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |