Connected laptop acts entirely different when lid is open versus closed
I recently purchased an ASUS laptop and added it to our Central account as a device to connect to. Laptop is Windows 11 Home, and it has integrated Intel Xe graphics. No dedicated GPU and no external monitors hooked up to it. The laptop was configured to never go to sleep when on AC power, and power mode was set to performance. The first two days of use had no issues. The lid was closed, and I was able to do my work remotely. Immediately after two days I noticed the following behavior: Some of my Windows programs and folders will either open or not open. File explorer will not show at all. Entirely a hit or miss on what will open. The Start menu will not display when clicked on. I can open a program like MS Edge, but I cannot close it. I can Alt+Tab to see the available open windows to cycle thru, but it will not display the window I want. Here's what happens next... When my laptop lid is opened, all of these windows and registered clicks will then work. Meaning that instance of MS Excel I tried to open or File Explorer will pop up multiple times. Basically, it appears everything decides to "work" once the laptop's lid is open. Before anyone says it's the laptop, I hooked up an external monitor to see if it has to do with the lid being closed at all. I can confirm the issues are NOT repeated with an external monitor. Laptop works like normal. We have a Dell Latitude laptop connected to our Central account, and after turning off all the sleep settings etc.., that one has no issues when the lid is closed. Apps and windows work perfectly fine. It also has an integrated Intel GPU (I forget if it's Xe or an older chip). So, in short, I need help troubleshooting why this is happening when the lid is closed and connected to Logmein and how to make it work while keeping the lid closed.40Views0likes3CommentsLogmein Client no longer installing along side Control Panel
All of a sudden, for some reason, Logmein control panel is installing, but the client is not. Normally they both install at the same time. I have to run a repair on the install and then it installs the control panel. I am not sure why this all of a sudden started. This is what I use to install the Windows Host LMI start-process C:\windows\system32\msiexec.exe -argumentlist "/I C:\temp\$lmilatest /qn /l*v C:\temp\lmiinst.log SETPOWERMANAGEMENT=0 LMIDESCRIPTION=`"$compname - $compmodel - `" COMPANYNAME=[companyname] ACCOUNTEMAIL=[accountemail] DEPLOYID=[deployid] SHOWCLIENT=0 SHOWCONTROLPANEL=0" -waitSolved1.9KViews0likes7CommentsCentral not detecting anti-virus software, real-time protection, or virus definition on Win 11 Pro
We have successfully used LogMeIn Antivirus for a year on many Windows 10 Pro computers; however, I just installed it on several new Windows 11 Pro computers. The program appears to install and the policies seem to apply correctly; however LMI Central is not getting updated information from the computers. The Windows 11 Pro computers show successful installation. Scans are running as scheduled and the firewall turned on (although I have since turned it off for testing). In Central, the anti-virus software column says "Unknown", the real-time protection column says "Disabled", and the virus definition column says "Out-of-date." I have changed the LMI AV policy to turn off the firewall and have also disabled the Windows firewall as requested by LMI support. I enabled logging in LMI Control Panel and uninstalled, rebooted, and reinstalled LMI AV and sent the debugging logs to LMI support. So far they keep saying it is a firewall issue but don't know what to suggest to fix it. The log says "Error (in recv): An existing connection was forcibly closed by the remote host" and "Error (in send): An established connection was aborted by are in your host machine." I feel it must be something unique to Windows 11 Pro. Does anyone have any idea what needs to be changed on these computers to get them to report properly to LMI Central?Solved2KViews0likes6CommentsHamachi Network in Gateway Mode is Giving Gateway an APIPA Address
As the title says, trying to run a Hamachi network setup in Gateway mode. The computer that I have designated as the gateway, however, is getting an APIPA address (169.254.x.x). In truth I'm not entirely sure how this system is intended to work, so I'm not sure if its the fault of my DHCP server on my router or if it's a fault on Hamachi's side. I have even manually set the IP range in the gateway settings on hamachi to match that of my home network's IP range (though higher so that there's no ip conflics, i.e. 192.168.0.200-255). Because of this none of the client computers on the network can access anything on the gateway's network. Anybody run into this issue before or know what's going wrong?Solved3.6KViews0likes4Commentscommand prompt issue
we are using logmein central. throur the logmein client when you click on the home icon then go through computer management and clicking on command prompt you receive the following error: error title: script error error header: an error has occured in the script on this page. Line: 1136 Char: 59 Error: the operation attempted to access data outside the valid range code: 0 URL: https://console-xlyfethvvn.lmi-app22-02.logmein.com/htem/htem_all.js Do you want to continue running scripts on this page? yes or no. does not make any difference what option you select. however, if we go via the loginme website and selecting command prompt it works with no issues. Does anyone have any suggestion on how to fix this?2.5KViews0likes7CommentsIs it possible to create a new plan with failed endpoints on a previous task?
I have a task to upgrade software for 400+ endpoints. The task failed on 100+ endpoints. I found myself creating a new plan and selected all endpoints, then deselected the successful 100+ endpoints. This is very tedious. Is it possible to run a new task on the failed endpoints? Preferably, running a new task for the failed endpoints (or offline endpoints) is ideal. Giving an option to rerun failed tasks found in History would be nice, too.529Views1like0CommentsLogMeIn Client Bug After Forced Password Resets
After the forced password resets last week, a couple people in our organization were getting the following message: Turns out to be something related (at least from what I can tell), to the "I trust this device. Keep me logged in." checkbox when first opening up the client. Had to go into options, delete all stored login credentials, then uncheck the box for trusting the device, for these users to be able to use the program again.Solved3.9KViews1like19CommentsMouse issues and Dual Cursors
over the last couple days, i have a few users complain that they have been having issues with their mouse cursor either not showing, disappearing or in some cases showing multiple mouse cursors. Has anyone else experienced similar issues and have a permanent fix for them? I think if i have the users check the box for Lock the keyboard and mouse on the logmein toolbar that seems to help.1.2KViews0likes1Comment