The integration tool is coming along ok I decided to go full on with it, meaning: - If you have already mounted an image it will integrate to that otherwise, - If you have a dvd or iso image it will ask you where you would like to copy the files to (or use the default location) and then use robocopy to copy the files to that location - If you have it on the hard drive already you can mount and integrate to that instead, otherwise it will mount from the location you have copied to. The files needed to be copied so you can commit the changes - You can select the index you wish to integrate to So, all of the above has been done, now its time for the integrating part. i've already modified the installer to use dism instead of pkgmgr, I think my earlier suggestion of it being faster was anomalous, since pkgmgr/wusa calls dism anyway I do have a couple of questions though for those that have integrated in the past: - What updates have caused issues with integrating? besides kb943790 and I also believe KB958559? - If successful integrating the above two (and any other troublesome updates) how do you go about it? It isn't any trouble skipping over the above two, but I would want to make the integration process as complete as possible. Also are updates KB2023591, KB2495879. and KB2521168 just as simple as extracting and copying over manually? Whats left to do: - Resolving the above, if possible! - Addition of driverr integrating. If this is added, I would only recommend things like chipset drivers and AHCI drivers etc, things which may be beneficial for the install process. Display drivers could be beneficial, but would also require resinstalling once installation has completed as there are elements not contained in the actual drivers themselves. With AMD for example, there's OpenCL drivers which are separate (installed by a .msi), AVIVO, WMVDecoder etc. - Once integrating has completed asking whether you would like to create an iso. This is the only part of the whole process for any part of the installer that will require an external program. I intend to use oscdimg for this, which if it isn't found in the installer location will ask you the location... (I'd probably add the question at the beginning). So, has anyone got the latest oscdimg? there seems to be various versions floating around, but I would only want to include (or more correctly, make available as a separate download) the absolute latest. Thanks!
I have no problem integrating KB943790, never have; and don't use Virtual PC-KB958559 (I create a VHD file for sysprep etc. and run nothing I require XP anything for. Actually, I have PCA completely disabled in Group Policy.) First, I disable any features and remove any packages offline using DISM.exe in system32 (7601 version, although 7600 works just as well). Secondly, I integrate the following first in the order listed before anything else (Windows 7 Ultimate SP 1 integrated by M$): Windows6.1-KB943790-x64 Windows6.1-KB969168-x64 Windows6.1-KB974405-x64 Windows6.1-KB2484031-x64 Windows6.1-KB2488113-x64 Windows6.1-KB2159360-v4-x64 (hotfix for KB974405) Windows6.1-KB982861-x64 (IE9) When preparing the image for sysprep I stop here, save the changes, create the cat file using imageX, install to VHD, go into sysprep, customize the GUI, complete all Group Policy edits and capture the result as my base wim Then I integrate all of the rest of the repo' including the LDR placeholders all at once Lastly the drivers I install all runtimes via first logon command from the answer file. ..to my knowledge latest oscdimg.exe=v.2.55.0.1010, 7/14/2009 available within WAIK; OPK has the same version. I copy oscdimg.exe to system32. Because all of the repo' is now exclusively post SP1 and IE 9, the above is my default and works well every time. I capture a base wim because of all the time I spend in Group Policy. I always sysprep my base wim. I only install any upates via the extracted cab files, never using the msu. The above method also worked well when I used the SP 0 wim and installed SP 1 live. The only exception is Windows6.1-KB2484031-x64 is integrated along with the rest of the repo'. The reason I integrate this the way I do is to run the "KB2484031 USB driver Fix" in sysprep so that all is normalized in the base wim. Anyways, hope this helps ya'
kb943790 is not a problem when integrating via MUM, only KB958559 (VPC) The trick with these problem updates is simply not to extract them, just point /packagepath to the CAB/MSU As for OSCDIMG what command are you using to build the ISO?
"oscdimg.exe" -u2 -m -o -l<iso name> -b"<path to etfsboot.com>" -yo"<path to bootorder.txt>" "<path to installation files folder>" "<path to iso>" ...for me it looks like this: "oscdimg.exe" -u2 -m -o -lGRMCULXFREO_EN_DVD -b"D:\DISM_Folders\DISM_Temp\etfsboot.com" -yo"D:\DISM_Folders\DISM_Temp\bootorder.txt" "D:\GRMCULXFREO_EN" "C:\GRMCULXFREO_EN_DVD.iso"
Well, I have worked out that for a successful integration you should first integrate with a packagepath set to the .cab file, then you can successfully integrate the update-bf.mum files. Not sure why with the online image you can directly integrate the mum files, but with an offline image you have to (seemingly) integrate the cab file first then the mums?... Any thoughts on that?!
Not sure why you came up with that conclusion, I have no problem integrating using MUM (only VPC you point to the full CAB)
So you have found a difference with the 7601 version of dism? when I mentioned this earlier it was suggested the difference was only that it was built later!...
Well, thats what I originally thought, however what I get without doing the cab files first is error 0x800f081f Also interestingly enough, DISM claims the image version is 6.1.7600.16385 The image was the one downloaded from the Windows 7 pages on here, supposedly the genuine SP1 image. The setup files and files in the image all point it to being 6.1.7601.17514, what are others getting?
None that I can see; I just feel that if the newer file is available, and you came up with such an easy way to overwrite the older files that don't get updated with SP1 install, why not use them....ya' know
...same thing here, and they are the genuine SP1 integrated by M$ image-at least according to any hashes I have viewed; I think somehow M$ retains the original version for some reason...perhaps for compatability-present and future?.....I don't know and have experienced no adverse affects due to this that I know of.
I just simply point to the cab files-extracted from the msu's and Bob's your uncle. for a live OS I use: DISM /Online /Add-Package /PackagePath:\Windows6.1-UpdatePack-x64.SP1\Slipstream ....of course everyone's paths will differ; "Slipstream" is the folder where I keep the cabs extracted from the msu's in SoLoR's repo.
That is a path error, cant find the file specified And you can ignore what image version dism is reporting
ah ok! thats good to know, I was a little worried there for a second that the image version was actually correct and the iso I had was wrong lol. The issue with integrating the cab package and the mum files directly is the issue of GDR and LDR. The purpose of the integrator is to also force integrate LDR versions so they are utilised instead of their GDR counterparts in all cases, not just when dism feels its 'necessary' . I can still do this, its not any more hassle to first integrate the cab file then explicitly integrate the contained update-bf.mum file. it just would be nice to know whether this is a common issue or just one I'm having!
Ah ok, is this just an error that I'm getting, or is it common? if common, is there a 'workaround'? like I said, no hassle doing the cab file first, but to me it seems like it shouldn't need to be done!
Something may be wrong with your script, manually extract and integrate the MUM file and you should see no error
I haven't included it in the script yet, I wanted to sort everything out first before doing that The command I use to integrate the mum files directly is: dism /image:imagelocation /add-package /package-path:location of extracted cab file\update.mum (the stuff highlighted are specific locations) That fails. If I set the package-path to the cab file first, then enter the same as above (even by pressing the up key from the command prompt so its quite literally the same command) it works! for both the update.mum file and update-bf.mum (which needs to be explicitly integrated for force LDR integration) files.
/packagepath is the correct switch, there is no "-" in this second switch, only the the first /add-package Code: dism /image:imagelocation /add-package /packagepath:location_of_extracted_cab_file\update.mum /packagepath:etc
Oops, that was my mistake in the explanation, I had typed packagepath in the command prompt. The process fails aroound half way through, no matter what I try :S unless I integrate the cab first... I should point out that this is on a completely fresh unintegrated & untouched SP1 image.
Are you talking about 1 update (VPC) or all updates fail? The problem has got to be the script (check your log files), manually extract and integrate using MUM and you will see there is no problem Or use your old script and just change pkgmgr with dism commands with a path to the mounted folder and you will also see no problems