WSUS Synchronization changes

I have an upstream and downstream WSUS server. When I set the upstream for say 2 am, it immediately changes to something between 2 and 2:30. I get that, it says the schronization will start up to 30 minutes after your schedule.
On my downstream server, I set the sync for 3am.  I checked this morning and it ran at 6am.  I then looked at the schedule for the downstream server and it is set to 6am.  Why did it jump 3 hours?

On my downstream server, I set the sync for 3am.  I checked this morning and it ran at 6am.  I then looked at the schedule for the downstream server and it is set to 6am.  Why did it jump 3 hours?
The only logical response I have to this is that you are mistaken about what time you set the synchronization event for -- or somebody else changed it after you set it.
There are no known misbehaviors regarding the synchronization configuration functionality of WSUS.
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.

Similar Messages

  • SCCM 2012 and WSUS Synchronization error. Message ID: 6703.

    Hi,
    I am facing issues with synchronising updates in WSUS server with SUP in SCCM 2012. I am using web proxy, which has full access to all microsoft update websites. I have configures SUP for both intranet and internet clinets. I am posting some logs below
    that may help to resolve the issue:-
    wsyncmgr.log-
    Synchronizing WSUS server SCCMSERVER.domain.com SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 3824 (0x0EF0)
    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 6368 (0x18E0)
    Sync failed: UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 11/1/2012
    11:58:04 AM 3824 (0x0EF0)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
    ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
    NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
    WCM.log-
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:21 AM 4016 (0x0FB0)
    Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>1403f223-a63f-f572-82ba-c92391218055</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>84f5f325-30d7-41c4-81d1-87a0e6535b66</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>8c3fcc84-7410-4a95-8b89-a166a0190486</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>6964aab4-c5b5-43bd-a17d-ffb4346a8e1d</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
    11:52:21 AM 4016 (0x0FB0)
    Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~ <Id>cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
    11:52:22 AM 4016 (0x0FB0)
    WSUSCtrl.log-
    WSUS registry key change notification triggered. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~  
    at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Failed to set WSUS Local Configuration. Will retry configuration. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Urgent Help Appreciated.
    Thanks,
    Deepak

    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
    ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
    ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
    System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~  
    at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Those errors are unrelated to ConfigMgr. The first one is a name resolution error; the second one tells that the servers is not allowed to connect to the proxy.
    Torsten Meringer | http://www.mssccmfaq.de

  • SMS Server 6703 - SMS WSUS Synchronization Failed

    Hi,
    i am getting the following error on SCCM server,
    "on 3/6/2011 12:00:00 PM component SMS_WSUS_SYNC_MANAGER on computer "ComputerName"  reported:   SMS WSUS Synchronization failed.  Message: WSUS server not configured.  Source: CWSyncMgr::DoSync.   The operating system
    reported error 2147500037: Unspecified error " with message ID 6703
    i have SCCM server and WSUS server, it was working suddenly it started behaving as above.
    i have check all SUP configuration, Proxy Settings, and all related.
    why it is unable to sync with WSUS server, any idea ?\
    Regards

    Hi Owais,
    I've found a few more posts with the same error you mentioned.
    Problems Synchronizing System Center Configuration Manager Software Updates "SMS WSUS Synchronization Failed":
    http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server/Q_24025939.html
    which mentions: Found a useful tip that solved this problem for me in a SCCM/WSUS installation on the same server. It all comes down to removing the FQDN in the SUP role. Do this by removing the SUP role and reinstalling it. Uncheck the FQDN checkbox and
    it works (at least it did in my case).
    WSUS Error:
    http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/98c8b384-7e15-4143-820f-ff165ec7623e
    WSUS SERVER not configured (Error 6703):
    http://www.myitforum.com/forums/tm.aspx?high=&m=179760&mpage=1#179760
    which mentions: I have check Automatic Detect Setting and I have filled proxy address and it works !!!!
    Regards, Henk
    My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

  • SCCM WSUS Synchronization fails with error 0x80131904

    With no reason the software update point in SCCM 2012 CU3 fails to synchronize update from the local installed WSUS service. I have checked the WSUS Sync manager log and what I have got is in the image below. I have tried to uninstall and the WSUS service
    and reinstalled it but no success. I have also used the clean up option from the WSUS console and no success yet. 
    From the log below I am quite sure that if I can force the removal or clean up those updates that are failing to get saved the SCCM Update point synchronization might be able to fully synchronize. I hope someone can help me out. Thanks in advance.
    Event view error - 2148734208
    Wsyncmgr.log

    I need WCM.log for investigation. Please upload this file to Skydrive and post the link here.
    Juke Chou
    TechNet Community Support

  • WSUS synchronization Progress struck at 0%

    Hi,
    When trying to synchronize a WSUS 3.2 computer, it may not sync and progress may remain at 0%. When this occurs you may not see any obvious errors and the sync may never completely fail. Firewall port is open. When this occurs you may not see any obvious
    errors and the sync may never completely fail.
    Syed

    Hi,
    Could you tell the hierarchy of your WSUS? Is this a updatetream server? Does this server sync from proxy server or microsoft update?
    Please review softwaredistribution.log, this may give us some clues about synchronization.

  • Failure to Synchronize Changes

    Hello,
    I am fairly new to itunes in general.  I have one machine I consider the master since the files all reside on that machine and it was used for initial configuration.  I had inadvertently double added most of my music library on the master before signing up for Match.  Thus Match also adopted the duplicate song listings.  I have since cleaned up the local library and iTunes on that machine and it now accurately reflects my music library with no duplicates(and yes I did check the box to remove files from the cloud as well).
    The problem arises when I access Match from one of my other machines that have no downloaded content but stream my library from Match(like my ipad mini).  All of these devices still show duplicates.  An amusing feature is that only half of the songs actually play.  That is to say if I have a song listed twice then one instance will play and the other will not.  So shuffle mode play is a real treat with delays of up to a minute between songs as it tries to find songs that will actually play.  
    I have tried doing an "update Match" but that doesn't seem to make any difference.  What do I need to do to get this all synchronizing automatically or in this case manually?
    Thanks.

    Hello Jim,
    I have not tried that "Shift+turn off", what does it do?
    I have already had too much fun with the itunes file system approach.  If I need to create yet another directory for itunes every time I want Match to take an update then I need to re-evaluate my decision to use apple products.
    I have tried turning Match off and back on in the settings on the remote devices(ipad and ipod) which did not seem to make a difference.
    Nothing is grayed out anywhere.  The master machine has all music listed appropriately with no visible duplicates gray or otherwise.  I then issued the command to update Match which took a while but eventually reported that it was done.  The reduced number of songs did suggest that duplicates had been removed from Match.  But the updates apparently don't push out to the other devices.  Does anything in iTunes synchronize automatically?
    Thanks
    -Nick-

  • Sharepoint Meeting Workspace Does Not Synchronize Changes Made in Sharepoint Calendar

     I have a Sharepoint Meeting Workspace that is no longer able to track changes to individual Workspace Meetings that I make in the Sharepoint Calendar. I get a message
    "Changes to the event were saved, but they could not be communicated to the Meeting Workspace associated with the event. For more information, contact the server administrator. "
    I am looking for clues on how to fix this issue.....

    Hi Amit,
    you can not move specific changes from Dev to production.
    but you can follow this process to make your workflow as it is as in Dev:
    Create a new workflow on the new list in Product.
    Create at least one step, one condition and one action in this workflow.
    1. In Dev server open your .xomal file as XML and copy the entire contents.
    2.In Production server Open your .xoml file as XML and Paste the entire contents
    3. repeat this operation for the xoml.rules file
    4.Double click the .xoml file for the new workflow to open the workflow in the Workflow Designer and click Check Workflow to verify no errors and then click Finish to ensure the workflow is saved.
    Whenever you need to make changes apply the same.
    Please Mark Answer and Vote me if it will to resolve your issue

  • 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.

  • SUP changes update source on WSUS

    So im trying to set up the SUP on SCCM. initially i had the WSUS installed on another server along with SUP. SCCM would never get updates because WSUS would change its source to itself(sync from an upstream source which was the server it was on) and not
    update. If i change the source to sync from microsoft, SCCM would then be able to get updates. so after uninstalling the role and reinstalling the WSUS, the issue still remained and i decided to install the WSUS on the primary server and go from there. Now,
    that the WSUS is on the primary server, the update source gets changed to reflect the old server that it was previously on. i have tried rebooting the servers and the SUP settings are also set to pickup updates from microsoft. Has anyone else encountered this
    issue?

    I understand that WSUS shouldnt be configured because the ConfigMgr does the configuration.. ConfigMgr is configuring the settings incorrectly. Like stated before, the SUP is configured to get updates from microsoft but in WCM.log it states "Successfully
    configured WSUS Server settings and Upstream Server to another
    server" 
    WCM.log should read "Successfully
    configured WSUS Server settings and Upstream Server to microsoft" 

  • WSUS errors - no longer able to sync with MS

    Our environment is SCCM 2012 R2 CU1.  We have a primary site server with local SQL (2012) on a Windows 2012 R2 server.  We also have WSUS and the SUP on this server as well.
    Permissions were changed on the C:\Program Files\Update Services folder.  TrustedInstaller was the owner.  This was changed, which in turn "broke" WSUS.  The permission was restored back to TrustedInstaller.  Unfortunately,
    there were other permission changes as well.  Subfolders under the C:\Program Files\Update Services have domain\Domain Admins as the owner.
    Due to these changes, I can no longer sync with MS for updates.  There are also multiple errors for the SMS_WSUS_CONFIGURATION_MANAGER, SMS_WSUS_CONTROL_MANAGER and the SMS_WSUS_SYNC_MANAGER.
    In the wcm.log file, the errors are:
    System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.Internal.ApiRemoting' threw an
    exception. ---> System.UnauthorizedAccessException: Access to the path 'Update Services' is denied.~   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)~   at System.IO.Directory.InternalCreateDirectory(String fullPath,
    String path, Object dirSecurityObj, Boolean checkHost)~   at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)~   at Microsoft.UpdateServices.Log.GetUsableLogFileName(String fileName, LogFileLocation&
    actualLogLocation)~   at Microsoft.UpdateServices.Log.InitializeFromConfig()~   at Microsoft.UpdateServices.Log.InitializeIfNeeded()~   at Microsoft.UpdateServices.Internal.ApiRemoting..cctor()~   --- End of inner exception
    stack trace ---~   at Microsoft.UpdateServices.Internal.ApiRemoting..ctor()~   --- End of inner exception stack trace ---~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~  
    at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)
    Remote configuration failed on WSUS Server.
    In the wsusctrl.log file,
    System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.Internal.ApiRemoting' threw an
    exception. ---> System.UnauthorizedAccessException: Access to the path 'Update Services' is denied.~   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)~   at System.IO.Directory.InternalCreateDirectory(String fullPath,
    String path, Object dirSecurityObj, Boolean checkHost)~   at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)~   at Microsoft.UpdateServices.Log.GetUsableLogFileName(String fileName, LogFileLocation&
    actualLogLocation)~   at Microsoft.UpdateServices.Log.InitializeFromConfig()~   at Microsoft.UpdateServices.Log.InitializeIfNeeded()~   at Microsoft.UpdateServices.Internal.ApiRemoting..cctor()~   --- End of inner exception
    stack trace ---~   at Microsoft.UpdateServices.Internal.ApiRemoting..ctor()~   --- End of inner exception stack trace ---~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~  
    at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)
    Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes
    The SMS_WSUS_CONFIGURATION_MANAGER messages are Message ID 6600:
    WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "server.domain.com".
    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.
    The SMS_WSUS_CONTROL_MANAGER  errors are Message ID 700 and 7003:
    WSUS Control Manager failed to configure proxy settings on WSUS Server "server.domain.com".
    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.
    WSUS Control Manager failed to monitor WSUS Server "server.domain.com".
    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.
    The SMS_WSUS_SYNC_MANAGER errors are message ID 6703:
    WSUS Synchronization failed.
     Message: WSUS server not configured. Please refer to WCM.log for configuration error details..
     Source: CWSyncMgr::DoSync.
      The operating system reported error 2147500037: Unspecified error
    The SUP WSUS configuration is set to use ports 8530/8531.  We do not have "Require SSL communication to the WSUS server" selected.
    We do have both "Use a proxy server when synchronizing software updates" and "Use a proxy server when downloading content by using automatic deployment rules" selected. 
    We do not use a WSUS connection account.
    If I open the WSUS console, I cannot connect to the server at all.
    In IIS, under the WSUS Administration site, the bindings are set to http-8530, https-8531.  Authentication for the site has the "Anonymous Authentication" enabled.
    I'm trying to restore the permissions and get WSUS working again without having to un-and re-install.
    Is there a document which outlines the permissions needed for the C:\Program Files\Update Services folder(s)?

    Unfortunately, what I've found is that you cannot remove WSUS and leave the DB (at least in Server 2012 R2).
    So the only option is backup the SUSDB, remove WSUS and the DB, reinstall with a new DB, then restore/replace with the "original" SUSDB.

  • SUP not in sync with WSUS

    we recently sttod-up our sccm 2012 environment.  We are still in configuration phase per se.
    our CAS server also has the SUP role.  We installed WSUS on the server prior to setting up the SUP role.
    Nothing is showing up in the Software Library. We have not seen anything that stands out in log.
    We have not found any article that addresses how to troubleshoot issue.
    the servers are all 2008 R2 with SP.  the storage for the WSUS files is considered local and WSUS was setup using Windows Internal Database.
    Any directions?
    Michael Pace Client Services Team Allegis Group, Inc.

    Thanks Jorgen;
    WSUSCtrl.log does nor show any arrors.  however the SMS_WSUS_CONFIGURATION_MANAGER and SMS_WSUS_CONTROL_MANAGER indicate many errors.
    extract of logs as follows.
    SMS_WSUS_CONFIGURATION_MANAGER :
    Error Milestone CAS 10/11/2012 8:31:51 AM SCCM2012CAS.allegisgroup.com SMS_WSUS_CONFIGURATION_MANAGER 6600 WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "SCCM2012CAS.allegisgroup.com".   
    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.
    SMS_WSUS_CONTROL_MANAGER :
    Error Milestone CAS 10/11/2012 8:26:04 AM SCCM2012CAS.allegisgroup.com SMS_WSUS_SYNC_MANAGER 6703  WSUS Synchronization failed.   Message: WSUS server not configured. Please refer to WCM.log for configuration
    error details..   Source: CWSyncMgr::DoSync.    The operating system reported error 2147500037: Unspecified error
    WCM.log:
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
    Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
    WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
    Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
    Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:12 AM 6232 (0x1858)
    Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:12 AM 6232 (0x1858)
    Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:13 AM 6232 (0x1858)
    Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:13 AM 6232 (0x1858)
    Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:14 AM 6232 (0x1858)
    Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
    Not yet ready to set WSUS Server subscription as returned by WSUS Server. Will try again. SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
    This error is transient and will be retried in 1 minutes. SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
    Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
    Wait timed out after 1 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:29:19 AM 6232 (0x1858)
    Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:29:24 AM 6232 (0x1858).
    thanks again
    Michael Pace Client Services Team Allegis Group, Inc.

  • Recommended order for running clean-up wizard in wsus upstream / replica hierarchy

    Hi :)
    Is there anywhere documented recommended order for running clean-up wizard in wsus upstream / replica hierarchy ?
    Should I first run on Upstream and than on Replica or vice versa ?
    I've found on this blog
    http://www.madanmohan.com/2010/10/sms-wsus-synchronization-failed.html that clean-up should be run always from bottom (replica) to the top (upstream).
    Also, is there any news for WSUS 4 :) ?
    Best regards

    YES,you'd better run the WSUS Server Clean-up Wizard from the bottom of the WSUS hierarchy to the top and NEVER from the top down.
    I totally disagree! The Server Cleanup Wizard should be run on the upstream server first, to ensure that
    updates that will be deleted are no longer synchronized to the downstream server. Furthermore, if you run the SCW on the downstream server first, and it deletes updates that have had status changes on the upstream server that need to be replicated,
    this may throw a synchronization error on the downstream server. The downstream server should NEVER be intentionally put in a configuration that makes it different from the upstream server, and running the SCW on a downstream server before running it on an
    upstream server would do exactly that.
    For more details on my thoughts about how to use the Server Cleanup Wizard in a replica environment, please view my webcast from Sep 2010
    Using the WSUS Server Cleanup Wizard - Expert Tips and Tricks".
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • How to export and import "Computer Groups" and "Patch approvals" in WSUS 4.0 ?

    Hi,
    I have a query regarding the export and import options for "Computer Groups" and "Patch Approvals" in WSUS 4.0.
    In WSUS 3.2 once we install WSUS 3.0 API Samples and Tools, we get "WSUSMigrationExport" and "WSUSMigrationImport" tools under
    C:\Program Files\Update Services 3.0 API Samples and Tools\WsusMigrate\ folder. 
    Using the 'WSUSMigrationExport' tool we can export the Computer Groups and the Patch Approvals in a XML file. And using the 'WSUSMigrationImport' tool we can import the 'Computer Groups' and the 'Patch Approvals' from that XML file into a different WSUS
    3.2 server. We can run the import tool as below:
    a. Run command prompt as administrator.
    b. In the command prompt, go to C:\Program Files (x86)\Update Services 3.0 API Samples ans Tools\ WsusMigrate\WsusMigrationImport
    c. Type WsusMigrationImport filename.xml TargetGroups None. Press enter; this will import Computer Groups to the WSUS 3.2 server.
       Type WsusMigrationImport filename.xml Approvals None. Press enter; this will import "Patch Approvals" to the WSUS 3.2 server.
    This is easy and useful.
    Now, for WSUS 4.0 I did not find  "WSUS
    4.0 API Samples and Tools". So I installed "WSUS 3.0 API Samples and Tools" in my WSUS 4.0 server. And tried to import a valid XML file in the above mentioned process. But the command returned an error.
    The error says the "Microsoft.UpdateService.Administration.dll" file was not found.
    I further searched in the internet about this issue and I found that the "WSUS 3.0 API Samples and Tools" is not supported in WSUS 4.0 as the .net framework used in "WSUS 3.0 API Samples and Tools" is 2.0 and WSUS 4.0 uses .net Framework
    4.5.
    So, Here are my questions.
    1. Is it correct that "WSUS 3.0 API Samples and Tools" is not supported in WSUS 4.0?
    2. Is "WSUS 4.0 API Samples and Tools" available?
    3. Is there any alternative way in WSUS 4.0 to export and import XML file consisting "Computer Groups" and "Patch Approvals" configurations?
    I need an urgent reply. Thank you in advance.

    Hi Tapojyoti,
    >>1. Is it correct that "WSUS 3.0 API Samples and Tools" is not supported in WSUS 4.0?
    Yes, WSUS 3.0 API Samples and Tools is not supported in Windows Server 2012R2 by default. We may try to rebuild it in Windows Server 2012R2. For detailed information about how the rebuiled, please refer to the readme document of the WSUS 3.0 API Samples
    and Tools.
    >>2. Is "WSUS 4.0 API Samples and Tools" available?
    No, I can't find the WSUS API Samples and Tools for 2012R2.
    >>3. Is there any alternative way in WSUS 4.0 to export and import XML file consisting "Computer Groups" and "Patch Approvals" configurations?
    As I have mentioned above, due to WSUS 3.0 API Samples and Tools is released with source code, we can try to rebuild it in the Windows Server 2012R2.
    If it doesn't work, as a workaround, we can configure the new WSUS server as the replica server of the existing WSUS server. After the synchronization, change the server mode to stand alone.
    Best Regards.
    Steven Lee
    TechNet Community Support

  • SCCM 2012 and WSUS

    I know this horse has been beat, and is probably just dust now but I am still having a problem. I am not sure what to do next. I see others have had this problem but their resolutions have not worked.
    Site Config:
    OS - Windows Server 2012 Datacenter
    SQL - SQL Server 2012 Enterprise SP1
    SCCM - SCCM 2012 SP1
    WSUS : Database and WSUS Services
    I have done the setup in the Server Manager window and can open the console. Below are the errors I am getting.
    From SMS_WSUS_SYNC_MANAGER
    WSUS Synchronization failed.
    Message: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details..
    From SMS_WSUS_CONFIGURATION_MANAGER
    WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "SERVER".
    Error in WCM.log
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
    Error in wsyncmgr.log
    Sync failed: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVER SITE=CM1 PID=1548 TID=1740 GMTDATE=Fri Sep 13 19:08:50.063 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on
    site CM1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    Sync failed. Will retry in 60 minutes

    Re-set the WSUS and SUP roles according to your doco, which is nice by the way, but I am still getting errors in WCM.
    Assembly WSUSMSP loaded in .NET runtime v4.0.30319.17929 SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
    Successfully configured WSUS Server settings and Upstream Server to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    Set DBServerName property in SCF to 'VRC1SCCMPRIP01' on this site for <SERVER.DOMAIN>. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (<SERVER.DOMAIN>) is submitting SDK changes from site(CM1) SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:18e5ea77-e3d1-43b6-a0a8-fa3dbcd42e93 (Windows 8.1 Dynamic Update) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:3e5cc385-f312-4fff-bd5e-b88dcf29b476 (Windows 8 Language Interface Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:5312e4f1-6372-442d-aeb2-15f2132c9bd7 (Windows Internet Explorer 8 Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:6407468e-edc7-4ecd-8c32-521f64cee65e (Windows 8.1) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:97c4cee8-b2ae-4c43-a5ee-08367dab8796 (Windows 8 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:f4b9c883-f4db-4fb5-b204-3343c11fa021 (Windows Embedded Standard 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:37:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:38:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:39:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:22 PM 5108 (0x13F4)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    From SUPSetup.log
    <09/17/13 13:36:13> ====================================================================
    <09/17/13 13:36:13> SMSWSUS Setup Started....
    <09/17/13 13:36:13> Parameters: I:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:<SERVER.DOMAIN> SMSWSUS 0
    <09/17/13 13:36:13> Installing Pre Reqs for SMSWSUS
    <09/17/13 13:36:13>         ======== Installing Pre Reqs for Role SMSWSUS ========
    <09/17/13 13:36:13> Found 1 Pre Reqs for Role SMSWSUS
    <09/17/13 13:36:13> Pre Req SqlNativeClient found.
    <09/17/13 13:36:13> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
    <09/17/13 13:36:13> Pre Req SqlNativeClient is already installed. Skipping it.
    <09/17/13 13:36:13>         ======== Completed Installation of Pre Reqs for Role SMSWSUS ========
    <09/17/13 13:36:13> Installing the SMSWSUS
    <09/17/13 13:36:13> Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    <09/17/13 13:36:13> Checking runtime v2.0.50727...
    <09/17/13 13:36:13> Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    <09/17/13 13:36:13> Checking runtime v4.0.30319...
    <09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
    <09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
    <09/17/13 13:36:13> Supported WSUS version found
    <09/17/13 13:36:13> Supported WSUS Server version (6.2.9200.16384) is installed.
    <09/17/13 13:36:13> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
    <09/17/13 13:36:13> CTool::RegisterManagedBinary: Registered I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll successfully
    <09/17/13 13:36:13> Registered DLL I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll
    <09/17/13 13:36:13> Installation was successful.
    <09/17/13 13:36:13> ~RoleSetup().
    Second to last line shows completion.

  • SCCM 2012 complains about WSUS version

    Our SCCM 2012SP1 cannot communicate with the newly installed WSUS 6.2.
    They're both on Server 2012.  Is there any special patch to install on WSUS 6.2 to get it to work?
    We've changed the default port to port 80/443.
    From WCM.log:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
    3/21/2013 10:26:31 AM 680 (0x02A8)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
    3/21/2013 10:26:31 AM 680 (0x02A8)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)
    Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
    3/21/2013 10:26:31 AM 680 (0x02A8)
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=XXX-SCENTER SITE=XXX PID=6496 TID=680 GMTDATE=Thu Mar 21 17:26:31.636 2013 ISTR0="XXX-WSUS" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)

    After installing the admin console on site server, software updates in software library started to show up.  v(^.^)
    However, I am still getting error messages all over the place.
    I have not tried to uninstall/reinstall WSUS 6.2 yet; that would be the last thing I try.
    From SMS_WSUS_SYNC_MANAGER:
     WSUS Synchronization failed.
     Message: Failed to sync some of the updates.
     Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
    This is from SMS_WSUS_CONTROL_MANAGER:
    WSUS Control Manager failed to configure proxy settings on WSUS Server "CTB-WSUS.CHINATRUST.CORP".
    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.
    I confirmed that the SCCM default site and WSUS's Administration site are both using port 80.

Maybe you are looking for

  • Iphone Sync deleted all contacts on google, Mac Address Book and Itunes

    I have my phone synced to my google contacts. I did a sync trying to sync itunes, google and my address book and now everything has been deleted. I created a back up a month ago but when I do a restore from back up, it still does not give me my conta

  • Workflow for Vendor Creation through a portal.

    Hi All Workflow Experts,                                      I have a scenario here.In my project  vendor is created through a portal.On submit button from portal the workflow is to be triggered.I have to design the workflow process.So can you pleas

  • My new tab doesn't work like before.

    Hello, I can't speak English well. Please don't use difficult words. Before when I clicked on + for open a new tab, a tab opened. On the new tab I could see icons for famous web like Facebook, YouTube, Google , yahoo and .... But now when I open a ne

  • FreeBSD didn't install, i can no longer boot into Windows

    I unsuccessfully installed FreeBSD and I can no longer boot into an OS from the HD.  I attempted to install BSD onto the "G" drive below however the the install gave me some kind of storage error and I can no longer boot into Windows.  While going th

  • Adding a vlan

    Hello, We have a 4506 router/switch that we have been running 4 vlans on. I wanted to add anothe vlan, vlan 5 and configure two ports for this vlan. I created the vlan 5 and set these two ports for vlan5 but when I do a sh vlan command, their is no v