Remote Desktop Gateway

Remote Desktop Gateway (RDG)… IS NOW LIVE

The new RDG service is one of the workstreams delivered under the Managed Service Rollout (MSR) Project.

This is officially QMs new secure remote access capability which went live early last month, is now fully embedded within BaU and currently have over 40 users.

Our new ‘Remote Access Gateway’ service allow you to connect to your desktop machines based onsite at Queen Mary. 

This service is available to both staff and students. All you need to use this service are: 

1. Office Desktop PC on campus is a QM Managed Device, a laptop/device off campus with a Wi-Fi connection.  
2. Multi Factor Authentication– A onetime set-up on the QMUL  multi factor authentication (MFA) service. 
3. To get set up on this service please send a request to our Service Desk. You will be required to submit a brief business case for your request.  This allows the team to assess whether this this service best fit your needs.  
   • Business requirements for the service (i.e. a business case) 
   • Location of desktop device(s) from and to 

We have created a 'How to' document which provides a step by step guide on how to use the ‘Remote Desktop Gateway’ service please download from here. 

Change request was approved by Project Board last week the migration of Remote Desktop Protocol (RDP) which is now part of this project.

---------------------------------------------------------------------------------------------------------------------------------------------

Plan of Action

1. Use Landesk to verify RDP owners and users 
2. Comms - inform owner of RDP> RDG migration and confirm process for users
3. Gather intel from owner on machine (business case) and user - RDG suitable
   • Confirm Users
   • Gather user approvals and complete RDG checklist 
4. RDP not suitable - Next steps (meet user requirements whilst ensuring mitigration of risks)
5. Action to remove RDP confirmed
6. Confirm - Successful migration of RDP
7. Contact users to confirm remote access via RDG is successful 
8. Re-confirm - remote access to server successful via RDG