No but you can call the SDK in WMI through a PoSH script to do it There's a script on Technet gallery to install outstanding updates
> On 28 Oct 2014, at 16:06, sccmfun <[email protected]> wrote: > > 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? > <image001.jpg> > > 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]] > On Behalf Of Steve Whitcher > Sent: Tuesday, October 28, 2014 9:24 AM > To: [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]> 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 > > > > >
