We are seeing several incidents on a wide range of installed Windows 2003 computers where the Logmein Rescue client is maxing out the CPU. This CPU uasge is so severe that it makes remote support impractical and we need to end the session so the client's pc can resume normal operations. The issue persists across reboots and with or without the Rescue client session running as a service.
Research has shown that other users of Rescue have similar issues, however there does not seem to be any solution forthcoming.
Any suggestions (ideally from a Logmein Rep) are welcome.