Table of Contents
Updated
Over the past week, some readers reported that a supported version of wsus was not found in sccm 2012.
Execution:
sccm 1910 due to KB4537079
server1: windows server 2019 + configuration management console
server2: windows server 2019 + sql computer 2017 (wsus db)
server3: Windows Server 2019 + WSUS
Updated
Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!
I used Server1 console to add SUP Server3 tasks, but it doesn’t work correctly
WCM.log@serveur1:
Checking the supported WSUS version (min. WSUS 3.0 SP2 + KB2720211 + KB2734608) ~
Read check v4.0.30319 … ~
Supportno live version of assembly Microsoft.UpdateServices.Administration was found. ~
Check runtime v2.0.50727 … ~
Failed to create assembly name theme for Microsoft.UpdateServices.Administration.
Supported WSUS version not found ~
I have currently set up a separate main SCCM site for the coming year with R2 SP1.CU1.
I have configured WSUS on a separate machine from WinServer 2012 R2. WSUS version6.3.9600.16384.
I am actually trying to sync the SCCM site with WSUS. Doesn’t work with the following errors (checking WCM.log):
Changes were detected in the active SUP list. New active SUP list: ~ $$
SUP0: MYSCCM.contoso.corp, group =, nlb matches ~ $$
Find a supported WSUS version (min WSUS 3.0 SP2 + KB2720211 + KB2734608) ~ $$
Failed to create assembly name object for Microsoft.UpdateServices.Administration. The error implies 0x80131701. ~ $$
A supported version of the Microsoft.UpdateServices.Administration assembly was not found. ~ $$
STATMSG: ID = 6607 SEV = E LEV = M SOURCE = “SMS Server” COMP = “SMS_WSUS_CONFIGURATION_MANAGER” SYS = MYSCCM.contoso.corp SITE = MRA PID = 2832 TID = 4612 GMTDATE = Monday 16 September 06: 04: 14.179 2015 ISTR0 = “MYSCCM.contoso.corp” ISTR1 = “” ISTR2 = “” ISTR4 = “” istr3 = “” ISTR5 = “” ISTR6 = “” ISTR7 = “” ISTR8 = “” ISTR9 = “” NUMATTRS = 0 $$
STATMSG: ID = 6600 SEV = E LEV = M SOURCE = “SMS Server” COMP = “SMS_WSUS_CONFIGURATION_MANAGER” SYS = MYSCCM.contoso.corp SITE = MRA PID = 2832 TID = 4612 GMTDATE = Monday 14 September 06: 04: 14.183 2015 ISTR0 = “MYSCCM.contoso.corp” ISTR1 = “” ISTR2 = “” ISTR4 = “” istr3 = “” ISTR5 = “” ISTR6 = “” ISTR7 = “” ISTR8 = “” ISTR9 = “” NUMATTRS = 0 $$
Let us know when WSUS version 6.3.9600.16384 for SCCM will be supported next year R2 SP1.
I have two Windows 2012 R2 servers, one with SCCM 2012 SP1 configured and the other with WSUS v4 (6.3.9600.16384). I SCCM cannot install the best SUP / WSUS on the remote server. When comparing the two servers, the firewall ports are not blocked and I added the service side on the computer and the SCCM side as local admin ra.
There are guides that include installing WSUS and running the wizard until you select a product and change your configuration. Then insert SCCM SUP, but I keep seeing WCM.log if there is a lag indicating that the WSUS version is probably not supported.
Supported WSUS version not foundRemote settings on a failed WSUS serverSet the new config to 3 (WSUS_CONFIG_FAILED)
Most of the tutorials I’ve seen have been about setting up a local SUP, but I need a SUP on some kind of remote server. This is an unrepaired installation, not an update. There is also a line like this:
Check the supported version by WSUS (min.WSUS 3.0 SP2 + + kb2720211 KB2734608)
But it seems to work. I have SCCM version 5.0.7804.1000 (SP1). I saw cumulative changes, but couldn’t guess what it was for WSUS.
This entry was filed on Windows-Treffpunkt Server and tagged SCCM, SCCM 2012 WSUS, SCCM Software Update Point, SCCM Software Update Point Prereq, WSUS, WSUS 3.0, WSUS 3.0 SP2.
SCCM 2012: WSUS 2.0 SP2 Or Higher Is Not Installed Or Cannot Be Contacted
This week Iran into an issue where I had to rebuild the shared WSUS server to be used by my next SCCM software update point. Uninstall / reinstall according to WSUS via Server Roles, I downloaded and installed SP2 for WSUS 3.0 because that is the benchmark for SCCM 2012 which should be good in the end! No. This is not the case.
Issues with SMS_WSUS_CONFIGURATION_MANAGER status showed many errors that were unfortunately not installed or even unavailable from “WSUS Server Version 2.0 SP2 with the above” as well as other related status queries in WSUS. Dig, dig, dig! Is this where newspapers can come in handy.
Open WCM.log in CMTrace and verbosity will save your life!
You will definitely find that, like all similar components of SCCM, if any obstacles are present, it will retry every 60 minutes. “No supported version of WSUS found,” but wait – one of the log entries tells you exactly what it is looking for (would it be nice to know how incredible the requirement is?). WSUS 3.0 SP2 + KB2720211 + KB2734608. After normal installation, thistheir two KB fixes, restart the SMS_WSUS_CONFIGURATION_MANAGER component (or restart this computer) and restart VOILA! Everything begins to take root and to be treated correctly. I’ll add a link to the website with two fixes below. Have a nice update!
I hope I made your day easier.
Speed up your computer today with this simple download.
Sugestões Para Corrigir Uma Versão Suportada Do Wsus Não Encontrado Sccm 2012
Vorschläge Zur Behebung Einer Unterstützten Version Von Wsus Nicht Gefunden Sccm 2012
Sugestie Dotyczące Naprawy Obsługiwanej Wersji Wsus Nie Znaleziono Sccm 2012
Suggesties Om Een ondersteunde Versie Van Wsus Te Repareren Niet Gevonden Sccm 2012
지원되는 버전의 Wsus를 수정하기 위한 제안 사항 Sccm 2012를 찾을 수 없음
Sugerencias Para Corregir Una Versión Compatible De Wsus No Encontrada Sccm 2012
Förslag För Att Fixa En Version Av Wsus Som Stöds Hittades Inte Sccm 2012
Suggerimenti Per Correggere Una Versione Supportata Di Wsus Non Trovata Sccm 2012
Предложения по исправлению поддерживаемой версии Wsus не найдены Sccm 2012
Suggestions Pour Corriger Une Version Prise En Charge De Wsus Introuvable Sccm 2012
