You could use a new WSUS instance and point your MDT 2012 Update 1 instance at it (via CustomSettings.ini) so your MDT OSD builds get patched against that.
Then just have a mechanism for deploying the SCCM client when the user logs in. Once the SCCM client is present patches would be automatically applied from the SCCM WSUS instance via Software Updates according to how you configure it. You would have to manage two WSUS environments but it would only be until you complete your cut over. In my opinion, I wouldn’t install the SCCM client as part of your MDT build. Cheers Damon From: [email protected] [mailto:[email protected]] On Behalf Of sccmfun Sent: Wednesday, 29 October 2014 2:03 AM To: [email protected] Subject: RE: [mssms] SCCM 2012 / MDT 2012 Update 1 The problem is once the SCCM client is installed via MDT there isn’t a step like there is in SCCM OSD to Install Software Updates right now is there? [cid:[email protected]] The SCCM client would have to get installed via MDT, end up in my correct patching collection (could take a bit) and then patch. How do you ensure if your using MDT to build the box and SCCM to install the patches that the whole process happens quickly/in the right order? Since we have the build split (MDT to build) and SCCM to patch how do you ensure the box goes to the user fully patched? We don’t want the machine to be at the users’ desk for a day till it finally ends up in the right patch collection and then patchs a day later. Thanks From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Steve Whitcher Sent: Tuesday, October 28, 2014 9:24 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] SCCM 2012 / MDT 2012 Update 1 Currently, you don't use SCCM at all, just MDT stand alone, correct? As long as you keep the MDT environment separate from your SCCM environment, there is nothing that would prevent the use of MDT for OSD and SCCM for patching etc. Once the OSD task sequence is done, the workstations won't have anything to do with MDT anymore, and can be added clients to the SCCM server without issue. I would suggest that the MDT team look at adding a step to install the SCCM client as part of their existing OSD task sequence. On Tue, Oct 28, 2014 at 7:57 AM, sccmfun <[email protected]<mailto:[email protected]>> wrote: We currently have MDT 2012 Update 1 and are in the process of designing SCCM 2012 R2 CU3 for our company. The MDT team isn’t ready to go to MDT 2013 and want to keep the MDT 2012 Update 1 process separate from SCCM 2012 for a few months after rollout of SCCM. Anyone have any ideas how to get machines patched via SCCM when the machine is built via MDT is that possible or do I need to have a separate WSUS infrastructure for the builds until there ready to upgrade to MDT 2013 and integrate into SCCM 2012? I’m assuming there is no way for them to reference out WSUS/SUP points during their MDT 2012 builds? Thanks ________________________________ 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.
