Dear WSUS users,
I am very excited to announce the release of WSUS 3.0 SP1, now live and ready for download! This is a significant release that represents a huge milestone for all involved and we thank you greatly for your feedback and support throughout the life cycle of this project.
WSUS 3.0 SP1 can be installed stand-alone or as an in place upgrade to WSUS 2.0 SP1 or WSUS 3.0 RTM.
The improvements that SP1 offers compared to WSUS 3.0 RTM include:
· Support for Windows Server 2008
· Support for Microsoft SQL Server 2008
· Enhanced bulk approval capability, preserving existing approvals
· Support for separate proxy servers and ports for SSL and non SSL traffic
· Better performance
· Detailed computer reports that can be imported to Excel
For those of you who are still on WSUS 2.0, a description of the new features in WSUS 3.0 RTM is quite long and can be found in the overview guide.
WSUS 3.0 SP1 is now located at the Microsoft Download Center. It will also be released via Microsoft Update, the Catalog, and WSUS in late March. To download and to obtain installation instructions, please visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?FamilyId=F87B4C5E-4161-48AF-9FF8-A96993C688DF&displaylang=en
Congratulations team and WSUS community on this great milestone, enjoy!
WSUS Program Manager
Where can I find info on how to migratye from 2.0 to 3.0? I have searched everywhere and cannot find anything on this. Thanks
Where can we view a list of fixes / updates in SP1? The release notes on the SP1 download page point to a generic V3.0 page..
And will the service pack distribute itself via WSUS?
The improvements that SP1 offers include: 1. Support for Windows Server 2008. 2. New Client Servicing API: Supports client registration, filters updates by category and classification, provides applicability rule extension mechanism and obtains pac
If you got your Thursday Heads up Security bulletin notification you would know that you are looking
Thanks Aaron - I've read the blurb.
I'm after the release notes / fixes that Microsoft provide with any other product's service pack.
Great news, thanks a lot.
One question, will there be a localized version of WSUS 30 SP1 or can one safely install the new (US) build on German SBS 2003 R2 (following the special upgrade instructions for SBS)?
The release notes are here:
Cannot Install. Trying to upgrade from 3.0 and it is failing with the following errors:
2008-02-08 09:33:47 Success MWUSSetup Validating pre-requisites...
2008-02-08 09:33:47 Error MWUSSetup SetPropertyFromStringRegistryValue: Could not read regkey SmtpUserPassword (Error 0x800700EA: More data is available.)
2008-02-08 09:33:47 Error MWUSSetup CUpgradeDriver::PerformPresetupActions: Failed to set SMTP_USERPASSWD property from SmtpUserPassword registry value (Error 0x800700EA: More data is available.)
2008-02-08 09:33:47 Error MWUSSetup CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x800700EA: More data is available.)
2008-02-08 09:33:47 Error MWUSSetup CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
2008-02-08 09:33:53 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x800700EA: More data is available.)
Same error as TOM - Please hire some testers.
2008-02-08 07:15:20 Success MWUSSetup Validating pre-requisites...
2008-02-08 07:15:20 Error MWUSSetup SetPropertyFromStringRegistryValue: Could not read regkey SmtpUserPassword (Error 0x800700EA: More data is available.)
2008-02-08 07:15:20 Error MWUSSetup CUpgradeDriver::PerformPresetupActions: Failed to set SMTP_USERPASSWD property from SmtpUserPassword registry value (Error 0x800700EA: More data is available.)
2008-02-08 07:15:20 Error MWUSSetup CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x800700EA: More data is available.)
2008-02-08 07:15:20 Error MWUSSetup CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
2008-02-08 07:15:38 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x800700EA: More data is available.)
Would like a workaround ASAP for the pre-requisite failure!!!
I've upgraded our primary WSUS server and when I open the OPtions, it has a banner at the bottom stating that it is still processing a configuration change. Does the system require a post-installation reboot?
If the SMTP password is long (>= 12 chars), then the upgrade could fail with the above issue.
A work-around is to set the SMTP password to be something smaller temporarily, do the upgrade and set to the correct password after upgrade.
Here's more info:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.WebException -- The operation has timed out
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetSyncInfoRow(WsusSynchronizationInfo syncInfo)