Bartlett Hospital Web Services  
     
Support for Remote Desktop and Remote App

Operating System Requirements

Required Updates for Windows XP SP3

Remote Desktop Requirements

Web Browser Requirements

.NET Framework Requirements

Antivirus and Antimalware Requirements

  • Antivirus and Antimalware (with up-to-date definitions). Must integrate with Windows Security Center to pass health check. If health check fails, access will be denied. If you do not have up-to-date Antivirus and Antimalware, please install a free version of Microsoft Security Essentials via the link below:
  • Microsoft Security Essentials (Free Version)
    http://www.microsoft.com/security_essentials

Firewall Requirements

  • Firewall may be a hardware device or software based. Firewall should be configured to block unsolicited incoming connections. Firewall must allow HTTP (TCP 80) and HTTPS (TCP 443) outgoing to the Remote Desktop Gateway (brh-webservices.bartletthospital.org). Direct connections that do not use the Remote Desktop gateway must allow RDP (TCP 3389) outgoing to the respective Remote Desktop server.

Communication Traffic Flows

  • Remote Desktop Client (without Remote Desktop Services Gateway)
    Remote Desktop Protocol uses TCP 3389 outgoing to connect from the client to the server
    Remote Desktop Client binary name is mstsc.exe and is typically contained in %SYSTEMROOT%\System32
  • Remote Desktop Client (using Remote Desktop Services Gateway)
    Remote Desktop Client uses TCP 443 (RPC over HTTPS) outgoing to connect from the client to the gateway
    Remote Desktop Client binary name is mstsc.exe and is typically contained in %SYSTEMROOT%\System32
    Remote Desktop Client does not support HTTPS inspection at the client side firewall; such functionality will need to be disabled

Preconfigured Files for Direct Access

  Home