Sounds like a good candidate for a pre-staged image scenario. Here's some 
example steps: 
http://sccmguy.com/2014/08/15/creating-prestaged-image-using-configuration-manager-2012-r2/


Provide them the WIM that contains the first part of your task sequence, they 
deliver the PC's to a final location, someone unboxes, plugs into your network 
and resume with the second half of the task sequence (Join domain, SCCM client, 
domain apps etc) The second half of the TS you still control for app version 
upgrades, branding mods, SCCM client CU's etc.  The major vendors are already 
aware of the prestage process and giving them a WIM.

Providing them a fully baked image with everything in it means after 3+ months 
all your flash, readers, silverlight's, java's will be outdated leaving a 
period of time of vulnerability until updating catches up, still have to join 
the domain manually(or offline join) etc.


________________________________
From: [email protected] <[email protected]> on behalf 
of Daniel Ratliff <[email protected]>
Sent: Tuesday, December 15, 2015 12:10 PM
To: [email protected]
Subject: [mssms] RE: Creating an reference computer and having our vendor mass 
disk clone


You shouldn't ever join a reference image to the domain.



Any reason you can't do a complete build and capture? Automate the entire 
process and it will clean any GUIDs and such with the prepare steps at the end.



Daniel Ratliff



From: [email protected] [mailto:[email protected]] On 
Behalf Of Darin Nelson
Sent: Tuesday, December 15, 2015 12:00 PM
To: '[email protected]'
Subject: [mssms] Creating an reference computer and having our vendor mass disk 
clone



Hello.



We are working on building a reference image for a lab of 100 PC's that we will 
be deploying soon.  The vendor has agreed to mass clone them back at their 
warehouse.  We figured this would help free up some of our deployment time.



I am wondering once we have the reference image all fine-tuned, we will be 
taking it out of the domain and having it in a workgroup.  As far as the 
ConfigMgr client goes, should we be uninstalling that as well?  Im a bit 
nervous about how the ConfigMgr site will see all of these that were mass 
cloned (disk copied).



Any insight into this would be greatly appreciated.



Thank you.



Darin







The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.




Reply via email to