none
SCCM 2012 Nach Update auf SP1 funktioniert der SUP nicht mehr RRS feed

  • Frage

  • Hallo TechNet-Forum,

    ich bin Auszubildender zum Fachinformatiker in der IT-Abteilung in einem mittelständischen Unternehmen. Seit mehr als einem Jahr bin ich Hauptverantwortlicher für unsere System Center-Umgebung.

    Aktuell ein Problem mit meinem Software Update Point. 

    Hier erstmal die Konfiguration:

    DESTS074 ->Server 1 (Windows Server 2008 R2): Primary Site Server, DP, MP, Application Catalog Webservice Point, Application Catalog Website Point, Asset Intelligence synchronization point, Endpoint Protection Point, Aktuell noch Haupt-WSUS, aber noch nicht von SCCM gesteuert (SP2 mit KB2734608 + KB2720211 + Adminkonsole);

    DESTS076 ->Server 2 (Windows Server 2008 R2): Test-WSUS um den SUP erstmal zu testen (SP2 mit KB2734608 + KB2720211)

    DESTS081 ->Server 3 (Windows Server 2008 R2): SQL-Server mit der Site-Database (SQL Server 2008 R2 + Updates);

    und noch 4x Windows Server 2008 R2 an unseren Außenlokationen mit DP-Rolle.

    Da wir aktuell die Updates über WSUS alleine verwalten und ausrollen (installiert auf Server 1), habe ich mir vor einigen Tagen Server 2 aufgesetzt mit wie oben beschrieben WSUS und der SUP-Rolle. Meine Deploymentrules und Updatesynchronisation funktionierten alle bestens. 

    Heute habe ich nun das Update auf SCCM 2012 SP 1 gemacht und plötzlich funktionierte es nicht mehr. Also habe ich die SUP-Rolle und den WSUS von Server 2 deinstalliert und nochmal neu installiert. Aber auch nach mehrmaligem Versuchen kein Erfolg. 

    Ich bedanke mich jetzt schon für Antworten

    Grüße Gobbo

    Hier die letzten Einträge des WCM.log

    Verify Upstream Server settings on the Active WSUS Server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:41.851-60><thread=4556 (0x11CC)>
    System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'HAERTER-LAN\DESTS076$'.~~   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)~~   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetConfiguration()~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()~~   at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)~~   at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetConfiguration()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.SetUpstreamServerSettings(Boolean SyncFromMicrosoftUpdate, Boolean ReplicaServer, String UpstreamWSUSServerName, Int32 UpstreamWSUSServerPortNumber, Boolean UseSSL, Boolean HostBinariesOnMU, Int32 ReportingLevel, Int32 MaximumAllowedComputers)  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:41.872-60><thread=4556 (0x11CC)>
    Done using HAERTER-LAN\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:41.872-60><thread=4556 (0x11CC)>
    Remote configuration failed on WSUS Server.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:41.873-60><thread=4556 (0x11CC)>
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=DESTS074.HAERTER.LAN SITE=DES PID=2780 TID=4556 GMTDATE=Sat Jan 19 17:40:41.873 2013 ISTR0="DESTS076.HAERTER.LAN" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:41.873-60><thread=4556 (0x11CC)>
    Setting new configuration state to 3 (WSUS_CONFIG_FAILED)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:41.873-60><thread=4556 (0x11CC)>
    Waiting for changes for 17 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:41.875-60><thread=4556 (0x11CC)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:46.800-60><thread=4556 (0x11CC)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:51.802-60><thread=4556 (0x11CC)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:51.802-60><thread=4556 (0x11CC)>
    Waiting for changes for 17 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:40:51.812-60><thread=4556 (0x11CC)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:36.871-60><thread=4556 (0x11CC)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:41.876-60><thread=4556 (0x11CC)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:41.876-60><thread=4556 (0x11CC)>
    Waiting for changes for 15 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:41.904-60><thread=4556 (0x11CC)>
    Trigger event array index 0 ended.  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:46.898-60><thread=4556 (0x11CC)>
    SCF change notification triggered.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:51.901-60><thread=4556 (0x11CC)>
    Populating config from SCF  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:51.901-60><thread=4556 (0x11CC)>
    Waiting for changes for 15 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:42:51.911-60><thread=4556 (0x11CC)>
    Wait timed out after 15 minutes while waiting for at least one trigger event.  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:37.950-60><thread=4556 (0x11CC)>
    Timed Out...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.951-60><thread=4556 (0x11CC)>
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.951-60><thread=4556 (0x11CC)>
    Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.951-60><thread=4556 (0x11CC)>
    Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.953-60><thread=4556 (0x11CC)>
    Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.954-60><thread=4556 (0x11CC)>
    Supported WSUS version found~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.954-60><thread=4556 (0x11CC)>
    Using HAERTER-LAN\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.966-60><thread=4556 (0x11CC)>
    Attempting connection to WSUS server: DESTS076.HAERTER.LAN, port: 80, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.966-60><thread=4556 (0x11CC)>
    Successfully connected to server: DESTS076.HAERTER.LAN, port: 80, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.980-60><thread=4556 (0x11CC)>
    Verify Upstream Server settings on the Active WSUS Server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:47.980-60><thread=4556 (0x11CC)>
    No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.002-60><thread=4556 (0x11CC)>
    Done using HAERTER-LAN\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.006-60><thread=4556 (0x11CC)>
    WSUS Server configuration has been updated. Updating Group Info.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.006-60><thread=4556 (0x11CC)>
    Updating Group Info for WSUS.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.006-60><thread=4556 (0x11CC)>
    Set DBServerName property in SCF to 'DESTS081\SCCM2012' on this site for DESTS076.HAERTER.LAN.~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.015-60><thread=4556 (0x11CC)>
    user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (DESTS074.HAERTER.LAN) is submitting SDK changes from site(DES)  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.015-60><thread=4556 (0x11CC)>
    Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.062-60><thread=4556 (0x11CC)>
    Refreshing categories from WSUS server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.079-60><thread=4556 (0x11CC)>
    Using HAERTER-LAN\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.928-60><thread=4556 (0x11CC)>
    Attempting connection to WSUS server: DESTS076.HAERTER.LAN, port: 80, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.929-60><thread=4556 (0x11CC)>
    Successfully connected to server: DESTS076.HAERTER.LAN, port: 80, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:48.940-60><thread=4556 (0x11CC)>
    Done using HAERTER-LAN\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:56.283-60><thread=4556 (0x11CC)>
    Successfully refreshed categories from WSUS server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:57:58.634-60><thread=4556 (0x11CC)>
    Using HAERTER-LAN\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.646-60><thread=4556 (0x11CC)>
    Attempting connection to WSUS server: DESTS076.HAERTER.LAN, port: 80, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.646-60><thread=4556 (0x11CC)>
    Successfully connected to server: DESTS076.HAERTER.LAN, port: 80, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.659-60><thread=4556 (0x11CC)>
    Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.678-60><thread=4556 (0x11CC)>
    Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.692-60><thread=4556 (0x11CC)>
    Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.706-60><thread=4556 (0x11CC)>
    Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.720-60><thread=4556 (0x11CC)>
    Starting WSUS category sync from upstream...  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.743-60><thread=4556 (0x11CC)>
    WSUS sync was already in progress  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.755-60><thread=4556 (0x11CC)>
      WSUS sync running~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:59:03.913-60><thread=4556 (0x11CC)>
      WSUS sync running~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 19:00:04.060-60><thread=4556 (0x11CC)>
      WSUS sync running~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 19:01:04.219-60><thread=4556 (0x11CC)>
      WSUS sync running~  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 19:02:04.459-60><thread=4556 (0x11CC)>

    Und das wsyncmgr.log

    Full sync required due to changes in main WSUS server location.  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.301-60><thread=4564 (0x11D4)>
    Read SUPs from SCF for DESTS074.HAERTER.LAN  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.302-60><thread=4564 (0x11D4)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.310-60><thread=4564 (0x11D4)>
    Found active SUP DESTS076.HAERTER.LAN from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.310-60><thread=4564 (0x11D4)>
    Sync failed: WSUS update source not found on site DES. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.312-60><thread=4564 (0x11D4)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DESTS074.HAERTER.LAN SITE=DES PID=2780 TID=4564 GMTDATE=Sat Jan 19 18:37:51.312 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site DES. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.317-60><thread=4564 (0x11D4)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.317-60><thread=4564 (0x11D4)>
    Setting sync alert to active state on site DES  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.318-60><thread=4564 (0x11D4)>
    Sync time: 0d00h00m00s  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.361-60><thread=4564 (0x11D4)>
    Next scheduled sync is a regular sync at 1/19/2013 8:00:00 PM  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 19:37:51.368-60><thread=4564 (0x11D4)>
    Wakeup for scheduled regular sync  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.326-60><thread=4564 (0x11D4)>
    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.326-60><thread=4564 (0x11D4)>
    Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.326-60><thread=4564 (0x11D4)>
    Read SUPs from SCF for DESTS074.HAERTER.LAN  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.339-60><thread=4564 (0x11D4)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.343-60><thread=4564 (0x11D4)>
    Found active SUP DESTS076.HAERTER.LAN from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.344-60><thread=4564 (0x11D4)>
    Sync failed: WSUS update source not found on site DES. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.345-60><thread=4564 (0x11D4)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DESTS074.HAERTER.LAN SITE=DES PID=2780 TID=4564 GMTDATE=Sat Jan 19 19:00:00.346 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site DES. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.346-60><thread=4564 (0x11D4)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.346-60><thread=4564 (0x11D4)>
    Setting sync alert to active state on site DES  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.346-60><thread=4564 (0x11D4)>
    Sync time: 0d00h00m00s  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:00:00.399-60><thread=4564 (0x11D4)>
    Wakeup by inbox drop  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:04.282-60><thread=4564 (0x11D4)>
    Found local sync request file  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.329-60><thread=4564 (0x11D4)>
    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.329-60><thread=4564 (0x11D4)>
    Performing sync on local request  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.329-60><thread=4564 (0x11D4)>
    Read SUPs from SCF for DESTS074.HAERTER.LAN  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.334-60><thread=4564 (0x11D4)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.340-60><thread=4564 (0x11D4)>
    Found active SUP DESTS076.HAERTER.LAN from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.340-60><thread=4564 (0x11D4)>
    Sync failed: WSUS update source not found on site DES. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.342-60><thread=4564 (0x11D4)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DESTS074.HAERTER.LAN SITE=DES PID=2780 TID=4564 GMTDATE=Sat Jan 19 19:18:09.342 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site DES. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.348-60><thread=4564 (0x11D4)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.348-60><thread=4564 (0x11D4)>
    Setting sync alert to active state on site DES  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.348-60><thread=4564 (0x11D4)>
    Sync time: 0d00h00m00s  $$<SMS_WSUS_SYNC_MANAGER><01-19-2013 20:18:09.366-60><thread=4564 (0x11D4)>


    • Bearbeitet Gobbolas Samstag, 19. Januar 2013 19:26
    Samstag, 19. Januar 2013 19:25

Antworten

  • Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.678-60><thread=4556 (0x11CC)>
    Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.692-60><thread=4556 (0x11CC)>
    Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.706-60><thread=4556 (0x11CC)>
    Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.720-60><thread=4556 (0x11CC)



    Das wird das Problem sein. Du könntest mal schauen (WSUS Konsole), ob diese Kategorien synchronisiert werden und ggfs wieder hinzufügen. Alternativ die 4 Kategorien in der Software Updates Konfiguration (ConfigMgr) entfernen (dabei die beiden Logs oben beobachten) und wieder hinzufügen.

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

    • Als Antwort markiert Gobbolas Samstag, 19. Januar 2013 20:40
    Samstag, 19. Januar 2013 19:50
    Beantworter

Alle Antworten

  • Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.678-60><thread=4556 (0x11CC)>
    Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.692-60><thread=4556 (0x11CC)>
    Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.706-60><thread=4556 (0x11CC)>
    Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS  $$<SMS_WSUS_CONFIGURATION_MANAGER><01-19-2013 18:58:03.720-60><thread=4556 (0x11CC)



    Das wird das Problem sein. Du könntest mal schauen (WSUS Konsole), ob diese Kategorien synchronisiert werden und ggfs wieder hinzufügen. Alternativ die 4 Kategorien in der Software Updates Konfiguration (ConfigMgr) entfernen (dabei die beiden Logs oben beobachten) und wieder hinzufügen.

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

    • Als Antwort markiert Gobbolas Samstag, 19. Januar 2013 20:40
    Samstag, 19. Januar 2013 19:50
    Beantworter
  • Super danke für die schnelle Antwort. Das war es. :)
    Samstag, 19. Januar 2013 20:41