Per @georgejhunt's request, we need new remote support infrastructure, as XSCENET is showing its age (and its risks).

Naturally there are many competing (in fact conflicting!) requirements. So let's start by gathering some of the more common/dominant possible requirements for this new remote collaboration/support infra:

• works BEFORE Internet-in-a-Box install begins, so screensharing/mentoring is legit: Install OpenVPN/TeamViewer/support tool(s) BEFORE installs begin [or near the very beginning!] #317
• secures volunteers' homes, schools and clinics strictly and/or incrementally (security is like an onion…)
• takes the pain out of remote support allowing “Almost All Kinds Of Testing” WHEN escalated/trusted parties so choose
• highly available and highly reliable (self-recovers, holding connection for days/weeks/months) such that it also can (when you're lucky!) work over fragile 2G and 3G connections to the developing world
• cloud-based console should enable tech support and testing people to get hassle-free access to IIAB machines they need (sticky issues around NAME + GUID need to be resolved!)
• manual override when things inevitably go wrong: iiab-remote-on and iiab-remote-off
• BONUS/DESIRED/OPTIONAL: allows vnc-like access to IIAB servers within schools/homes that are completely offline.
• BONUS/DESIRED/OPTIONAL: cloud console could enable schools to check their server(s) online/offline history (and on/off power history, and bandwidth consumption history) as many principals (and funders/NGO's) badly want. This has also proved useful with a theft, allowing 1 school to trace precisely when theft of their hardware took place!