LogMeIn and Legacy Architecture

Sean_K

With the ever-evolving software landscape, we have found the need to update our coding methodology.  This comes at the price of backwards compatibility related to legacy architectures. After much discussion, we, like Microsoft, have decided to freeze support for all Processor Architectures that do not support SSE2 or better.  This applies to any processor made approximately 10 years ago, or older.

 

While this will only impact a small (and shrinking) subset of devices in market, we recognize it could be upsetting to a segment of our user base. However we here at LogMeIn are committed to bringing the best presentation to our customers that we can.  In gardening, this includes pruning the older, dying branches. However, unlike gardening, we are still providing you a version that will work.  At the bottom of this post is version 2700, and it is the last version, barring critical updates, that will support this older hardware.

 

It will not answer to new updates, and will not be provided a new feature set.  The only time we will update this, again, is if there are critical issues that must be addressed. 

 

Thank you all for your time.

 

https://secure.logmein.com/LMI4012700nh.msi

STick170

Just in case it helps anyone else, here’s how I got my Server 2000 machines working again, I had no experience in the use of certificates so I found the GlobalSign instructions too vague for me and wasted lots of time trying to import the certificate into the LogMeIn service to begin with.  Big thanks go to DannyMichael for the tip on exporting from a Server 2003 machine!

 

On an updated XP/Server 2003 machine with LogMeIn working correctly:

 

1. Click Start > Run, type MMC.

2. On the Console 1 window, Click File > Add/Remove Snap In...

3. In the Add/Remove Snap In window, click Add.

4. In the Add Standalone Snap In window, select Certificates and click Add.

5. In the Certificate Snap In window, select Computer account and click next.  Then select the Local Computer option and click Finish.

6. In the Add Standalone Snap In window, select close.

7. In the Add/Remove Snap In window, click OK.

8. In the Console Root, expand Certificates (Local Computer), then expand Trusted Root Certification Authorities (Second one down) and highlight Certificates.

9. In the list of installed certificates, scroll down to find GlobalSign Root CA, there are two, make sure you highlight the one that expires 28/01/2028.  Right click it, select All Tasks > Export.

10. In the Wizard, click Next twice then enter a file name (I used GlobalSign Root CA) and select Browse to find a suitable location to save the certificate (I used a network drive), click Next again and Finish.

11. Exit the Console 1 window, discarding the changes.

 

On the affected Server 2000 machine:

 

1. Click Start > Run, type services.msc.

2. Find and stop LMIGuardianSVC, LogMeIn and LogMeIn Maintenance Service.  I’m not sure if these are all necessary or not.

3. Follow steps 1 to 8 above, there may be a few small differences between Server 2000 and 2003 but nothing major.

4. Right click on the Certificates folder, select All Tasks > Import.

5. In the Wizard, click next and then Browse.

6. In the Open window, before navigating to the exported certificate, change the Files of Type to X.509 Certificate (*.cer, *.crt), then browse to your saved certificate and click Open.

7. Back in the Wizard, click Next twice and Finish.

8. In the Import Successful window, click OK.

9. Exit the Console 1 window, discarding the changes.

10. Back in Services, start the three LogMeIn services and close the window.

11. Keep your fingers crossed and LogMeIn should appear in the system tray and show as Enabled and Online!