Sccm update distribution point not updating
Information going site to site does so based on priority.
Before we get into the next step of the solution, you must first understand what an SCCM distribution point is. If you look at the file on any of your SCCM clients, you’ll see a lot of URLs that look like the following: What your client is basically doing is grabbing the files from these URLs and storing them into your local cache directory underneath the package ID. Since we saw an error in our bitsadmin /list /allusers, we need to find out exactly what that error is.
This sender is typically used in scenarios where large amounts of data need to be transferred and the WAN environment is insufficient to handle the load.
Further discussion of the courier sender is beyond the scope of this post.
However when I looked at my cache folder, I saw that only a couple of MB of data was downloaded and it never increased in size. Unfortunately there’s no good logging for BITS without doing some nasty logmon stuff.
The good news is that BITSAdmin is a great utility (at least for now, according to BITSAdmin on a Windows 7 box they reference new BITS Related powershell cmdlets which I didn’t find all that particularly useful).
I’ve only seen another type of sender in use once years ago.