OK, let me back up a second and see if we can clarify a few things. Are the following correct?
1. Are you using ConfigMgr to do a build and capture of an OS image? 2. Is your build and capture is performing a domain join during the image process? 3. Each time you are running the build and capture, are you initiating it from WinPE (CD/USB media or PXE) or from Software Center? 4. Are you importing the captured image and deploying it with a separate task sequence? 5. For imaging of existing machines, is the Task Sequence being initiated from WinPE or from Software Center? 6. For new machines, how is the imager being prompted for a computer name to populate the OSDComputerName variable (and at what point in the process)? Sorry for all of the questions, but something isn't adding up so I'm trying to get a better understanding of your overall OSD process. Also, can you send the setuperr.log and netsetup.log files (with sensitive info redacted of course)? -Phil From: [email protected] [mailto:[email protected]] On Behalf Of Taxter, Latisha Sent: Wednesday, April 9, 2014 7:55 PM To: [email protected] Subject: [mssms] RE: mssms: OSD Capture image I do have a network access account. Its not locked out. Its joining build and capture images to the domain with the names that were on the computer previously. Its just this capture media task image that's causing me grief. I am assuming that the not joining to the domain had to do with the old name being on the domain before and maybe the network access account needs to be a domain admin. It works fine on other builds. Its not in the computers OU. Setuperr.log has net joindomain failed error code is 5. I'm more concerned with the computer name being the same as it was imaged with. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Wednesday, April 9, 2014 4:41 PM 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.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
<<inline: image005.jpg>>
