Help needed for strategy to Review / Approve / Schedule / Install WSUS updates in organization
-
2012年4月28日 4:47
Hi, all,
I got the task to implement WSUS in the organization for hundreds computers.
I created GPOs to setup clients (W2k8, W2k3, XP, 7 etc) to point to WSUS server with different download/install levels. The business requires that certain if not all updates should be implemented on partial servers / workstations, ie not in one go just in case any unforeseen problems. Once these test machines run OK I can then push the updates to the rest all.
I have setup Options in WSUS auto-approve "critical" "security" updates to all "Domain controllers" "Member servers" most "workstations" but not to DEV computers - is it a good setting?
As I am facing thousands and thousands of updates, how should I make sure they are tested in part of "member servers" then rolled over to the rest? I can create in WSUS computer groups like "test servers" and approve some (how to decide?) updates, but my GPO applies to all the "Server" OU. If I have to split in AD "Servers" Ou into "test servers" OU and "rest servers" OU and then apply different GPO to force "test servers" to install tonight and "rest server" to install week later, I'd rather to write some scripts to change a list of computers' registery to Install tonight, and then change "rest servers" registry next week.
Again, when dealing with thousands of updates I really could not say any particular server has got how much. Especially processing those non-auto-approved updates, it would be impossible to trace how many of them have been manually approved and installed on how many computers (groups) and when.
Could any WSUS specialist recommend what the Strategy should be considered / adopted?
Thanks.
GPING
すべての返信
-
2012年4月29日 14:26モデレータ
This forum is replete with such conversations from several different points of view. The ultimate answer is that you need to employ the strategy that meets the objectives as defined by your organization. Everybody has different strategies. But first, to implement any strategy, you need to understand the product, what it can and cannot do, how to configure, and how to manage it. For starters you should review this forum. Second, you should review the articles in Update Management, as well as the WSUS Product Documentation. Finally, I would also offer a collection of webcasts I did on 2009 and 2010 that discuss this topic. One you understand the product, and the philosophies and methodologies of update management itself, I believe the specific strategy you need to employ will be self-evident.Could any WSUS specialist recommend what the Strategy should be considered / adopted?
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin- 回答としてマーク Clarence ZhangModerator 2012年5月7日 2:36

