The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
KevinA
16 years agoRetired GoTo Contributor
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. ...
- 8 years ago
https://github.com/knix15/LogMeIn-One2Many-Community-Scripts/
Scripts can be found here as well for better future organization.
GeorgeK78
10 years agoNew Contributor
Hi all,
I don't know if I'm missing something glaringly obvious with the One2Many functionality, but, in my searches in the forums, I found exactly one post about running Powershell scripts through One2Many.
With PS being such a powerful scripting language, I'm surprised that we're still sticking with batch and vb scripts to perform certain tasks.
1- I would think that LMI should include running native Powershell scripts directly from the task setup pages within Central.
2- Have some guidance as to how to easily trigger and run a Powershell script on Windows.
So far, I have been unsuccessful. Would anyone have a specific way that worked for them for running a PS script? (including the specific command lines)
I have tried certain ways of triggering it, using a custom command, with something like this:
"C:\Windows\System32\WindowsPowerShell\v1.0\Powershell.exe" -ExecutionPolicy RemoteSigned "C:\Scripts\ControlCPU_wuapp.ps1" where the Powershell script is in that location (c:\scripts).. but I keep getting run failures, even though the script runs just fine when ran on the server workstation itself.... so, looking for guidance if anyone has any?
Thanks all!
Beep-Beep
10 years agoActive Contributor
For one-liners, I get around set execution policy on PowerShell scripts by using the command:
powershell "put command here"
Watch out for commands that use double quotes though.
Example:
powershell "(Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -eq 'Some Name Here' }).Uninstall()"
What One2Many really needs is the ability to chain tasks sequentially. I know you can just send a script with complex logic but if you already have the individual pieces as tasks, it would be nice to be able to just chain those together.
- bsimon5044 years agoActive Contributor
I'm here 6 years later and am wondering if I'm just missing this functionality or if it's still not available.