question

Left the following response on your other thread. "Sounds about right. You can do without the option of requiring pre-stage for content in DP properties. I don't think I have ever used it when pre-staging the content. The status should sync back."

Hi, @lalajee

Thank you for posting in Microsoft Q&A forum.

Maybe george9078907890's reply in this thread help:
https://social.technet.microsoft.com/Forums/en-US/c2084a4d-34da-4908-8ea4-b91e06e15c93/locked-sccm-client-package-waiting-for-prestaged-content-cant-use-client-push?forum=configmanagerdeployment

As soon as you create a DP it appears that the client installation package automatically tries to distribute to the DP. If you created the DP as "Enabled for Prestage" while doing the setup then the SCCM client package will just wait for you to copy it manually. To reslove this I had to remove the "Enabled for Prestage Content" from the DP then go into the SCCM client Package, content location tab, select the DP and redistribute the package to the DP.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

I have remove the Prestage tick from new DP but 2000 packages are still say

Waiting for prestaged content Distribution Manager is waiting for package xxxxxxx content to be prestaged on the distribution point ["Display=\\xxxxxxx\"]MSWNET:["SMS_SITE=xxx"]\\xxxxxxx. You must manually prestage the package xxxxxxx on the distribution point before the content will be available. In Progress xxxxxxx

All of the packages are already on the DP - I can see them in the content library application

How do I force site server to mark these packages as successful

2000? That could be the reason for the sync not reflecting. Did you check the DP and MP logs to check if there things are working in the background or not? State messages may have got into a backlog.

I just did this migration and originally set the distribution point to enable prestaged content. 90% of the content was restored using ExtractContent.exe but the last 10% had changed since the export took place. Those remaining packages were stuck on "waiting for prestage content" that would never come.

I unchecked "enabled prestaged content" on the distribution point configuration but they still remained on "waiting for prestaged content". I found that you could get it to distribute it you clicked on "redistribute content" but this required getting a list of packages that were stuck, right clicking the properties of each one, visiting the content locations tab, then clicking redistribute on each one.

Here is a better way. Some of the code was borrowed from other more capable sources, but I found that a status of 7 was "waiting for prestaged content". Fix the final line with your sitecode and the distribution point FQDN. Run using PowerShell with admin rights on your MP.

 Function Redistribute-Content {
     [CMDletBinding()]
     param (
     [Parameter(Mandatory=$True)]
     [ValidateNotNullorEmpty()]
     [String]$DistributionPoint,
     [Parameter(Mandatory=$True)]
     [ValidateNotNullorEmpty()]
     [String]$SiteCode
     )
     Process {
        
     $query = 'SELECT * FROM SMS_PackageStatusDistPointsSummarizer WHERE State = 7' #waiting for prestaged content
     $Packages = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query $query | Select-Object PackageID, @{N='DistributionPoint';E={$_.ServerNalPath.split('\')[2]}}
     $FailedPackages = $Packages | Where-Object {$_.DistributionPoint -like "$DistributionPoint"} | Select-Object -ExpandProperty PackageID
     foreach ($PackageID in $FailedPackages) {
         $List = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID' AND ServerNALPath like '%$DistributionPoint%'"
         $List.RefreshNow = $True
         $List.Put()
         }
     }
 }
    
 Redistribute-Content -sitecode XXX -DistributionPoint server01.domain.com