none
SCUP Probleme RRS feed

  • Frage

  • Guten Tag,

    ich habe einen SCCM 2012 in Deutsch, auf dem gleichen Server ist auch ein Software Updatepunkt aktiv. Dazu habe ich den SCUP 2011 installiert. Ich bekomme meine Updates aber nicht auf den Verteilpunkt geschoben weil immer eine Fehlermeldung kommt. Als Zertifikat habe ich das Root-Zertifikat der Domäne genommen das ich das Zertifikat nicht neu ausrollen muss. Nachdem ich aber die Fehlermeldung bekommen habe wollte ich es mit einem selbst erstellten Zertifikat des SCCM testen, das hat aber auch nicht funktioniert. Kann es sein das das es Probleme gibt weil der SCCM in Deutsch ist und das SCUP in englisch?

    Hier das SCUP.log:

    File C:\Users\Administrator\AppData\Local\Temp\1\\oh5320f0.kai\install_flash_player_11_active_x.msi appears to be signed, retrieved certificate, checking signature... Updates Publisher 12.10.2012 15:05:49 7 (0x0007)
    PublishItem: --- SDP XML file for publishing created at C:\Users\Administrator\AppData\Local\Temp\1\tmp5296.tmp Updates Publisher 12.10.2012 15:05:49 7 (0x0007)
    PublishItem: --- Calling update server API for publishing update 'Adobe Flash Player 32-bit/64-bit ActiveX 11.4.402.287 (UpdateId:'f28e393f-22e3-46b7-9f58-786688415619' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')' Updates Publisher 12.10.2012 15:05:49 7 (0x0007)
    2012-10-12 13:05:56.751 UTC Info Scup2011.7 ThreadEntry _ThreadPoolWaitCallback.PerformWaitCallback Updates Publisher 12.10.2012 15:05:56 7 (0x0007)
    2012-10-12 13:05:56.766 UTC Info Scup2011.7 CabUtilities.CheckCertificateSignature File cert verification failed for C:\Program Files\Update Services\autest.cab with 2147942402 Updates Publisher 12.10.2012 15:05:56 7 (0x0007)
    2012-10-12 13:05:56.772 UTC Info Scup2011.7 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed Updates Publisher 12.10.2012 15:05:56 7 (0x0007)
    2012-10-12 13:05:57.107 UTC Info Scup2011.7 CabUtilities.CheckCertificateSignature File cert verification failed for \\sccm01\UpdateServicesPackages\f28e393f-22e3-46b7-9f58-786688415619\502690a6-eb9d-4946-8931-daefe6b48926_1.cab with 2148098073 Updates Publisher 12.10.2012 15:05:57 7 (0x0007)
    2012-10-12 13:05:57.111 UTC Error Scup2011.7 Publisher.VerifyAndPublishPackage VerifyAndPublishPackage(): Failed to Verify Signature for file: \\sccm01\UpdateServicesPackages\f28e393f-22e3-46b7-9f58-786688415619\502690a6-eb9d-4946-8931-daefe6b48926_1.cab   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Microsoft.UpdateServices.Internal.BaseApi.Publisher.VerifyAndPublishPackage()   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishOperation.Start()   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading.ThreadPoolWorkQueue.Dispatch()   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Updates Publisher 12.10.2012 15:05:57 7 (0x0007)
    2012-10-12 13:05:57.116 UTC Error Scup2011.7 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Fehler bei Verifizierung der Signatur f..r Datei: \\sccm01\UpdateServicesPackages\f28e393f-22e3-46b7-9f58-786688415619\502690a6-eb9d-4946-8931-daefe6b48926_1.cab   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishOperation.Start()   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading.ThreadPoolWorkQueue.Dispatch()   01.01.1601 00:00:00 2002082667 (0x77555B6B)
       bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Updates Publisher 12.10.2012 15:05:57 7 (0x0007)
    PublishItem: InvalidException occurred during publishing: Fehler bei Verifizierung der Signatur f..r Datei: \\sccm01\UpdateServicesPackages\f28e393f-22e3-46b7-9f58-786688415619\502690a6-eb9d-4946-8931-daefe6b48926_1.cab Updates Publisher 12.10.2012 15:05:57 7 (0x0007)
    Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured. Updates Publisher 12.10.2012 15:05:57 7 (0x0007)
    Publish: Background processing completed. Updates Publisher 12.10.2012 15:05:57 1 (0x0001)
    WizardBase: closing Publish Software Updates Wizard wizard. Updates Publisher 12.10.2012 15:06:29 1 (0x0001)
    Updates workspace: publish wizard completed. Updates Publisher 12.10.2012 15:06:30 1 (0x0001)
    Workspace: Starting settings dialog... Updates Publisher 12.10.2012 15:06:32 1 (0x0001)
    Settings: user cancelled dialog. Updates Publisher 12.10.2012 15:06:34 1 (0x0001)
    Workspace: Settings dialog has completed. Updates Publisher 12.10.2012 15:06:34 1 (0x0001)
    Workspace: Starting settings dialog... Updates Publisher 12.10.2012 15:06:38 1 (0x0001)
    Connecting to a local update server with locally detected settings. Updates Publisher 12.10.2012 15:06:43 1 (0x0001)
    Element nicht gefunden Updates Publisher 12.10.2012 15:06:45 1 (0x0001)
    RemoveCertificate: Removed current signing certificate from update server. Updates Publisher 12.10.2012 15:06:45 1 (0x0001)
    Settings: TestConnection selected. Updates Publisher 12.10.2012 15:06:49 1 (0x0001)
    TestConnection: Verifying current update server settings... Updates Publisher 12.10.2012 15:06:49 1 (0x0001)
    Connecting to a local update server with locally detected settings. Updates Publisher 12.10.2012 15:06:49 1 (0x0001)
    Element nicht gefunden Updates Publisher 12.10.2012 15:06:49 1 (0x0001)
    TestConnection: Verification succeeded. However, no signing certificate was detected for the update server. You will not be able to publish content to the update server without first registering a signing certificate. Updates Publisher 12.10.2012 15:06:50 1 (0x0001)
    Settings: user cancelled dialog. Updates Publisher 12.10.2012 15:06:52 1 (0x0001)
    Workspace: Settings dialog has completed. Updates Publisher 12.10.2012 15:06:52 1 (0x0001)
    Workspace: Starting settings dialog... Updates Publisher 12.10.2012 15:06:55 1 (0x0001)
    Settings: user cancelled dialog. Updates Publisher 12.10.2012 15:07:04 1 (0x0001)
    Workspace: Settings dialog has completed. Updates Publisher 12.10.2012 15:07:04 1 (0x0001)
    Updates workspace: Starting publish wizard with 2 updates. Updates Publisher 12.10.2012 15:07:10 1 (0x0001)
        Publish: Preparing list of selected updates for publishing. Updates Publisher 12.10.2012 15:07:14 7 (0x0007)
        Connecting to a local update server with locally detected settings. Updates Publisher 12.10.2012 15:07:14 7 (0x0007)
        Publish: Update server name: sccm01 Updates Publisher 12.10.2012 15:07:14 7 (0x0007)
        Publish: Publish operation starting for 2 updates. Updates Publisher 12.10.2012 15:07:14 7 (0x0007)
        Publish: Publish: Verifying update server is configured with a certificate prior to publishing. Updates Publisher 12.10.2012 15:07:14 7 (0x0007)
        Publish: Update server does not appear to be configured with a certificate for publishing, publishing aborted. Updates Publisher 12.10.2012 15:07:14 7 (0x0007)
        Publish: Background processing completed. Updates Publisher 12.10.2012 15:07:14 1 (0x0001)
        WizardBase: closing Publish Software Updates Wizard wizard. Updates Publisher 12.10.2012 15:07:17 1 (0x0001)
    Updates workspace: publish wizard completed. Updates Publisher 12.10.2012 15:07:17 1 (0x0001)
    Updates workspace: Starting publish wizard with 2 updates. Updates Publisher 12.10.2012 15:07:20 1 (0x0001)
        Publish: Preparing list of selected updates for publishing. Updates Publisher 12.10.2012 15:07:25 13 (0x000D)
        Connecting to a local update server with locally detected settings. Updates Publisher 12.10.2012 15:07:25 13 (0x000D)
        Publish: Update server name: sccm01 Updates Publisher 12.10.2012 15:07:25 13 (0x000D)
        Publish: Publish operation starting for 2 updates. Updates Publisher 12.10.2012 15:07:25 13 (0x000D)
        Publish: Publish: Verifying update server is configured with a certificate prior to publishing. Updates Publisher 12.10.2012 15:07:25 13 (0x000D)
        Publish: Update server does not appear to be configured with a certificate for publishing, publishing aborted. Updates Publisher 12.10.2012 15:07:25 13 (0x000D)
        Publish: Background processing completed. Updates Publisher 12.10.2012 15:07:25 1 (0x0001)
        WizardBase: closing Publish Software Updates Wizard wizard. Updates Publisher 12.10.2012 15:07:49 1 (0x0001)
    Updates workspace: publish wizard completed. Updates Publisher 12.10.2012 15:07:49 1 (0x0001)
    Workspace: Starting settings dialog... Updates Publisher 12.10.2012 15:07:54 1 (0x0001)
    Connecting to a local update server with locally detected settings. Updates Publisher 12.10.2012 15:07:56 1 (0x0001)
    Element nicht gefunden Updates Publisher 12.10.2012 15:07:56 1 (0x0001)
    SetCertificate: Successfully created a new signing certificate. Updates Publisher 12.10.2012 15:07:56 1 (0x0001)
    Settings: TestConnection selected. Updates Publisher 12.10.2012 15:07:56 1 (0x0001)
    TestConnection: Verifying current update server settings... Updates Publisher 12.10.2012 15:07:56 1 (0x0001)
    Connecting to a local update server with locally detected settings. Updates Publisher 12.10.2012 15:07:56 1 (0x0001)
    TestConnection: Verification succeeded. Updates Publisher 12.10.2012 15:07:56 1 (0x0001)
    Settings: Applying settings changes. Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
    Current settings: Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: SCUP Database File: <default> C:\Users\Administrator\AppData\Local\Microsoft\System Center Updates Publisher 2011\5.00.1727.0000\scupdb.sdf Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: WSUS Publishing Enabled: True Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: WSUS Publishing is configured to use local server. Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: ConfigMgr Integration Enabled: True Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: Configuration Manager integration is configured to use local server. Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: Configuration Manager client threshold is 1 Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: Configuration Manager client threshold is disabled (0). Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: Proxy Server settings used: True Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Proxy Server: 10.207.39.2 Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Proxy Port: 8080 Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Proxy User: <no value> Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: CRL Checking Enabled: False Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: CheckCatalogSubscriptionsOnStartup: True Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
        Setting: Always check for local update content before downloading : False Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
    Settings: user closed dialog. Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
    Workspace: Settings dialog has completed. Updates Publisher 12.10.2012 15:08:04 1 (0x0001)
    Updates workspace: Starting publish wizard with 2 updates. Updates Publisher 12.10.2012 15:08:07 1 (0x0001)
        Publish: Preparing list of selected updates for publishing. Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
        Connecting to a local update server with locally detected settings. Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
        Publish: Update server name: sccm01 Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
        Publish: Publish operation starting for 2 updates. Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
        Publish: Publish: Verifying update server is configured with a certificate prior to publishing. Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
        Publish: Publish: Update server appears to be configured with a certificate. Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
        Building dependency graph for update 'Adobe Flash Player 32-bit/64-bit ActiveX 11.4.402.287 (UpdateId:'f28e393f-22e3-46b7-9f58-786688415619' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')' Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
        No dependencies found for update 'Adobe Flash Player 32-bit/64-bit ActiveX 11.4.402.287 (UpdateId:'f28e393f-22e3-46b7-9f58-786688415619' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')' Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
    Found total of 0 dependencies (may include duplicates). Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
    PublishItem: Update ''Adobe Flash Player 32-bit/64-bit ActiveX 11.4.402.287 (UpdateId:'f28e393f-22e3-46b7-9f58-786688415619' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')'' has no dependencies. Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
    PublishItem: Publishing update 'Adobe Flash Player 32-bit/64-bit ActiveX 11.4.402.287 (UpdateId:'f28e393f-22e3-46b7-9f58-786688415619' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')'. Updates Publisher 12.10.2012 15:08:11 9 (0x0009)
    PublishItem: --- Evaluating software update 'Adobe Flash Player 32-bit/64-bit ActiveX 11.4.402.287 (UpdateId:'f28e393f-22e3-46b7-9f58-786688415619' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')' for publishing as FullContent. Updates Publisher 12.10.2012 15:08:11 9 (0

     Ich bin sehr dankbar für Hilfe.

    Gruß
    Karl

    Freitag, 12. Oktober 2012 15:57

Antworten

Alle Antworten

  • "TestConnection: Verification succeeded. However, no signing certificate was detected for the update server. You will not be able to publish content to the update server without first registering a signing certificate. Updates Publisher "
    Was wurde denn mit dem Zertifikat gemacht? Ist es ein Codesigning-Zertifikat? Wurde dies zu den Trusteb Publisher und Trusted Root Certification Authorities hinzugefügt?

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

    Sonntag, 14. Oktober 2012 15:26
    Beantworter
  • Hallo Torsten,

    das ist das Root-Zertifikat einer Domäne, das haben wir einfach exportiert das wir eine .pfx-Endung haben. Im Trusted Root ist es sowieso drin, ich meine sogar zweimal. Bei den trusted Publisher ist es auch drin.

    Gruß

    Karl

    Sonntag, 14. Oktober 2012 19:36
  • Ist das Zertifikat denn in SCUP unter Optionen -> Update Server -> Signing Certificate zu sehen? Ist es ein "code signing" Zertifikat?

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

    Montag, 15. Oktober 2012 06:40
    Beantworter
  • Hallo Torsten,

    nein, das war kein code signing Zertifikat, das war Problem. Wir haben jetzt eines aus unserer CA erstellt und jetzt geht es.

    Vielen Dank für Dein Hilfe.

    Gruß

    Karl

    Dienstag, 16. Oktober 2012 20:24
  • Hallo,

    ich würde das Thema gerne nochmal aufgreifen, woran erkenne ich denn ob es ein code signing Zertifikat ist, wir haben hier das selbe Problem.

    Danke

    Donnerstag, 26. September 2013 07:46
  • In der Certificates-MMC, Spalte "Intended Purposes".

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

    Donnerstag, 26. September 2013 08:32
    Beantworter