Not sure how far you've got with this, but just in case:
mrview clearly works, since you can use it when logged in locally. So the issue is purely down to OpenGL not being supported over a remote desktop connection.
This is not a limitation of MRtrix3 per se - we make use of Qt5 and OpenGL 3.3, both of which are industry-standard and well supported. However, this does rely on the operating system providing access to the capabilities of the graphics card, and here the issue is that Microsoft's RDC protocol does not provide any guarantees on that front - Microsoft leaves it up to the graphics card manufacturer to provide support for this in their drivers.
This will apply to any application that relies on OpenGL - MRtrix or otherwise. There's plenty of information on that if you search for 'OpenGL RDC' (e.g. this forum post). But as @rsmith hints at, this is not something that we can provide support for...
However, if you can access the data that you're trying to view over e.g. a network share, then there's nothing stopping you from viewing these data using a local installation of
mrview - this is how I typically get around the problem, and is also one of the suggestions in the documentation.