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]] On Behalf Of Linkey, Mike Sent: Monday, January 13, 2014 11:58 AM To: [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.
