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.
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.
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.
Ok, I went back and checked a bunch of clients where I was NOT logged in with an active profile through Logmein (unlike the tests) after running the job, and it seems to have worked. I didn't audit the entire network, but I'll say, THANKS for the script. I think this will do EXACTLY what I wanted!
Can anyone suggest a way to use one2many to silently uninstall LogMeIn?
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.
- Well, the first two client tests it prompted me (but I was also remoted into the machine to see the desktop, so maybe that's it)...
I may have spoken too soon, as when I logged into other machines after pushing it out to a larger group (a few dozen machines) AFTER the job finished, I didn't see any interaction prompts.
I may have just applied it incorrectly, so I'll keep playing with it. If I find something (including me being silly) I'll post details, until then, just disregard my post.
