Why is it that only this one package shows that it is awaiting content prestaging?

I have many more packages than just the SCCM 2012 R2 client and I know I have to distribute the packages to the remote DP after I extract the .pkgx file on the remote DP, but I don't want some packages being sent over the slow WAN links. 

Thanks

Hi,

First, you can cancle the content distribution with DP Job Manager.

Did you enable content prestaging before distributing content? Can you reproduce if you redistribute the content?

What does it say in distmgr.log?

 

I do NOT want to cancel content prestaging. I NEED it desperately due to having slow WAN links.

Yes, I enabled content prestaging before distributing content. Why would I distribute content and then enable content prestaging? Wouldn't that be defeating the purpose?

Thanks

• Edited by I AM Sir Ask Alot 3 hours 17 minutes ago

please look for the below links

https://technet.microsoft.com/en-us/hh692395.aspx?f=255&MSPPError=-2147217396

http://blogs.technet.com/b/inside_osd/archive/2011/04/11/configuration-manger-2012-content-prestaging.aspx

https://technet.microsoft.com/en-us/gg682083.aspx

Could you please add details? What has been done so far? What is (not) working?

It's not that something is NOT working, it's just that I am trying to gain more understanding here. 

Okay, let me be more specific. 

When I go to \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status and I click on the Details tab, I see the following shown in the snippet below:

Then when I click on it, it states the following:

Distribution Manager is waiting for package PR100003 content to be prestaged on the distribution point ["Display=\\MY-SCCM-DP.my.domain.com\"]MSWNET:["SMS_SITE=PR1"]\\MY-SCCM-DP.my.domain.com\. You must manually prestage the package PR100003 on the distribution point before the content will be available. 

So what I am trying to understand is, if I have other packages and NOT just PR100003, how come they are NOT showing up in this message as well? Why is it that only PR100003 is showing up? It leads me to believe that PR100003 is the ONLY package that is enabled for content prestaging, but the others are NOT. So, if I begin distributing the packages over to the remote site from my Site Server after I run the ExtractContent.exe tool, the PR100003 package be the ONLY one that gets processed, but all the other packages will get sent over the slow WAN links.

I just want to ensure that NO package whatsoever is actually sent over the WAN. 

I hope that was more clear, if not, please let me know.

Thanks for your help everyone. 

• Edited by I AM Sir Ask Alot 34 minutes ago

I do NOT want to cancel content prestaging. I NEED it desperately due to having slow WAN links.

Yes, I enabled content prestaging before distributing content. Why would I distribute content and then enable content prestaging? Wouldn't that be defeating the purpose?

Thanks

• Edited by I AM Sir Ask Alot Tuesday, July 21, 2015 4:31 AM

I do NOT want to cancel content prestaging. I NEED it desperately due to having slow WAN links.

Yes, I enabled content prestaging before distributing content. Why would I distribute content and then enable content prestaging? Wouldn't that be defeating the purpose?

Thanks

• Edited by I AM Sir Ask Alot Tuesday, July 21, 2015 4:31 AM

I do NOT want to cancel content prestaging. I NEED it desperately due to having slow WAN links.

Yes, I enabled content prestaging before distributing content. Why would I distribute content and then enable content prestaging? Wouldn't that be defeating the purpose?

Thanks

• Edited by I AM Sir Ask Alot Tuesday, July 21, 2015 4:31 AM

It's not that something is NOT working, it's just that I am trying to gain more understanding here. 

Okay, let me be more specific. 

So far all I have done was just check the "Enable this distribution point for prestaged content" checkbox on the Distribution Point Properties General tab.

After that, when I go to \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status and I click on the Details tab, I see the following shown in the snippet below:

Then when I click on it, it states the following:

Distribution Manager is waiting for package PR100003 content to be prestaged on the distribution point ["Display=\\MY-SCCM-DP.my.domain.com\"]MSWNET:["SMS_SITE=PR1"]\\MY-SCCM-DP.my.domain.com\. You must manually prestage the package PR100003 on the distribution point before the content will be available. 

So what I am trying to understand is, if I have other packages and NOT just PR100003, how come they are NOT showing up in this message as well? Why is it that only PR100003 is showing up? It leads me to believe that PR100003 is the ONLY package that is enabled for content prestaging, but the others are NOT. So, if I begin distributing the packages over to the remote site from my Site Server after I run the ExtractContent.exe tool on my remote DP to extract the contents of the .pkgx file, will the PR100003 package be the ONLY one that gets processed and all the other packages will get sent over the slow WAN links?

Is this normal to NOT show all the other packages in this message and it indicates that my remote DP is simply ready for the content to be processed?

I just want to ensure that NO package whatsoever is actually sent over the WAN. 

I hope that was more clear. If not, please let me know.

Thanks for your help everyone.

• Edited by I AM Sir Ask Alot 17 hours 35 minutes ago

It's not that something is NOT working, it's just that I am trying to gain more understanding here. 

Okay, let me be more specific. 

So far all I have done was just check the "Enable this distribution point for prestaged content" checkbox on the Distribution Point Properties General tab.

After that, when I go to \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status and I click on the Details tab, I see the following shown in the snippet below:

Then when I click on it, it states the following:

Distribution Manager is waiting for package PR100003 content to be prestaged on the distribution point ["Display=\\MY-SCCM-DP.my.domain.com\"]MSWNET:["SMS_SITE=PR1"]\\MY-SCCM-DP.my.domain.com\. You must manually prestage the package PR100003 on the distribution point before the content will be available. 

So what I am trying to understand is, if I have other packages and NOT just PR100003, how come they are NOT showing up in this message as well? Why is it that only PR100003 is showing up? It leads me to believe that PR100003 is the ONLY package that is enabled for content prestaging, but the others are NOT. So, if I begin distributing the packages over to the remote site from my Site Server after I run the ExtractContent.exe tool on my remote DP to extract the contents of the .pkgx file, will the PR100003 package be the ONLY one that gets processed and all the other packages will get sent over the slow WAN links?

Is this normal to NOT show all the other packages in this message and it indicates that my remote DP is simply ready for the content to be processed?

I just want to ensure that NO package whatsoever is actually sent over the WAN. 

I hope that was more clear. If not, please let me know.

Thanks for your help everyone.

• Edited by I AM Sir Ask Alot Tuesday, July 21, 2015 2:14 PM

It's not that something is NOT working, it's just that I am trying to gain more understanding here. 

Okay, let me be more specific. 

So far all I have done was just check the "Enable this distribution point for prestaged content" checkbox on the Distribution Point Properties General tab.

After that, when I go to \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status and I click on the Details tab, I see the following shown in the snippet below:

Then when I click on it, it states the following:

Distribution Manager is waiting for package PR100003 content to be prestaged on the distribution point ["Display=\\MY-SCCM-DP.my.domain.com\"]MSWNET:["SMS_SITE=PR1"]\\MY-SCCM-DP.my.domain.com\. You must manually prestage the package PR100003 on the distribution point before the content will be available. 

So what I am trying to understand is, if I have other packages and NOT just PR100003, how come they are NOT showing up in this message as well? Why is it that only PR100003 is showing up? It leads me to believe that PR100003 is the ONLY package that is enabled for content prestaging, but the others are NOT. So, if I begin distributing the packages over to the remote site from my Site Server after I run the ExtractContent.exe tool on my remote DP to extract the contents of the .pkgx file, will the PR100003 package be the ONLY one that gets processed and all the other packages will get sent over the slow WAN links?

Is this normal to NOT show all the other packages in this message and it indicates that my remote DP is simply ready for the content to be processed?

I just want to ensure that NO package whatsoever is actually sent over the WAN. 

I hope that was more clear. If not, please let me know.

Thanks for your help everyone.

• Edited by I AM Sir Ask Alot Tuesday, July 21, 2015 2:14 PM

It's not that something is NOT working, it's just that I am trying to gain more understanding here. 

Okay, let me be more specific. 

So far all I have done was just check the "Enable this distribution point for prestaged content" checkbox on the Distribution Point Properties General tab.

After that, when I go to \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status and I click on the Details tab, I see the following shown in the snippet below:

Then when I click on it, it states the following:

Distribution Manager is waiting for package PR100003 content to be prestaged on the distribution point ["Display=\\MY-SCCM-DP.my.domain.com\"]MSWNET:["SMS_SITE=PR1"]\\MY-SCCM-DP.my.domain.com\. You must manually prestage the package PR100003 on the distribution point before the content will be available. 

So what I am trying to understand is, if I have other packages and NOT just PR100003, how come they are NOT showing up in this message as well? Why is it that only PR100003 is showing up? It leads me to believe that PR100003 is the ONLY package that is enabled for content prestaging, but the others are NOT. So, if I begin distributing the packages over to the remote site from my Site Server after I run the ExtractContent.exe tool on my remote DP to extract the contents of the .pkgx file, will the PR100003 package be the ONLY one that gets processed and all the other packages will get sent over the slow WAN links?

Is this normal to NOT show all the other packages in this message and it indicates that my remote DP is simply ready for the content to be processed?

I just want to ensure that NO package whatsoever is actually sent over the WAN. 

I hope that was more clear. If not, please let me know.

Thanks for your help everyone.

• Edited by I AM Sir Ask Alot Tuesday, July 21, 2015 2:14 PM

HELP ME!! 

Is anyone going to offer anything more?

I really need to get this remote DP setup with these packages, but I am waiting to hear back from an MVP, MCC, guru, etc. 

Thanks

It leads me to believe that PR100003 is the ONLY package that is enabled for content prestaging, but the others are NOT.

Are other objects (packages, applications etc) already deployed to the DP? How many objects are assigned to it if you bring up the properties?

Torsten, 

When I go to \Administration\Overview\Distribution Points and I open up the DP properties of my remote DP and I click on the Content tab, the only package that shows up is PR100003, which is the SCCM 2012 R2 client, but nothing else. 

So have you already distributed any content to that DP? If not: that would be the expected behavior.

No, I have not distributed anything to it, because I do not want any packages to be sent across the WAN, right?.

I don't understand why it's showing that package PR100003 is awaiting to be prestaged when it's already on the DP.

So once I extract the .pkgx file on the remote DP, it will then send the status message to the Site Server telling it that it is ready for the packages that were extracted to be distributed, then perhaps my other packages will show up under Distribution Point Configuration Status?

Thanks

• Edited by I AM Sir Ask Alot 16 hours 42 minutes ago

No, I have not distributed anything to it, because I do not want any packages to be sent across the WAN, right?.

I don't understand why it's showing that package PR100003 is awaiting to be prestaged when it's already on the DP.

So once I extract the .pkgx file on the remote DP, it will then send the status message to the Site Server telling it that it is ready for the packages that were extracted to be distributed, then perhaps my other packages will show up under Distribution Point Configuration Status?

Thanks

• Edited by I AM Sir Ask Alot Friday, July 24, 2015 3:09 PM

No, I have not distributed anything to it, because I do not want any packages to be sent across the WAN, right?.

I don't understand why it's showing that package PR100003 is awaiting to be prestaged when it's already on the DP.

So once I extract the .pkgx file on the remote DP, it will then send the status message to the Site Server telling it that it is ready for the packages that were extracted to be distributed, then perhaps my other packages will show up under Distribution Point Configuration Status?

Thanks

• Edited by I AM Sir Ask Alot Friday, July 24, 2015 3:09 PM

No, I have not distributed anything to it, because I do not want any packages to be sent across the WAN, right?.

I don't understand why it's showing that package PR100003 is awaiting to be prestaged when it's already on the DP.

So once I extract the .pkgx file on the remote DP, it will then send the status message to the Site Server telling it that it is ready for the packages that were extracted to be distributed, then perhaps my other packages will show up under Distribution Point Configuration Status?

Thanks

• Edited by I AM Sir Ask Alot Friday, July 24, 2015 3:09 PM

Okay, I ran the ExtractContent.exe tool on my .pkgx file and it produced the following output:

Prestaging content to content library D:\SCCMContentLib
        uncompress      25 %
        uncompress      50 %
        uncompress      75 %

My questions now are how come the uncompress does not show 100% and is each uncompress there for each package that was contained in the .pkgx file? Because as I recall, I only prestaged 3 packages, so showing the 3 uncompress statuses above makes sense. 

Perhaps the uncompress percent statuses mean that the original compression was 25%, 50%, and 75%, so that is why it is showing these values? 

I guess there is no such thing as 100% compression, obviously. 

Also, when I go back to check the Distribution Point Configuration Status it still shows the one package (PR100003) as awaiting content prestaging, but no others after I ran the ExtractContent.exe tool. 

Thanks

• Edited by I AM Sir Ask Alot 9 hours 4 minutes ago

Okay, I ran the ExtractContent.exe tool on my .pkgx file and it produced the following output:

Prestaging content to content library D:\SCCMContentLib
        uncompress      25 %
        uncompress      50 %
        uncompress      75 %

My questions now are how come the uncompress does not show 100% and is each uncompress there for each package that was contained in the .pkgx file? Because as I recall, I only prestaged 3 packages, so showing the 3 uncompress statuses above makes sense. 

Perhaps the uncompress percent statuses mean that the original compression was 25%, 50%, and 75%, so that is why it is showing these values? 

I guess there is no such thing as 100% compression, obviously. 

Also, when I go back to check the Distribution Point Configuration Status it still shows the one package (PR100003) as awaiting content prestaging, but no others after I ran the ExtractContent.exe tool. 

Thanks

• Edited by I AM Sir Ask Alot Friday, July 24, 2015 10:47 PM

I am getting nowhere in this thread so I will be asking this question in another. 

There were errors in the PrestageContent.log and it seems that the package transfer issue is related to corrupt packages. After re-creating and re-distributing the packages, it seems to be working just fine now. 

• Marked as answer by I AM Sir Ask Alot 10 hours 55 minutes ago

There were errors in the PrestageContent.log and it seems that the package transfer issue is related to corrupt packages. After re-creating and re-distributing the packages, it seems to be working just fine now. 

• Marked as answer by I AM Sir Ask Alot Thursday, July 30, 2015 8:56 PM