![]() We also have GotoAssist and that works just fine, it's just LogMeIn Rescue Console. 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. But you know Win10, it will NOT let you stay with the previous version for more than 7 days. I rolled it back to the previous version and it works fine. ![]() 1002 (rs5_release) was installed, Rescue Console will try to start, then immediately close and give me the crash screen. Anything should work, as long as you can create a permanent spoof entry to make believe you are running Windows.Īnd that’s all there is to it! I’m not a power-user, but I’ve used it several times now to help remote users and the desktop control works great.Since Windows 10 Insider Preview 10. It won’t launch when called via xdg-open otherwise, and I’m damned if I know why.Īlso, be sure to ‘chmod +x ~/bin/logmein’ to make it executable!įinally, you just need to install a user agent spoofer. Make sure you specify wine64 and not just wine. This batch file modifies the URL into the parameters expected by the executable. WINEDEBUG=-all exec wine64 LMIRTechConsole.exe $url Url=$(echo $url | sed 's/%22//g') # The exe counts on the shell eating the quotes, so don't pass them - even as real quotes. Url=$(echo | sed 's/^lmidtc:\(.*\)/\1/' ) # Chop off protocol identifier ![]() # The web protocol handler URI is just a list of parameters for the executable I put this in my ~/bin/ directory so that it will be in my path:Ĭd "/home/evil/.wine/drive_c/Program Files (x86)/LogMeIn Rescue Technician Console/LogMeIn Rescue Technician Console/LogMeInRescueTechnicianConsole_圆4/" X-scheme-handler/lmidtc=sktopįinally, let’s create that ‘logmein’ batch file we referenced in the desktop entry. Next, update the file ~/.local/share/applications/mimeapps.list and add the following line to the end: Using nano, or some other editor of choice, create the file ~/.local/share/applications/sktop and put the following in it. Install a user-agent spoofer so that you can masquerade as Windows on the LogMeIn site so that they don’t redirect you to “Unsupported Operating System” when you attempt to use the SSO launcher.Not just so you can easily run the technician console from the terminal, but so that you can re-write the parameters from xdg-open to the format needed by the executable. Not just so you can easily launch the technician console from your desktop launcher, but so that you can get the correct mime-type associations needed by xdg-open. Here are the things that need to be done: This is about how to get the SSO integration working, even though the LogMeIn site doesn’t normally allow it. This is not about copying those directories, as that’s fairly mundane. If you install it on a Windows system (or Windows VM), you can copy the two directories it creates in Program Files to a WINE prefix and run it without issue! However, the problem is only with the installer. While experimenting with the LogMeIn Technician Console a few weeks back, I was sad to discover that the installer did not work with WINE.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |