Step 4. Sign in to follow this Followers 2. Recommended Posts. Report post. Posted September 11, Step 1. Share this post Link to post Share on other sites More sharing options Posted September 12, Quick access. Search related threads. Remove From My Forums. Answered by:.
Archived Forums. Configuration Manager General. Sign in to vote. I understand how to roll out updates, so that's not really the issue, rather, it is how to roll out the first set of updates to get my network "current" on updates. Basically, all of the updates from have NOT been performed. Question: As for rolling out all of the and part of updates, do you reccomend pulling the updates by month or just making it one large software update?
Thanks in advance for your input. Tuesday, February 17, PM. I like to keep things neat as well. Here's what I do. Marked as answer by seanka79 Wednesday, February 18, PM. Wednesday, February 18, PM. I would use 1 pacakge per product. So if you are strictly talking XP then 1 package. If you also want to add office then there's another package. If want to do server another package. So on and so on. This ish always how I do updates. I do not create monthly packages. John Marcum, Systems Management Architect - www.
Wednesday, February 18, AM. I don't see a benefit in having a package per product. Apart from extra operational overhead, what added value does it bring? I would rather use 1 package per month, per quarter or even per year and create Search Folders to filter out only those you want to deploy.
In addition, I would even use the same deployment management for various products. Because I usually don't want an automatic reboot on my clients or my servers and both should be compliant within the same time frame, I only create a new deployment management if new updates need to be deployed.
If you target SMS clients, you should should be careful and make sure they run the installation from the DP. Unless I'm missing something? I wouldn't say there's a benefit it's just my personal preferance on how to do it. It's really not extra overheard, once your packages are setup you can add new patches to the each month in under 5 minutes. If you retire a product you can simply remove the associated patch pacakge since you do not need it any longer.
It's much easier to add patches to an exsisting package each month that to create a new one each month. I know some people do a new package for each month and put all the patches from that month into it. I think that's too much work. That is one of the things that I've been wondering about. The guy who showed me how to deploy updates in SCCM showed me that it is a good idea to do it by month.
After looking at the way the console is structured, it seemed like the Deployment Management area would get super messy right-quick since you can group them into folders.
I'm kind of obsessive about keeping my stuff neat and organized for easy reference. Beautiful, again John as per usual - thanks for the excellent info. John, how do you stop your production machines from installing the "new" month's patches before all testing is complete if you are just adding them directly to the Deployment Packages each month? If so, then how are you leaving the already tested and approved patches available for machines for OSD patch deployment or machines that may have been offline during the Deployment before it was deleted?
Also, you didn't mention how you deal with Expired or Superseded patches in your process How do you remove the Expired or Superseded patches from your Deployment Packages? Wednesday, March 11, PM. I delete the advertisment, add the patches, advertise them to a test collection then after they are certified advertise them to a real collection.
So then there is a section of time where machines are not able to get patches until you recreate the Deployment to the production collections? Are you able to share your process for "cleaning up" the Deployment Packages and Update Lists?
For me that amount of time is less than 1 day. This is 1 month after the previous patches went out so in theory most computers should have gotten patched by then. After you verify the test group successfully installed the software updates, add a new deployment to the rule. You could also change the targeted collection in the existing deployment to one that includes a larger set of clients. Consider the following behaviors when deciding upon the strategy to use:.
The ADR automatically deploys software updates to clients when you add them to the target collection. When you or the ADR adds new software updates to the software update group, the site automatically deploys them to the clients in the target collection.
After you create an ADR, add additional deployments to the rule. This action helps you manage the complexity of deploying different updates to different collections.
Each new deployment has the full range of functionality and deployment monitoring experience. For more information and detailed steps, see Automatically deploy software updates. Starting in version , create phased deployments for software updates.
Phased deployments allow you to orchestrate a coordinated, sequenced rollout of software based on customizable criteria and groups.
For more information, see Create phased deployments. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Tip If a distribution point isn't available, clients on the intranet can also download software updates from Microsoft Update.
0コメント