kbar
Active Contributor
Joined 17 years ago
User Profile
User Widgets
Contributions
Re: Black screen when using remote control on RDP connection to Windows Server 2016
Not our experience. The requirements for dongles seem to be new to us. Headless machines used to work reliably. We routinely apply the Microsoft updates and use the the Intel display drivers. We really don't want using LMI to restrict applying updates. It's annoying, even having a monitor plugged in (USB C cable), but turned off sometimes gives up the black screen with no way of fixing it without a physical presence.839Views0likes0CommentsRe: Black screen when using remote control on RDP connection to Windows Server 2016
It appears that some recent LMI update now requires a monitor to be attached and turned on. We've gotten around it by using the "fake display dongles" so LMI thinks there is a monitor attached. But for remote diagnostics and help it kind of is a big missed. LMI update? Crickets.983Views0likes2CommentsRe: Issue with recent build and W11
More digging yielded the result that LogMeIn no longer supports "headless" machines -- may be a W11 feature drop. You must have monitor plugged in our the results become very wonky. This was not true in earlier releases (or with MS remote desktop). Kind of a bummer that it's not documented.270Views0likes0CommentsIssue with recent build and W11
I'm seeing an issue with the most recent build of LMI where windows don't get keystrokes or refresh. I've updated all the drivers and seems somewhat random. Sometimes going to the taskbar and closing the window or alt-tabbing helps, but not always. I think the most recent release might have been "rushed" since it seems like the basic feature of reliable remote control stopped working. More frequently I'm relying on (the included) Microsoft RDC to fix issue when LMI stops working. Others seeing this same issue.329Views0likes2CommentsRe: Crowdstrike Outage
It seems like the crowdstrike issue exposed a lot of single points of failures at LogMeIn. The inability to provide timely updates ... beyond blaming a third party and saying that "we're working really hard", logmein really dropped the ball. It's really sad how logmein has pushed untested updates to logmein (changing permissions in June locking out users) and third-party updates across its entire infrastructure. And not having a way of notifying customers because our email was down. The service pages updates were pretty useless... no eta and "not my fault".550Views0likes0CommentsRe: Host Version 15512 - New "Keystrokes" Permission Defaults to Disabled?
I had a somewhat of disaster of a morning because of this update. Many of my users were able to connect, but not type after connecting. After a fairly long tech support call the solution they offered was to give the users "full control" permissions which fixes the problem. Not ideal, but it works. It seems like the update was rushed for "pro" (read expensive) SaaS software. Big miss on LogMeIn.782Views0likes0Comments- 1.6KViews0likes3Comments
Re: Can't See Icons on Host Computer (OSX)
I'm having the same issue on a newish M1 mac mini. Tried the options listed above with no success. Remoting in works for awhile (2 or 3 hours) and then goes into the mode where only the menu bar and backgrounds is visible. No help for logmein support (and not very surprised).1.7KViews0likes5CommentsBlank screen when controlling a Mac system
When I use LogmeIn central to remote into a Mac running OS Version 12.0.1 from a PC I'm getting either a blank (black) screen or just the menu bar and the desktop background. This happens on the second time I remote in -- rebooting the system will fix it. The first time I use logmein against this machine, it works fine. Subsequent session yield either the black screen or just the menu bar. I've given LogMeIn the correct privacy rights in the mac control panel as LogMeIn control works correctly after a reboot. The LogMeIn products on both PC (controlling system) and Mac (controlled systems) are upto date.Solved5.8KViews0likes16CommentsHigh CPU usage macOS 12.0.1
When connected to remote Mac Mini via LogMeIn Pro (from W10, if it matters) the CPU usage as reported by Mac Application Monitor is 165%, and by Linux top 175%. Makes the machine pretty much usable. Is this bug in LogMeIn or an incompatibility with macOS 12? Details: Mac Mini (Late 2014) macOS 12.0.1 Mem 16GB LogMeIn 4.1.0.11887657Views0likes0Comments