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
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. ...
https://github.com/knix15/LogMeIn-One2Many-Community-Scripts/
Scripts can be found here as well for better future organization.
Any chance of an updated script to update the LMI client? Apart from being badly written (goto's and even worse duplicate labels), it doesn't work - all it does is re-run the last downloaded update file which of course is what is already running. If anyone knows how to kick off the update check and download, I'll happily add it to my amended script and share it here.
Hello regarding how to Force the LMI Host to be updated on demand, I has been asking for that to Logmein Support since more that 2 years ago, but nothing.
Under Central should bea predefined task or a way to Trigger the Logmein Host update On-Demand for one or many Hosts at the same time, becuase I notice that not all our Host are udpated and we have 3723 Hosts:
- LogMeIn Host Software Versions
Number of Host --> Software Version
1--> 2504
2--> 2651
1--> 2694
8--> 3268
8--> 3430
5--> 3888
13--> 4132
2--> 4144
12--> 4306
9--> 4380
24--> 4400
2123--> 4408
200--> 4634
878--> 4652
717--> 4670
The issue with not being able to update the LMI client from One2Many or any built-in function is especially bad when there is a bug in version 4634 that causes high cpu usage constantly (svchost.exe process) and there is no way to automatically force clients to update.
I have automatic updates enabled for all the LMI Pro clients and still have about a third of them on 4634 instead of 4670.***Update:
I finally got to test the batch script for updating LMI and it seems to be working fine for me. I used a condensed version of the script linked in the first post of this topic that I found on spiceworks:
http://community.spiceworks.com/scripts/show/2544-logmein-silent-update-heartbleed-counter
I just saved this as a .bat file and uploaded into a One2Many "Run a batch file or executable" type script. When I run this the machine goes offline after a bit and stays offline for a few minutes and then comes backonline one LMI is updated. I have successfull update two machines so far this way with no issues. I upgraded from version 4634 to 4670.
Obviously, this functionality should be backed into LMI Central, but this is atleast usable in my experience so far. Below is the script from the SpiceWorks post that I used.
@echo off cd %TEMP% if %PROCESSOR_ARCHITECTURE% equ AMD64 goto amd64 echo cd "%ProgramFiles%\logmein\x86\update" > lmiupdate.cmd goto x86done :amd64 echo cd "%ProgramFiles(x86)%\logmein\x64\update" > lmiupdate.cmd :x86done echo raupdate.exe /s >> lmiupdate.cmd echo exit >> lmiupdate.cmd REM Now it'll run it start lmiupdate.cmd
This is great, and it worked fine on my clients...however, it does require user interaction. Something I'd rather avoid.
Considering the way Logmein is going, automatic update and install for the LMI client really should be a feature, or at least a job that can be done without user interaction.
Am I missing something?
- Englanddg -
What user interaction did you run into? For me it was pretty seamless. The /s with the raupdate.exe command should run it silently.
I have been having trouble getting the latest update that just came out to install. No errors just doesn't seem to be available for all my nodes yet. But I'll need to test more to be sure of what the issue is and it did work for a couple of machines so far.
