Resolution-Wrestling with Windows 8 and LogMeIn Pro (and/or ignition)

Host system is running Windows 8 Pro, most-current versions of LogMeIn Pro and Hamachi. Client is Windows 7 Enterprise running most-current version of Ignition and Explorer with LogMeIn add-ins.

Behavior described below is identical regardless which client interface gets used.

When I do the following:

Access the host via RDP from inside the firewall (host native resolution is 1920x1080), displays fine.
Log out of RDP.
Connect client to an external network, outside the firewall.
Access the same host via LogMeIn, either from the Web or from the Ignition client.

Then the connection is correctly made, and the host desktop displays at 1920x1080. Scaling the resolution in the LogMeIn client works fine as well. But, if I

Disconnect from LogMeIn.
Immediately attempt to reconnect from the same client to the same host via the same network.

Than the Host desktop displays at 1280x720, with no ability to scroll. Mouse location is out of synch, so clicks go to the wrong place. Essentially, the remote desktop becomes useless.

This behavior is consistent. The only way to convince LogMeIn to display the host in full resolution is to first connect with RDP and then immediately reconnect with LogMeIn.

Since the entire point of using LogMeIn is to enable access to systems that can't be reached via RDP, this dependency on RDP to enable proper use of LogMeIn is untenable.

I've gone through the registry with a fine-tooth comb, looking for any option for forcing the remote desktop resolution to 1920x1080, but I can't find anything.

If LogMeIn never worked at all at full resolution, that would be somewhat frustrating, but having it work correctly once, and then immediately fail to work across a disconnect/reconnect is hugely frustrating!

Incidentally, I saw the threads recommending QRES, and I tried it. I can modify the host screen resolution from the command line, but it does not seem to change the faulty display characteristics of the LogMeIn client.

Clearly, LogMeIn is capable of operating correctly at 1920x1080. But something's getting reset across sessions that makes it go haywire. The only way to reset that something back to what it should be is to establish a conventional RDP session, which defeats the purpose of LogMeIn.

Is there a resolution to this, or do I just need to give up on LogMeIn until this is fixed?

Find more posts tagged with

Comments

Misty-8

Was there a fix for this? I am having this problem now (just upgraded host to Win8 Pro).

Sean_K

While this is certianly a very detailed explanation of your reproduction procedure, we are going to need debug logging to further process this. I suggest that you contact our support lines, and reference this post, stating you would like to go to Level 2. We will then go through the procedure of reproducing this with debug logging on in both the client and host, and most likely Ignition as well.

On a side note, the Host software does not control the screen resolution the way you think. It is actually passed to it from the client.

In the web-based control method, the key is:

HKCU\Software\LogMeIn\Client\Options\<LMIDescription>_<IDString>

String Value RemCtrlScreenRes <screen resolution>

In Ignition:

HKCU\Software\LogMeIn Ignition\<ProfileID>\Software\LogMeIn\Client\Options\<LMIDescription>_<IDString>

String Value RemCtrlScreenRes <screen resolution>

So it is dictated by the client, but actually applied via the host.

Quick Links

Join the conversation!

If you found this discussion useful, why not register/sign-in? It only takes a minute to share your feedback, ask a question, or vote for a new feature!