Typically an error like this:
Import failed as \\aaa.bbb.com\windows_software$\Packages SCCM\OSD\Drivers\HP
elitebook 8x0 G1 - ZBook xx Win7 x64\storage\realtek\P008X2B2\DrvBin64\* is a
Reparse Point that SMS does not support via downloads. DriverCatalog
20-Nov-13 10:56:44 5152 (0x1420)
Failed to build driver content information for
"\\aaa.bbb.com\windows_software$\Packages SCCM\OSD\Drivers\HP elitebook 8x0 G1
- ZBook xx Win7 x64\storage\realtek\P008X2B2\DrvBin64". Code 0x80004005
DriverCatalog 20-Nov-13 10:56:44 5152 (0x1420)
From: [email protected] [mailto:[email protected]] On
Behalf Of Roland Janus
Sent: Monday, January 20, 2014 11:19 AM
To: [email protected]
Subject: RE: [mssms] Server 2012 Deduplication
What happens if used?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Russ Rimmerman
Sent: Montag, 20. Januar 2014 18:04
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Server 2012 Deduplication
Correct, ConfigMgr 2012 doesn’t support reparse points (which server 2012
de-dupe creates). The issues can mostly be seen when importing drivers from a
de-dupe enabled drive where the driver packs have file overlap (and therefore
the reparse points are created to de-dupe the contents of said driver packs.)
So it’s not currently supported.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Monday, January 20, 2014 9:09 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Server 2012 Deduplication
There is a known issue with 2012 disk de-deup on the sccmcontentlib, Russ
Rimmerman posted on it on this list a while back (I think). It has to do with
symbolic links which ConfigMgr does make use of in the contentlib for certain
content types.
J
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Monday, January 20, 2014 8:41 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] Server 2012 Deduplication
Roland
On the SOURCE folder, yes - that would be a good plan, as would the
deduplication of VHDs both of which is not only supported but exceedingly good
practice. I thought that my comment was pretty explicit that I was referring
to DPs only.
As for supportability I am pretty sure that there would not have been a test
plan to test the interaction - ergo there would be no support for it. As far
as I know, and having asked the question directly before this should not work
although not tested it myself.
Sent from Windows Mail
From: Roland Janus<mailto:[email protected]>
Sent: Monday, 20 January 2014 14:32
To: [email protected]<mailto:[email protected]>
Not supported says it where?
CM12: file based only, the exact same file twice is stored once only but for
the library only.
Server2012: Content based and for the whole volume, also works e.g. with VHDs.
Use Dedup for example on the source folder of the packages…
I use it also for the content library, it squeezes even more out of it.
-R
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Montag, 20. Januar 2014 14:53
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] Server 2012 Deduplication
Matt
SCCM 2012 has its own dedupe mechanism for content. It would not be supported
or recommended to implement dedupe on DPs
Sent from Windows Mail
From: Matt Wilkinson<mailto:[email protected]>
Sent: Monday, 20 January 2014 13:49
To: [email protected]<mailto:[email protected]>
Can this work on DPs to cut down on the amount of storage needed?
Is it supported?
_____________________________________________________________________
This email has been scanned by the MessageLabs Email Security System on behalf
of Leeds College of Building.
For more information please visit http://www.symanteccloud.com
_____________________________________________________________________
