LODS Virtual Lab: Lab Orientation & Connectivity Check – Launch Lab

Connectivity Requirements


To launch and use a lab, the following requirements must be met:

  1. Use a supported Windows operating system (Windows 7 or later). For Hyper-V hosted labs that also require the use of RDP, will also need Remote Desktop Connection installed.

  2. Have a supported browser. (IE 8+, Edge 1+, Chrome 16+, Firefox 11+, Safari 6+)

  3. For Hyper-V hosted labs that also require the use of RDP, be able to launch an unsigned .rdp file (the Windows default).

  4. For Hyper-V hosted labs that also require the use of RDP, be able to accept a certificate from an unknown publisher (the Windows default).

  5. Be connected to a network that allows at least one of the following:

    1. Secure Web sockets on HTTPS port 443

    2. Web sockets over HTTP port 80 and HTTP over Port 843 (Flash control) (Hyper-V only)

    3. RDP over port 21xxx or 443 (Enhanced control)

    4. VMRDP (Port 21xxx) (If you will also use the Enhanced control - Hyper-V with RDP only)

    5. VMware custom protocol over port 902 (VMware Remote Console Plug-in – vSphere only))

  6. Have administrative rights on the local machine if installing the Enhanced control (Hyper-V w/RDP only).

  7. Have administrative rights on the local machine if installing the VMware Remote Console Plug-In (vSphere only).

Browser/Control Support

Machines in your lab can be accessed using any one of five virtual machine controls depending on the type of lab you are running. For RDP labs, at least one of your virtual machines will be accessed via the Windows Remote Desktop (RDP) Connection available in Windows 7 and later. You can freely change between controls on those virtual machines not using RDP to find the one that works best for you.

Virtual Machine Control Chrome Firefox Internet Explorer Microsoft Edge
Version Protocol Ports Version Protocol Ports Version Protocol Ports Version Protocol Ports
Remote Desktop (RDP) 16+ RDP over HTTPS 443 11+ RDP over HTTPS 443 8+ RDP over HTTPS 443 1+ RDP over HTTPS 443
Choose one HTML5 1 16+ Websockets 443 11+ Websockets 443 10+ Websockets 443 1+ Websockets 443
Flash 11+ Websockets 80 & 843 2 11+ Websockets 80 & 843 2 11+ Websockets 80 & 843 2 11+ Websockets 80 & 843 2
Silverlight 4+ HTTP 80 4+ HTTP (RDP), HTTPS 80 (RDP), 443 4+ HTTP 80 (RDP), 443 N/A N/A N/A
Enhanced 3 N/A N/A N/A N/A N/A N/A 8+ VMRDP 21xxx or 443 N/A N/A N/A
VMware Remote Console (vSphere) 4 N/A N/A N/A 11+ Custom 902 8+ Custom 902 N/A N/A N/A

1 Preferred

2 Port 843 is required by Flash Socket Policy to authorize the use of Web sockets

3 Requires Internet Explorer. The 21xxx value depends on which host server in the cloud the lab is running on. If connection on port 21xxx fails, the Enhanced client will rollover and attempt the connection on port 443.

4 Windows and Linux Only

Important Note: When Connections Traverse a Proxy

When connecting to a lab instance via a proxy, certain configuration requirements must be met for each remote controller. For more information, please review the Proxy Requirements article.

Important Note: When Using Windows Server Operating Systems

When connecting to Learn on Demand Systems Training Management Systems (TMS) portals with a computer having Windows Server operating systems on it, you may experience difficulty in connecting to the sign-in page or clicking on some buttons. Steps to remediate can be found here.

Connection Assessment Test

If you are experiencing frequent disconnects or lag when controlling your machines, you may run a connection assessment test. For help with analyzing the results of your test, please review the Interpreting Your Connection Assessment Results article.

Firewall Exception Rule Information

For those that need to create a firewall exception rule to allow connectivity to the Lab on Demand servers(this isn’t common), the following information can be used to create a limited destination rule to only allow the above protocols and ports from your network to the Lab on Demand cloud.

The Lab on Demand system is a cloud platform that automaticallyprovisions and connects the learner with private sandboxed resources. There isno way to predict which IP address in the cloud the learner will connect to forthe provisioning of their virtual machines. This is why we provide a range of IP addresses and only a second level domain name.

For Hyper-V and Hyper-V w/RDP only labs, the domains and IPaddresses in the table below may also be required as firewall exceptions. Westrongly encourage using names, and not IP addresses, for firewall and proxyconfiguration if at all possible, as the IP addresses may change withoutwarning (and without documentation update). This allows access even in networkfailover and future geographic targeting scenarios. If specific IP addressesmust be used, use the following table as a guide for IP addresses:

DNS name IP Address 1 IP Address 2
holsystems.blob.windowsazure.com (refer to Microsoft’s documentation)  
holsystems.blob.core.windows.net (refer to Microsoft’s documentation)  

Lab Software Whitelisting Information

Software that communicates with remote servers outside of the lab environment may need addresses whitelisted with the vendor to work. The below address ranges are used by NAT internet access labs.