none
Redistribute Configuration Manager Client Upgrade Package (XXX00003)

    Question

  • I am completing the implementation of a ConfigMgr 2012 environment for a customer.  We have migrated the packages and clients from a ConfigMgr 2007, but the migration has been clunky at best. 

    We have all of the packages on all of the remote DPs except for the "special" package, "Configuration
    Manager Client Upgrade Package" (XXX00003).  It has failed on about 1/3 of the remote distribution points.  The reason it failed is that the Distribution Point Upgrade process did not retry sending the package.  We observed that initial attempt to install this package as well as the "Configuration
    Manager Client Package" (XXX00002) early in the DP upgrade process, before the DP is actually installed.  At some point in the future (maybe an hour), it tries again and succeeds. 

    However, before we had figured this out, we had a number of DPs that were interrupted for some reason, and it never retries the packages.  We are able to redistribute the "Configuration
    Manager Client Package" on those that failed, but we are not able to do for "Configuration
    Manager Client Upgrade Package" (XXX00003). 

    Any ideas on how we can trigger this redistribution to occur? 

    Friday, August 17, 2012 2:45 PM

Answers

  • You can try it with powershell:

    $SiteCode = "XXX"
    $PackageID = "XXX00003"
         $distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
            foreach ($dp in $distpoints)
            {
                    $dp.RefreshNow = $true
                    $dp.Put()
            }
    • Marked as answer by mccollett Monday, September 10, 2012 5:20 PM
    Monday, August 20, 2012 11:08 AM

All replies

  • You can try it with powershell:

    $SiteCode = "XXX"
    $PackageID = "XXX00003"
         $distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
            foreach ($dp in $distpoints)
            {
                    $dp.RefreshNow = $true
                    $dp.Put()
            }
    • Marked as answer by mccollett Monday, September 10, 2012 5:20 PM
    Monday, August 20, 2012 11:08 AM
  • Michael,

    That powershell snip works perfectly - I can see it trigger redistribution to all of my DPs. However, I'm still h aving an issue. Every time the site tries to copy to a remote DP, I get the following in my PkgXferMgr log. For referece, my "CAS00002" corresponds to mccollett's "XXX00003" - the "Configuration Manager Client Upgrade Package".

    Sending legacy content CAS00002.1 for package CAS00002	SMS_PACKAGE_TRANSFER_MANAGER	8/27/2012 8:01:22 PM	4196 (0x1064)
    CContentDefinition::TotalFileSizes failed; 0x80070003	SMS_PACKAGE_TRANSFER_MANAGER	8/27/2012 8:01:22 PM	4196 (0x1064)
    Redistribute=1, Related=	SMS_PACKAGE_TRANSFER_MANAGER	8/27/2012 8:01:22 PM	4196 (0x1064)
    CSendFileAction::SendFiles failed; 0x80070003	SMS_PACKAGE_TRANSFER_MANAGER	8/27/2012 8:01:22 PM	4196 (0x1064)
    CSendFileAction::SendFiles failed; 0x80070003	SMS_PACKAGE_TRANSFER_MANAGER	8/27/2012 8:01:22 PM	4196 (0x1064)
    Notifying pkgXferJobMgr	SMS_PACKAGE_TRANSFER_MANAGER	8/27/2012 8:01:22 PM	4196 (0x1064)
     Sending failed. Failure count = 1, Restart time = 8/27/2012 8:31:22 PM Central Daylight Time	SMS_PACKAGE_TRANSFER_MANAGER	8/27/2012 8:01:22 PM	4196 (0x1064)

    It looks like it can't find files of some kind, although I don't know which ones...the source, the hash, the signature...what? I had this problem affect several of my packages, and with "normal" packages, I could update the distribution points, which updates the source version and forces the site to completely regenerate hash values and signatures, etc. But I can't just right click this "special" upgrade package and update distribution points. So is there a way to somehow modify the properties of this package such that it has a new source version? Or trigger a re-run of the hash/signature generation operations?

    I do notice that when I try to get this package using WMI, it's not actually present. Everything else is present in the SMS_Packages class, but not the package I'm struggling with.

    Thanks,

    Andrew


    Andrew Topp

    Tuesday, August 28, 2012 1:13 AM
  • MichaelW506,

    Your Powershell script worked for me!  Thanks!

    Monday, September 10, 2012 5:20 PM
  • Hi,

    i dont get it. I make a txt with your text. Change the ditecode and package id, rename the txt to a ps1 and let it run? Right?

    When i do this its opening a window for 1/10 second and after that its closed again. I dont see any changes in the sender.log where i normally should see that the package is send again! Am i right?

    Thanks for the help!

    Andy

    Tuesday, October 2, 2012 8:29 AM
  • Open Powershell and start the script within the PoSh console.

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

    Tuesday, October 2, 2012 9:43 AM
  • Open Powershell and start the script within the PoSh console.

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


    Worked! Danke :)
    Tuesday, October 2, 2012 10:17 AM
  • The script works however we have 100 distribution points and it would be best if i can change the script to only update on the single distribution point thats missing the package.

    How would i adjust the script so i can choose the distribution point to refresh the package on?

    Cheers

    Wednesday, October 10, 2012 6:19 PM
  • I had the same problem. I only wanted to refresh the package on one distribution point so I modified MichaelW506's script to be able to target one distribution point based on the ServerNalPath.

    Here is my script:

    $SiteCode = "XXX"

    $PackageID = "XXX00004"

    $nalpath = '["Display=\\server.domain.COM.AU\"]MSWNET:["SMS_SITE=XXX"]\\server.domain.COM.AU\'

    $distpoint = Get-WmiObject -class SMS_DistributionPoint -namespace "root\SMS\Site_$($SiteCode)" | Where-Object{$_.PackageID -match "$PackageID"}


    foreach($dp in $distpoint)
    {

        If($nalpath -eq $dp.ServerNalPath)
        {
        $dp.RefreshNow = $true
        $dp.Put()
       
        }
    }

    Wednesday, January 16, 2013 4:27 AM
  • Hi Michael,

    Any idea why the default CM Client Upgrade package gets in this state?

    Thanks,

    Jeff


    Jeff

    Thursday, May 9, 2013 3:33 AM
  • Thanks, worked a trick. Does this package not distribute like a normal package because SCCM creates it when you set it up?
    Monday, September 9, 2013 11:53 PM
  •  I set the PS Execution policy to unrestricted, created the script in the C: when I try to execute it I get the following error:

    Get-WmiObject : Invalid namespace
    At C:\SCC.ps1:3 char:33
    +      $distpoints = Get-WmiObject <<<<  -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * Fro
    Point WHERE PackageID='$PackageID'"
        + CategoryInfo          : InvalidOperation: (:) [Get-WmiObject], ManagementException
        + FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCom

    Property 'RefreshNow' cannot be found on this object; make sure it exists and is settable.
    At C:\SCC.ps1:6 char:21
    +                 $dp. <<<< RefreshNow = $true
        + CategoryInfo          : InvalidOperation: (RefreshNow:String) [], RuntimeException
        + FullyQualifiedErrorId : PropertyNotFound

    You cannot call a method on a null-valued expression.
    At C:\SCC.ps1:7 char:24
    +                 $dp.Put <<<< ()
        + CategoryInfo          : InvalidOperation: (Put:String) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull

    Please help..

    Monday, March 17, 2014 8:03 PM
  • Make sure that you are running this script on the Primary site server.... then it will work..

    I saw the same error while trying to run on the secondary site server where i had a console installed.

    Hope this helps


    Pavel

    Wednesday, April 30, 2014 6:58 PM
  • Hi All

    I had the same problem with the client upgrade package (XXX00002) 

    Thx for the script it works perfect only I have 8 distribution points and 2 of then still have an error on the client upgrade package (XXX00002)  

    Anyone knows how I can correct those 2 distribution points

    Regards

    Johan

    Tuesday, May 27, 2014 4:10 PM
  • Hi All

    The following article did the tric for me

    http://scexblog.blogspot.nl/2014/04/configuration-manager-client-upgrade.html

    regards

    Johan

    • Proposed as answer by Johan Erven Wednesday, May 28, 2014 7:56 AM
    Wednesday, May 28, 2014 7:56 AM
  • Hi All

    The following article did the tric for me

    http://scexblog.blogspot.nl/2014/04/configuration-manager-client-upgrade.html

    regards

    Johan

    This works like a Magic. 
    Wednesday, January 23, 2019 3:42 PM