Yeah, we simply won’t move it to the OU you specified, but the domain join will work assuming the appropriate permissions are there.
I’ve seen some interesting permissions/restrictions against computer objects by some people, where you can’t update an existing object, etc, those types of things will certainly cause a failure. Chris Nackers Microsoft MVP – Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected] [mailto:[email protected]] On Behalf Of obrien.david Sent: Thursday, April 10, 2014 2:13 AM To: Ben Glenz; [email protected] Subject: RE: [mssms] RE: mssms: OSD Capture image If it already exists in a different OU then whatever you configure is just being ignored. Domain join will work. At least that is how it's always been in those environments I worked in. That's why you usually have some process that moves the account into the correct OU. David Sent from Samsung Mobile -------- Original message -------- From: Ben Glenz Date:10/04/2014 16:57 (GMT+10:00) To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: mssms: OSD Capture image Exactly David. If you leave it blank it will point to the default Computers OU set in AD (remember, this can be changed starting with AD 2008) However, if the Computer Account already exists in AD and you set the TS to a specific OU where the Computer account is not already located at the Domain Join will fail. Ben From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David O'Brien Sent: Donnerstag, 10. April 2014 01:57 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: mssms: OSD Capture image Shouldn’t leaving it blank default to the Computers container? I just think you can’t point it to Computers directly. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Thursday, April 10, 2014 9:41 AM To: '[email protected]' Subject: [mssms] RE: mssms: OSD Capture image Have you specified an OU in your task sequence under the Apply Network Settings step? This can’t be blank otherwise the domain join will fail, also can’t be set to the Computers container. Have you specified a network account / verified it’s not locked out and that a network account has been specified within SCCM and verified that the password is set correctly? Sounds like it’s not even attempting to join the domain with your variable set by the collection. The logs Phil mentioned will confirm what’s happening. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Taxter, Latisha Sent: Thursday, 10 April 2014 9:24 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: mssms: OSD Capture image I am re-imaging existing machines. New ones will have the OSDComputername variable to allow them to enter the name when they deploy. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Wednesday, April 9, 2014 4:20 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: mssms: OSD Capture image Sysprep should indeed do that. I would check the setuperr.log and netsetup.log files on the machine to see what errors are being generated during the process. As far as the names going forward, is there a particular naming convention you are looking to implement? There are several options to automate the naming depending on what the convention is. Also, when you say “pushing this out to a group of computers” are you reimaging existing machines or new ones? -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Taxter, Latisha Sent: Wednesday, April 9, 2014 6:38 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: mssms: OSD Capture image I have an osdcomputername on the unknown collection, but if I am going to be pushing this out to a group of computers, I want to automate it and not have to touch each computer to set the name. I thought sysprep was going to get rid of the name on the capture. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Wednesday, April 9, 2014 3:31 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: mssms: OSD Capture image How are you setting the computer name during deployment? -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Taxter, Latisha Sent: Wednesday, April 9, 2014 6:25 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] mssms: OSD Capture image I created an OSD capture image using the capture media task sequence. Reference computer was joined to workgroup with blank admin password. However, when I deploy it, it comes down with the name it originally had and does not join the domain. I looked up several articles and can’t see what I am missing. What do I need to do to fix this? Thanks. Latisha Taxter Server Administrator III Kootenai Health 2003 Kootenai Health Way Coeur D’Alene, Idaho 83814 • 208-625-4192 È509-953-9085 [email protected]<mailto:[email protected]> http://www.kh.org [cid:[email protected]] Confidentiality Statement: The contents of this email and any attachments are confidential. They are intended for the named recipients only. If you have received this email in error, please notify the system manager or the sender immediately and do not disclose or provide copies of the contents to anyone. ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
