@McRip Thank you for your answer. I have no problem with your current arrangement. The component table allows me to know exactly which hotfix supersedes the older hotfix. This knowledge is very important to me, as I do not install every hotfix in the repository. In other words, I choose which hotfix that is relevant to be installed in my system. I can understand the labour-intensive effort spent by you, to a certain extent. Each time when such huge number of hotfixes are released, I have to manually sort out which hotfixes I want to install and it takes a long time for me to do so. I also have to exercise care in removing the older hotfixes. After all, Old Update Remover by burfadel is not applicable for my case, since I do not install all hotfixes.
I dont see any reason why you should do that and not install all hotfixes. why ? You have some super special system ?
Why that? I don't grasp that. If you have a new invented Win 7 or Server 2008 R2, let me know about it.
Well there was a problem this week, scan broke down, didnt notice until today and im kinda working all the time :s so thats why this wasnt updated yet this week... not sure if ill even find time, usually im working in the afternoon and have random stuff to do before work :s edit: i found out why scan failed... somehow cookie for EULA is not working anymore....
So is the repository up-to-date now as of 15th April or are there more update batches coming? Just want to know if it's ok to download now or wait a few days.
Thanks for the info Rick. I use a builder that can integrate updates, do wim and iso overlays. It can also create custom PE's as it has WinBuilder routine as part of the build process (optional). It's kind of a modular builder that can also use lite OS sources to build with (except for the PE part that needs full win source). But anyway, we use a (dual arch) autounattend.xml file there, which is why I had not utilized the xml method on the simple sysprepped images, so I can use it with this builder without conflict. It's just a private builder right now but it sure beats the heck out of anything I've ever come across so far, save MS' own tools of course. But as far as an integral approach to making customized images the MS methods aren't really that convenient for highly customized builds, but then again I'm not an IT pro so I'm sure a lot more is possible with those tools then I can currently achieve with them. But not in one app with a gui anyway
@RickSteele, Note that the image you create with unattend.xml with a setting of SkipRearm=1 indeed does not increase the rearm counts however the image must be installed and activated within 30 days of initial sysprep which might not be a good idea. it is better to sysprep first time with SkipRearm=1 and then sysprep again with SkipRearm=0. This way the pending updates problem will be solved and you have used only 1 rearm instead of 2. Also I tried sysprep->reboot first before generalizing and it did not work for me. I was not able to integrate all updates into my final images I kept getting lots of error 5 access denied errors however syspreping in the way I described solved this problem and slmgr /dlv showed that I have 2 rearms left so I am happy with my sysprep.
Did you do Sysprep: OOBE -> Generalize -> Reboot, though? This is what I did and it resulted in all updates integrating correctly. As I indicated, doing it this way is considered a full sysprep run because it takes off one rearm count. So when you do both the above-mentioned OOBE-generalize-Reboot, and then do your final OOBE-generalize-Quit, this accounts for 2 rearm counts. This is why I used that delwpa.bat method after the generalize-Reboot, so that only one rearm count gets taken off during generalize-Quit only, leaving one with 4 rearm counts on the final sysprepped image.