Follow the instructions on my blog post. It's for CU2 but just swap out the CU3 installer file and you are off and running.
http://deploymentramblings.wordpress.com/2013/08/22/installing-configmgr-2012-sp1-cu2-during-osd/ Dustin Hedges Sr. Systems Engineer GETOps - Global Client Engineering eBay Inc. 512 691 4227 M 512 887 2587 [email protected]<mailto:[email protected]> ebayinc.com Skype: dhedges01 [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Monday, January 13, 2014 12:46 PM To: [email protected] Subject: [mssms] RE: Client Update to CU3 during TS I've been successfully deploying the patched SCCM client during TS in the way described in the Deployment Guys blog here http://blogs.technet.com/b/deploymentguys/archive/2013/06/04/automatically-populate-the-patch-property-for-the-configmgr-client-installation-script-update.aspx There are a couple of notes about problems people have run into along with script changes that were made to correct the problems. I can't take 2012 update 1 yet due to the need to support XP, but the older version of the script that is not dependent on 2012U1 works fine in my environment. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Monday, January 13, 2014 12:23 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Client Update to CU3 during TS Yes, but it's not reliable because it is set in WinPE and not updated once booted into the OS. I typically hard-reference it at c:\_SMSTaskSequence\Packages\<pkgid>\... J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Monday, January 13, 2014 11:58 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Client Update to CU3 during TS That makes sense. Is there a TS variable that points to that location by default or do I have to create one? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Monday, January 13, 2014 11:44 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Client Update to CU3 during TS Anywhere that is accessible to the client. The usual path, which mimics the way it was in 2007, is to copy the MSPs to the built-in client agent package because it gets automatically downloaded during the Install Windows and ConfigMgr task already. Be aware that there are two separate MSPs though, one for x86 and one for x64 so you have to account for that also. And of course make sure you update your client agent package on all DPs. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Monday, January 13, 2014 11:30 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Client Update to CU3 during TS Where does the CU3 MSP file go so that you can upgrade the client during the TS? I have seen several examples of using the PATCH= on the command line, I just don't know where that path is located. Can anyone point me in the right direction? Thanks Mike L. ________________________________ 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. ________________________________
<<inline: image001.jpg>>
