BITS in Pieces

I like BITS, however the bandwidth control and resiliency comes at a cost.

There is a tiny processing overhead for each file downloaded by BITS which is OK when you are dealing with only double digit numbers of files to download, however this overhead soon mounts up and can become a real problem when you have complex package content that contains hundreds or thousands of files – the client will take a very long time to download the entire package.  You should of course resolve the root cause, which is to simply create installation packages that contain a single msi for example, but sometimes this is not an available option and you need a workaround.

Regular non-HTTP/BITS download via SMB can be utilised in these scenarios.

Create a share on your server (giving SYSTEM and Administrators full control, whilst allowing EVERYONE else Read-Only of course) and add this as a server share to your ConfigMgr site.  You could give this share an appropriate name such as SMSSMB$.  Assign this new server share the role of a Standard Distribution Point but do not enable the HTTP/HTTPS transfer options.

Create a Distribution Point Group and add the SMB shares that you have created in your environment to this group, then for any troublesome package that isn’t suited to BITS transfer distribute these only to your SMB Distribution Points.

Do be aware that this is really a workaround and not a permanent fix – you are sacrificing the resiliency of BITS and the ability to control the bandwidth usage between the client and the DP.


About madluka

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: