You need to create a separate task sequence that is designed for creating an image for duplicating. This is similar to giving an OEM an image to apply to computers before being sent to the your end user. You need to enable MDT integration or just do it with MDT. I like using pure MDT because it's a little cleaner. Once you have created the image you'll capture it. You can then apply that image to a hard drive. A final MDT process will run on first boot of the computer. Here you can run LTI/ZTI processes such as set computer name, join domain, etc.
Take a look at these. It's more work but the better way. Happy imaging. http://blogs.msdn.com/b/alex_semi/archive/2011/01/18/creating-faster-oem-ima ges-with-osd-and-mdt.aspx http://technet.microsoft.com/en-us/windows/ee430892.aspx From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Wednesday, January 29, 2014 1:12 PM To: [email protected]; [email protected] Subject: [MDT-OSD] RE: Imaging Questions The CM client will detect the hardware change and generate a new GUID. Of course that's gonna foul things up in the database because there will be duplicate records for the machines for a little while. _____ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP _____ From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Wednesday, January 29, 2014 11:50 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [MDT-OSD] RE: Imaging Questions Yeah, I dunno about this. The GUID and MAC addresses will be new, but the computer will have an established SCCM account (and McAfee EPO and any other managementy type IDs or licensed software that gloms on to the GUID) that will get all fouled up. Maybe - best case, you would just end up with a bunch of duplicate system objects in SCCM that would clean themselves out over a few weeks. An old obsolete record from when the computer was in chassis A and then a new object for the same name in Chassis B. I am not sure what happens to your Windows license when it activates in one hardware and then finds itself in another machine - certainly the hardware GUID is going to change. Windows license sometimes gets lost when you swap a processor - let alone the whole system. Would you have to go through a rearm process or will Windows reactivate on the new hardware automatically ? I dunno. I'd think to the Windows licensing service this would look similar to piracy. (I'm not suggesting that it is piracy or illegal - clearly it is not. I just mean that to the automated systems it is going to look like you are licensing in one spot and then putting that Windows license into one or more new computers) Maybe if you ran a sysprep on the computer after imaging and before placing it in the new computer - that might work.. This sounds like a mess to me. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Wednesday, January 29, 2014 11:30 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [MDT-OSD] RE: Imaging Questions A better solution IMO would be to deliver the machine in which the drive was imaged to the user, remove their computer and recycle it. At the VERY least you are going to have to rename each machines (assuming your TS doesn't prompt for a computer name). Once the client sees that it's in a new machine it's going to generate a new unique ID and this is all probably going to wreak havoc on CM for a day or so. _____ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP _____ From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Barnes,Chris Sent: Wednesday, January 29, 2014 10:11 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [MDT-OSD] Imaging Questions Hey guys, I have a remote site that is wanting to deviate a bit from our standard imaging setup. They have 2012R2 Secondary site / DP local to them, using PXE, with the TS advertised to the Unknown Computers collection. They have a bunch of machines that they want to re-image from XP to 7 that are all the same model. What they want to do is to buy new hard drives, image that drive, take the drive out of that computer and put it in the destination computer. They then want to re-use the initial chassis to re-image another drive, and so on. To keep the TS available for unknown computers they will need to delete the newly registered client out of SCCM after each image, right? The client should re-register itself with the new MAC, I assume. I am not a big fan of this, but I may not have a choice in supporting it. I am trying to think of any issues that I may come up against that I will need to solve. Can anyone think of anything that might be a show stopper, or that I may need to watch out for? Chris Barnes Senior Technical Specialist - Penske Automotive Group <mailto:[email protected]> [email protected] Desk: (248) 648-2528 Cell: (248) 767-4415 _____ Penske Automotive Group and its affiliates will never sell or rent your email address in violation of applicable law. This email and any files transmitted with it are confidential and intended solely for use of the individual or entity to whom they are addressed. Please delete all copies if you are not the intended recipient. _____ 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. _____ 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. _____ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. _____ _____ 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. _____ 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.
