OSD process slow and using up majority of site's bandwidth.
We have recieved report from a secondary site that when attempting to OSD 1 it takes several hours and the tech notices bandwidth spikes making the network almost un-usable to other people working on the network. Being new to troubleshooting OSD and network utilization issues I was hoping you can help! Here is the user's words; "I have been attempting to image a new comuter and the process is taking a very long time. Normally it would have been completed within 30 -45 minutes at the very most. My most recent attempt the image process was at 20% complete after an hour. Also whenever I image a computer my network traffic spikes and slows everything else down dramatically. It appears that the image process takes all available bandwidth, this happens whether I am imaging a single computer or multiple computers. I should be able to image atleast one computer without impacting the network for the rest of my office." Please let me know what information I can scrounge up and Ill make sure I update the site. A little background on this issue is, I work at the central site, we distribute our images to a local DP. This local DP hosts the boot and osd image as well as the task sequence and the device drivers. Our image is an updated WinXPSP3 image with no special software and our device drivers install during the task sequence.
April 27th, 2011 9:07am

A couple of questions: - You mention both a secondary site and a DP. Is there a secondary site server in the branch office or just a DP? - Is the DP protected? - Have you verified that all packages are actually copied successfully to the DP in the branch office? - Which network is jammed? WAN link or LAN at branch office?
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2011 9:22am

is bits throttling configured or enabled ? you should check it out, (site settings, client agents, computer client agents, bits) also, are your computers pulling the WIM file from the local server or over the WAN, check SMSTS.log file for details and if from the WAN check how your boundaries are configured My step by step SCCM Guides I'm on Twitter > ncbrady
April 27th, 2011 9:24am

A couple of questions: - You mention both a secondary site and a DP. Is there a secondary site server in the branch office or just a DP? - Is the DP protected? - Have you verified that all packages are actually copied successfully to the DP in the branch office? - Which network is jammed? WAN link or LAN at branch office? We have a primary site where we place our enterprise wide packages...etc. They have a primary site for their state's office as well as secondary sites for their field offices. The field offices are experiencing issues with deployments, so I am to assume that their LAN is getting jammed. I emailed the user to find out more about the situation. Sadly like most enterprise situation, if it is a network issue I have to pass the buck but more often than not the network shop points the finger at software configuration. So, it's best to check out everything I can on my end, thanks!
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2011 10:20am

We have recieved report from a secondary site that when attempting to OSD 1 it takes several hours and the tech notices bandwidth spikes making the network almost un-usable to other people working on the network. Being new to troubleshooting OSD and network utilization issues I was hoping you can help! Here is the user's words; "I have been attempting to image a new comuter and the process is taking a very long time. Normally it would have been completed within 30 -45 minutes at the very most. My most recent attempt the image process was at 20% complete after an hour. Also whenever I image a computer my network traffic spikes and slows everything else down dramatically. It appears that the image process takes all available bandwidth, this happens whether I am imaging a single computer or multiple computers. I should be able to image atleast one computewithout impacting the network for the rest of my office." Please let me know what information I can scrounge up and Ill make sure I update the site. A little background on this issue is, I work at the central site, we distribute our images to a local DP. This local DP hosts the boot and osd image as well as the task sequence and the device drivers. Our image is an updated WinXPSP3 image with no special software and our device drivers install during the task sequence. Here is how everything is "working" here. Our primary SCCM site is distributing to a state office SCCM site. This main State office SCCM site is then distributing to a local distribution server (DS). Everything that is needed for OSD is distributed and local to the client workstations (Boot Image, OSD Image, Device Drivers..etc). I am not sure the BITS throttling would effect the imaging and saturation of the network. Would it? Forgive me if I seem dense, but because everything is hosted on the DS and the clients are pointing to that DS, why would it take so long and so much bandwidth?
April 27th, 2011 11:06am

If everything is distributed down to a local distribution server (you still haven't specified if the secondary site is in fact a secondary site or a distribution point. Do you know the difference? Not an insult, I didn't realize it fully myself until somebody explained how very different it is), then the package installs should be happening on the local lan. IF you can verify all packages are local then I would check with a local lan engineer and make sure your speed and duplex settings are OK on the switch. If that's not it then you are getting stuff coming across your WAN, and you have a misconfiguration somewhere. Really it will be up to you or another SCCM admin to verify your package versions match and that they are in fact installed for all of your packages. From OS to apps, to anything in between. Anything worth doing is worth doing right.
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2011 4:18pm

It is definitely a distro server. Our next step is to talk to the Network guys to see if there are any issues on their end. I want to make sure I am checking everything on the software end before I hand it off. I have compared our set up and packages to other sites and everything is the same. I have even followed some of the advice from others on this discussion and edited the BITS Threshold and enabled HTTP and HTTPS. The more and more I look at it, it looks like a network issue. I'll update you all with more as I get it. Thanks for the help!
April 27th, 2011 4:37pm

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

Other recent topics Other recent topics