Mark,

 

I sent you an e-mail offline a few minutes ago. It has a screenshot of how
it's configured correctly in my lab (and similarly at a customer). I'm using
the task sequence variable instead of hard-coding c:\, but it works the same
in most cases. Jason has pointed out that occasionally the variable will
cause issues.

 

And yes, I'm using \Packages, not \OSD.

 

When the failure happens, launch PowerShell and use the Test-Path cmdlet to
confirm that the file exists (copy / paste the MSP path from the failed
ccmsetup.log).

 



 

Cheers,

Trevor Sullivan

 

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of Kent, Mark
Sent: Tuesday, November 26, 2013 12:39 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] RE: Where to include client patch

 

Hi Trevor,

 

So you use \Packages instead of \OSD?

 

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Trevor Sullivan
Sent: Tuesday, November 26, 2013 1:35 PM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: RE: [mssms] RE: Where to include client patch

 

Mark,

 

If you ask Jason, you should use c:\_SmsTaskSequence, because it's more
predictable. But my point was more that it looks like you're missing
\Packages.

 

Cheers,

Trevor Sullivan

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kent, Mark
Sent: Tuesday, November 26, 2013 12:26 PM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

Should I use "C:\_SMSTASKSEQUENCE" or "%_SMSTSMDataPath%" ?

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, November 26, 2013 1:20 PM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

:)

 

Yeah, good thought.

 

J

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dzikowski, Michael
Sent: Tuesday, November 26, 2013 12:13 PM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

Right, I had to copy the files to a folder etc.

 

Just giving a visual for Mark.  

 

 

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, November 26, 2013 1:11 PM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

The command-line is fine as long as the msp is in the HOTFIX\x64\ folder of
the client folder - these folders do not exist by default.

 

Have you dropped to a command-line to verify the above path during the TS?

 

J

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dzikowski, Michael
Sent: Tuesday, November 26, 2013 11:58 AM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

This works for me:



 

 

 

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kent, Mark
Sent: Tuesday, November 26, 2013 12:48 PM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

Yes, yes, and yes.  Is my command line correct?  I recall there being a
proper way to set the command line.

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, November 26, 2013 12:42 PM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

It's supported and is the only way to get it done actually.

 

Is S0300002 your ConfigMgr client install package?

 

Did you add the msp from the hotfix folder to the client package's source
files (in the client folder if you are using the default package)?

 

Did you update your DPs?

 

J

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kent, Mark
Sent: Tuesday, November 26, 2013 11:11 AM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

When I use that, it tells me it cannot find the patch: Unable to create a
temp copy of patch
'C:\_SMSTASKSEQUENCE\OSD\S0300002\CONFIGMGR2012AC-R2-KB2905002-I386.MSP'.

 

I know that it's not supported, but what is the proper usage for it again?
I know you commented somewhere on the proper usage.  Can you point me to it?
Thanks.

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, November 26, 2013 11:41 AM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] RE: Where to include client patch

 

Both (using the PATCH property).

 

J

 

From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kent, Mark
Sent: Tuesday, November 26, 2013 9:53 AM
To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 
Subject: [mssms] Where to include client patch

 

We are using SCCM2012 to both build an image and deploy it.  Both task
sequences include the "Setup Windows and ConFigMgr step".  I want to include
the recent post-R2 patch (KB2905002).  Should I include that in the image
build, the image deployment, or both?  Thanks!

 

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

 

 

 

 

 

 

 

 

 

 

 

 



<<image002.png>>

<<image003.png>>

Reply via email to