Ted the Chilehead

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

Ok. I see what you were saying in a different post which clears this up for me. When you synch your update respository, you can pick new updates and: 1) Add the new updates to the update list (if reporting) 2) Add the new updates to the update repository 3) Add it to a NEW update management task using a deployment template What I did to make selecting expired and superseded items easier to select and find was to change the column view so that "Expired" and "Superseded" were the first two columns. I have the following columns whenever I am viewing updates either in search folders, deployments, and deployment packages... Expired, Superseded, Bulletin ID, Article ID, Title, Downloaded, Date Released, Dave Revised. Using this method I better able to choose which have been expired or been superseded to delete. Then, when adding new updates, I can sort by date revised and date released OR by the bulletin ID... this comes in handy when downloading definition updates such as updates for FCS as they don't have bulletin ID's. So, most of my steps follow yours in the plan I'm laying out for our helpdesk folks with the primary exception being: while cleaning up updates from the list and the repository, remove the deployment task from the previous month. Then, add new updates to the update list, respository and deploy the new updates to a new task for the current month. Thanks for your posts and screen shots. It's a great base to start with as you can see I believe we'll adapt this method you've demonstrated.

I'm tryin to wrap my head around something that could be, but no luck. I was just confused about the steps at the end. I need to play around with this. I like the simplicity of WSUS by itself, but I do like the flexibility of software updates and reporting in SCCM. If I find something or come up with an alternate method, I will post it. One great thing about your post here is that it's one of the more clearer "how to guides" with screen shots. You don't find many other examples out there like that.

This seems very confusing. So, you are cleaning up MULTIPLE management tasks AND MULTIPLE deployment packages each month?