Distributing wim image
We have a wim image for Windows XP SP3 and this is referenced through the operating system images node in the SCCM console. When we look at the properties for the wim image and browse for the file, we can select it and the package ID is correctly
displayed as the relevant wim image in the data source location. Also within this location is another version of the wim image with a slightly lower file size and a different date - this was created previously by someone else who has since left.
The problem is that when we try and update some distribution points with this image, the incorrect version is copied over (the other copy with a lower file size) - we have checked the smspkgd$ folder on the distribution points and can confirm that the correct
package ID for the image we want to distrribute is showing, although the file size and date show the wrong version of the wim file. The source version is showing as 1 and this is the same at all distribution points within the site. When we distribute
the image to other sites, the correct version is copied across. We cannot determine why the incorrect (lower file size version) is copied at certain sites and why the correct one is copied to others. The incorrect wim image is not even referenced
in the operating system images node of the console!!!
We have also tried removing the incorrect version from the DP and adding it again from scratch, but this results in the same. At this point in time, we are strongly considering just manually copying the image from another DP to this one and getting
the right version copied. Would this present any problems gooing forward if we cannot resolve the issue?
August 29th, 2011 5:42am
as you are having the issue only on some sites, are those sites using antivirus (or network caching software) which could be interfering with your dp's ?
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
August 29th, 2011 8:35am
Yes, manually copying items into the DP folders will cause issues. Have you reviewed the distmgr.log on the primary as well as the sites having issues?
What happens when you "Update" the package?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
August 29th, 2011 9:58am
Well all the site servers have been built identically so even though there may be antivirus software, it will be the same configuration at all sites and for the main part the correct wim image is distributed to the DP's - with the exception of just a couple
where the incorrect file is copied across.
Updating the distribution point at the sites results in the same incorrect wim image being redistributed and not the correct one with the package ID referenced with the SCCM console (operating system images). I will look at the distmgr.log file on
the primary and secondary sites and see what is listed. We just cannot understand why the incorrect file is being copied when it is not even within SCCM - could this be a historical thing if it was previously distributed at some sites?
Free Windows Admin Tool Kit Click here and download it now
August 29th, 2011 2:43pm
try deleting the package, remove it from the dps' verify it's gone, then add it again, then update the dps' is it working right then ?
My step by step
SCCM Guides
I'm on Twitter > ncbrady
August 29th, 2011 5:21pm
Well we tried deleting the package and removing it from the DP's, then adding it back and updating the DP's but the result is the same - the wrong image still gets distubuted. The only other thing we can think of is Binary Differential Replication
being enabled on the OS image - would disabling this make any difference in the wim file that is being copied to DP's?
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2011 5:04pm
Well we tried deleting the package and removing it from the DP's, then adding it back and updating the DP's but the result is the same - the wrong image still gets distubuted. The only other thing we can think of is Binary Differential Replication
being enabled on the OS image - would disabling this make any difference in the wim file that is being copied to DP's?
August 30th, 2011 5:04pm
that's worthwhile investigating
Binary Differential Replication, sometimes known as "delta replication," is used by Configuration Manager 2007 to update package source files with a minimum of additional
network traffic.
When Configuration Manager 2007 updates the source files for a package, and the source files have already been distributed, it sends the parts of the package that have changed since the last time the package was sent (originally, as an update, or as
a refresh). This minimizes the network traffic between sites, especially when the package is large and the changes are relatively small. A file is considered to be changed if it has been renamed, moved, or its contents have changed.
The originating site keeps the differences between the current version of a package and the previous five versions. If a child site or distribution point has one of the previous five versions of the package, the originating site will send the appropriate
changes to that site. If the child site has an older version of the package, the originating site will send the entire package.
If the originating site sends the changed files for a package but the receiving site no longer has the package, or the package has been altered at that site, the receiving site will send a status message to the originating site reporting the problem.
so, can you check your status messages to see if any problem is reported relating to the above ?
if that doesnt help then talk to your network team, see what if anything is different between those two sites and the others network wise...
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2011 5:25pm
that's worthwhile investigating
Binary Differential Replication, sometimes known as "delta replication," is used by Configuration Manager 2007 to update package source files with a minimum of additional
network traffic.
When Configuration Manager 2007 updates the source files for a package, and the source files have already been distributed, it sends the parts of the package that have changed since the last time the package was sent (originally, as an update, or as
a refresh). This minimizes the network traffic between sites, especially when the package is large and the changes are relatively small. A file is considered to be changed if it has been renamed, moved, or its contents have changed.
The originating site keeps the differences between the current version of a package and the previous five versions. If a child site or distribution point has one of the previous five versions of the package, the originating site will send the appropriate
changes to that site. If the child site has an older version of the package, the originating site will send the entire package.
If the originating site sends the changed files for a package but the receiving site no longer has the package, or the package has been altered at that site, the receiving site will send a status message to the originating site reporting the problem.
so, can you check your status messages to see if any problem is reported relating to the above ?
if that doesnt help then talk to your network team, see what if anything is different between those two sites and the others network wise...
My step by step
SCCM Guides
I'm on Twitter > ncbrady
August 30th, 2011 5:25pm
that's worthwhile investigating
Binary Differential Replication, sometimes known as "delta replication," is used by Configuration Manager 2007 to update package source files with a minimum of additional
network traffic.
When Configuration Manager 2007 updates the source files for a package, and the source files have already been distributed, it sends the parts of the package that have changed since the last time the package was sent (originally, as an update, or as
a refresh). This minimizes the network traffic between sites, especially when the package is large and the changes are relatively small. A file is considered to be changed if it has been renamed, moved, or its contents have changed.
The originating site keeps the differences between the current version of a package and the previous five versions. If a child site or distribution point has one of the previous five versions of the package, the originating site will send the appropriate
changes to that site. If the child site has an older version of the package, the originating site will send the entire package.
If the originating site sends the changed files for a package but the receiving site no longer has the package, or the package has been altered at that site, the receiving site will send a status message to the originating site reporting the problem.
so, can you check your status messages to see if any problem is reported relating to the above ?
if that doesnt help then talk to your network team, see what if anything is different between those two sites and the others network wise...
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2011 5:25pm
Disabling BDR did the trick and the correct image is now distributed
Thanks for all the replies guys.
September 1st, 2011 2:12pm
just to confirm, did you check the status messages, did they reveal anything interesting
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2011 5:05pm