Introducing Live Mesh Remote Desktop: Part 1

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

Introducing Live Mesh Remote Desktop: Part 1 | MS Tech News — Fri, 14 Nov 2008 03:08:45 GMT

PingBack from http://mstechnews.info/2008/11/introducing-live-mesh-remote-desktop-part-1/

re: Introducing Live Mesh Remote Desktop: Part 1

Jeff — Sat, 15 Nov 2008 10:06:01 GMT

Can you not control a Vista 64 bit machine?

re: Introducing Live Mesh Remote Desktop: Part 1

Max — Mon, 17 Nov 2008 09:18:08 GMT

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

re: Introducing Live Mesh Remote Desktop: Part 1

Casey Dvorak [MSFT] — Mon, 17 Nov 2008 22:34:03 GMT

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.

re: Introducing Live Mesh Remote Desktop: Part 1

Casey Dvorak [MSFT] — Mon, 17 Nov 2008 22:41:20 GMT

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?

re: Introducing Live Mesh Remote Desktop: Part 1

Jeff — Wed, 19 Nov 2008 09:25:57 GMT

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

Thanks

re: Introducing Live Mesh Remote Desktop: Part 1

Jeff — Wed, 19 Nov 2008 09:51:49 GMT

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

re: Introducing Live Mesh Remote Desktop: Part 1

John Lichina — Wed, 03 Dec 2008 16:45:06 GMT

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?

re: Introducing Live Mesh Remote Desktop: Part 1

Tom — Sat, 06 Dec 2008 03:23:21 GMT

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.

re: Introducing Live Mesh Remote Desktop: Part 1

Derrel — Sun, 21 Dec 2008 17:16:59 GMT

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.)

Live Mesh Cursor/Mouse registration

peter — Fri, 23 Jan 2009 18:56:25 GMT

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.

re: Introducing Live Mesh Remote Desktop: Part 1

Casey Dvorak [MSFT] — Sat, 24 Jan 2009 03:48:48 GMT

Hi Jeff,

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

re: Introducing Live Mesh Remote Desktop: Part 1

Casey Dvorak [MSFT] — Sat, 24 Jan 2009 03:53:26 GMT

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.

re: Introducing Live Mesh Remote Desktop: Part 1

Casey Dvorak [MSFT] — Sat, 24 Jan 2009 04:05:51 GMT

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).

re: Introducing Live Mesh Remote Desktop: Part 1

Andy Erickson — Fri, 06 Feb 2009 05:23:57 GMT

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

Mouse Coordinate Issue

Casey Dvorak [MSFT] — Sun, 22 Feb 2009 12:30:13 GMT

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.

re: Introducing Live Mesh Remote Desktop: Part 1

Aveek Datta — Tue, 10 Mar 2009 01:57:25 GMT

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.

Two or more users sharing remote machine

KC — Wed, 11 Mar 2009 22:21:21 GMT

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

re: Introducing Live Mesh Remote Desktop: Part 1

EM — Fri, 13 Mar 2009 01:59:50 GMT

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

re: Introducing Live Mesh Remote Desktop: Part 1

Adrain Taylor — Thu, 22 Oct 2009 19:11:27 GMT

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

re: Introducing Live Mesh Remote Desktop: Part 1

Adrain Taylor — Fri, 23 Oct 2009 19:05:16 GMT

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

re: Introducing Live Mesh Remote Desktop: Part 1

Casey Dvorak [MSFT] — Fri, 23 Oct 2009 20:32:35 GMT

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.

re: Introducing Live Mesh Remote Desktop: Part 1

Adrain Taylor — Fri, 23 Oct 2009 20:42:13 GMT

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?

re: Introducing Live Mesh Remote Desktop: Part 1

Adrain Taylor — Fri, 23 Oct 2009 21:37:52 GMT

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?

re: Introducing Live Mesh Remote Desktop: Part 1

JJ — Mon, 02 Nov 2009 22:07:26 GMT

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!