Sorry, just curious here, why and what’s the difference? J
From: <[email protected]> on behalf of Brian McDonald <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, December 13, 2016 at 4:54 PM To: "[email protected]" <[email protected]> Subject: [MDT-OSD] Re: Create Computer AD Object in MDT 2013 Stand Alone TS In my environment, I have a requirement that the computer account MUST exist in AD before we image/deploy a server. ________________________________ From: [email protected] <[email protected]> on behalf of Sean Chapman <[email protected]> Sent: Tuesday, December 13, 2016 3:01:56 PM To: [email protected] Subject: [MDT-OSD] RE: Create Computer AD Object in MDT 2013 Stand Alone TS I have it built in to my customsettings.ini. Im sure it can be added to a TS if you would rather do it that way. I removed my identifiable info and pasted it here JoinDomain=domain.com DomainAdmin=domainadminname DomainAdminDomain=NTFS_DomainName DomainAdminPassword=Password MachineObjectOU=OU=OUNAME,DC=DOMAIN,DC=com From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Tuesday, December 13, 2016 2:25 PM To: '[email protected]' Subject: [MDT-OSD] Create Computer AD Object in MDT 2013 Stand Alone TS Everyone, I'm looking for a solution to add/create computer accounts for server builds when using MDT TS. There doesn't appear to be any built-in functionality natively to allow this. I'm looking to see if anyone has attempted to automate this in a task sequence and how they have achieved this. Thanks, Brian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The information contained in this communication and all accompanying documents from Coilcraft may be confidential and/or legally privileged, and is intended only for the use of the recipient(s) named above. If you are not the intended recipient you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance on the contents of this transmitted information is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and destroy the original message or accompanying materials and any copy thereof. If you have any questions concerning this message, please contact the sender.
