Why could an Orchestrator Runbook activity not be used for this? It could be invoked as an embedded task sequence step which would not have any sensitive credentials associated with it. The Orchestrator Runbook could also have security associated with it to prevent users without permissions from viewing its contents.
Thanks, ________________________________ Mark Mears [email protected]<mailto:[email protected]%0d> Phone: (757) 945-2651 [cid:[email protected]]<http://www.cireson.com/> [cid:[email protected]]<http://twitter.com/teamcireson> Check out our System Center App Store: www.cireson.com/app-store ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Thursday, January 23, 2014 10:30 AM To: [email protected] Subject: RE: [MDT-OSD] Remove Computer From AD I think the reason that a web service is more ideal, is because you might otherwise have to embed highly sensitive credentials into a client-side PowerShell script. Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Thursday, January 23, 2014 10:25 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Remove Computer From AD What options are there to remove a computer from AD prior to running a bare metal on it? I know a webservice is one option but I was wondering if there's anything easier. ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
<<inline: image005.png>>
<<inline: image006.jpg>>
