none
SCCM Software Updates RRS feed

 > 

  • Frage

  • Question
    Anmelden
    0
    Anmelden

    Hallo,

    in meiner Umgebung wurde der WSUS schon mal konfiguriert weil noch kein SCCM vorhanden war.

    Jetzt möchte ich die Software Updates übers SCCM ausrollen.

    Frage: Darf der WSUS Konfiguriert sein oder nicht?

    ich hab schon mal gelesen das der nicht Konfiguriert sein darf

    LG
    Phil

    Freitag, 1. März 2013 09:39
    |

Antworten

  • Question
    Anmelden
    0
    Anmelden

    oder doch ned.

    Wakeup by inbox drop SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:30 984 (0x03D8)
    Found local sync request file SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Starting Sync SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Performing sync on local request SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Full sync required due to changes in category subscriptions. SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Read SUPs from SCF for consccm001.intern.conova.com SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Found 1 SUPs SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Found active SUP consccm001.intern.conova.com from SCF File. SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:08:35.870 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Synchronizing WSUS server consccm001.intern.conova.com SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:36 984 (0x03D8)
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:08:36.988 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:36 984 (0x03D8)
    Using account CONOVA\areph to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 984 (0x03D8)
    Synchronizing WSUS server consccm001.intern.conova.com ... SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 5172 (0x1434)
    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 5172 (0x1434)
    Sync failed: The operation has timed out SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:23:39.582 2013 ISTR0="" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Setting sync alert to active state on site S01 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Sync time: 0d00h15m03s SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Next scheduled sync is a regular sync at 01.03.2013 14:00:00 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)

    kann das sein das der aktuelle WSUS das Problem ist?

    Sync failed: The operation has timed out 

    Wsus Service erreichbar? Internet ist da? Microsoft als update Quelle angegeben?

    was sagt denn: WSUSCtrl.log und PatchDownloader.log/ScanAgent.log


    Edit 2: nicht konfiguriert.... http://technet.microsoft.com/en-us/library/bb735874.aspx

    • To check the update source settings in WSUS

      1. Open the WSUS console on the active software update point for the site.

      2. Click Options in the console tree pane.

      3. Click Update Source and Proxy Server in the display pane.

      4. Verify that This server is a replica of the upstream server is not selected unless you are in the WSUS console on the active software update point for a secondary site. Child primary sites should never be configured as a replica of the upstream server.

    • Check that Update Services is running on the WSUS server.


    • Bearbeitet Sanw Montag, 4. März 2013 09:43
    • Als Antwort markiert Philipp Reichl Mittwoch, 6. März 2013 13:28
    Montag, 4. März 2013 09:34
    |

Alle Antworten

  • Question
    Anmelden
    0
    Anmelden

    Hi,

    nicht "sinnig" zwei Wsus zu haben bzw. doppelte konfig.

    Einfach über den SCCM konfigurieren.



    • Bearbeitet Sanw Freitag, 1. März 2013 09:50
    Freitag, 1. März 2013 09:49
    |
  • Question
    Anmelden
    0
    Anmelden

    warscheindlich funktionierts deswegen nicht ;)

    dann wird ich mal den WSUS deprovisionieren. und mit dem SCCM neu aufziehen.

    Freitag, 1. März 2013 10:09
    |
  • Question
    Anmelden
    0
    Anmelden
    Funktionieren sollte es trotzdem (einen bestehenden WSUS zum SUP zu machen); empfohlen ist es aber nicht.
    Was genau klappt denn nicht? Bekommst Du eine explizite Fehlermeldung?

    Torsten Meringer | http://www.mssccmfaq.de

    Freitag, 1. März 2013 10:12
    |
    Beantworter
  • Question
    Anmelden
    0
    Anmelden

    WCM.LOg

    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:30.092-60><thread=10480 (0x28F0)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.238-60><thread=10480 (0x28F0)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.268-60><thread=10480 (0x28F0)>
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.820-60><thread=10480 (0x28F0)>
    Changes in active SUP list detected. New active SUP List is:~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.840-60><thread=10480 (0x28F0)>
        SUP0: consccm001.intern.conova.com, group = , nlb = ~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.984-60><thread=10480 (0x28F0)>
    Updating active SUP groups...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.992-60><thread=10480 (0x28F0)>
    Updating Group Info for WSUS.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.005-60><thread=10480 (0x28F0)>
    Set UseParentWSUS property in SCF to 1 on this site for consccm001.intern.conova.com.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.039-60><thread=10480 (0x28F0)>
    user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (consccm001.intern.conova.com) is submitting SDK changes from site(S01)  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.047-60><thread=10480 (0x28F0)>
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.205-60><thread=10480 (0x28F0)>
    Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.253-60><thread=10480 (0x28F0)>
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.289-60><thread=10480 (0x28F0)>
    Checking runtime v4.0.30319...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.296-60><thread=10480 (0x28F0)>
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.307-60><thread=10480 (0x28F0)>
    Supported WSUS version not found~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.335-60><thread=10480 (0x28F0)>
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=10480 GMTDATE=Fr Mär 01 10:56:36.342 2013 ISTR0="consccm001.intern.conova.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.342-60><thread=10480 (0x28F0)>
    Remote configuration failed on WSUS Server.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.369-60><thread=10480 (0x28F0)>
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=10480 GMTDATE=Fr Mär 01 10:56:36.378 2013 ISTR0="consccm001.intern.conova.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.378-60><thread=10480 (0x28F0)>
    Setting new configuration state to 3 (WSUS_CONFIG_FAILED)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.394-60><thread=10480 (0x28F0)>
    Waiting for changes for 23 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.403-60><thread=10480 (0x28F0)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:40.449-60><thread=10480 (0x28F0)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:45.699-60><thread=10480 (0x28F0)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:45.716-60><thread=10480 (0x28F0)>
    Waiting for changes for 22 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:45.762-60><thread=10480 (0x28F0)>

    wsyncmgr.log

    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.282-60><thread=984 (0x3D8)>
    Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.380-60><thread=984 (0x3D8)>
    Read SUPs from SCF for consccm001.intern.conova.com  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.493-60><thread=984 (0x3D8)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.510-60><thread=984 (0x3D8)>
    Found active SUP consccm001.intern.conova.com from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.524-60><thread=984 (0x3D8)>
    DB Server not detected for SUP consccm001.intern.conova.com from SCF File. skipping.~  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.529-60><thread=984 (0x3D8)>
    Sync failed: WSUS update source not found on site S01. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.548-60><thread=984 (0x3D8)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 10:56:35.556 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site S01. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.565-60><thread=984 (0x3D8)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.573-60><thread=984 (0x3D8)>
    Setting sync alert to active state on site S01  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.582-60><thread=984 (0x3D8)>
    Sync time: 0d00h00m00s  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.603-60><thread=984 (0x3D8)>
    Next scheduled sync is a regular sync at 01.03.2013 12:11:00  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.788-60><thread=984 (0x3D8)>
    Wakeup by SCF change  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:40.449-60><thread=984 (0x3D8)>
    Next scheduled sync is a regular sync at 01.03.2013 12:11:00  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:45.664-60><thread=984 (0x3D8)>

    ich hab bei der SUP Installation am SCCM den WSUS (der am gleichen Server wie das SCCM läuft) angegeben. nur ich find den fehler nicht warum der sich nicht hinverbinden kann.

    lg

    phil

    Freitag, 1. März 2013 11:02
    |
  • Question
    Anmelden
    0
    Anmelden
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.205-60><thread=10480 (0x28F0)>

    [...]
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.289-60><thread=10480 (0x28F0)>
    [...]
    Supported WSUS version not found~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.335-60><thread=10480 (0x28F0)>


    Sind die beiden Hotfixes denn installiert?

    Torsten Meringer | http://www.mssccmfaq.de

    Freitag, 1. März 2013 11:09
    |
    Beantworter
  • Question
    Anmelden
    0
    Anmelden

    WCM.LOg

    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:30.092-60><thread=10480 (0x28F0)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.238-60><thread=10480 (0x28F0)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.268-60><thread=10480 (0x28F0)>
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.820-60><thread=10480 (0x28F0)>
    Changes in active SUP list detected. New active SUP List is:~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.840-60><thread=10480 (0x28F0)>
        SUP0: consccm001.intern.conova.com, group = , nlb = ~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.984-60><thread=10480 (0x28F0)>
    Updating active SUP groups...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:35.992-60><thread=10480 (0x28F0)>
    Updating Group Info for WSUS.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.005-60><thread=10480 (0x28F0)>
    Set UseParentWSUS property in SCF to 1 on this site for consccm001.intern.conova.com.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.039-60><thread=10480 (0x28F0)>
    user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (consccm001.intern.conova.com) is submitting SDK changes from site(S01)  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.047-60><thread=10480 (0x28F0)>
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.205-60><thread=10480 (0x28F0)>
    Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.253-60><thread=10480 (0x28F0)>
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.289-60><thread=10480 (0x28F0)>
    Checking runtime v4.0.30319...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.296-60><thread=10480 (0x28F0)>
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.307-60><thread=10480 (0x28F0)>
    Supported WSUS version not found~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.335-60><thread=10480 (0x28F0)>
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=10480 GMTDATE=Fr Mär 01 10:56:36.342 2013 ISTR0="consccm001.intern.conova.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.342-60><thread=10480 (0x28F0)>
    Remote configuration failed on WSUS Server.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.369-60><thread=10480 (0x28F0)>
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=10480 GMTDATE=Fr Mär 01 10:56:36.378 2013 ISTR0="consccm001.intern.conova.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.378-60><thread=10480 (0x28F0)>
    Setting new configuration state to 3 (WSUS_CONFIG_FAILED)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.394-60><thread=10480 (0x28F0)>
    Waiting for changes for 23 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:36.403-60><thread=10480 (0x28F0)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:40.449-60><thread=10480 (0x28F0)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:45.699-60><thread=10480 (0x28F0)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:45.716-60><thread=10480 (0x28F0)>
    Waiting for changes for 22 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-01-2013 11:56:45.762-60><thread=10480 (0x28F0)>

    wsyncmgr.log

    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.282-60><thread=984 (0x3D8)>
    Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.380-60><thread=984 (0x3D8)>
    Read SUPs from SCF for consccm001.intern.conova.com  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.493-60><thread=984 (0x3D8)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.510-60><thread=984 (0x3D8)>
    Found active SUP consccm001.intern.conova.com from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.524-60><thread=984 (0x3D8)>
    DB Server not detected for SUP consccm001.intern.conova.com from SCF File. skipping.~  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.529-60><thread=984 (0x3D8)>
    Sync failed: WSUS update source not found on site S01. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.548-60><thread=984 (0x3D8)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 10:56:35.556 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site S01. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.565-60><thread=984 (0x3D8)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.573-60><thread=984 (0x3D8)>
    Setting sync alert to active state on site S01  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.582-60><thread=984 (0x3D8)>
    Sync time: 0d00h00m00s  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.603-60><thread=984 (0x3D8)>
    Next scheduled sync is a regular sync at 01.03.2013 12:11:00  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:35.788-60><thread=984 (0x3D8)>
    Wakeup by SCF change  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:40.449-60><thread=984 (0x3D8)>
    Next scheduled sync is a regular sync at 01.03.2013 12:11:00  $$<SMS_WSUS_SYNC_MANAGER><03-01-2013 11:56:45.664-60><thread=984 (0x3D8)>

    ich hab bei der SUP Installation am SCCM den WSUS (der am gleichen Server wie das SCCM läuft) angegeben. nur ich find den fehler nicht warum der sich nicht hinverbinden kann.

    lg

    phil

    Did not find supported version of assembly Microsoft.UpdateServices.Administration.

    Supported WSUS version not found

    Remote configuration failed on WSUS Server

    Sync failed: WSUS update source not found 

    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  

    Wie ist der Wsus im Moment Konfiguriert? 

    Wsus Rolle ist ohne Fehler installiert worden? Nachdem der Wsus installiert wurde, SoftwareupdatePoint installiert?

    Patch installiert?



    • Bearbeitet Sanw Freitag, 1. März 2013 11:13
    Freitag, 1. März 2013 11:12
    |
  • Question
    Anmelden
    0
    Anmelden

    sieht so aus als würde es doch funktionieren.

    Freitag, 1. März 2013 12:11
    |
  • Question
    Anmelden
    0
    Anmelden

    oder doch ned.

    Wakeup by inbox drop SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:30 984 (0x03D8)
    Found local sync request file SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Starting Sync SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Performing sync on local request SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Full sync required due to changes in category subscriptions. SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Read SUPs from SCF for consccm001.intern.conova.com SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Found 1 SUPs SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Found active SUP consccm001.intern.conova.com from SCF File. SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:08:35.870 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Synchronizing WSUS server consccm001.intern.conova.com SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:36 984 (0x03D8)
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:08:36.988 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:36 984 (0x03D8)
    Using account CONOVA\areph to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 984 (0x03D8)
    Synchronizing WSUS server consccm001.intern.conova.com ... SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 5172 (0x1434)
    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 5172 (0x1434)
    Sync failed: The operation has timed out SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:23:39.582 2013 ISTR0="" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Setting sync alert to active state on site S01 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Sync time: 0d00h15m03s SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Next scheduled sync is a regular sync at 01.03.2013 14:00:00 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)

    kann das sein das der aktuelle WSUS das Problem ist?

    Freitag, 1. März 2013 12:27
    |
  • Question
    Anmelden
    0
    Anmelden

    oder doch ned.

    Wakeup by inbox drop SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:30 984 (0x03D8)
    Found local sync request file SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Starting Sync SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Performing sync on local request SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Full sync required due to changes in category subscriptions. SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Read SUPs from SCF for consccm001.intern.conova.com SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Found 1 SUPs SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Found active SUP consccm001.intern.conova.com from SCF File. SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:08:35.870 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:35 984 (0x03D8)
    Synchronizing WSUS server consccm001.intern.conova.com SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:36 984 (0x03D8)
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:08:36.988 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:36 984 (0x03D8)
    Using account CONOVA\areph to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 984 (0x03D8)
    Synchronizing WSUS server consccm001.intern.conova.com ... SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 5172 (0x1434)
    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 01.03.2013 13:08:37 5172 (0x1434)
    Sync failed: The operation has timed out SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=consccm001.intern.conova.com SITE=S01 PID=5336 TID=984 GMTDATE=Fr Mär 01 12:23:39.582 2013 ISTR0="" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Setting sync alert to active state on site S01 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Sync time: 0d00h15m03s SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)
    Next scheduled sync is a regular sync at 01.03.2013 14:00:00 SMS_WSUS_SYNC_MANAGER 01.03.2013 13:23:39 984 (0x03D8)

    kann das sein das der aktuelle WSUS das Problem ist?

    Sync failed: The operation has timed out 

    Wsus Service erreichbar? Internet ist da? Microsoft als update Quelle angegeben?

    was sagt denn: WSUSCtrl.log und PatchDownloader.log/ScanAgent.log


    Edit 2: nicht konfiguriert.... http://technet.microsoft.com/en-us/library/bb735874.aspx

    • To check the update source settings in WSUS

      1. Open the WSUS console on the active software update point for the site.

      2. Click Options in the console tree pane.

      3. Click Update Source and Proxy Server in the display pane.

      4. Verify that This server is a replica of the upstream server is not selected unless you are in the WSUS console on the active software update point for a secondary site. Child primary sites should never be configured as a replica of the upstream server.

    • Check that Update Services is running on the WSUS server.


    • Bearbeitet Sanw Montag, 4. März 2013 09:43
    • Als Antwort markiert Philipp Reichl Mittwoch, 6. März 2013 13:28
    Montag, 4. März 2013 09:34
    |
  • Question
    Anmelden
    0
    Anmelden

    Hallo,

    bist Du hier inzwischen weitergekommen?

    Gruss,
    Raul

    Raul Talmaciu, MICROSOFT 
    Bitte haben Sie Verständnis dafür, dass im Rahmen dieses Forums, welches auf dem Community-Prinzip „IT-Pros helfen IT-Pros“ beruht, kein technischer Support geleistet werden kann oder sonst welche garantierten Maßnahmen seitens Microsoft zugesichert werden können.

    Mittwoch, 6. März 2013 10:47
    |