OIS - Integration Pack for PowerShell Script Execution 1.00

re: OIS - Integration Pack for PowerShell Script Execution 1.00

Ahmed Adly — Mon, 25 Mar 2013 11:24:39 GMT

Hello Charles,

Thanks for the wonderful integration package

Actually we are using v1.1, and we are implementing a solution in an enterprise enviroment that consists of thousands of subsites.

I'm writing a script to iterate on all subsites to get some data, it takes pretty long time, is there any way to make some kind of progresss bar.

This command as u know (Write-Progress -Activity) is responsible for this,but how can it be appeared while I'm running my Orchestrator Runbook.

Regards

re: OIS - Integration Pack for PowerShell Script Execution 1.00

Ibrahim — Mon, 28 Jan 2013 13:44:26 GMT

Is there a way to specify a ‘run as’ account?

re: OIS - Integration Pack for PowerShell Script Execution 1.00

Michael — Thu, 07 Jun 2012 03:19:29 GMT

Thanks for the great tool. One question though. Is there a way to specify a ‘run as’ account? I need to run a script with admin rights and I’ve specified an account in the ‘Execute PS Script’ options. But that account only seems to be used to connect to the target computer and not to run the script. Am I missing something?

re: OIS - Integration Pack for PowerShell Script Execution 1.00

Armand Campo — Fri, 18 May 2012 02:17:10 GMT

Hello Charles. Great stuff! I'm hoping\assuming this IP helps get around the whole SCORCH=32bit Exchange etc 64bit Powershell comandlets issue etc correct? I'm speaking specfically to this issue: social.technet.microsoft.com/.../53d58dce-d4d4-41f1-bb88-37be4d424c7e

I believe I've installed the IP sucessfully & have the config correct as I no longer receive any errors about connectivity when running in the tester but alas while the runbook completes with out error nothing is actually happening.

Let me explain what I'm trying to do; very simple PS script to set FullAccess perms on an Exchange mailbox. the alias of the mailbox and the person needing access are inputs to the PS script via the published data in the bus. It runs fine, but nothing happens and I know the scipt is exactly perfect because it runs in PS fine. Is this still the 32bit vs. 64bit debacle above perhaps yet its somehow not producing an error?

We were able to find a different workaround using the following in a PS script using the .Net object:

$ErrorActionPreference = "Stop"

C:\Windows\Sysnative\WindowsPowershell\v1.0\Powershell.exe `

-NonInteractive -Command {Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin

Add-MailboxPermission -Identity User1 -AccessRights FullAccess -User User2}

The above is from this article: www.purgar.net/using-exchange-2010-cmdlets-in-system-center-orchestrator

Lastly...any idea when MS will simply make SCORCH 64bit? It seems ridiculous that it was recoded from Opalis 6.3 to 64 bit in the first place yet it's full power using the .Net object is really limited due to this architecture mismatch. Many thanks!!!

re: OIS - Integration Pack for PowerShell Script Execution 1.00

Kevin Verhoeven — Tue, 15 May 2012 21:14:09 GMT

Nice job Charles, I love the IP! I have one question. If the PowerShell script fails, like in your VMM PowerShell Snap-in example above, why wouldn't the object fail?

Thanks!

re: OIS - Integration Pack for PowerShell Script Execution 1.00

Charles Joy [MSFT] — Thu, 14 Jul 2011 19:40:40 GMT

a) Yes

b) This sounds like a configuration issue with one of the objects generating multiple values, which downstream objects have to execute individually (one of the rules of pipeline runbook execution). Please refer to this: www.youtube.com/watch. Looping does not occur unless explicitly configured. If nothing else works, you can create two separate workflows, one for each object, and then have another workflow call those sub-workflows sequentially.

re: OIS - Integration Pack for PowerShell Script Execution 1.00

Dung K Hoang — Mon, 11 Jul 2011 16:58:07 GMT

Thanks for a very convenient IP for PowerShell. Just 2 quick comments:

a) Can I run a PS script instead of typing the code in the windows? I assume that the answer is Yes.

b) I notice that when I added 2 PS scripts in the pipeline, the last one goes into an endess loop.

The PS code in those activitites ( objects) are exaclty the same. If there is only one object, the workflow stops correctly.

Any hint?