Windows 32bit Family XP RTM - 5.1.2600
XP SP1a - 1106
XP SP2 - 2180
Server 2003 RTM - 5.2.3790
Server 2003 SP1 - 1830
Server 2003 SP2 - 3959
Vista RTM - 6000.16386
Server 2008 Beta 3 - 6001.16510
Windows 64bit Family XP 64bit RTM - 5.2.3790.1830
XP 64bit SP2 - 3959
Server 2003 64bit RTM - 5.2.3790.1830
Server 2003 64bit SP2 - 3959
Vista 64bit RTM - 6000.16386
Server 2008 64bit Beta 3 - 6001.16510
Update 12:vLite now includes direct Vista SP1 integration support however the recommended option is to continue using the Reverse Integration method due to the fact that MS had something against direct Slipstreaming and further testing will be required.
Update 10: Additional/new info is available here and Microsoft's Deployment Guide for SP1 is available here.
Update 1: Microsoft has confirmed that there will no way to directly slipstream SP1. Of course, that doesn't mean it can't be done. The method outlined below will still work and direct integration is also now possible (see Update 6). Read more for further updates.
Update 6: Microsoft now seem to be claiming that Offline Installations (which does not include the method outlined below) will corrupt the Vista image: "Offline installation of Windows Vista SP1, or of any of the update packages included in the service pack, is not supported. Offline installation will cause the Windows image to be corrupted" and that slipstreaming will not be possible until SP2.
Update 7: It appears that SP1 integration has been dropped as a planned feature for vLite for the moment leaving the Reverse Integration guide as the only way to integrate SP1
As we reported a few days ago, the latest build of Vista SP1 released to testers (6001.16633) is in the EXE standalone update format. Many of you will no doubt be wondering as to how exactly the bits can be integrated into a Vista RTM ISO if at all possible.
There's some good news and there's also some bad news.
First of all, it must be noted that we are still unsure if the SP1 update will remain in the EXE format and that anything noted below is subject to change. The primary reason being Microsoft's documentation for Vista Service Packs state that they will be provided in the MSU format whereas it is currently being offered to testers in the EXE format. (This does not make much of a difference in regards to integration if it were to change)
(Update 3: Since the first beta preview of Vista SP1 released to testers was also in the EXE format, we can mostly say for certain now that the final version of the standalone SP1 will be delivered in the same format. As noted previously, this does not make much of a difference in regards to integration.)
Unlike previous service pack updates for older Windows OSs, Microsoft does not provide any switches in the EXE to allow for simple integration. Part of the problem has to do with the completely different format that the Vista Setup DVD uses where each edition of Vista is a separate index in the install.wim and that each index needs to be separately updated. While Microsoft could implement a switch to allow the user to select which index to update or a switch to update all the indexes, it will turn out to be a very lengthy and time-consuming process as we are talking about gigabytes of files that need to be updated/replaced, saved and recompressed. Unfortunately, Vista also does not implement an Updates folder unlike Office 2007 where one could drop all the latest updates in the folder in the ISO and setup would automatically pick them up and install them.
The format of Vista SP1 as an update is broken up into 5 CAB files which the Vista SP1 installer installs on top of Vista RTM using a single EXE installer (spinstall.exe). For those of you that have been following how to integrate Hotfixes via our guide or have used vLite, there's reason to rejoice as both methods support CAB integration. Unfortunately, since the currently available tools from the Windows Automated Installation Kit (WAIK) are not designed for SP1, one runs into a few issues. Namely, the main SP1 CAB, windows6.0-kb936330-X86.cab cannot be integrated with the tools from the RTM version of WAIK (peimg and pkgmgr error out) nor can it be integrated with vLite (yet). The updated WAIK tools from Beta 3 of Server 2008 do not work either.(Update 4: Newer WAIK tools have been released to testers with the SP1 beta.) Some good news out all this is that the other smaller supplementary CAB files have no issues being integrated with peimg/pkgmgr since they are using the same old internal servicing stack being used with current Hotfixes.
Until Microsoft release newer tools, that option should be avoided unless a workaround is found for the main SP1 CAB.
(Update 2: For more info, a forum discussion regarding the use of an updated pkgmgr is available here. Levien has added experimental SP1 integration support to his Vista Update Integrator found here (Update 5: And has removed it for some unknown reason). Nuhi is also working on adding SP1 integration support to vLite. I've personally manually tried Levien's method (which he should be publishing sometime later) by creating my own batch files to do the job and found that it works... most of the time. I have only personally tested this method on Build 16633 so if MS's claim that Offline Installation will corrupt a Vista image is valid, it will most likely start with Beta 1.)
Long story short, if you want to integrate Vista SP1 into a Vista RTM DVD, the only option for the moment one of the options (seems we're flip-flopping on this one with every update) is to reverse integrate it:
1. Install Vista RTM to a secondary partition (not the main boot partition). The primary reason for this is one doesn't want all the boot associated files of that computer related to BCD and boot.ini being part of the final image. (Update 8a (Optional?): Microsoft also suggest running PostReflect.exe, a Vista SP1 tool, against the *offline* image of Vista SP1 (Note: Offline in this case = not booted/running the Vista SP1 install) after sysprepping (Steps 5-6) the Vista install to "to reflect all boot critical device drivers out of the driver store". Personally, I've never had to do this and neither I nor anyone else in the vLite forums seem to have run into any issues by not doing this.)
2. Once in the Out of Box Experience (OOBE) after setup, type Ctrl-Shift-F3 to enter Audit mode. In case you're wondering what/where OOBE is, it is the part after setup where the user is setting up his/her username, password etc.
3. The system will then reboot into Audit mode and a Sysprep window will pop up. Do not close the Sysprep window.
4. Run the Vista SP1 installer and let it do its thing.
5. After the SP1 setup is complete, you'll find yourself back at the main Vista desktop with the Sysprep window open and SP1 will be installed and ready to go. (Update 8b (Optional/Recommended): Microsoft has included a new tool with SP1 called Vsp1cln.exe which can be used to remove older versions of components that have been upgraded to new versions in SP1 to save space. Once SP1 is installed, simply run Vsp1cln.exe via Winkey+R (Run command) or via the command prompt). Afterwards, from the Sysprep selection window, select OOBE, Generalize, and to Shut Down the system.
6. Boot the system into a WinPE disk or another OS install (ie. XP), do NOT boot back into the new Vista SP1 install, and run the following imagex command (imagex can be found in WAIK):
(Update 9: Note that GimageX (a gui front-end for imagex) should NOT be used for the capture process. Users have been reporting incorrect XML info when capturing the Vista install using GimageX so just use the regular imagex via the command line.)
imagex /compress maximum /flags "Business" /capture d: c:\install.wim "Windows Vista Business"
where d: is the drive Vista is installed on and c:\install.wim is the location to store the new install.wim. Replace "Business" with whatever edition of Vista you installed and replace the drive letters (d: and c:\install.wim) with your own.
(Update 11: Also note that the "Business" specified after /flags should be replaced with one of the following if another version of Vista/S2008 is being captured:
The emphasis being there should be no space between the words.)
7. Once the image has been built, replace the old install.wim in the Vista RTM ISO in \Sources\ with the newly created install.wim using a registered version of UltraISO (Version 8.0 or higher). Save the ISO and you're done.
You can also rebuild the ISO using vLite by extracting the contents of the Vista RTM ISO to a temporary directory, replacing the install.wim and using vLite's Vista Burning/ISO creation features. One can also use vLite to remove unwanted features in Vista SP1.
It has to be noted that the above method is for a single edition of Vista. If one wanted to integrate SP1 into all the editions of Vista, they would have to follow Steps 1-5 for each edition and use the imagex /append function to build an install.wim that contains all the editions of Vista.
Posted by sivaji (3 posts) on Thursday, Mar 27, 2008, 5:47 pm
(1 replies to this Comment) | - IP: Hidden
Here is the tool called "Vista Update Integrator" beta 3. I tested it with x86 32 bit all five major verson to integrate Service Pack 1. Takes some time but integrate flawlessly. It made with dot net framework. I do not have 64 bit system. Please somebody test it on 64 bit system.
Interface is like "vLite" Download Here "NO VIRUS dear"
Posted by sivaji (3 posts) on Friday, Mar 28, 2008, 5:41 am
- IP: Hidden
To "austinaut"
The time taken by this software about 1.5 hors on Pentium D 2.8 Ghz/512 MB DDR/Vista system. I rebuild the complete image ( all five major version Ultimate, Home Basic, Home Premium, Business, Starter).
Welcome to WinBeta.Org Betas - News - Reviews. 
1
4
3
1
0
0
Sponsored Links 
News Source: 
