Manually Update a Package on Distribution Points ?
Hi, is there a way to update packages manually on DP's ? The idea is to copy (in my case an approx. 4 GB Windows 7 Image) by using the Windows Explorer to all assigned DP's instead of using choosing Update Distribution Points within SCCM. Why ? Because it's much more faster. Using the Windows Explorer I need approx 30 minutes, using Update Distribution in SCCM it takes about 2-3 days !
May 17th, 2012 3:48am

Hi, You cannot simply copy the package directory you need to use the Packagepreload tool, the process is described here.. http://blogs.technet.com/b/configurationmgr/archive/2009/05/07/configmgr-2007-the-preload-package-tool-preloadpkgonsite-exe-explained.aspx Why does it take so long to copy the package using SCCM? Can't you increase the number of threads used by Distribution Manager? or what is the problem? Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2012 5:35am

Hi, thanks for your answer. My idea was to copy files manually and increase the version number manualy in the database, but I think there are some other additional things to do. I'll try the preload tool. Don't know why it takes so long, I've already increase the number of threads and I've removed the bandwith limit. The replication is like a blackbox for me, maybe it has been finished tomorrow, maybe in two days. Is there a way to see the current state of replication (something like "percent copied...") For the moment I only look in the sender.log and I see it's in progress, but can't see how long it still takes till it has been finished. Probably we've 2 Windows 7 Images (4 GB and 15 GB). Each 3 months we rebuild these images with the latest Hotfixes, Updates, etc. We're speaking about 30 secondry sites where it must be replicated. The Build is running on Friday and the replication will be started in the evening. The goal is, all DP's should be updated latest Monday in the morning, otherwise the local IT Stuff is not able to use the OS Deployment. The only idea I have is to work with 2 versions of these images. One image which can be used (because it's replicated), the another one will be replicated. If all replications has been finished I will change the OS Image to the second one (the latest build) in the Task Sequence.
May 17th, 2012 5:55am

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

Other recent topics Other recent topics