What can you expect in WSUS 3.0?

WSUS 3.0 will be the next iteration of Update Services and the beta is slated for 3rd qtr this year (CY). Craig Marl [MSFT] has added some light on the improvements on microsoft.public.windows.server.update_services. Quoting from the Craig's post.

NEW MMC UI:
For 3.0 we're adding a new MMC UI that allows us to do a lot more than the old web UI, one of these things is much richer views.

NEW Custom Views:
In 3.0 you'll be able to define custom views based on products, classifications, sync date, and the groups the updates are approved for. This should make it much easier to create views specifically for test to production scenarios - you'll be able to have views specific to your test deployments.

NEW Filtering:
You can also filter the views based on approvals and the status on your clients; so you can see approved updates with failures, and with a single click see approved updates that are still needed etc.

Reducing the complexity around approving for detection:
Basically in 3.0 the whole notion of approved for detection goes away - so we'll always have stats on which updates are needed etc. This allows us to build views where you can see which updates are unapproved & needed by clients which should help make it simpler to decide which updates to test 1st.

NEW Nested Target Groups:
One other thing I'll mention is that we're beefing up targeting significantly for 3.0 - we'll allow nested target groups. So you'll have much more flexibility in how you organize your groups, and much improved inheritance semantics.

Go ahead and add your WSUS-Wishes on http://www.wsuswiki.com/WishList.

***UPDATE - 4/15/2006: Some more wishes answered on WIKI.***

Purge Content 
http://wsus.editme.com/WishlistPurgeContent 
Comment Added by christianw 
 
Email Notification 
http://wsus.editme.com/EmailNotification 
Comment Added by christianw 
 
Show Superceded 
http://wsus.editme.com/ShowSuperceded 
Comment Added by christianw 
 
Mandatory Updates 
http://wsus.editme.com/MandatoryUpdates 
Comment Added by christianw 
 
Client Troubleshooting Tools Needed 
http://wsus.editme.com/ClientTroubleshootingTools 
Comment Added by christianw 
 
Download Updates By Schedule 
http://wsus.editme.com/DownloadUpdatesBySchedule 
Comment Added by christianw 
 
Report By Computer Instead Of By Update 
http://wsus.editme.com/ReportByComputerInsteadOfByUpdate 
Comment Added by christianw 
 
WSUS Integration With AD 
http://wsus.editme.com/WSUSIntegrateWithAD 
Comment Added by christianw 

***UPDATE - 4/16/2006 - I am born today (April, 16 1981)***

NEW Reporter User:

We'll have support for a reporters user role. They'll get read only access for the server to generate reports.

Published Wed, Apr 12 2006 17:57 by Mohammed Athif Khaleel
Filed under:

Comments

Saturday, April 15, 2006 10:19 AM by PatchAholic...The WSUS Blog!

# WSUS Client Troubleshooting Tools Needed

WISH - Client Troubleshooting Tools Needed on WSUS-WIKI
Sunday, April 16, 2006 1:22 AM by PatchAholic...The WSUS Blog!

# Some more WSUS wishes are answered - What can you expect in WSUS 3.0?

Some more WSUS wishes are answered - What can you expect in WSUS 3.0?
Monday, April 17, 2006 11:54 PM by PatchAholic...The WSUS Blog!

# When can you expect WSUS 3.0?

When can you expect WSUS 3.0?
Wednesday, April 26, 2006 7:42 AM by PatchAholic...The WSUS Blog!

# Delete Older Not Reported Stale Computers

Delete Older Not Reported Stale Computers from WSUS
Wednesday, April 26, 2006 7:43 AM by PatchAholic...The WSUS Blog!

# Deploying Internet Explorer 6.0 using WSUS

Deploying Internet Explorer 6.0 using WSUS
Wednesday, May 10, 2006 5:56 AM by PatchAholic...The WSUS Blog!

# Delete Older Not Reported Stale Computers

Delete Older Not Reported Stale Computers from WSUS
Thursday, May 11, 2006 10:06 AM by smithers

# re: What can you expect in WSUS 3.0?

[Reducing the complexity around approving for detection:
Basically in 3.0 the whole notion of approved for detection goes away - so we'll always have stats on which updates are needed etc. This allows us to build views where you can see which updates are unapproved & needed by clients which should help make it simpler to decide which updates to test 1st.]

Does this effectively mean that the 'Not Approved' status will disappear too, leaving just 'Install' and (presumably) a new 'Don't Install' as the only approval options? I hope, in that case, that the in-place upgrade from 2.0 to 3.0 will automagically change 'Not Approved' to be 'Don't Install'? :)
Monday, May 15, 2006 1:44 AM by PatchAholic...The WSUS Blog!

# Delete Older Not Reported Stale Computers

Delete Older Not Reported Stale Computers from WSUS
Monday, May 15, 2006 1:57 AM by PatchAholic...The WSUS Blog!

# Deploying Internet Explorer 6.0 using WSUS

Deploying Internet Explorer 6.0 using WSUS
Thursday, May 18, 2006 7:02 AM by George SImos

# re: What can you expect in WSUS 3.0?

1) It would be nice if there is a way to find the directory and filename of an update (in case we want to get the file and install it manually).

2)The superseded updates should be automatically and hierarchically get declined or not approved (which will mark them for deletion) after the superseding update gets approved for installation.

Thursday, June 15, 2006 10:20 PM by Spike Kong

# re: What can you expect in WSUS 3.0?

More reboot options required for mobile users. When they connect to WSUS after a patch deadline has passed, the download, installation & reboot time is undeterministic - which means the user can be reboot while he least expects it losing his work. At least the max 30min  countdown period should be increased.
Tuesday, July 04, 2006 4:13 PM by Daniel VanMeter

# re: What can you expect in WSUS 3.0?

I hope the deadline installation will respect the no autorestart.
Friday, August 18, 2006 6:45 PM by ShadowChaser

# re: What can you expect in WSUS 3.0?

In regards to:

>Mandatory Updates
>>This exists in the final version. When >>approving an update for installation, a date >>deadline can be specified, after which the >>client cannot reject the update.

I believe that this doesn't accurately resolve the problem.

When establishing installation deadlines, it overrides all other settings and forces a reboot of the workstation if necessary.

Mandatory updates are different - what is needed is a way to prevent the end-user from "unchecking" updates to be installed *WITHOUT* establishing a deadline, which would do things like reboot the workstations with unsaved work or production servers!

Deadlines are of minimal use - I quickly learned to avoid them in WSUS. We desperately need a *real* Windows policy enforcement option to prevent users from thinking "they know better" than the IT security staff.
Monday, August 21, 2006 12:20 PM by vigrx

# re: What can you expect in WSUS 3.0?

And  concerta what I oughtn't to have written to had is girls to she affected no his countenance,  concerta and were silent for an unexpected  concerta  concerta letter presented himself of which she shared concerta

<a href=" http://concertaxl.acb.pl/ ">concerta</a> concerta
<a href=" http://ingredientvigrx.acb.pl/ ">link prices.html vigrx vigrx.tabs.michikusa.jp</a> link prices.html vigrx vigrx.tabs.michikusa.jp
<a href=" http://cheaphtmllinkvigrxvigrxxdiscountnomakijp.acb.pl/ ">vigrx</a> vigrx
Friday, October 27, 2006 9:04 PM by SeaGROL

# re: What can you expect in WSUS 3.0?

Ever since I've become aware of the SUS/WSUS program I've been asking for two very simple things. Office 2K and Load-From-Disk Support.

Can we please get Office 2K support? Office 2K is used heavily throughout the Government and Commercial world, even though it is old.

The ability to load patches off of a removeable disk would be extremely useful. I'm on a network with a maximum bidirectional data rate of 32 kilobits a second. I routinely see ping times of close to 1000ms. A large sevice pack can take WEEKS to download.

I've found a tool (OHotFix) that is a stop gap, but it'd be more useful to see it integrated into WSUS.

Thanks,

SeaGROL