Solved

Cross-Forest WSUS Patch Management

Posted on 2012-04-02
2
1,857 Views
Last Modified: 2012-06-27
Hi,

My current employers are co-hosting a number of client's Win 2003/2008 AD forests on our own infrastructure, and because the combined infrastructures are relatively small (~80 server hosts), I want to implement a single WSUS server that roll patches out to all servers.

Has anyone implemented a cross forest WSUS server, and if so, do you have any tips/advice/steps/manuals?
0
Comment
Question by:cpadm
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 1

Author Comment

by:cpadm
ID: 37796868
I have the following roll-out steps in my head:

1.) Install WSUS server (make sure patches not stored on OS drive...)
2.) Create a WSUS folder for each forest, with subfolders for each server OS/Role.
3.) Create a server WSUS group policy in each forest to point at the single WSUS server.
4.) Set all servers to download patches, but manually install
0
 
LVL 17

Accepted Solution

by:
Tony Massa earned 500 total points
ID: 37799287
WSUS isn't domain specific, so all you would need to do is configure all of the clients to point to a single WSUS server and then set up different groups for patching.

When I used to patch, I preferred not to use target groups, instead, manage the reboots on the computers, and managed the groups on WSUS instead.  I then set up patching and reporting groups that all computers were members of.  Because of our weird patching schedules, I did have to manually move servers into (and out of) the patching groups the week they were scheduled to patch, but servers are always a member of their respective reporting groups.

You generally would pick a subset of low-risk servers to patch first (can be from different 'forests'), then release the same patches to servers that are more important, but not business critical.  The last servers will be your 'critical' production group(s).  Some multi-teired apps need reboots in specific order, but if you are manually pushing the patches and not auto-rebooting, there isn't a lot to worry about.  It will save Internet bandwidth.  :)

You would probably want to use client-side targeting to prevent accidental grouping (mixing) of WSUS clients from the WSUS Admin console.  http://paulslager.com/?p=10
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question