Awesome, but i cant get through the configuration because it wont get passed the proxy stage. Using the same information for my proxy as i did on the last version, and it wont take. Even when i use our proxy that allows anonymous connections it times out, and when i use our proxy that requires authentication, and i provide it, locks my domain admin account out and says requires authentication.  :/

Many bugs fixed and hopefully not much broken. You can read about it here.

Matt i was having the same problem, try looking in your eventlog for crypt32 errors, if you have them try looking at:

http://support.microsoft.com/kb/317541

Thanks tommy, i cleared out the root cert updates per the KB article but still cant get through the proxy config. No idea what to try at this point.

Hello,

I have the same problem, at the proxy stage, I receive an error "could not establish trust relationship for the SSL/TLS secure channel - the remote certificate is invalid according to the validation procedure".

It is the same proxy configuration as it was for the WSUS3 beta 2 test server. (and there was no problem)

I have tried the possible resolution of the kb317541 article but it doesn't work :(

ME too, same problem same upgrade from a wsus 2.0 version but a small différence. With a proxycfg -u, i've been able to use the synchro during 12 minutes before this error append again. And now no more synchro

When is the final release due out?

Update: I was able to get through the proxy config by running proxycfg -d and forcing it to our proxy server that allows anonymous traffic, but this still doesnt explain why i cant set it up through our normal proxy like i had it setup in the beta 2 version.

Does the RC install over Beta2?  I ran the setup and it uninstalls beta 2.  I was allowed to keep my database, downloads, etc, but then when installing RC, it says the database is a old one and can't be used.  What's up?

Upgrading from pre-release Versions of WSUS 3.0 is not supported. Quote from the Release Notes:

"If you have a prerelease version of WSUS 3.0 already installed, you will need to uninstall it and delete the database before installing a later version of WSUS 3.0.".

Same problem with Proxy authentication here.  

I was running WSUS 3 Beta2 and just upgraded to RC.  I'm using the exact same settings for proxy but am getting the following error message:

WebException: The remote server returned an error: (407) Proxy Authentication Required.

at System.Net.HttpWebRequest.GetRequestStream()

  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

  at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()

  at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)

  at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)

  at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()

  at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

Anyone find the fix for this??  

We're also having the same proxy problems listed above.  Our proxy server requires user authentication.   Our WSUS 2.0 works fine.

Are you all of you having this problem sitting behind proxy servers that require user authentication?

We're also having the same proxy problems listed above.  Our proxy server requires user authentication.   Our WSUS 2.0 works fine.

Are you all of you having this problem sitting behind proxy servers that require user authentication?

Im not behind a proxy server that requires auth.

So proxycfg -u worked for me (took the settings from internet explorer), after that i could sync just fine, and my crypt32 errors went away.

I have a clean install of this on two servers and neither of them will sync to get updates... The last sync result says... The upstream server experienced an unexpected error. Please try again later... The upsteam server for both of these is the outside MS server not any of mine. Anyone else seeing this?