WSUS Configuration Wizard - Sync error choosing MS Update as upstream server
-
mardi 5 février 2013 11:28I've got a Windows Server 2008 R2 x64 machine with all updates.
I've configured WSUS 3.0 SP2 server role as of official MS detailed guide; IIS role has been added as part of WSUS Server Manager wizard role; I've used a remote SQL Server 2005 instead of Windows Internal Database.
In Configuration Wizard, I choose using Microsoft Update in the step "Upstream Server"; I've got no proxy, so I skip following step.
When time to "Start Connecting" to the upstream server (that is, to Microsoft Update), I've got a Web Exception saying "Object moved to".
Full error trace available on request.
Toutes les réponses
-
mardi 5 février 2013 22:50Modérateur
When time to "Start Connecting" to the upstream server (that is, to Microsoft Update), I've got a Web Exception saying "Object moved to".
Full error trace available on request.This issue has been observed by a number of people installing new WSUS servers over the past 24 hours.
It was also discussed in this thread.
One indication is that the issue was transient and is now resolved.
In another case we were able to successfully work around the issue by applying KB2734608 and then running the setup wizard.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Distribution (2005-2013)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.- Marqué comme réponse Clarence ZhangModerator lundi 18 février 2013 03:20
-
jeudi 14 février 2013 16:05Thanks Lawrence. KB2734608 sorted the issue for me on a new WSUS SP2 install on a Server 2008 R2 SP2 DC.
-
mardi 5 mars 2013 23:36It works for me too!! Thanks!!!
mbrenes
-
mercredi 13 mars 2013 13:35yessssss!!! the KB2734608 it the only way that i could solve this problem!!!! thanks a lot!!!!
-
jeudi 25 avril 2013 10:25As an FYI, it must be a very long transient, because a new install I just performed also required the KB update. It worked great after that. Thanks!

