I was checking the We had a package that was stuck “In Progress” distributing content to a couple of our DP’s. It was the Client Upgrade Package. I couldn’t find it in the packages when I looked for it, at least not with the same package ID. We did have a Client Upgrade Package, but with a different ID. I eventually opened a ticket with Microsoft.
We had recently upgraded to R2 CU1 and come to find out, somehow, we got a new Client Upgrade Package created and it was hidden. Now, this is the way it’s supposed to be and evidently, when we performed the upgrade, our old package was made visible and a new package was created and distributed. But, the distribution was hung up for weeks on two DP’s.
After some research, Microsoft came back with a way to push the package along and this solved our issue.
First, you need to get the NAL path of the package, so query the site server database with the following query:
select NALPath from PkgServers where PkgID =
(select PkgID from SMSPackages where Name = 'Configuration Manager Client Upgrade Package')
From the results, select the problem DP
Connect to rootSMSSite_<site code> (if not running on the site server use the path
Click Execute Method and enter: SMS_Site and click OK
In the Method: Dropdown, select RedistributeAutoUpgradeClientContent
Click the Edit In Parameters… Button
This was the solution to our issue. The challenge was the fact we had both a hidden and non-hidden package. I had to plug in the packageID manually in the SQL query.