From a feature perspective, I was simply looking for something similar to the Google Chrome Remote Desktop or the Microsoft Remote Desktop but, if possible, without the need to install anything on the PC; i.e.: a purely web client mirroring an Android screen .

I did test first AirDroid which is great, advanced, quite complete from a feature perspective. But first, it’s a bit too complex to “simply” remote access Android and next requires to install.

I tried next Mobizen. This one is not as complete as AirDroid which comes with its own interface to access SMS, calls, files, photos, videos, contact, …, without the need to use the full remote access (mirroring the screen). But some of the missing features in Mobizen are already available in Beta.

Here is what the remote access to my Galaxy S7, from Chrome, looks like.

It requires an App on the Mobile: Mobizen mirroring. Nb.:A dedicated version exist for Samsung.

Next to that, I am also using TeamViewer, which is great as the same product can be used in both direction. I.e.: with the TeamViewer “host” App for Android, PC’s can remotely access mobiles and tablets. And with the TeamViewer “for remote control” App for Android, mobiles and tablet can remotely access PC’s.

To access my PC and servers using Remote Desktop, I should define one port forwarding per machine on my router and configure Remote Desktop on each machine to listen on “its” port. Next, I should be able to remind the ports used for each machine – or create bookmarks – or … I could possibly use the “Anywhere Access” feature of Server 2012 Essentials, but it requires to setup a domain, buy and install a SSL certificates, etc…

With TeamViewer, instead, I log onto there website with my account and see a list of my machines. I simply click on a machine in the list, “et voilà”… from a single location, easy to remember, I can get remote access to the desktop of any PC at home or transfer any files from those. Even better, it supports remote desktop on PC with mutliple screens. And finally, I can also print any documents from my home machines on the printer next to me (e.g.: at the office).

For sure, the machine to be accessed must be up and running and TeamViewer must have been previously installed and configured to authorize unattended remote access (with a password).

To be noticed: TeamViewer may not be installed without a licence on a Windows Server. A Server is assumed to be for “commercial” use. That’s a pity as Windows Home Server is clearly a Server for personal use only… If you try to install it, it will not let you choose the “free-flavor” setup… Interesting to note however: “Ninite“, which is a free software used to silently download, install and update softwares, is actually able to setup TeamViewer on Servers too, in the free-flavor (the only inconvenient is that TeamViewer does not appear on the Start Screen and is not searchable from the Charm Bar.

To setup TeamViewer as a System Service:

1. Run “TeamViewer.exe”, 
2. Go to Extras > Options > General Tab,
3. Enter a  Display Name
4. Check the option – Start TeamViewer with Windows
5. Enter a Password & confirm it
6. Select the option – Accept incoming LAN connections

Download: http://www.teamviewer.com/en/download/windows.aspx

To remotely access files on one of my machines, without taking remote control of it, I could use the SkyDrive App. Maybe to be tested later…

First, check that Remote Desktop is enabled on the server, just to be sure:

1. On the Start Screen, type SystemPropertiesRemote and run that tool
2. Allow remote connection to this computer.

Next, I have disabled the Firewall, I don’t need to allow Remote Desktop Connection as an exception in this firewall.

Finally, Windows Server 2012 Essentials being a domain controller, accounts created on that machine belongs to the domain defined at the end of the installation. So, the user name to be provided in Remote Desktop must be like <domain name>\<user name> instead of simply <user name> (equivalent to <remote machine name>\<account> as by default, Remote Desktop uses the target machine name as domain name).

This subtle difference between Server 2012 Essentials and WHS 2011 (which was not a domain controller) could be a source of confusions while trying to connect for “end-users” used to work with workgroups instead of domains.

I was hesitating because, although the account name is the Windows Live email, the “user” folder name is only the name part of this email.

While checking which credentials to provide, I found by accident a way to get access to the logon screen of the remote machine, where the user currently logged appears => no need to remember the account name at all in this case :).

1. I did run the command “mstsc -v:<machine name>“
2. I did use another account: “<machine name>\administrator” without password (I don’t know it anyway).
   • The Domain initially displayed was: MicrosoftAccount
3. I did accept the certificate of the remote PC
4. I was next presented with an error message: “The username or password is incorrect” on logon screen of the remote machine. I did click OK.
5. I did click on “Switch user“, the left arrow on the top-left side.
6. And finally, I did select my Windows Live Account displayed as currently logged…

To connect directly with a Windows Live account:

1. Run the command “mstsc -v:<machine name>“
2. Select Use another accountand type your Windows Live email as a user name.
   • The domain displayed will be the one of your email.
3. Et voilà

Notice: I was able to remotely connect to Windows 8 because the Firewall was off. Otherwise I would have had to enable Remote Desktop as an “allowed apps”.

1. On the Start Screen, type “Firewall” and select Settings to find it.
2. Run Windows Firewall.
3. click Allow an app or feature through Windows Firewall.
4. Click Change settings if enabled (You might be asked for an admin password or to confirm your choice).
5. Under Allowed apps and features, select the check box next to Remote Desktop, and then use the check boxes in the columns to select the network types you want to allow communication on (should be private for your intranet).
6. Et voilà.