Manually copying the source files into a package
I am updating a "Operating System Images" package with a new source file ( a 4Gig .wim file). Every time I do that, I have to wait for the engine to process this request and it sometimes takes longer than manually copying the source file and pasting it in the package folder (for example SD1000AB folder on a DP), which seems like what it does in the background.Are there any implications when I manually do this instead of modifying the package source and then updating the DPs?Thanks,MayurMayur
March 4th, 2009 6:34pm

Why not turn off binary differential replication for that package which is on by default for image packages? Then it will copy the whole file every time you update the package. With it on, ConfigMgr calculates a hash for the source the the destination,creates a differential file, copies the diff file to the destination system in a temporary location and merges this in with the destination package in the temporary folder and then copies the final file to the package share -- a lot of copying going on. This is great for bandwidth, but not time as you've found out. With BDR off, it simply copies the file from the source straight to the DP share.That is unless you actually need binary differential replication which it sounds like you don't care about at this point.Jason | http://myitforum.com/cs2/blogs/jsandys
Free Windows Admin Tool Kit Click here and download it now
March 6th, 2009 4:54am

Jason, thanks for replying. I have not tried this yet. I have been busy with other OSD related issues and million other things that I am working on. I will definitely give this a try and post the results. Mayur
March 23rd, 2009 5:40am

I know this is a old post but... When I distribute a OS image (about 5 GB .wim) it takes over 2 hours to copy. If I copy the same to my DP manually outside of SCCM, it takes 15 minutes. I believe one of the reasons that it takes this long is because it is a secondary site. Binary replication is already off. Is there any harm in copying the package manually to the DP's? Package mismatch?
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2011 6:51pm

You can use PreloadPkgOnSite.exe (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=C36FCDA8-9336-4D44-9568-5530FF7635DD&displaylang=en) if you have previosuly distributed the package to another child or secondary site. The extra time is all about saving bandwidth because that should be the only reason that you have a secondary site -- the package must be compressed on the source site and then uncompressed on the destination. The compressed file copy is also subject to any throttling you may have configured on the site's address. If it only takes 15 minutes for you to copy 5GB to the secondary, why do you have a secondary?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
March 17th, 2011 7:27pm

If it only takes 15 minutes for you to copy 5GB to the secondary, why do you have a secondary? Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys Saving on SQL license and management overhead?Mayur
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2011 5:12pm

??? A standard DP does not use SQL Server and requires less overhead than a secondary site. I'm not suggesting a primary site, I'm suggesting no additional site. Secondary sites are for bandwidth control. With 5GB in 15 minutes, it doesn't sound like you really need any bandwidth throttling.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
April 5th, 2011 6:39pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics