Jump to content


jason999

Established Members
  • Posts

    3
  • Joined

  • Last visited

jason999's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for taking the time to write this guide, it was quite helpful and easy to grasp. I have made some minor changes to suit my purpose by deploying the update to a master collection (prefix with ADR) which includes the second set of collections below. This allow me to distribute the updates to test systems automatically as well as production systems based on their maintenance windows. ADR:Software Updates - Windows Server 2008 R2 _Preproduction ADR:Software Updates - Windows Server 2008 R2 Automatic Software Updates - Windows Server 2008 R2 Automatic Software Updates - Windows Server 2008 R2 Maintenance Window [Fri 10pm - 4am] Software Updates - Windows Server 2008 R2 Maintenance Window [sat 10pm - 4am] I do however have a question in regards to the best practice for systems that require manual interaction. Would I ... 1) Update the existing software update group and create a new deployment set the deployment to be available rather than required? 2) Create a new ADR with a deadline of 30 days and uncheck default behavior settings for software installation and check to supress restarts? 3) ??? I am more inclined to use process 1 as that is the simplest to manage unless there is an easier way. These updates would target the following collection: Software Updates - Windows Server 2008 R2 Manual
  2. Alright, I thought about doing that but wanted to confirm if the deployments will still adhere to the maintenance windows of the included collections?
  3. Excellent tutorial. It helped me get started with this months patching. My experience with 2012 is about a month old so forgive me if this is already covered. Current Setup I have multiple collections for Software Updates: Windows Server 2008 with various maintenance windows in each of them. WS2008 Automatic WS2008 MW 1 WS2008 MW 2 WS2008 MW 3 WS2008 Manual I have one ADR that will download all Windows Server 2008 patches that are required on at least one (1) system, not superseded and not expired. This ADR deploys the patches to my Automatic collection for systems that can be patched at any time. My understanding is that the ADR will evaluate each collection and only download/deploy the updates required for that collection based on my criteria above Is there an efficient way to download/deploy the patches to the other collections while ensuring a minimal footprint and automating the process? Do I simply create an ADR for each collection? Will the updates not get duplicated if using multiple or is it a single shared repository of updates?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.