Installing WSUS 2012 R2 console on server 2012 data center

Question

Hi,
Our SCCM site server is on Server 2012 and the WSUS server is on Server 2012 R2.
We are getting the below error in WCM log. in SCCM we are seeing the below error
PublishApplication(8427071A-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String
sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) SMS_WSUS_CONFIGURATION_MANAGER        
9/20/2014 1:47:42 PM    4644 (0x1224)
ERROR: Failed to publish sms client to WSUS, error = 0x80131509               SMS_WSUS_CONFIGURATION_MANAGER               
9/20/2014 1:47:42 PM    4644 (0x1224)
STATMSG: ID=6613 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MIC0-TK5DMR2PS1.redmond.corp.microsoft.com SITE=RD2 PID=1776 TID=4644 GMTDATE=Sat Sep 20 20:47:42.713 2014 ISTR0="8427071A-DA80-48C3-97DE-C9C528F73A2D"
ISTR1="5.00.7958.1000" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0   SMS_WSUS_CONFIGURATION_MANAGER               
9/20/2014 1:47:42 PM    4644 (0x1224)
Failed to publish client with error = 0x80131509  SMS_WSUS_CONFIGURATION_MANAGER         9/20/2014 1:47:42 PM                4644 (0x1224)
completed checking for client deployment          SMS_WSUS_CONFIGURATION_MANAGER         9/20/2014 1:47:42 PM               
4644 (0x1224)
HandleSMSClientPublication failed.         SMS_WSUS_CONFIGURATION_MANAGER         9/20/2014 1:47:42 PM    4644 (0x1224)
Do to this we are not able to publish SCCM client.
Any idea or recommended work around?

Answer 1

Publishing operation failed because the console and remote server versions do not match.
The issue is exactly what the message says. When doing local publishing (i.e. when using SCUP), the version of the console (used by SCUP) must match the exact version of WSUS being published to.
To wit, the following are valid publishing scenarios. Anything not listed here will not work:
WSUS v6.3 (on Windows Server 2012 R2) with SCUP running on WS2012R2 or Windows 8.1
WSUS v6.3 + KB2938066 (on WS2012R2) with SCUP + KB2938066 running on WS2012R2 or Win8.1
WSUS v6.3 + KB2819484 (on WS2012R2) with SCUP + KB2819494 running on WS2012R2 or Win8.1
WSUS v6.2 (on Windows Server 2012) with SCUP running on WS2012 or Windows 8
WSUS v6.2 + KB2938066 (on WS2012) with SCUP + KB2938066 running on WS2012 or Windows 8
WSUS v6.2 + KB2818494 (on WS2012) with SCUP + KB2818494 running on WS2012 or Windows 8
WSUS v3.2 + KB2938066 (on Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003) with SCUP + KB2938066 running on anything WS2008R2 or earlier
WSUS v3.2 + KB2828185 (on WS2008R2, WS2008, WS2003) with SCUP + KB2828185 running on anything WS2008R2 or earlier
WSUS v3.2 + KB2734608 (on WS2008R2, WS2008, WS2003) with SCUP + KB2734608 running on anything WS2008R2 or earlier
WSUS v3.2 + KB2720211 (on WS2008R2, WS2008, WS2003) with SCUP + KB2720211 running on anything WS2008R2 or earlier
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.