GeorgeK78
New Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: One2Many Script Repository
Thanks Joe. I have ran plenty of Powershell scripts from batch files, I even have a vb script I use for Powershell scripts in the task scheduler: set arg = Wscript.Arguments command = "powershell.exe -nologo -command " & Wscript.Arguments.Item(0) set shell = CreateObject("WScript.Shell") shell.Run command,0 That works fine in Scheduler.. but not sure about the syntax in LMI. I guess I'll try it. As for the user running the script. the LogMeIn service runs as LocalSystem, and the scripts that I typically run, are system related... as in, controlling a service if it meets certain conditions, etc ... so I'm not sure that this is really user dependent? (unless of course, I misunderstood what you were stating) p.s: I completely agree with you regarding the developments on One2Many. I'm really not that impressed. I honestly think that having more functionality with One2Many would've been more important than having a whole Anti-Virus section, which, frankly, doesn't do a lot more than previously. Cheers!12KViews0likes3CommentsRe: One2Many Script Repository
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!12KViews1like7Comments