Hi Jorgen,
I've applied the hotfix and rebooted my SCCM servers however I am still seeing the same symptoms. This is what happens
1. Two new OS packages are created on the primary site server and in the Data Sources tab Binary Differential Replication is enabled.
2. The both packages are assigned to a new distribution point on the secondary site server.
3. I then select Update Distribution Points.
4. Under the root of the distribution point drive on the Primary Site Server there are two files created in the format "_S Meqcl.TMP" These two files as far as I can tell represent the two OS packages that I created.
5. These files first appear at 0kb the size of one file slowly increases until it reaches the size of the OS wim defined in the package.
6. The file increases in size by around 1GB per hour.
7. Once the file reaches the correct size a file appears in the same location on the secondary site server as the file is copied over to the DP.
8. At this time the second TMP file for the second package starts to increase in size as if it's only processing one package at a time.
9. The first file is then decompressed in the SMSPKGS$ folder on the DP which takes around the same time as the compression did.
10. The second package then follows the same steps as the first until both packages are installed on the DP.
The problem with this is that any package updates that happen after the initial distribution starts get put into t a queue and it can take hours before everything filters though, it even took a day in the case of one 30GB wim.
I just wondered if there was a setting I'd missed or something, maybe I shouldn't be using BITS for large packages?
Under resource manager on the Primary site server, disk access remains constant at about 1Mb per second. RAM, CPU and network usage all remain pretty consistent, I have tested R/W on the disk and it will happily transfer data many times faster than this so I know it's not a hardware limitation.
Does anyone have any more ideas?
Much appreciated.
Spencer