What's the recommended order of offline integration? general > additional > security > hotfixes > ie11 ?
I dont think order matters much. You cant get everything right on first pass anyway. I suggest two passes. On first pass possible prerequisites are integrated but certain hotfixes will surely fail. On second pass any missed ones should also integrate since prerequisites should be in place. Just make sure to do a unmount and commit between passes to solidify changes.
That's interesting to know, all along, -each time there's a new update list-... i would grab a clean vanilla sp1 install.wim and just integrate them following numerical order.. with ie11 last. so are you strongly suggesting that i now repeat the exact same thing twice? Would anyone like to share a second opinion on this?
This is my order.... Code: Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp00.WUClient" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp01.General" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp02.Security" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp03.Hotfix" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp04.Platform" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp05.PlatformUpdates" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp06.WindowsMediaCenter" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp07.WinHelp" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp08.NFS" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp09.WAT" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp010.IE11Prerequisites" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp011.IE11CABs" Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp012.IE11Updates
For me All hotfixes (LDR) Windows6.1-KB2685811-x64 and Windows6.1-KB2685813-x64 (GDR) IE cabs IE Updates
This is exactly why sysprep is becoming the way to go for Windows 7. Less problems, you can use WU, even, and no pending updates, etc. Offline integration is inferior to me now, for Windows 7 and its ton of updates especially.
My script generates something like this Code: /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2545698-x64.cab\update.mum" /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2545698-x64.cab\update-bf.mum" /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2547666-x64.cab\update.mum" /packagepath:"Z:\solor\tmp\_x_\22Windows6.1-KB2547666-x64.cab\update-bf.mum" and so on... it's very big Which way do you recommend? to integrate from KB9x to KB2x ALL update-bf.mum that exist and then update.mum starting from KB9 to 2x again?? or to integrate update.mum & update-bf.mum for each KB before moving on to the next? I may have been doing this wrong all along oh dear. What I currently do is integrate update.mum first and then update-bf.mum (if existant) from kb9x to kb2x sequentially.
Well, after further check, 2492386 has two non-superseded components: msimain.sdb, pcamain.sdb (both can be found in Windows\AppPatch) so i take this update as not superseded It's a regular update, why would it generate issue? i can verify that it gets integrated without an issue here nevertheless, i will remove it from General category (it's already found in RDC 8.1 Prerequisites )
Yeah im using a sysprepped image as a base image with NET 4.5 integrated (4.5.1 was not out at that time). That way i can integreate WPF 4.0 without the installation failing ( i need Powershell v3). Atleast sysprep works on Win7. It fails utterly and miserably on Win8 even with slightest changes.
I'm rewriting my offline integration script.... Need some advice on this LDR and GDR part Looking at the script generated by KUC with force LDR.. it integrates all cabs first and then integrates all update-bf's The old solor script I've got integrates update-bf if it exists, otherwise update.mum only I've no basis for selecting the optimal method of offline integration. How does this really work? Say I integrate all GDR first (dism the cabs) and then LDR later (dism the update-bf) the LDR will override the out of date GDR components? What if I integrate all LDR first, and then GDR later, if LDR has newer components, will GDR override them?
If you select "forced installation of LDR.." and "only install the LDR..", KUC will generate scripts to integrate normal updates as cabs and ldr updates as update-bf.mum the old solor script integrates LDR packages separately one by one which takes more time whereas KUC integrate 10 LDR packages together (i think) No components will be overrided, both GDR and LDR co-exist together
RicaNeaga some question about the not integratable folder , i have test the KB2685811 & KB2685813 integrated to offline with out any problem issue (test Windows 7 PRO , Home Premium , Home Basic , Starter , just integrated to GDR only , not for LDR mode) and KB2862330-v2 also integrated to offline with out any problem , just the KB2895729-v2 need to be non-integratable , may i ask if the KB2685811 , KB2685813 & KB2862330-v2 integrated with offline have any error ?? or have any stuff integrated the three update have any error issue ?
some info already mentioned in the above post, like... About 2862330, it has Usbforcereboot.exe inside, so I thought it was the best idea for that to run right after (at the same time as) the other USB-related hotfix (2895729-v2) is installed. Very likely, when integrated, Usbforcereboot.exe has no effect whatsoever, it's just another .exe copied into its appropriate folder