I have a test environment, all servers are on 2012 R2.
WSUS is a separate server from ConfigMgr.

I get this message and I cannot figure it out.

Updates are being downloaded and show up in ConfigMgr but do not show up on the WSUS server, but it says:  All Updates 1 update of 667 shown but none are shown.

On 8/19/2014 10:28:42 AM, component SMS_WSUS_CONTROL_MANAGER on computer WSUS.TESTENV.INTERNAL reported: WSUS Control Manager failed to configure proxy settings on WSUS Server "WSUS.TESTENV.INTERNAL".

Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted.

Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid.

When I install WSUS-KB2734608 it says not the right version.

Any suggestions
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

did you follow the known issues on the KB?

•If you use the Local Publishing feature from a remote WSUS console, when your WSUS Server is updated with this update, the remote WSUS consoles must also be updated to make sure the API versions match.
•If you have locally published updates, you will have to re-sign and republish all local updates after you apply this update. Be aware that a minimum of a SHA1, 1024 key-length certificate is required. For more information about how to do local publishing of updates, go to the following Microsoft Developer Network (MSDN) website:
Local Publishing
David Paris VicenteSystems and Comunications  Administrator Commented:
Hi wynnie2,

Can you try to install this KB and see what happens.

You should also check this because there have been some changes in WSUS in Windows Server 2012. In older versions of WSUS, the default communications ports were ports 80 and 443. In Windows Server 2012, the new default ports for WSUS communication are ports 8530 (HTTP) and 8531 (HTTPS). There have been some reports that SCCM, after the application of SP1, may change the WSUS/SUP port configuration. If you're having trouble with WSUS and SCCM 2012, check these settings out, too.

I hope it helps.
techgeniousAuthor Commented:
The ports are configured for 8530/8531 and when I try installing KB2720211 this is what I get.error
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

David Paris VicenteSystems and Comunications  Administrator Commented:
Hi wynnie2,

Can you write down here your test environment?
I already know that you have W2k12 R2, but we don´t know the SQL versions installed, Service packs and so on.

Please check the version of your WSUS you can follow this link. to help you identify the version.

You can also check the version by clicking  Help, About on the WSUS.

You should also check the logs, you can check here how to.

And insert here all the info.

techgeniousAuthor Commented:
WSUS == Version 6.3.9600.16384
SQL 2012 V. 11.0.5532

Failed to set WSUS Local Configuration.  WIll retry configuration in 1 minutes.
Failures reported during periodic health check by the WSUS server Cm2012.test.internal

WCM.log no error messages

If you need anything else let me know
David Paris VicenteSystems and Comunications  Administrator Commented:
Thank you for the feedback.

The log just have 2 lines? If not insert all the log here.

I also suggest remove WSUS role, then update W2k12R2 and also update SQL to SP1.

After all reboots needed by the updates are done then install again the WSUS and check if any update is needed or available for WSUS.

Let us know regards.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
techgeniousAuthor Commented:
I called Microsoft and this was the solution:

--  My setup is configured correctly
-- The error message above concerning:  Verify that the WSUS Server version 3.0 SP2 or greater is installed
    This error message is for Server 2008 R2 OS and can be ignored.   I installed WSUS through the Add Features options
    on Server 2012 R2
--  Ran:  wsusutil.exe /checkhealth then ran wsusutil.exe /reset    
--  Then ran:   iisreseterror
Now no more error messages except for Verify that the WSUS Server version 3.0 SP2 or greater is installed, and MS advised that can be ignored.
techgeniousAuthor Commented:
This KB2720211 is for Server 2008 R2 not Server 2012 R2.
techgeniousAuthor Commented:
I've requested that this question be deleted for the following reason:

I solved it myself
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.