COVID19 is hitting all industries globally, not in the least education. Depending on geography and what school system the impact can be very different. Some schools simply closed down, in other cases they focused on giving remote classes over Zoom or Teams calls, or yet other cases classes were still (in part) physical but with smaller groups of students. And then there is probably a mix of all scenarios.

The reality is that – like most industries – the education sector was not prepared for remote teaching (excluding a minority of online universities). That said: certain student groups (think minors) need a physical ‘school’ to attend classes. To develop their social skills, and not in the least because they can’t be alone at home all the time. And even in higher education, I’m personally not yet convinced that a full online or remote system can fully replace the physical experience. I can perfectly see hybrid scenarios. COVID19 is accelerating this new ‘hybrid’ equilibrium for online and remote learning with physical systems.

Now let’s look at a reality in a lot of Universities around the globe: they have large PC rooms, sometimes with thousands of computers, running specific software (statistics, etc). Software which often is just too expensive or difficult to provide in any other way to students. Due to Covid19, these classes are now closed or sometimes open at 50% capacity to guarantee social distancing. This means a lot of students are not optimally equipped in their learning experience. Most students will have a personal computer somewhere, but they just lack the specific required software and tools. For the school itself, there is a big investment in hardware and software which is useless… This is where Awingu can step-in and give students secure remote access to these PC room computers.

In a previous blog post we describe how Awingu enables a very easy yet secure remote access to desktops in a company network. The same applies to computers in a school PC room. In short: Awingu acts as an HTML5 gateway and translates the desktop into HTML5 and makes it available security to the outside world.

Getting it up-and-running in no time

Getting the Awingu deployed is fast and easy. You can just install the virtual appliance in your existing network. No changes are needed on the desktops etc. You just keep operating these as before.

In the above high-level picture, we illustrate how the Awingu virtual appliance is set up in an existing network.

      • Awingu’s virtual Linux appliance is installed on one or more Virtual Machines (as guidance: up to 500 concurrent app/desktop sessions can run on 1 virtual machine with 8Gb Memory and 8vCPU)
      • Awingu is connected per RDP to each desktop (they must be powered on), and coupled to the AD. No installations are needed on the AD or desktops. It also means students can probably keep using their existing AD credentials.
      • Note: Awingu can also be connected to RDS-based environments, to file shares and SaaS apps such as Office 365 and GSuite. In this blog post, we make an abstraction of this and focus solely on the remote desktop access.
      • Awingu is typically installed behind a firewall or proxy and only needs access via port 443.
      • Students log in via their browser on their private device: a Windows laptop, an Apple Macbook, a Chromebook, … any device with a browser will work.

Example of an Awingu login page in the browser, Google Chrome in this case

Screenshot of remote access to a full Windows desktop in the browser

Get up and running with minimum investments

To enable the above use case, the only thing you will need:

      • A virtual machine (at least one)
      • Awingu licenses (check out our pricing, or contact us for more info)

Interested how this can work out for your organization? You can start a free pilot and reach out to us for more information and a quote.