MultiTunnel Contact us

Services

Servers, gateways, relays and kiosks run under a service, not a person. Create a service, join its computer for it, and move a device between a person and a service.

Every membership is a person's, or a service's

  • A person's

    A membership on a computer belongs to the Windows account that joined: the person's own. It connects while they are signed in, and nobody else who uses the computer gets it. On a computer several people use, each person joins from their own account, and each is a device of their own in the network.

  • A service's

    A server, gateway, relay or kiosk runs under a named service. Its membership belongs to the computer's MultiTunnel service, so it stays connected whoever is signed in, or nobody. Only administrators create services, and a person in the network is responsible for each.

  • Nothing for everyone

    Nothing is set up for everyone on a computer. One account joins a network once: to join again, it leaves first.

A service is never a person. It takes no seat, on every plan, the Free plan included. Rules that name people never apply to its devices: rules name it with service: and its name. Access rules

One person's own computer

They join from their own Windows account, as usual: the network is theirs on this computer. Join, step by step

A computer several people use

Each person joins from their own account, with an invite of their own. Each is connected only while they are signed in; removing one person leaves the others on that computer as they are. One Windows account shared by several people is not a person: give each their own account, or run the computer as a kiosk, under a service. A computer several people use

A server, gateway, relay or kiosk

Create a service for it, invite the computer for that service, and join on it for the service. Set up a server as a service

Set up by an IT tool

A device management tool, or an administrator's remote PowerShell or SSH session, runs with nobody at a desktop, so MultiTunnel can't tell whose the membership is: a join from there says whose, with -account or -service. Installs with nobody signed in

Set up a server as a service

Here Sam sets up Northwind Clinic's file server as the service File server.

  1. Create the service. Open Administer, then Services. Under Create a service, give Its name as people would know it (File server), choose What it is (a server, a gateway to a network, a relay, a kiosk or shared screen, or something else) and the Responsible person (you, unless you choose someone), and choose Create service….
  2. Invite the computer for it. Under Invite and approve, choose the service under Who is it for?, and send the invite to whoever will set up the computer. Invite and approve
  3. Join on the computer, for the service. It needs the computer's own administrator. In the app: Join a network, paste the invite, and tick This computer runs a service (a server, gateway or kiosk), not a person's. There is no name to type. Choosing Ask to join, Windows asks for permission.
  4. Approve it, as any device: the approve screen says it joins for a service, and if the invite wasn't for the service, you type the service's name. MultiTunnel refuses a service's request approved for a person, and a person's approved for a service, and the computer checks again when it joins.

Several devices can run under one service, such as three kiosks under Reception kiosks. In Services, each service shows what it is for, who is responsible for it, and its devices.

Command line

On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start

Create the service (server, gateway, relay, kiosk or other). You are responsible for it unless -contact names someone:

Windows
& $mt service $st northwind add "File server" -purpose server -contact sam
Linux
sudo multitunnel service /var/lib/multitunnel northwind add "File server" -purpose server -contact sam

Make an invite for it:

Windows
& $mt invite $st northwind -for "service:File server"
Linux
sudo multitunnel invite /var/lib/multitunnel northwind -for "service:File server"

On the server, as its administrator (Terminal (Admin) on Windows, root on Linux), join for the service:

Windows
& $mt join $st auto files "<paste the invite here>" -service
Linux
sudo multitunnel join /var/lib/multitunnel auto files "<paste the invite here>" -service

Approve its reply code. An invite for the service names it already; without one, name it:

Windows
& $mt approve $st northwind "<paste the reply code here>" -service "File server"
Linux
sudo multitunnel approve /var/lib/multitunnel northwind "<paste the reply code here>" -service "File server"

List the services:

Windows
& $mt services $st northwind
Linux
sudo multitunnel services /var/lib/multitunnel northwind

Installs with nobody signed in

A join run with nobody at a desktop, such as by a device management tool, by an administrator over remote PowerShell or SSH, or as root on Linux, can't be anyone's own. MultiTunnel refuses it unless it says whose the membership is, and says what to type:

  • -service for a server, gateway, relay or kiosk: the computer's service's, always connected.
  • -account and a person's account for a person's computer: a Windows account (DOMAIN\name, or a name Windows can look up) or a Linux user name. The membership is theirs from the start: it can be approved before they sign in, and it connects when they do.

Only a computer's administrator can use either, and only one of the two at a time. -account takes a person's account, never a group, a built-in account or root. To create a network from such a session, add -account to init in the same way. Create a network

Command line

On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start

For a person, who connects when they sign in:

Windows
& $mt join $st auto dana-pc dana "<paste the invite here>" -account NORTHWIND\dana
Linux
sudo multitunnel join /var/lib/multitunnel auto dana-pc dana "<paste the invite here>" -account dana

For a service:

Windows
& $mt join $st auto reception-pc "<paste the invite here>" -service
Linux
sudo multitunnel join /var/lib/multitunnel auto reception-pc "<paste the invite here>" -service

Move a device between a person and a service

For a server that joined as someone's device. Here Sam moves the file server, files, from himself to the service File server. MultiTunnel shows what changes before you sign.

  1. Find the device

    Open Administer, then Devices, and choose Manage beside the device. If the service doesn't exist yet, create it under Services first.

  2. Choose the service

    Under Move to a service, choose it in Move to the service, here File server.

  3. Move it

    Choose Move…. Windows asks for permission.

  4. Read what changes

    MultiTunnel says what changes before anything is signed: what the device can reach, whom it proves itself as to apps, and rules naming its old owner that stop applying to it. Choose Yes only if that's what you want.

  5. Your PIN

    Windows asks for your admin PIN, in its own window.

  6. Moved

    In the network, the device is now the service's. On the server itself, one more step may be needed: see below.

On the device itself. A move changes the network, not the computer. A membership that was joined for a person still connects only while they are signed in, until an administrator on that computer opens the network's page and chooses Run it for the service… (Windows asks for permission). It then stays connected whoever is signed in. A membership set up for everyone on that computer by an earlier version follows by itself.

Back to a person. The same place offers Move to a person for a service's device: in the network it becomes their device, and their rules apply to it. On the computer it keeps running for whoever is signed in until it leaves and joins again from that person's own account.

The computer that created the network is always its maker's, a person's. If it is also the network's server or gateway, move its device to a service, then choose Run it for the service… on it.

Command line

On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start

It shows what changes and asks before going on (or add -yes):

Windows
& $mt move-device $st northwind files "service:File server"
Linux
sudo multitunnel move-device /var/lib/multitunnel northwind files "service:File server"
Windows
& $mt move-device $st northwind files user:sam
Linux
sudo multitunnel move-device /var/lib/multitunnel northwind files user:sam

Then, on the device itself, as its administrator, if it was joined for a person:

Windows
& $mt owner $st northwind service
Linux
sudo multitunnel owner /var/lib/multitunnel northwind service

Change who is responsible, or remove a service

Under Services, choose Manage beside the service.

  • Who is responsible: under Responsible person, choose who Answers for it from now on, and Change….
  • Remove it: its devices are removed too, and are listed before you go ahead. Choose Remove File server… (with the service's name).
  • Removing a person who is responsible for a service asks who answers for their services from then on, so no service is left with nobody responsible.
Command line

On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start

Windows
& $mt service $st northwind set "File server" -contact dana
Linux
sudo multitunnel service /var/lib/multitunnel northwind set "File server" -contact dana

It lists the devices that go with it, and asks (or add -yes):

Windows
& $mt service $st northwind remove "File server"
Linux
sudo multitunnel service /var/lib/multitunnel northwind remove "File server"

Remove a person, passing their services on in the same step:

Windows
& $mt remove-user $st northwind sam -contact dana
Linux
sudo multitunnel remove-user /var/lib/multitunnel northwind sam -contact dana

A network set up for everyone on a computer

Networks that an earlier version set up for everyone on a computer still work, and say For everyone on this computer. Move each to its owner:

  • A person's computer: at their own desktop, they open the network's page, open This computer is only used by me, and choose Make it mine…. Windows asks for permission. It stays the same membership, with the same keys, and from then on it is theirs: it connects while they are signed in, and others who sign in to that computer no longer get it.
  • A server, gateway, relay or kiosk: move its device to a service, as above. Its membership then runs for the service by itself.
Command line, for a person

On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start

On their computer, signed in as themselves:

Windows
& $mt owner $st northwind me
Linux
sudo multitunnel owner /var/lib/multitunnel northwind me

Still stuck?

Email us and a person will reply. For a security problem, write to security@multitunnel.co.uk instead.

enquiries@multitunnel.co.uk