The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

KevinA's avatar
KevinA
Retired GoTo Contributor
16 years ago
Solved

One2Many Script Repository

Welcome to the LogMeIn Central Script Repository!   What is it? A library of scripts to help you execute automated tasks and manage LogMeIn Pro² computers without having to access them manually. ...
atilley's avatar
atilley
New Contributor
11 years ago
Also, I believe credit for this script is due to joelasaro, from this very thread :).
joelasaro's avatar
joelasaro
Active Contributor
11 years ago

Thanks, but to be fair I just reposted what I had scrapped from other places like spiceworks and this random LMI page: /html/assets/UpdateLogMeIn.txt

 

Now to your question, this process of updating from the command line (what the batch file is doing) has always been a bit inconsistent for me.  It definitely doesn't seem to work as consistently as doing the update form the GUI of the LMI client.  That said, I just ran the script (I haven't run it in a while as I haven't had a real need) and it is definitely updating at least some LMI endpoints to the latest 5220.  I think you may have to just be patient with it.  I vaguely recall a support ticket I opened once about this where I was told something to the effect that LMI pushes the latest updates out incrementally and not to all instances at once. 

 

Hope that helps.  Sure which LMI would just build what I feel is very basic functionality for an RMM tool into the package and we could skip this stuff.

  • atilley's avatar
    atilley
    New Contributor
    11 years ago

    Thanks, I appreciate your input! This is kind of what I expected, I've noticed something like this in the past when updating the Logmein client.