Apparently only required for driver packages..since regular packages or OS
images didn't have the issue..but did have the checkmark enabled.. K .?

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Frederic Le Royer0
Sent: Wednesday, September 04, 2013 7:15 PM
To: [email protected]
Subject: RE: [mssms] Prestage Content - Solved

 

Well looks like removing the check box on "Copy the content in this package
to a package share on the dp" actually fix the problem for dp configure for
prestage content.

If you are distributing the content to others dp's just make sure you put
the check mark back.

 

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Johan van Dijk
Sent: August-29-13 10:47 AM
To: [email protected]
Subject: RE: [mssms] Prestage Content

 

Bump.

 

(seeing the same issue here..all other packages are OK..just driver packages
aren't.)

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Frederic Le Royer
Sent: Monday, August 26, 2013 3:14 PM
To: [email protected]
Subject: [mssms] Prestage Content

 

Hello,

.         I'm currently Having issues importing some of my prestaged content
to my remote distribution point. I'm getting the following errors at the end
of the PrestageContent.log. (edited to remove timestamps)

CContentDefinition::ExpandContentDefinitionItems failed; 0x80070003
PrestageContent 

Failed to expand content of package CGN0003C PrestageContent

ArchiveFile::Transform2ClassicContentForSMB failed; 0x80004005
PrestageContent 

Error transforming single instance storage to classic storage for SMB access
PrestageContent 

ArchiveFile::RemoteDpPostExtractProcessing failed; 0x80004005
PrestageContent 

ArchiveFile::PostExtractProcessing failed; 0x80004005 PrestageContent

ArchiveFile::ExtractContent failed; 0x80004005 PrestageContent

I have been able to prestage some packages, mainly my OSD image file but the
issue seems to be with the driver packages. at the beginning of the log file
it states Content type:"LegacyContentBased" for the non-working packages
while my working packages specify a "Classic" content type. I presume i<m
looking at the right place with the issue, i just don't know what to do
about it.

Any Suggestions?

 

 

 

 



Reply via email to