Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1052
  • Last Modified:

SCCM 2007R3 SW Distribution Delay

I'm currently testing SCCM 2007 R3 on Win 2003 SP2. I'm concerned about the delay for  software distribution to local machines within the same subnet of the Site Server. A test with small app like Winrar took about 30 minutes before being installed to the client PC. I understand BITS is used as Distribution mechanism , but still this is unacceptable delay! Am I missing something here ?
0
eyad77
Asked:
eyad77
  • 2
1 Solution
 
malkaj01Commented:
By what you've described I suppose you've set the advertisement to As soon as possible.

BITS transfer throttling is only used when the boundary has been assigned as a Slow connections from within the site properties. If the subnet has been configured as a Fast boundary SMB transfers will work at your normal network speeds.

Remember that software distribution has to go through many different internal processes from the moment you create the advertisement for you package until it actually starts pushing the install to the clients. Including SQL updates to your SCCM database and push engine processing.

At the beginning being patient with SCCM is essential, specially in lab environments where you only have a few clients and want everything done "on the fly". Considering the scalability of SCCM and the time it will save you in the future, a 30 minute delay for pushing WinRAR to 1000 clients won't seem that bad!

This TechNet overview will give you a good idea of the whole process:
http://technet.microsoft.com/en-us/library/bb632532.aspx
0
 
eyad77Author Commented:
Thanks malkaj01. Apparently I did not use the "Mandatory Assignment" option with As Soon as possible. Doing this along side using "SCCM Console Extensions" by Dan Ireland to trigger client "Machine Policy Retrieval Cycle" did the installation as fast as expected.
my question though would be, If I use a branch distribution point to advertise the package to machines within the same branch , will it automatically SMB despite being set on the main distribution point on the site server as "Slow Connection" ?
0
 
malkaj01Commented:
No, they will not use SMB, BITS will continue to their transfer method. Once you've setup the BDP you can go ahead and set the BDP's boundary as Fast Connection in order to enable SMB.

To ensure that clients from your BDP don't fallback to your site's distribution point you could configure your Site to use protected boundaries guarantee that clients from the branch site never download from your site system over a slow WAN link for example.

Here is an article on how to set this up:
http://technet.microsoft.com/en-us/library/bb932133.aspx

0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now