Yes I did point the engineers to your blog entry that stated this http://www.petervanderwoude.nl/post/using-the-power-of-orchestrator-to-move-a-computer-to-a-different-ou-via-configmgr-2012/
Specifically Prerequisites In this post I want to show this new feature by creating a runbook for, an often requested script, or step, to move a(n existing) computer to a different OU. For the rest of the post the following points are prerequisites: - A Microsoft Deployment Toolkit 2012 Update 1 –package. This package contains the necessary scripts to execute a runbook during a task sequence. - The Nework Access Account needs to be “Orchestrator User”. By default the *Execute Runbook* –step will use the credentials of the Network Access Account to connect with Orchestrator. - Register, Deploy and Configure the Active Directory IP <http://scorch.codeplex.com/releases/view/88949> from Ryan Andorfer <http://www.codeplex.com/site/users/view/randorfer>. I used this one, because it was easy to set up and, even more important, it works (even with Orchestrator 2012 SP1 BETA)! - The account used in the Connection Credentials needs to be at least member of the Account Operators –group in the Active Directory (AD). Otherwise it can’t move an object in the AD. Let me check the info supplied and get back to them to discuss. Thanks for the info Peter and I'll update later. Cheers Paul On Thu, Aug 28, 2014 at 10:50 AM, P.T. van der Woude < [email protected]> wrote: > Out of memory, I thought the users has to be a member of the Orchestrator > Users group. > > > > Here are a couple of links that should help: > > · How to Install an Integration Pack: > http://technet.microsoft.com/en-us/library/hh420346.aspx > > · System Center Integration Pack for System Center 2012 > Configuration Manager: > http://technet.microsoft.com/en-us/library/hh967537.aspx > > · Orchestrator Security Planning: > http://technet.microsoft.com/en-us/library/hh420367.aspx > > · Deploying System Center 2012 – Orchestrator: > http://technet.microsoft.com/en-us/library/hh420337.aspx > > > > Peter > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Paul Winstanley > *Sent:* donderdag 28 augustus 2014 11:36 > *To:* [email protected] > *Subject:* Re: [mssms] SCOrch connection to ConfigMgr > > > > Cheers Peter. > > > > I'm actually asking the wrong thing here. Bear with me - noob to SCOrch! > > > > The permission question actually relates to the service account required > when installing the SCOrch integration pack. Any technet articles or > tutorials out there? > > > > Thanks > > Paul > > > > On Thu, Aug 28, 2014 at 10:25 AM, P.T. van der Woude < > [email protected]> wrote: > > Hi Paul, > > > > That completely depends on what activities you want to perform through the > connection. > > > > Regards, > > Peter > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Paul Winstanley > *Sent:* donderdag 28 augustus 2014 11:19 > *To:* [email protected] > *Subject:* [mssms] SCOrch connection to ConfigMgr > > > > Hi. > > > > Can someone please advise the rights required for the service account when > connecting to ConfigMgr through the SCOrch Runbook designer (as below)? > > > > Thanks > Paul > > > > [image: Connection Settings 02] > > > > > > > > > >
