aarnold@sd68.bc.ca

Not sure how to say this exactly but it seems that when a package gets update the Task Sequence is not getting the new version number so for example the package is AD100001:1 in the Task Sequence and it the package gets updated at some point and it now version 2. The task sequence seems to still be looking for version 1 of that package. If I open up the package and change something in it it seem to fix this error until the next package gets changed. IS there something I can do to fix this?

sounds like multi-cast isn't work in your network, so you are doing unicast and flooding the network. So when you try and get the third the network just drops the first.

I was looking at your SCCM 2012 ADR updates page. But there is one thing that I couldn't find how to exclude say Internet Explorer 9,10,11, etc. As we are stuck in my org at the IE 8. So I want the updates for IE8 and if you have IE9 10 or even 11 (When released) but I don't want Windows 7 Machines or Windows 8 Machines to update to the newest browser. How would I do this with your example?

I'm getting this now on all my packages even ones that worked prier to windows updates. I'm thinking with update did something but am unsure. It first blew up my iis which I fixed with a restore of the IIS files (Crypto files and xml files).