none
SCUP 2011 and Large File Sizes

    Question

  • Hello.


    I am hoping someone here can provide a definite answer on as to rather or not SCUP 2011 can support the signing and distribution of large files sizes.  Our scup publishes to wsus with sccm as the distribution mechanism of updates.  I've been using SCUP to package and deliver updates on a variety of different pieces of software without issues.  Recently though I tried to create two new updates one has a file size of 571mb's the other has a file size of 1.58gb.  Keep in mind I can publish updates that are of smaller size just fine.  It is just these two updates.  Both of these updates are failing with the following error:

    PublishItem: Update ''Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')'' has no dependencies.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: Publishing update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')'.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: --- Evaluating software update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')' for publishing as FullContent.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: Item 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')' is already published on the update server without content, it will need to be revised adding content.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: --- Software update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')' needs to be revised to add full content.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: Retrieving content for update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')'.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: --- Content will be saved to C:\Users\jefcrawf\AppData\Local\Temp\\w4duuks0.sj2\CreativeSuite5.5PatchStore.sfx.exe.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: --- Update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')' specifies local source publishing, checking for local content.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: Local content for update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')' found at E:\LocalPublishZone\CreativeSuite5.5PatchStore.sfx.exe.    Updates Publisher    8/25/2011 2:23:34 PM    26 (0x001A)
    PublishItem: Successfully retrieved content for software update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')' to local file: C:\Users\jefcrawf\AppData\Local\Temp\\w4duuks0.sj2\CreativeSuite5.5PatchStore.sfx.exe    Updates Publisher    8/25/2011 2:23:40 PM    26 (0x001A)
    TrustChecker: File 'C:\Users\jefcrawf\AppData\Local\Temp\\w4duuks0.sj2\CreativeSuite5.5PatchStore.sfx.exe' is not signed.    Updates Publisher    8/25/2011 2:23:57 PM    26 (0x001A)
    TrustChecker: User trusts file.    Updates Publisher    8/25/2011 2:26:06 PM    1 (0x0001)
    PublishItem: --- SDP XML file for publishing created at C:\Users\jefcrawf\AppData\Local\Temp\tmpC11C.tmp    Updates Publisher    8/25/2011 2:26:06 PM    26 (0x001A)
    PublishItem: --- Calling update server API for publishing update 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' Vendor:'Adobe Systems, Inc.' Product:'Creative Suite 5.5')'    Updates Publisher    8/25/2011 2:26:06 PM    26 (0x001A)
    2011-08-25 18:37:18.013 UTC    Info    Scup2011.26    ThreadEntry    _ThreadPoolWaitCallback.PerformWaitCallback    Updates Publisher    8/25/2011 2:37:18 PM    26 (0x001A)
    2011-08-25 18:37:18.121 UTC    Info    Scup2011.26    CabUtilities.CheckCertificateSignature    File cert verification failed for \UpdateServicesPackages\cb8d0536-7508-4af0-b3b5-a61ae056820c\aa6a140c-e8c0-458c-834c-7235677a9c13_2.cab with 2147943792    Updates Publisher    8/25/2011 2:37:18 PM    26 (0x001A)
    2011-08-25 18:37:18.125 UTC    Error    Scup2011.26    Publisher.VerifyAndPublishPackage    VerifyAndPublishPackage(): Failed to Verify Signature for file: \UpdateServicesPackages\cb8d0536-7508-4af0-b3b5-a61ae056820c\aa6a140c-e8c0-458c-834c-7235677a9c13_2.cab    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Microsoft.UpdateServices.Internal.BaseApi.Publisher.VerifyAndPublishPackage()    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishOperation.Start()    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading.ThreadPoolWorkQueue.Dispatch()    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()    Updates Publisher    8/25/2011 2:37:18 PM    26 (0x001A)
    2011-08-25 18:37:18.128 UTC    Error    Scup2011.26    Publisher.PublishPackage    PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:\UpdateServicesPackages\cb8d0536-7508-4af0-b3b5-a61ae056820c\aa6a140c-e8c0-458c-834c-7235677a9c13_2.cab    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishOperation.Start()    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading.ThreadPoolWorkQueue.Dispatch()    Updates Publisher    1/1/1601 12:00:00 AM    26 (0x001A)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()    Updates Publisher    8/25/2011 2:37:18 PM    26 (0x001A)
    PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \UpdateServicesPackages\cb8d0536-7508-4af0-b3b5-a61ae056820c\aa6a140c-e8c0-458c-834c-7235677a9c13_2.cab    Updates Publisher    8/25/2011 2:37:18 PM    26 (0x001A)
    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    8/25/2011 2:37:18 PM    26 (0x001A)
    Publish: Background processing completed.    Updates Publisher    8/25/2011 2:37:18 PM    1 (0x0001)
    Thursday, August 25, 2011 8:35 PM

Answers

  • Hello,

    You have the following error: CabUtilities.CheckCertificateSignature File cert verification failed for \UpdateServicesPackages\cb8d0536-7508-4af0-b3b5-a61ae056820c\aa6a140c-e8c0-458c-834c-7235677a9c13_2.cab with 2147943792.  This usually means the file that is trying to be published is too big to check the certificate signature. Is 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' the 571mb or 1.58GB file?  The 1.58GB file is definitely too big for publishing.


    These postings are provided "AS IS" with no warranties, and confer no rights.
    Learn more about SCUP & ConfigMgr on my blog at: http://blogs.technet.com/jasonlewis
    Thursday, August 25, 2011 9:10 PM

All replies

  • Hello,

    You have the following error: CabUtilities.CheckCertificateSignature File cert verification failed for \UpdateServicesPackages\cb8d0536-7508-4af0-b3b5-a61ae056820c\aa6a140c-e8c0-458c-834c-7235677a9c13_2.cab with 2147943792.  This usually means the file that is trying to be published is too big to check the certificate signature. Is 'Creative Suite 5.5 Update 1 (UpdateId:'cb8d0536-7508-4af0-b3b5-a61ae056820c' the 571mb or 1.58GB file?  The 1.58GB file is definitely too big for publishing.


    These postings are provided "AS IS" with no warranties, and confer no rights.
    Learn more about SCUP & ConfigMgr on my blog at: http://blogs.technet.com/jasonlewis
    Thursday, August 25, 2011 9:10 PM
  • This copy was of the 1.58gb file size one, but both of them have the same error code.  Can you tell me what the maximum file size that scup supports is?

    Thanks for the reply/answer.

    2011-08-25 19:36:39.846 UTC    Error    Scup2011.11    Publisher.VerifyAndPublishPackage    VerifyAndPublishPackage(): Failed to Verify Signature for file: \UpdateServicesPackages\33ddf392-40b0-49a0-acd2-e0498ddcb191\da561df5-48ef-40cb-aa98-4d7bd93db432_2.cab    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at Microsoft.UpdateServices.Internal.BaseApi.Publisher.VerifyAndPublishPackage()    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at Scup.Wizards.PublishOperation.Start()    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.Threading.ThreadPoolWorkQueue.Dispatch()    Updates Publisher    1/1/1601 12:00:00 AM    2876568 (0x2BE498)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()    Updates Publisher    8/25/2011 3:36:39 PM    11 (0x000B)
    2011-08-25 19:36:39.891 UTC    Error    Scup2011.11    Publisher.PublishPackage    PublishPackage(): Operation Failed with Error: Verification of file signature failed for file: \\bl-ait-wsusprd.ads.iu.edu\UpdateServicesPackages\33ddf392-40b0-49a0-acd2-e0498ddcb191\da561df5-48ef-40cb-aa98-4d7bd93db432_2.cab    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at Scup.Wizards.PublishOperation.Start()    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.Threading.ThreadPoolWorkQueue.Dispatch()    Updates Publisher    1/1/1601 12:00:00 AM    11 (0x000B)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()    Updates Publisher    8/25/2011 3:36:39 PM    11 (0x000B)
    PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \UpdateServicesPackages\33ddf392-40b0-49a0-acd2-e0498ddcb191\da561df5-48ef-40cb-aa98-4d7bd93db432_2.cab    Updates Publisher    8/25/2011 3:36:40 PM    11 (0x000B)
    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    8/25/2011 3:36:40 PM    11 (0x000B)
    Publish: Background processing completed.    Updates Publisher    8/25/2011 3:36:40 PM    1 (0x0001)

    Friday, August 26, 2011 5:22 AM
  • The limitation is not driven by Updates Publisher, but rather other factors.  In our testing we have have successfully testing software updates up to 375mb in size. 


    These postings are provided "AS IS" with no warranties, and confer no rights.
    Learn more about SCUP & ConfigMgr on my blog at: http://blogs.technet.com/jasonlewis
    Monday, August 29, 2011 9:02 PM
  • Hi,
     
    I know this thread is old, however I wanted to add our findings. As Jason says, the limit is not with SCUP or any other publishing tool but rather WSUS itself. The code around solution below seems to work. There is no hotfix, however there is a way to configure it for larger files so publishing will succeed.
     
    Also, once you have published to your WSUS server, your clients may need an update too for large packages. if you have Windows 7 SP1 or Windows Server 2008 SP1, I would recommend the following Windows Update Agent update. http://support.microsoft.com/kb/2607070
     
    As to the original questions...
     
    If you have several files that make up a large package (say 1GB), as long as any given file in the package is less than 384MB, there is no problem.
     
    If the package is a single file (say an exe) OR any file as a part of the content  is OVER the 384MB limit, the package creation will fail as described.
     
    There IS a limit that is configurable on the WSUS server.
     
    server = AdminProxy.GetUpdateServer(servername, false, 8530);
     
    int maxcabsize = server.GetConfiguration().LocalPublishingMaxCabSize;
     
    //this defaults to 384MB
     
    IUpdateServerConfiguration config = server.GetConfiguration();
     
    //this bumps the limit to 1GB
     
    config.LocalPublishingMaxCabSize = 1024;
     
    config.Save()

    --------------------------------------------------------------------------------
    David G

    • Edited by DavidGayler Tuesday, November 22, 2011 1:42 PM
    Tuesday, November 22, 2011 1:18 PM
  • I was running into some issues with some HP Proliant Firmware Updates, while all other updates worked , this particular one failed when trying to publish it. Update Size was 435MB

    Max Size was set to 384MB


    Powershell Script:

    Note: Run as administrator locally on your WSUS

    [reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")
    
    $wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer()
    $size = $wsus.GetConfiguration().LocalPublishingMaxCabSize
    Write-host "Current Max Size: " $size $config = $wsus.GetConfiguration() $config.LocalPublishingMaxCabSize = 1024 $config.save()


    • Proposed as answer by Florian Bu Tuesday, November 12, 2013 9:17 AM
    • Unproposed as answer by Florian Bu Tuesday, November 12, 2013 9:17 AM
    • Edited by Anthony Geoffron Tuesday, December 24, 2013 9:21 PM
    Wednesday, June 19, 2013 12:12 AM
  • Hi,

    I am trying to deploy HP ProLiant Server Firmware (472.95MB) from SCUP 2011 to ConfigMgr 2012.

    So by running the PowerShell script it solved the issue of the size of the package to be published.

    But I still have an issue when I am trying to publish, apparently when publishing from SCUP to WSUS, after 30minutes I got a time out...

    Is there is any way to extend this time out?

    Best regard,

    Florian B.

    Tuesday, November 12, 2013 9:23 AM