P2219H, dual, work when connecting remotely?

@MNVOL  adding on to my reply above, I forgot to address your HDMI splitter question.  An HDMI splitter will only ever mirror a single source signal to multiple attached displays, because HDMI does not support running multiple independent displays from a single source port.  Only DisplayPort can do that (and USB-C, which uses DisplayPort signaling for video output, assuming the USB-C port in question supports video output at all, which not all do.)  So if you want to have a multi-display Remote Desktop session, first you need multiple displays working properly on the system you're actually connecting from.  Looking at the specs of the Inspiron 3671, it appears the only built-in video outputs are 1x VGA and 1x HDMI -- unless you added a graphics card that would have other inputs.  But assuming you didn't do that, then if you go back to connecting one display via HDMI and one via VGA, you should be able to get back to having simultaneous independent displays, i.e. Extend mode.  At that point, it's just a matter of setting up the Remote Desktop connection to use both of them, which it doesn't by default.

@jphughan(Let's try this again.  I replied to your original post, but when I clicked "Post" I got an error and my post disappeared.)

Thank you!   I was able to get Remote Desktop Connection to work across two monitors following the instructions on your original post.  My wife and I have tried playing around with GoToMyPC and so far have been unsuccessful.  The only thing we managed to do was pop her original GoToMyPC screen right in the middle across two monitors.  That won't work.  Hopefully a tech support person from her company will be able to give some suggestions.

As an FYI, the workstation that we're remoting from is set up in it's original configuration of one monitor with an HDMI cable and one monitor with a VGA cable. 

(For anyone else reading this thread who's familiar with GoToMyPC, any suggestions would be appreciated.)

Thanks again, @jphughan.

(Don't know what the issue is, but every time I reply to you I get a37FF74E2 error the first time, but then it posts the second time.)

@jphughanThe workstation that my wife is remoting in to has two monitors.  Hopefully she's be able to talk with a tech support person at her company to see if they have a solution.  Thanks again for your assistance.

@MNVOL  Glad I was able to help!

Out of curiosity, how many displays are actually attached to the systems you're remoting into?  The reason I ask is that Remote Desktop is a bit special in that it can set up a completely separate user session.  That's why the "console" shows the lock screen when a Remote Desktop connection is active.  In this case, the fact that Remote Desktop uses a capability built into the host OS itself means that when that mechanism is being used, Windows "understands" that the session is actually occurring elsewhere and therefore that it should care about what displays are attached to the client (or at least which displays the client has chosen to use for the connection) rather than which displays are physically attached to the system.  But GoToMyPC is a third-party tool that is simply running on top of Windows, not a remote desktop capability built into Windows itself.  Again, I haven't used it, so I may be wrong here, but my suspicion is that as a result of that distinction, GoToMyPC will NOT be able to just shift the entire Windows session to a purely remote mode the way Remote Desktop can.  Instead, it probably keeps the console active and just allows you to see and interact with that console session.  But in that case, it will matter how many displays are attached to the physical system, since that defines the display area of the console session that's being used even through GoToMyPC.

That's why I asked how many displays were physically attached to the systems you're remoting into.  If there are multiple displays there, and you have multiple displays where you are, then you might be able to have GoToMyPC "map" the remote view of each locally attached display to one of the displays you're actually using.  But if there's only one display physically attached to the system you're remoting into, then the console session that GoToMyPC would be exposing to you remotely would only be a single-display desktop, regardless of what you had available on your client.

@MNVOL  Thanks for reporting back!  Glad you've got GoToMyPC working if you prefer that solution, although the fix does confirm what I suspected, which is that GoToMyPC is just giving a remote view of a console session rather than establishing a completely independent remote session -- and therefore there's a dependency on the peripherals attached directly to the system.  On the other hand, Remote Desktop is harder to use over the Internet because you really need a VPN solution to secure it.  It just isn't safe to open up port 3389 on your firewall and expose your system's RDP listener to the public Internet.  Even using a non-default port to obscure it still isn't great.  By comparison, GoToMyPC seems to involve the listening host maintaining a connection to GoToMyPC so that when a client wants to connect, GoToMyPC's servers facilitate that connection, obviating the need for a VPN or other direct connection solution.

I personally use LogMeIn Hamachi for VPN purposes when I don't have the access or equipment necessary to set up a "standard" VPN hosted by a firewall router.  Hamachi allows you to create on-demand point-to-point VPNs with practically zero configuration.  It's fantastic.  There's a Free version that allows up to 5 clients, but it only works when the system's console is unlocked.  That works if you're creating a VPN so that multiple active users can exchange traffic, but it doesn't work for remote access where the console will be locked.  For that capability, you need the paid version.

@jphughan What we use for remote access is controlled by our respective employers.  Mine uses Remote Desktop Connection, along with PulseSecure as the VPN.  The Queen's employer uses GoToMyPC.