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