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.
User Profile
joelasaro
Active Contributor
Joined 12 years ago
User Widgets
Contributions
Re: One2Many Script Repository
Yes, it is criminal that LMI hasn't added powershell. Frankly, I haven't seen any development improvements in One2Many. Makes you wonder what they are spending all the money from their constant price increases on! I have ended up implementing most of my scripts in vbs or batch to keep it simple. I do feel like I have done a powershell script in the past through One2Many, but I can't find it now so maybe I didn't. One thing to note is that the commands are going to run as the user account you give LMI Central to use on that computer. Are you testing on the same computer and using the same account? Also, I would google for running powershell from the commandline or from a batch file. It looks like there might be some helpful resources on Stackoverflow for that.12KViews1like4CommentsRe: One2Many Script Repository
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.19KViews0likes1CommentRe: One2Many Script Repository
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:9020KViews0likes0CommentsRe: One2Many Script Repository
Lol. It really shouldn't be that tough to do the uninstall, though I confess I haven't tried it. Basically, you would write a batch file to do the unistall. I would probably try an msiexec unistall command or maybe wmic. The trick I think would jut be to use One2Many to write this as a .com file and then use the start command to kick it off like the upgrade script previously discussed in this thread.23KViews0likes8CommentsRe: One2Many Script Repository
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.23KViews0likes12CommentsRe: One2Many Script Repository
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.cmd20KViews1like14Comments