Managing monthly updates in SCCM

[hashirph 0]

Thanks for the great article ... It really helped a lot while configuring the setup in our company..

 

I have a question ...

 

When I deploy a software update ( Windows Patch ) to the clients, normally how much time it takes to get to the clients... I have seen when I create a software deployment task, it comes very fast, but in case of a patch update using software update in SCCM , I have to wait two or three days to see the result on the clients...

 

How can I make it more faster....

[Ted the Chilehead 0]

You have to note how the agent is set up (evaluation, available date, etc.) and then the re-evaluation period and if you sent an enforcement date. All those play a factor in relationship to when the client downloads/installs.

 

But, typically, once it's available for download, you have two options. You can kick off the updates scans from the configmgr client itself in the actions tab. Or, if you install the right click tools, you can remotely trigger those actions on the client using the SCCM console.

 

Ted

 

Thanks for the great article ... It really helped a lot while configuring the setup in our company..

 

I have a question ...

 

When I deploy a software update ( Windows Patch ) to the clients, normally how much time it takes to get to the clients... I have seen when I create a software deployment task, it comes very fast, but in case of a patch update using software update in SCCM , I have to wait two or three days to see the result on the clients...

 

How can I make it more faster....

[fqureshi 0]

Hi

 

I have managed to update all the monthly updates and deployed it.

But since I have updated the repositories and deployment packages, my deployment of OS freezes at "install updates" in the task sequence. It was working before. Before updating the updates; the install update step under the task sequence fetch all the required updates and installs on the new system during the deployment. But now it stays on the install update step and does not proceed. It says that downloading 1 of 90 updates but never proceeds. And this has started happening since I have updated the deployment packages for the updates.

 

May i request you to kindly let me know what could be the issues?

 

regards,

 

Farzan

[anyweb 480]

what does your smsts.log file say, have you applied the kb2509007.. hotfix ?

 

http://www.windows-noob.com/forums/index.php?/topic/3718-adding-a-hotfix-to-the-setup-windows-and-configmgr-step-in-a-task-sequence/

[SRed 1]

Sorry to resurrect this thread!

 

These are great steps Niall, but I'm not sure about Content Distribution. At what point do I push the content out to DPs for distribution to end clients? Does the "Automatically download content when packages are assigned to branch distribution points" handle this for me?

 

Note: I don't have any BDPs just standard DPs in my environment.

 

Thanks!

[Peter van der Woude 143]

Nope, that settings is for how the client has to act. To distribute the package to a DP, just right-click the package and click Distribute Content.

[Toxic 0]

Can i confirm once the initial deployment is done to phase 1,2 and 3 and you restart the process again, that you then end up with one deployment package with addition onthly updates being added to it, but you have a deployment management for each month.

 

is there anyway to add the next monthly updates to an existing deployment management? otherwise this would become full of deployment managements. these have to stay alive until ALL computers get updated.

[regan 1]

Great guide, can i ask what are the advantages of using SCCM to manage over day WSUS console? My biggest issue is it seems to be a longer process and the lack of removal of superseded updates