Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a Windows Client/(SQL-)Server application which is normally installed at the customer's premises.

We now need to provide a hosted solution, and browser-based isn't feasible in the short term.

We're considering hosting the database ourselves, and also hosting the client in a VM. We can set all this up easily enough, so we need to:

  • ensure that the customer can connect easily, and also
  • ensure that we suitably restrict access to the VM (and its host, of course)

We already access the host and guest machines across the internet via RDS, but we restrict access to it to only our own internal, very small, set of static IPs, and of course theres the 2 (or 3?)-user limit on RDS connections to a remote server.

So I'd greatly appreciate ideas on how to manage:

  • the security
  • the multi-user aspect.

We're hoping to be able to do this initially without a large investment in virtualisation infrastructure - it would be one customer only to start with, with perhaps two remote users.


share|improve this question
up vote 1 down vote accepted

There's only a limit on RDP connections if you don't buy any more licenses.

What hypervisor are you using? VMWare's ESX/i products have a web-based console system built in.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.