I don't install the client on a reference image. I don't even install the Endpoint Protection. My images are Windows + updates only. I let SCCM deploy the rest after it is applied to machines.
Nick Gailfus Computer Technician p. 602.953.2933 f. 602.953.0831 [email protected]| www.leonagroup.com On Tue, Dec 15, 2015 at 10:10 AM, Daniel Ratliff <[email protected]> wrote: > 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. > >
