Problem

135 Topics

MacOS: A keychain cannot be found to store....
Hi Lately, I've been having a lot of issues with LMI rescue unattended access and MacOS. I am receiving a window stating a "Keychain not Found" with the error: A keychain cannot be found to store "1:424688513186:ios:HexidecimalNumber_FIRAPP_DEFAULT" This occurs on Mac's that have previously had unattended access installed, on new installs and on clean installs of 10.12, 10.13, 10.14, 10.15 & 11.4. Resetting the keychain to default does not resolve the issue. Clicking on the cancel button results in another window being shown with the same error. Clicking on cancel again closes both the windows. I can log in as normal by either closing the error windows, or ignoring them.
Solved
InterpretIT
5 years ago Place Rescue Discussions
54KViews
0likes
4Comments
Mac OS Big Sur compatibility issue
With Mac OS 11 I can control the the Screen of the remote Mac, but when I click on the File manager Logmein crashes. Any Help would be greatly appreciated.
Solved
jcaustin
6 years ago Place Rescue Discussions
20KViews
1like
61Comments
Difficulty controlling client's OS X Catalina
Hello, When I remote control a customer's mac running macOS Catalina, I can see background, top bar and LMIrescue window but I can't see all other windows on Mac. In June, before the last macOS Catalina update , your article How-can-I-remote-control-a-customer-s-Mac-running-macOS-Catalina worked well for Catalina. But now, when I go into Systeme Preferences > Security & privacy > all LMIrescue are checked in Accessibility/ Full disk Access/ Screen recording but it doesn’t work. The customer cannot uncheck to recheck Lmirescue. The only thing possible is in Accessibility > "+" > Download > select Supportlogmeinrescue > Open and there I can move the mouse, click everywhere but I still do not see the windows as if Screen Recording does not work. Same thing after restart the Mac, customer's account is in Admin. We use Lmirescue in my company, latest version of the technicians console on MAC and Windows, it works for remote control on windows and MAC before Catalina. It’s hard for us not to be able to take control on Catalina. Do you know the case and have a solution? Thanks for your assistance
Solved
Letech
6 years ago Place Rescue Discussions
18KViews
1like
28Comments
Rescue Console won't run under Windows 10 Insider Preview 10.0.17713.1002 (rs5_release)
Since Windows 10 Insider Preview 10.0.17713.1002 (rs5_release) was installed, Rescue Console will try to start, then immediately close and give me the crash screen. I send the report to Logmein. I rolled it back to the previous version and it works fine... But you know Win10, it will NOT let you stay with the previous version for more than 7 days... So I updated every driver, made sure the software was updated...Figured it was the best I could do before letting it update to the latest Win10 Insider Preview again, but after I did... It stopped working. We also have GotoAssist and that works just fine, it's just LogMeIn Rescue Console. So, I installed it on another PC and it works fine on there also, UNTIL Windows 10 Insider Preview 10.0.17713.1002 (rs5_release) gets installed. So while, yes, I can roll it back and get it to work, it'll only be a short time until this release is pushed out to everyone and will be a major issue. Has anyone else ran into this, or have ideas? I've submitted it to LMI and Microsoft, but no response from either.
Solved
garybarr
8 years ago Place Rescue Discussions
9.5KViews
0likes
15Comments
Windows Defender Firewall issue
Hello, Remote users are getting a Windows Defender Firewall prompt about the Rescue applet when I start a connection. Hoping you can guide me to a fix. Here are the details... Users have an AD-joined local account with no admin permissions. They download and run the applet with the 6 digit pin as normal. I'm putting in the local admin password at the Rescue connect screen and elevating the session. When that connects, the user gets this pop-up, The path is c:\users\[username]\appdata\local\logmein rescue applet\lmir0f138001.tmp\lmi_rescue_srv.exe So it's actually a different temp folder path for the applet every time. I want to allow both public and private networks - they're working remote and I have no idea what type of connection they are on. I can actually get connected to their screen, but the pop-up is generating questions from the users, and if they hit Allow it goes to their local machine's UAC which I can't see and it disrupts my connecting. So question 1 is what are the firewall rules I want to create? Question 2 is do you have any advice on deploying such rules through InTune in this case where the applet folder is particular to the user? I've had troubles in the past establishing those types of rules because InTune only wants to manage rules for known paths like Program Files and doesn't seem to have a way to vary the path with a local user account. %appdata% resolves to the InTune admin user, not each local user. (If this part is outside this scope I'll take it to a Windows InTune forum once I know the details of the rule I want.) Thanks
Solved
Chris42
5 years ago Place Rescue Discussions
9.1KViews
0likes
7Comments
Can't control Mac client
When I am providing support for some of my Mac users, I am completely unable to control their computer. This only happens on machines that have already given LogMeInRescue permission to control the computer in a previous session. In the past I could just have the user go into the System Preferences privacy setting and uncheck the box for LogMeIn then re-check it. But now they can't uncheck it at all. This results in me not being able to remotely control their Macs and we end up having to use another product (Zoom or Skype screen sharing). They are all on the latest version of macOS 10.14.6 Mojave. Any advice is appreciated. Thanks.
Solved
DJRizzo
6 years ago Place Rescue Discussions
8.5KViews
1like
5Comments
Black screen when using remote control on RDP connection to Windows Server 2016
Our end users log into terminal servers via RDP. When we use LogMeIn Rescue, the remote control will typically start with a black screen (not always but it happens almost every time). I can see their cursor moving around but the screen is black. We can get the black screen to stop by ending remote control and launching remote control over and over again until it finally works. This only happens when we are remote controlling an RDP session, other Windows hosts work 100% of the time. We've tried changing the color quality but it doesn't appear to solve the issue. Mouse moving on customer session: Relaunching remote control to fix it:
Solved
diggio
5 years ago Place Rescue Discussions
7.4KViews
0likes
7Comments
Unable to login into the client software of Log me in Hamachi
Hi, I am unable to login to the client software of Log Me In Hamachi as there is no Captcha showing up and the software is telling me fill the captcha I don't know what to do I Need Help!!!
Neelay
8 years ago Place Rescue Discussions
7.2KViews
0likes
5Comments
Alert Sounds not working
I'm running version 7.12.3325 64bit and the alert sounds no longer work for one of my LogMeIn accounts. I have two accounts. I have all the sound alerts checked. Tried turning them off & back on. I've also done a reinstall of the software. I've reinstalled Windows 10. I got a new hard drive the other day (not because of this issue) and have a clean install of everything on there & still no sound alerts from the one account. Any ideas on why that would be happening? Any help would be much appreciated. Thanks, Gary
radicaltype
8 years ago Place Rescue Discussions
6.9KViews
0likes
12Comments
Invalid Administrator username or password. Error code (1722)
Hi everybody, my name is Piero, from Florence (Italy) I am having a connection problem (Invalid Administrator username or password. Error code (1722)) trying to connect via Logmein Tech Console (v. 7.12.3306 64 bit) from my pc to a host pc on a different domain. When I receveid the connection dialog to insert user&password, i try to use a local admin user of the host pc but i received: [2018-05-10 4:24:28 PM] Starting session on device 10.20.35.21... [2018-05-10 4:25:27 PM] Invalid Administrator username or password. Error code (1722) The user&password of the remore pc is correct, so i tried to do the same starting from a different pc (with same version of Logmein Tech Console) which is in the same domain of the host pc and this time it works, i can connect inserting user&password (as done before) Tried with and witout proxy settings (just to be sure). Did you get any cross domain connection error like this in your Logmein usage? Thanks Piero
pbugiani
8 years ago Place Rescue Discussions
5.9KViews
0likes
6Comments