One2Many Script Repository

Remote Command Type Task to unnistall.

cd c:\program files\logmein\x86

logmein uninstall

shutdown -r

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. 

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.

Hi all, I've been using the following script to update the Logmein client via One2Many.

@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
start lmiupdate.cmd

This was updating in Logmein client using a version prior to 5208 up to version 5208. Now version 5220 is available, but the script is not updating clients using 5208 to 5220. However, client's using a version before 5208 are being updated to 5220 using the script above. All that being said, any ideas why this might be occuring? Any input would be GREATLY appreciated!

Hi everyone,

I need to change the license keys of AVG business antivirus for all my users (about 120). We don't have a local or virtual domain and all are users are local admins. The best we have is LogMeIn :).

I'd like to create a script to update the licenses for our users. I'm not very script savvy so any information definitely helps. 

THANKS

I haven't done this before, but that is an interesting idea.  Scripting this looks like it would be pretty easy.  I would recommend taking a look at this page (scrolll down) for some example of what you can do with the local security policy via commandline using the "net accounts" command.

http://www.thewindowsclub.com/customizing-the-password-policy-in-windows-7

I think this would just be running the following command directly via One2Many or making a batch file to do it:

net accounts /maxpwage:90

We don't have a local or virtual domain. Our users are all local admins. However, I'd like to push a script that will enforce a password change policy of every 90 days, they must reset their password to their local user account. Any advice or scripts you can share?

Looks like wmic is the way to go.

bat file looks like this:

wmic product where name='LogMeIn' call uninstall

Setup the task as "Run a batch file or executable" and no Optional parameters needed.

Make the plan and then run it with an account with admin privileges. 

Of course it will look like the plan never completes since LogMeIn will not return a "completed" command, since it will then be uninstalled. However, if you check your computer list, it will be gone.

Looking to see if I can use wmic. Will report back