Alert: Synchronization failure alert for software update point ( SCCM 2012 R2)

SCCM 2012 R2
Alert: Synchronization failure alert for software update point: MY.net(MY)
Alert type: Software update synchronization failure
Severity: Critical
Active time (UTC): 13-09-2014 19:37:34
Condition: Generate an alert if software updates synchronization fails for the Software Update Point role at the
MY (MY) site.
Alert Text: Software updates synchronization for the Software Update Point role at the
MY (MY)) site failed.
Please let me know what will be the cause of this Alert, how to resolve it

The reason is stated in the message: "Generate an alert if software updates synchronization fails
for the Software Update Point role at theMY (MY) site"
Examine wsyncmgr.log
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

Client not receiving the software update FROM SCCM 2012 R2

We have SCCM 2012 R2 installed and configured for SUP.and i have synchonice the SUP with WSUS server in the same which is there in the same machine.
Now i can able to deploy the software update from SCCM 2012 R2 without any erro to the windows 7clients, but client side when i check there is no update installed in the clients , but seems there is no error in the client logs

Hi,
I'd start with running a "Software Updates Scan Cycle" from the configuration manager control panel applet and check the log file Windowsupdate.log, WUAhandler.log.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How would I rollback or remove a problematic software update using SCCM 2012?

How would I rollback or remove a problematic software update using SCCM 2012?
Primarily I'm thinking these patches would be Windows Vista/7/8 OS patches, but would include other Microsoft updates as well (eg. Office, etc.).
Thanks,
Bill

Hi,
You need to uninstall it using software distribution like a package/program, here is a script that can help you with the uninstallation.
http://blog.coretech.dk/jgs/vbscript-uninstall-updates-on-winxpwin2003-win7-and-win-2008-r2-automatically/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Open port for Software Update Point

hallo
i need open port for the Software Update Point (wsus) ?
thanks
אם תגובתי פתרה את בעייתך - לחץ/י, על "סמן כתשובה" ליד סימן ה V הירוק.

For a default installation of WSUS that would be HTTP 8530 or HTTPS 8531
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Remote Distribution Points for Software Update Point Site

Hi,
I have deployed Primary Site MP (SCCM 2012 R2) in the Main Office. In our environment, we have many remote offices with limited internet connection.
Is it best to setup Secondary Site in those remote offices or setup Distribution Points? What are the considerations?
Thanks.
~Andre

You only install one SUP. You can't install a SUP on DP's, and you don't need to install WSUS on DP's either, just IIS.
The clients will need to connect to the SUP (port 8530) to get the windows update catalogue. If they can't connect to your MP and SUP directly, then you will need to check your proxy configuration on the clients
Once the client has performed a scan, it will then match what it determines are "required updates" against what you have deployed in its client policy.
The client then connects to the local DP to download the updates and install them.
The client only downloads policy from an MP. If you have a DP on the same server as the MP then clients may try to download updates if you don't have your content boundaries configured correctly, and have also allowed them to use a fallback location.
To prevent clients going over the WAN to download the updates, check your update deployment under the "Download Settings" tab and choose "Do not install software updates" on both the options, and make sure you have your content location
boundaries configured correctly with the DP at each remote site assigned to the correct boundary.

RPC server is unavailable when trying to download software updates through SCCM 2012

I have read plenty of articles concerning RPC server problems and non of them seem to relate to this issue. I have been trying to set up my CM 2012 server to deploy software updates and I am to the point of just needing to filter the updates, download
and deploy them. When I try to download the updates from the internet, I get an RPC server unavailable error and it closes. I have checked the RPC service and all of its dependencies, verified that it is looking for a correct microsoft update service
point, disabled my firewall and opened all ports on the firewall just to verify that it wasn't that, and ping tested a few other external sites (aka: Newegg.com/google.com) to see if I could get replies (which I did).
Not really sure where to go from this point. Anyone else encounter this before or know how one might fix it?
Jeffrey IT - Tech Support Tier 2 Buyseasons, INC

Apologies, it was only like 6 lines in CMTrace and I thought it posted ok. Here is the text version:
Trying to connect to the root\SMS namespace on the syscenter.BUYSEASONS.com machine. $$<Software Updates Patch Downloader><06-28-2012 15:46:04.463+300><thread=4756 (0x1294)>
Connected to \\syscenter.BUYSEASONS.com\root\SMS $$<Software Updates Patch Downloader><06-28-2012 15:46:04.465+300><thread=4756 (0x1294)>
Trying to connect to the \\nbsccm01.buyseasons.com\root\sms\site_NB2 namespace on the nbsccm01.buyseasons.com machine. $$<Software Updates Patch Downloader><06-28-2012 15:46:04.467+300><thread=4756 (0x1294)>
ConnectServer() failed to connect to nbsccm01.buyseasons.com $$<Software Updates Patch Downloader><06-28-2012 15:46:04.480+300><thread=4756 (0x1294)>
ERROR: DownloadContentFiles() failed with hr=0x800706ba $$<Software Updates Patch Downloader><06-28-2012 15:46:04.481+300><thread=4756 (0x1294)>
Trying to connect to the root\SMS namespace on the syscenter.BUYSEASONS.com machine. $$<Software Updates Patch Downloader><06-28-2012 15:46:04.680+300><thread=4756 (0x1294)>
Connected to \\syscenter.BUYSEASONS.com\root\SMS $$<Software Updates Patch Downloader><06-28-2012 15:46:04.682+300><thread=4756 (0x1294)>
Trying to connect to the \\nbsccm01.buyseasons.com\root\sms\site_NB2 namespace on the nbsccm01.buyseasons.com machine. $$<Software Updates Patch Downloader><06-28-2012 15:46:04.683+300><thread=4756 (0x1294)>
ConnectServer() failed to connect to nbsccm01.buyseasons.com $$<Software Updates Patch Downloader><06-28-2012 15:46:04.685+300><thread=4756 (0x1294)>
ERROR: DownloadContentFiles() failed with hr=0x800706ba $$<Software Updates Patch Downloader><06-28-2012 15:46:04.687+300><thread=4756 (0x1294)>
Trying to connect to the root\SMS namespace on the syscenter.BUYSEASONS.com machine. $$<Software Updates Patch Downloader><07-23-2012 16:47:05.531+300><thread=7108 (0x1BC4)>
Connected to \\syscenter.BUYSEASONS.com\root\SMS $$<Software Updates Patch Downloader><07-23-2012 16:47:05.550+300><thread=7108 (0x1BC4)>
Trying to connect to the \\nbsccm01.buyseasons.com\root\sms\site_NB2 namespace on the nbsccm01.buyseasons.com machine. $$<Software Updates Patch Downloader><07-23-2012 16:47:05.552+300><thread=7108 (0x1BC4)>
ConnectServer() failed to connect to nbsccm01.buyseasons.com $$<Software Updates Patch Downloader><07-23-2012 16:47:05.565+300><thread=7108 (0x1BC4)>
ERROR: DownloadContentFiles() failed with hr=0x800706ba $$<Software Updates Patch Downloader><07-23-2012 16:47:05.566+300><thread=7108 (0x1BC4)>
Trying to connect to the root\SMS namespace on the syscenter.BUYSEASONS.com machine. $$<Software Updates Patch Downloader><07-23-2012 17:04:05.693+300><thread=5124 (0x1404)>
Connected to \\syscenter.BUYSEASONS.com\root\SMS $$<Software Updates Patch Downloader><07-23-2012 17:04:05.694+300><thread=5124 (0x1404)>
Trying to connect to the \\nbsccm01.buyseasons.com\root\sms\site_NB2 namespace on the nbsccm01.buyseasons.com machine. $$<Software Updates Patch Downloader><07-23-2012 17:04:05.696+300><thread=5124 (0x1404)>
ConnectServer() failed to connect to nbsccm01.buyseasons.com $$<Software Updates Patch Downloader><07-23-2012 17:04:05.699+300><thread=5124 (0x1404)>
ERROR: DownloadContentFiles() failed with hr=0x800706ba $$<Software Updates Patch Downloader><07-23-2012 17:04:05.700+300><thread=5124 (0x1404)>
Nbsccm01 is also our migration server that is no longer in service, is there anyway to disconnect this server permanently?
Thanks!
Jeffrey IT - Tech Support Tier 2 Buyseasons, INC

Software Update error - SCCM 2012 SP1

HI,
I have SCCM 2012 SP1 installed on Windows server 2008 R2 server. I have configured SUP role and tried sync from sccm console. I get the below error.
LOg:
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:11:42.047+00><thread=3840 (0xF00)>
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:12:42.255+00><thread=3840 (0xF00)>
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssCommunicationError: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning() $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.462+00><thread=3840
(0xF00)>
Done using DEVSWAD\SWDTR-SRV-CMPATCH credentials~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
Failed to set Subscriptions on the WSUS
. Error:(-2146233088)Unknown error 0x80131500~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=3840 GMTDATE=Thu Jan 30 14:13:12.479 2014
I have configured proper proxy account which can connect to microsoft website and the port i have configured in proxy to allow is
80 and 443. I feel the port i need to allow may be i am not sure 8530 and 8531. Or 80 and 443 is fine. Please help
Regards, Pratap

It says to check WCM.log which i posted above
wsync log:
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.118+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 14:02:14.119 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please
refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.123+00><thread=4388 (0x1124)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.132+00><thread=4388 (0x1124)>
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:14.495+00><thread=4388 (0x1124)>
Starting Sync $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.157+00><thread=4388 (0x1124)>
Performing sync on retry schedule $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.163+00><thread=4388 (0x1124)>
Read SUPs from SCF for DCMPSTPV01.devswad.net $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.577+00><thread=4388 (0x1124)>
Found 1 SUPs $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.830+00><thread=4388 (0x1124)>
Found active SUP DCMPSTPV01.devswad.net from SCF File.~ $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.833+00><thread=4388 (0x1124)>
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.876+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 15:02:15.882 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please refer
to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.892+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.912+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.915+00><thread=4388 (0x1124)>
Sync time: 0d00h00m01s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.024+00><thread=4388 (0x1124)>
Next scheduled sync is a retry sync at 31/01/2014 16:02:15 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.151+00><thread=4388 (0x1124)>
Regards, Pratap

Understanding background work for software distribution in SCCM 2012

Hi Team,
1.I want to know site to site communication for SCCM 2012.. and
2. want to know about package transfer to secondary site or content share background process.
3. In many of the content share server 200 package out of this 90 still showing inprogress.. I checked distribution point but no error.. I checked conponent status " saying xxx001 package processed.
Can some one answer this three question?

Hi,
Configuration Manager uses file-based replication to transfer packages between sites in your hierarchy.
Reference:http://technet.microsoft.com/en-us/library/gg712701.aspx#BKMK_File_based
The blog below is talking about the Site to Site Communication in SCCM 2007, but it can help you understand the process of packages transfer to secondary site.
Understanding Site to Site Communication in SMS/SCCM
http://blogs.msdn.com/b/steverac/archive/2010/07/16/understanding-site-to-site-communication-in-sms-sccm.aspx
You could check Distmgr.log and sender.log to get more information. It should take some time in order to transfer so many packages.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to remove the parent-child software update point in sccm 2012 sp1

I have a CAS , Primary site server(1) and secondary site servers (7). I have software update point installed on CAS, Primary server and Secondary site servers as well.
I have a situation to reinstall the software update point which is in primary site server.
So, How to reinstall the software update point in primary site server since this is located in the middle between CAS and secondary site servers.
So, please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
I have referred few posts on how to remove SUP
https://social.technet.microsoft.com/Forums/en-US/c7258aad-d968-427b-8826-4829916c14c9/remove-and-re-add-software-update-point-sccm-2012?forum=configmanagersdk
and how to install SUP
http://www.windows-noob.com/forums/index.php?/topic/4467-using-sccm-2012-in-a-lab-part-6-deploying-software-updates/

Hi,
>> please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
I just tried to reinstall the SUP on the Primary site(only one SUP on Primary site and there is a SUP on Secondary site). The SUP upstream data source of the Secondary site showed empty and greyed out. But the upstream data source resumed after a while.
It seems nothing special needs to be done.
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

Hi All,
Good day to all you.
I would like to seek all your help on this issue that i have encountering.
My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
Error:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
below are wsyncmgr.log:
Setting sync alert to active state on site C01 SMS_WSUS_SYNC_MANAGER (0x1690)
Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Starting Sync SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Read SUPs from SCF for MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
5776 (0x1690)
Synchronizing WSUS server MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
5776 (0x1690)
Using account sdb\SCCM-Admin to connect to WSUS Server
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Synchronizing WSUS server myhqkul990707s.sdb.com ...
SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
440 (0x01B8)
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
All response is much appreciated
Thank You

Hi,
I recommend you look at the IIS log. Maybe it can give us some clues.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Software Update Point Switching is not working for some Clients

Hi there,
I found nothing similar here and I hope this is the right section.
I´m running ConfigMgr 2012 R2 where one of the Site Systems from one of the Primaries is located in an untrusted Forest in a perimeter Network. The Site System there has the MP, SUP and DB Roles. In general it works great. The Systems in that untrusted Forest
get the SCCM Agent pushed, see and can install published Software packages and receive Windows Updates. But there are a few systems where everything works, except Windows Updates.
So I had a deeper look at what is happening and found out that the SUP switching is not working for them. They always try to contact the SUP from the Primary, which they cannot reach (this is intended).
From how I understand SUP switching as described here
http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/software-update-points-in-cm2012sp1.aspx#pi140062=1
the Windows Update Agent tries to connect to a SUP every 30 minutes and after 4 failed attempts he will try to connect to the next one until he finds one which works.
As I said before, this seems to work for most systems in the untrusted forest, but some do not make any intentions to switch the SUP.
So my next step was to find out from where the Update Agent can get the information of the available SUPs. I think they either don´t receive the information that other SUPs exist, or if the Information is there, they don´t realize that there´s an error and
make no attempt to switch.
I used the System Center Support Center to gather all Information from some of the systems with that problems (Log Files, WMI information, registry information, policies etc.) but I cannot find where SCCM or the Update Agent store the information which SUPs
are available in my environment.
I´m sure the problem is on the Systems which fail to connect to the right SUP and not in the SCCM infrastructure itself, because for most of the systems everything is working just perfect. Unfortunately in the Blog Post above there´s also no information
where this information is stored and how it is obtained by the clients. In the comments there´s even one post which describes the same problem I have here, but there was no answer. I hope someone can point me into the right direction, because I´m stuck currently.
Things I tried additionally to all the log file / WMI / registry sniffing:
Removing the Software Distribution Folder and restarting the Windows Update Agent
Removing the WindowsUpdate Registry folder in the HKLM\SOFTWARE\Policies\Windows section in the Registry and restarting the Windows Update Agent.
Tried to reset the WUAgent with wuauclt /Resetauthorization additionally to the steps above.
I also tried to manually set the WUServer and WUStatusServer Keys in the registry to the new Server, but as soon as the next Update Scan cycle runs, the value is set back to the URL of the Primary Sites SUP
Is someone having additional ideas? It seems to me older systems are more affected (which were configured for a standard WSUS before SCCM 2012 was deployed) than newer ones which were installed when SCCM was in place already. But I don´t know what else to
"reset" on those machines without reinstalling them.

Thank you very much for your response. I must have missed that one by looking through numerous Logfiles. In this, there´s indeed a list of all available SUPs. So according to the LocationServices.log the machine should have a choice.
The WMI Key however, contains just one entry and this is the URL of the Primaries SUP which is not reachable in the untrusted forest. Is it OK that the WMI entry includes only one entry? If yes, what process is putting the results from the LocationServices
into WMI? It seems like the Windows Update Agent is feeded from the WMI Key then. If this is the case my problems seems to be the "communication path" between these two components.
Is this the job from the SCCM Agent, the Windows Update Agent or maybe some third component I´m not aware of? I wonder how I can fix this.

Software Update Point doesn't show Win 2012 R2 and Windows 8.1 updates

I started deploying Windows 2012 R2 Datacenter servers and some Windows 8.1 workstations. I wanted to make sure that my Software Update Point was downloading updates available to those OS's and after going in to Administration -> Overview -> Site Configuration
-> Sites -> Configure Site Components -> Software Update Point, I notice that those OS's weren't available to select.
I then did some searches on the web and thought my problem was two fold:
1 - I was using SCCM 2012 SP1.
2 - My SCCM 2012 Software Update Point was on a Win 2008 R2 server
So the first thing I did was upgrade from SCCM 2012 SP1 to SCCM 2012 R2. I then created a Windows 2012 R2 Datacenter server and installed WSUS on it. I then added the server as a Site System Server, added the Software Update Point to it and configured it.
Unfortunately, this still didn't help me as you can see from the screen shots below:
What am I doing wrong and what needs to be done to have all the updated Operating Systems and Microsoft Software added to my Product list?
Thanks... Frank

To follow on to narcoticoo's statement, have you actually initiated a catalog sync from within the ConfigMgr console yet? If so, has it completed successfully (you can check the moniotring workspace or you can watch the wsyncmgr.log).
Jason | http://blog.configmgrftw.com
Jason...
I just ran a Synchronize Software Updates from ConfigMgr Console. I then went Monitoring -> Software Update Point Sync Status. It's showing my new WSUS server ( 2012 R2 ) but it's not showing any updates are being sync'd through it. See this screen shot:
I then went to the wsyncmgr.log file on my site server which is the OLD WSUS server ( Win 2008 R2 ) and say this:
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=PREP-SCCM12.<domain.org> SITE=STA PID=5224 TID=4028 GMTDATE=Wed Feb 26 19:00:40.236 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site STA. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.236+300><thread=4028 (0xFBC)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.279+300><thread=4028 (0xFBC)>
Setting sync alert to active state on site STA $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.313+300><thread=4028 (0xFBC)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.360+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win 7 Updates up to Aug 2012\0048da55-f46f-4452-b4c1-37c0f295333b\IE9-langpack-Windows7-x86-xho.exe, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.042+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win 7 Updates up to Aug 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.067+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win2k8 Updates Until Aug 2012\000f8a0a-825c-457b-a15b-57ade145a09b\windows6.0-kb2653956-x64.cab, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.119+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win2k8 Updates Until Aug 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.144+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win 7 Updates for Sept 2012\10f3ec1c-f096-4a82-ae41-440ba5328467\Windows6.1-RTM-Client-NEUTRAL-X86.EXE, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.173+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win 7 Updates for Sept 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.199+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\XP Updates Until Sept 30\17165524-99fa-49f7-91e6-457d43d4a48e\Windows-KB890830-V4.12.exe, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.228+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\XP Updates Until Sept 30, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.254+300><thread=4028 (0xFBC)>
It appears to me that when doing a Sync, it's still trying to use my OLD WSUS server instead of my new one. I removed the Software Update Point from the OLD WSUS server and uninstalled WSUS from it. I'm not sure why it's still trying to sync from the old
server rather than the new one. Any ideas?
Thanks... Frank

Software update point unable to be installed Sccm2012

Hey all,
I have come across a frustrating issue with SCCM 2012 while trying to install Software update point,
Environment: 1 X single site sccm 2012 SP1 5.00.7804.1300
Wsus to install updates - want to enable Service update point to deploy updates.
History: the Wsus server was configured and initialized
doring the original installation, i reinstalled the WSUS without initial config.
Problem:
the SCCM is unable to install the SMS_WSUS_Control_Manager
Event Log Errors:
Event 1016:
On 07/04/13 21:13:56, component SMS_SITE_COMPONENT_MANAGER on computer SCCMSRV.DOMAIN.LOCAL reported: Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Event 6703:
On 04/07/2013 21:10:35, component SMS_WSUS_SYNC_MANAGER on computer SCCMSRV.DOMAIN.LOCAL reported: WSUS Synchronization failed.
Message: WSUS update source not found on site SYN. Please refer to WCM.log for configuration error details..
Source: getSiteUpdateSource.
The operating system reported error 2147500037: Unspecified error
The WCM.log indicated that updates KB2720211 + KB2734608 event though the updates are installed several times.
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.056-180><thread=5972 (0x1754)>
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.058-180><thread=5972 (0x1754)>
Did not find supported version of assembly Microsoft.UpdateServices.Administration.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.196-180><thread=5972 (0x1754)>
Checking runtime v4.0.30319...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.197-180><thread=5972 (0x1754)>
Did not find supported version of assembly Microsoft.UpdateServices.Administration.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.210-180><thread=5972 (0x1754)>
Supported WSUS version not found~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.211-180><thread=5972 (0x1754)>
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCMSRV.domain.local SITE=SYN PID=3276 TID=5972 GMTDATE=יום ה יול 04 15:45:57.211 2013 ISTR0="SCCMSRV.domain.local" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.211-180><thread=5972 (0x1754)>
Remote configuration failed on WSUS Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.212-180><thread=5972 (0x1754)>
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCMSRV.domain.local SITE=SYN PID=3276 TID=5972 GMTDATE=יום ה יול 04 15:45:57.212 2013 ISTR0="SCCMSRV.domain.local" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.212-180><thread=5972 (0x1754)>
Setting new configuration state to 3 (WSUS_CONFIG_FAILED)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.214-180><thread=5972 (0x1754)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.214-180><thread=5972 (0x1754)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:45:57.215-180><thread=5972 (0x1754)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:46:02.977-180><thread=5972 (0x1754)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:46:02.977-180><thread=5972 (0x1754)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:46:02.981-180><thread=5972 (0x1754)>
Shutting down... $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:53:59.991-180><thread=5972 (0x1754)>
Shutting Down...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 18:53:59.994-180><thread=5972 (0x1754)>
SMS_EXECUTIVE started SMS_WSUS_CONFIGURATION_MANAGER as thread ID 7164 (0x1BFC). $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.486-180><thread=5940 (0x1734)>
This SCCMSRV.domain.local system is the SMS Site Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.539-180><thread=7164 (0x1BFC)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.551-180><thread=7164 (0x1BFC)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.554-180><thread=7164 (0x1BFC)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.554-180><thread=7164 (0x1BFC)>
SUP0: SCCMSRV.domain.local, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.555-180><thread=7164 (0x1BFC)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.555-180><thread=7164 (0x1BFC)>
Waiting for changes for 1 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:33.556-180><thread=7164 (0x1BFC)>
Wait timed out after 0 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:34.560-180><thread=7164 (0x1BFC)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><07-04-2013 19:15:44.598-180><thread=7164 (0x1BFC)>
Event 1:
System.NullReferenceException\r\nObject reference not set to an instance of an object.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryPropertySingleItem.get_IntegerValue()
at Microsoft.ConfigurationManagement.AdminConsole.SoftwareUpdateHelper.DisplayUtilities.GetSupSyncStatusIcon(Object sender, ScopeNode scopeNode, IResultObject resultObject, AssemblyDescription& resourceAssembly)\r\n
Any ideas?
Reagards
Asaf

WSUS was installed and configured and work fine a few monthes ago as a part of the first try to install SUP before aplying SP 1 to SCCM.
Both SCCM and WSUS are installed on the same server.
now we want to deploy all updates from SCCM SUP, and the installation failed.
after researching online, uninstalled WSUS completely from the SCCM server, and removed SUP from the Site and rebooted the server.
installed WSUS 3.0 SP2, when initial config of the WSUS popped up i canceled it, the only config i made
is at the installation wizard, set the port to 8530, folders location and internal DB.
>> i am able to open the WSUS console and connect to the "localhost" but no settings
are configured.
installed update 2734608, reboot.
Installed SUP.
and here we are.

HT5362 How do I turn off notifications for Software Updates? 'App Store' doesn't show in the list of notification apps. I want the background checks for updates, just not the notifications.

How do I turn off notifications for Software Updates?
In the 'Notifications' section of the 'System Preferences' app, there is no tab for managing the notifications of System Updates nor App Store.
Hey--- I like auto-checking for updates, and hey--- I like auto-downloading them in the background.
BUT I do not like being notified of updates in the middle of working! Especially when it's iTunes updates. Grrrr.
Any chance this is easy and I just missed it?
THANKS COMMUNITY!

Settings > Notification Center > Mail > Select the mail account (if more than one) > Alert Sound > None

New board for Software Updates - read this first!

Dear Nokia Support Discussions members,
we are happy to introduce this new section for discussing Nokia phone software updates with your PC or over-the-air.
Please use this board to discuss
- Nokia Software Updater PC application or over-the-air updates
- latest software versions for each product
- any changes you notice over previous software versions
- making a back-up of your phone data
- problems you may encounter with the update
etc.
First and foremost, Nokia Support Discussions is a meeting place for Nokia product owners. Here you can discuss Nokia products, ask for assistance and help other people by providing solutions. Nokia Moderators are here mainly to give assistance in using the boards and to keep the discussions on track.
However, these boards are also a feedback channel to Nokia and people from many different Nokia departments actively follow these discussions. Constructive feedback and criticism is valued and always welcome.
We at Nokia Support Discussions do not have any information about when new products are added to the update service - nor do Nokia contact centers. So you just need to keep checking the service webpage or the boards here. I am sure new products are announced here by our alert members within minutes after they have been added.
I wish to remind the community that posting any confidential information about Nokia product software versions will be deleted and may result in a permanent ban without warning.
Below is the introductory letter that we received from the Nokia Software Update Team - please read it for important information about new products and their schedule.
See you on the boards,
vandelay & Nokia Support Discussions Team
The Nokia Software Updater is a Windows application that enables you to update Nokia mobile device software (firmware) over the Internet using your PC. The application can be downloaded from the Nokia UK Product Support Internet pages at
www.nokia.co.uk/softwareupdate
The Nokia Software Updater offers the same updates you would receive at a Nokia Service Centre. The added advantage is the convenience, as you can now easily perform the update yourself from any location with an Internet connection, at a time suitable for you. Keep your phone software up-to-date, or fix a potential operation problem you may have by regularly updating your phone firmware.
In the future, every new S60 product will be compatible with the Nokia Software Updater, but at the moment the application is only available for selected Nokia devices including Nokia 6630, Nokia 6680, Nokia 6681, Nokia 6682, Nokia N70 and Nokia N72. During the autumn, the application will be available in different languages on different web pages and many other products will also be available for software updates.
The Nokia Software Updater has been made to be as customer-friendly as possible. All you need is a PC and the standard sales-pack data cable - no dongles, no adaptors, no fuss. A typical update takes around 30 minutes. Plus, you don’t need to wait for your device to be returned from Nokia Service Centre.
Regards,
Nokia Software Update Team
(letter dated August 21st, 2006)Message Edited by vandelay on 12-Oct-2006
09:12 AM
Message Edited by vandelay on 30-Oct-2007 02:11 PM
I wrote all my posts from 2005-2011 as an "Admin" for this community. I still work for Nokia as an external consultant, so my rank in all posts is now "Employee".

Read the comment!

Alert: Synchronization failure alert for software update point ( SCCM 2012 R2)

Similar Messages

Maybe you are looking for