Manually copy OSI to DP

[TomF]

Hey all, I have a question but also want to point out the amazing work/guides/posts on this site! Tons of information and has definately pointed me in the right direction multiple times.. but now back to business

 

We currently have SCCM 2007 SP2 with 1 primary site and multiple distribution points in the same forest but different domains. We have been deploying OS Images and some packages via SCCM for a while and have been experiencing this issue since day 1 (started this past summer) and have run out of ideas. When adding the OSI to SCCM, and setting up a Distribution Point it takes HOURS (almost 24 hours in total) to transfer the file to the Distribution Point. The connection between the 2 points is 100mb/s and file size is about 17gigs (a .wim file).

 

- BITS is enabled in IIS on both sites.

- BITS throttling is set to Not Configured in SCCM.

- All BITS throttling GPO's are set to Not Configured.

- Priority for the OSI's are set to High before setting up a Distribution Point.

- Both servers are Win Srv 2003 (latest SP).

- I can copy/paste the file between the points in roughly 11 minutes.

- The package will eventually be successful in sending, but is not realistic for it to take this long.

- Running a constant ping between the 2 sites shows excellent latency and no dropped response times.

 

So with that, I have 2 questions. 1) Is there anything else you can think of that can be causing this? 2) I haven't been able to find a guide on how to manually copy the OSI to the DP properly (where to put it, what to setup, etc) so does anyone know of one?

 

Please help!

[anyweb]

Hey all, I have a question but also want to point out the amazing work/guides/posts on this site! Tons of information and has definately pointed me in the right direction multiple times.. but now back to business

 

thanks !

 

have you checked if antivirus software on the dp is causing a problem ?

[TomF]

No, but good question. Just checking it now (we currently use Symantec EndPoint) and everything seems to check out fine. I'm not seeing any reports of virus' or threats on the server, but we also have no folder exceptions in place on the DP so is it possible that it's still causing issues?

 

I also checked our performance logs on the server incase AV or another service is kicking the **** out of the box while this is happening and the highest cpu spike in the past 2 days (during a deploy) was 40% and 45% ram utilization.

 

Just a side note, I added the OSI to the distribution point yesterday at 1:15pm and it JUST finished today at 2:55pm (shows the Source Version when looking at the Package Status).

 

Thanks for the quick reply!

[Jay P.]

Did you ever figure this out? We're having the same issue. Software Packages/Drivers/Updates get to the DP's just fine but OS packages takes for ever.

 

No, but good question. Just checking it now (we currently use Symantec EndPoint) and everything seems to check out fine. I'm not seeing any reports of virus' or threats on the server, but we also have no folder exceptions in place on the DP so is it possible that it's still causing issues?

 

I also checked our performance logs on the server incase AV or another service is kicking the **** out of the box while this is happening and the highest cpu spike in the past 2 days (during a deploy) was 40% and 45% ram utilization.

 

Just a side note, I added the OSI to the distribution point yesterday at 1:15pm and it JUST finished today at 2:55pm (shows the Source Version when looking at the Package Status).

 

Thanks for the quick reply!

[TomF]

Did you ever figure this out? We're having the same issue. Software Packages/Drivers/Updates get to the DP's just fine but OS packages takes for ever.

 

Nope, no resolution other than waiting.. yay

[Eswar Koneti]

Nope, no resolution other than waiting.. yay

 

 

Do you see anyother imp information from distmgr.log ?