Answered by:
integrating hotfix kb2905002 updates in TS

Question
-
Just applied the hotfix KB2905002 on a sccm2012r2 site server and looking into integrating the client update packages into the TS. But a few questions:
1. Since the hotfix has created client update packages, can I do the step "setup windows and configuration manager" without using PATCH= option, and right after that step add a step to apply the packages created by the hotfix?
2. Further, would it be possible not applying the update package in the TS and rather deploying the update package after TS completed?
thanks in advance
Monday, January 20, 2014 6:10 AM
Answers
-
Hi,
1. Why would you want to do that instead of using the PATCH= command it is must faster as well to install the update.
2. Yes, you could of course wait and deploy it until after the OSD Task Seqeunce is finished. but then you will miss out on any updates affecting the task sequence execution on the clients.
Regards,
Jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
- Marked as answer by TreeLeafs Monday, January 20, 2014 9:34 AM
Monday, January 20, 2014 6:38 AM -
I would recommend to follow this guide on how to do this http://blogs.technet.com/b/deploymentguys/archive/2013/06/04/automatically-populate-the-patch-property-for-the-configmgr-client-installation-script-update.aspx
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa
- Marked as answer by TreeLeafs Monday, January 20, 2014 9:34 AM
Monday, January 20, 2014 8:39 AM
All replies
-
Hi,
1. Why would you want to do that instead of using the PATCH= command it is must faster as well to install the update.
2. Yes, you could of course wait and deploy it until after the OSD Task Seqeunce is finished. but then you will miss out on any updates affecting the task sequence execution on the clients.
Regards,
Jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
- Marked as answer by TreeLeafs Monday, January 20, 2014 9:34 AM
Monday, January 20, 2014 6:38 AM -
I would recommend to follow this guide on how to do this http://blogs.technet.com/b/deploymentguys/archive/2013/06/04/automatically-populate-the-patch-property-for-the-configmgr-client-installation-script-update.aspx
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa
- Marked as answer by TreeLeafs Monday, January 20, 2014 9:34 AM
Monday, January 20, 2014 8:39 AM -
Thanks for all the responses.
I have read a few articles online and will take the idea that copy the update to %OSDDISK% to make the PATCH=<PATH> easier.
Monday, January 20, 2014 9:34 AM