Welcome to MSDN Blogs Sign in | Join | Help

Introducing Live Mesh Remote Desktop: Part 1

The Remote Desktop Protocol is an efficient and feature-rich protocol which we have invested in greatly over the years.   As such, we’ve worked to make RDP available not just in traditional Terminal Server scenarios, but also as a platform for additional products from Microsoft and third party ISV’s.  We are seeing the benefits of this work in very cool products like the Live Mesh Remote Desktop, which we developed with one of our partner teams.  This service was just released to public Beta during Microsoft’s PDC, and in this post we’ll walk you through how it is used.

If you’ve ever wanted to have quick access to one of your computers from anywhere without the hassle of advanced network configuration and VPNs, Live Mesh is for you. Live Mesh uses advanced routing technology to enable seamless connectivity to any of your machines that are connected to the internet, regardless of network topology.

Note that there are a number of other valuable features in Live Mesh, but this post will focus exclusively on Live Remote Desktop. For more information on the additional features of Live Mesh, feel free to stop by their blog at http://blogs.msdn.com/livemesh/. Now, let’s get you up and accessing your devices!

Adding Devices to Your Mesh

It is very simple to get started with Live Mesh. If you don’t already have a Windows Live ID, you can start by creating one from www.passport.net. Once you have an ID to use for your Live Mesh account, you’ll need to visit www.mesh.com and sign in.

clip_image002

After signing in with your Windows Live ID, you will be presented with a first look at your mesh of devices. Initially your list of devices will be empty, so the first step will be to add devices you’d like to access to your Mesh.

clip_image004

To add your device to the mesh, simply click the large Add Device button, select the operating system from the drop down menu, and click Install.

clip_image006

This process will accomplish two things. First, it will download and install the Live Mesh desktop software onto your computer. Installing this software adds all the Live Mesh functionality to your computer, including the components which make it remotely accessible. Second, it will register the computer with the Live Mesh service, to make your computer show up in your list of devices. After downloading and running the installer from the Mesh website, you will see a Live Mesh notification in your system tray.

clip_image008

Next, click Sign in and enter your Live ID to get your computer logged on to your Live Mesh account. By allowing Live Mesh to save your password and sign in automatically, you can ensure that you’ll always have access to your computer, even upon reboot before logging in to your user account.

clip_image010

After you’ve signed in to your Live Mesh account, you’ll be able to create a friendly name to identify the device you’ve added to your mesh.

clip_image012

After clicking “Add Device” you have officially added the device to your Mesh and are ready to access it from anywhere. You should repeat this process on all machines you’d like remote access to. I personally have it on every computer I own =).

Connecting to Your Devices

Now that you have added your desired devices to your mesh, the next step will be to connect to your computers. The Live Mesh desktop software will be installed on any Windows XP or Vista computer you add to your mesh, and can be accessed via the Live Mesh icon in your taskbar’s notification area.

To begin, ensure that the device you’d like to access is turned on and has been signed in to your mesh either manually or by configuring it for automatic sign-in. Note that any machines which are set to automatically sleep for power-saving reasons won’t be reachable while they are asleep. On the computer you’re connecting from, click the Live Mesh icon on the right of your taskbar to bring up your list of devices. You will see that any device in your mesh which is online and logged in to your Live Mesh account will have the “Connect to device” option below its name.

sign in screen_new

Upon connecting you’ll see the lock screen of the target device. For security reasons, the device you are connecting to is locked upon connection, ensuring that whoever is accessing the device has not only successfully signed in to your Mesh account, but also has full rights to the remote device’s user account. After you log in, you can control your device in the same manner as you would through traditional Remote Desktop.

So far we’ve gone through how sign up for Live Mesh, add your devices to the mesh, and get connected via the Live Mesh software. In Part 2 of this post, I’ll outline how you can use Live Mesh to access your devices from anywhere via the browser, as well as some of the ways that Live Mesh Remote Desktop is unique when compared to the well-known Windows Remote Desktop feature.

Published Thursday, November 13, 2008 3:53 PM by termserv

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# Introducing Live Mesh Remote Desktop: Part 1 | MS Tech News

Thursday, November 13, 2008 7:08 PM by Introducing Live Mesh Remote Desktop: Part 1 | MS Tech News

# re: Introducing Live Mesh Remote Desktop: Part 1

Can you not control a Vista 64 bit machine?

Saturday, November 15, 2008 2:06 AM by Jeff

# re: Introducing Live Mesh Remote Desktop: Part 1

The mouse doesn't work correctly. I have dual monitors and clicking in a window pops up another window!

Monday, November 17, 2008 1:18 AM by Max

# re: Introducing Live Mesh Remote Desktop: Part 1

Hi Jeff,

Live Mesh works fully on Vista 64-bit.  Simply click on the "Windows Vista - 64 bit" option from the drop down menu when you are installing the desktop software.  You can see it on the third picture above.

Monday, November 17, 2008 2:34 PM by Casey Dvorak [MSFT]

# re: Introducing Live Mesh Remote Desktop: Part 1

Hi Max,

Are you seeing a problem with the mouse click being registered on a different part of the screen than the position you clicked?  Can you provide some more detail on what you are clicking that causes a new window to open?  Does this happen with only a specific application?

Monday, November 17, 2008 2:41 PM by Casey Dvorak [MSFT]

# re: Introducing Live Mesh Remote Desktop: Part 1

Got it working on Vista 64.  It seems to require a reboot, whereas the 32 bit version or XP didn't.

Thanks

Wednesday, November 19, 2008 1:25 AM by Jeff

# re: Introducing Live Mesh Remote Desktop: Part 1

Is there a limit to the number of devices?  Could it be in the hundreds?

Wednesday, November 19, 2008 1:51 AM by Jeff

# re: Introducing Live Mesh Remote Desktop: Part 1

It says for faster performance it will not render the wallpaper but when I connect to my home PC that is running Vista home basic SP1 it renders the wallpaper which seems to really slow it down. Is this a bug or am I missing something?

Wednesday, December 03, 2008 8:45 AM by John Lichina

# re: Introducing Live Mesh Remote Desktop: Part 1

Remote Desktop over Live Mesh is unusable at present.  Full-screen is not properly implemented, causing problems when resolution of server and client don't match.  (Try a widescreen 1680x1050 display on a portrait-mode 768x1024 -- it's either lots of scrolling, or can't read the fit-to-screen text.  It won't resize the server screen to fit the client desktop.)

Performance is also suboptimal even with desktop turned off. All the tuning options that we know and love from the mstsc client are missing.

As it stands right now, Live Mesh is suitable only for a kiosk demonstration.  Unsuitable for serious work over Remote Desktop.  A real shame, because it's quite helpful to not have to tunnel in through the VPN.

This is not the only thing wrong with Live Mesh.  They call it a "Beta" but I'd say it's only CTP quality.

Friday, December 05, 2008 7:23 PM by Tom

# re: Introducing Live Mesh Remote Desktop: Part 1

I also had a problem with my mouse not being registered properly during remote desktop--my visible pointer was about three widths of the taskbar below where the selection happened. Scenario: Vista Ultimate connecting to Windows XP laptop with external monitor set up for extended desktop. I assumed the problem was because of the vastly different aspect ratios.

Gotta tell you--while it was nice to see the displays for both the laptop and external monitor, the fact that they were different resolutions and different aspect ratios really made the remote monitors hard to read. Even though my Vista was 1600px wide, the combined width of the XP display was almost 2500 px--I couldn't get good scrolling or good resizing and performance was very slow. Even slower than my normal Remote Desktop connection to the XP machine that requires me to first remote desktop into one machine available through the firewall, then remote desktop to the XP.

(And, if you are thinking of features, how about adding in the feature that allows us to browse the files of the remote machine a la Foldershare.)

Sunday, December 21, 2008 9:16 AM by Derrel

# Live Mesh Cursor/Mouse registration

I have also had problems with the cursor registration. I can connect to a 17" Dell Inspiron laptop from an HP Mini 1000 both running xp. However where I am placing the cursor on the mini does not correspond to the location of the cursor on the Dell. The mapping between the two resolutions is not correct making it impossible to click/select the correct item.

Friday, January 23, 2009 10:56 AM by peter

# re: Introducing Live Mesh Remote Desktop: Part 1

Hi Jeff,

I have confirmed that there is currently a limit of 100 devices per Mesh.  Hopefully this should the needs of your home :).

Friday, January 23, 2009 7:48 PM by Casey Dvorak [MSFT]

# re: Introducing Live Mesh Remote Desktop: Part 1

Hi Tom,

With regards to your problems with desktop resolution, there are a couple of ways to improve the experience.  First, you can lower the resolution of the host computer to match your client, which is not ideal, but will fix your problem.

Second, you can use our new panning features, which I will be outlining in more detail during Part 2 of this post.  By using the "Show desktop as actual size" option and going into full screen mode, you can pan the full resolution of the host computer by moving your mouse to the sides of your screen.

Regarding problems with performance tuning, I'd be interested to hear your feedback on which tuning options you would like to see.  One of the things that might impact performance over traditional RDP is the fact that all traffic goes through the internet, where your upstream bandwidth can often be a bottleneck.

Thanks for your feedback.

Friday, January 23, 2009 7:53 PM by Casey Dvorak [MSFT]

# re: Introducing Live Mesh Remote Desktop: Part 1

Hi Derrel/Peter,

The panning feature I mentioned in response to Tom's post would likely help you quite a bit with your problem of your view of the remote computer being "squished" when placed into a smaller window.  

Could you give me more detail about your problem with the cursor not clicking the proper area of the screen?  About how many pixels is it off?  Does the amount of offset from where you clicked to where the click was registered vary as you click on different areas of the screen (i.e. top of desktop vs. bottom).

Friday, January 23, 2009 8:05 PM by Casey Dvorak [MSFT]

# re: Introducing Live Mesh Remote Desktop: Part 1

I'm using remote desktop with both panning and "squished" mode. In both cases the mouse click registers in the incorrect place.

local display 1280x800

remote display 1400x1050

Poor quality because I used my mobile phone, but you can find video that shows what I'm trying to do.

http://andyerickson.org/stuff/resolution-differences.3GP

http://andyerickson.org/stuff/remote-desktop-issues.3GP

Look at the resolution-differences first.

You can see I'm trying to click on the top login button on the remote screen. On my local machine it looks like I'm clicking on it. On the remote machine I'm about 1/2 a screen off.

The video shows me trying to do this in both squished mode as well as panning mode.

andy at andyerickson dot org

Thursday, February 05, 2009 9:23 PM by Andy Erickson

# Mouse Coordinate Issue

We appreciate all of the detailed feedback on the incorrect mouse pointer offset issue.  It looks like this is specific to Windows XP with the "Hide desktop on remote device" feature.  We are looking into this with a high priority and will update you when a solution is available.

Sunday, February 22, 2009 4:30 AM by Casey Dvorak [MSFT]

# re: Introducing Live Mesh Remote Desktop: Part 1

I have the same problem and it doesn't matter if I select hide desktop on remote device. When I connect to my Windows XP machine I get the squished desktop and cursor that is off. I see its because the 'virtual' Mesh monitor has 'Extended my desktop to this monitor' checked. By unchecking this option, it works fine. However, when I reconnect, the option is back on.

When I connect to my Vista machine I don't have this problem. Both machines are Lenovo laptops that can support dual monitors but are not (ie just an external LCD is being used).

Its a nice feature and I hope MS can fix it.

Monday, March 09, 2009 6:57 PM by Aveek Datta

# Two or more users sharing remote machine

What if remote machine is used by two or more users and both want leave it signed on under their accounts so they can access it remotely from their homes. Is that possible? What will happen if they both start using same file and program? would they get their own instance of desktop and all installed programs or they can see other person using the machine. Thanks

Wednesday, March 11, 2009 3:21 PM by KC

# re: Introducing Live Mesh Remote Desktop: Part 1

@KC: As it currently stands, if you try to connect to a machine that is being used, that user will be logged off.

Thursday, March 12, 2009 6:59 PM by EM

# re: Introducing Live Mesh Remote Desktop: Part 1

My emachine T2698 will synchronize but cannot be remotely accessed.  I have followed all the fixes and nothing works.  I had a terrible time with installation; it did not work and would not uninstall Mesh.  Finally I found instructions on the net to workaround - had to delete two keys in the Registry and then save Livemesh.exe and run it from a command prompt.

So LiveMesh now recognizes my eMachine and synchronizes but will not allow me to access remotely.

What can I do?  Two other laptops are on my Livemesh and work fine.

tyl604@aol.com

Thursday, October 22, 2009 12:11 PM by Adrain Taylor

# re: Introducing Live Mesh Remote Desktop: Part 1

Are you still monitoring this feed?  Please see my question on Live Mesh dated October 22.

Friday, October 23, 2009 12:05 PM by Adrain Taylor

# re: Introducing Live Mesh Remote Desktop: Part 1

Adrain, with the workaround you found were you able to successfully uninstall Mesh and then reinstall it?  If you had to use a workaround to reinstall I'd imagine it may not have been installed properly the second time.

Friday, October 23, 2009 1:32 PM by Casey Dvorak [MSFT]

# re: Introducing Live Mesh Remote Desktop: Part 1

Dunno.  It felt like it installed properly the second time and it added the eMachine to the mesh and it synchronizes the eMachine.  However it has a message saying that -although the eMachine is snychronizing, it cannot be remotely accessed.  Unfortunately this is the exact machine that I need to access remotely.

What do you recommend that I do to get it to handle the remote access???  Is this a typical in the Mesh beta?

Friday, October 23, 2009 1:42 PM by Adrain Taylor

# re: Introducing Live Mesh Remote Desktop: Part 1

Casey - to be a little more clear.  Yes, I was finally able to uninstall Mesh; I verified by looking in the Add & Remove Programs file and it was gone - earlier I tried removing Mesh but it still showed in Add & Remove Programs.  So I am confident that I finally uninstalled all of it.  Then I installed again from the command prompt a fresh saved .exe file - my old DOS instincts working.  It seemed to install properly and completely - and I was glad that it asked me for a name for the computer.  So it added the eMachine to the mesh with my two laptops and I thought all was fine.  However I noticed when I clicked on the eMachine as a device Mesh warned me that the eMachine was synchronizing OK but it could not be remotely accessed.  Of course this is the one that I need to access remotely most often.

So 1) Mesh was completely uninstalled finally, 2) Mesh seemed to install fine from the command prompt, but 3) the eMachine cannot be accessed remotely though it synchronizes.

Any idea what I should do?  Do you recommend that I go through all the steps again to uninstall and reinstall from the command prompt hoping that it will do something differently this time?  Is this just a typical problem with Mesh as a beta?

Friday, October 23, 2009 2:37 PM by Adrain Taylor

# re: Introducing Live Mesh Remote Desktop: Part 1

Live Mesh Remote Desktop is totally unusable for me, and has been for months.  There is a 15-30 second delay between each mouse click and the corresponding screen changes, it's ridiculous!  

What happened to this?  When Live Mesh first came out Remote Desktop was awesome and there was very little delay.  Why is it unusable now?  It is definitely not my internet connection speed, either.

Thanks!

Monday, November 02, 2009 2:07 PM by JJ

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker