Yeah, it works great- the install takes a while since so much is processed (Office, then SP1, then post-SP1) but it's a nice clean install afterwards. I called it slipstreaming but technically, it's not true slipstreaming (like could be done in Office 2003). But it does make it easy to have a fully updated initial install.
I downloaded updates using WUD (76 Updates) and i moved 74 of them to a folder and then used RT 7 Lite (64-Bit) to add them to the windows 7 install media, and then i used a script to convert it to a VHD and make it sysprepped but after i ran it in Virtualbox i see there is some updates that shows up in Windows Update but i have added those updates to the install with RT 7 Lite (64-Bit). Does anyone know why not all updates that i added are integrated into the install media? I am doing something wrong?
I dont know how it works with RT7lite, but I always use Windows 7 Toolkit with LDR/QFE mode and never had a problem with updates showing in WU despite of integration.
Thanks! Will try with W7 toolkit . Edit: It works But there is still updates showing in Windows Update because WUD did not download these.. i noticed that SoLoR has some of them, but even SoLoR does not have them all... I am wondering also, is it better to use SoLoR then WUD, i see solor has over 300 updates but im not sure what it is all for cuz WUD has 76 updates only???
Yes, I've noticed that and it is annoying. I don't know of a fix to prevent it from installing. But at least it can be uninstalled. If you run the Office setup again after everything is installed you can uncheck the Sharepoint Workspace feature and it will uninstall (which prevents Grooveex.dll from constantly being loaded). But you're right- it shouldn't install in the first place if not selected. And I still can't remove the option for Sharepoint Foundation Support under the Office Tools section- it always re-enables itself after uninstalling. MS should fix these issues. Good tip on adding numbers to the filenames of the .msp's for install sequence.
Adding the number makes sense, it hopefully eliminates what I was talking about earlier with the install order issue (if there is actually an issue!)
Just receive an update: KB2633171 KB2644615 KB2639308 not sure if this is new but can't find on the Repo... anybody has a link to KB2608658(x86)...
Yes for me 3 updates are showing in WU, because they are not in SoLoR´s repository. Anyway, WU dont offer all updates that microsoft release, because lot of them are made on requests, for companies etc., and SoLoR have them all - Included the ones WUD downloads for you, minus the 3 showing in WU for me (still dont know why). I used WU for a long time, but then I was searching for something more, and SoLoR is offering it, so now Im using only his repository You cant go wrong with it. Windows runs great with all those updates. Give it a try, download the latest 19.march zip, and integrate all updates with ldr/qfe mode. If u use that mode, dont integrate LDR Placeholders then. And one more thing, there is a folder called "Not integrateable to offline image", which contains 2 updates that u cant integrate. You can make them silent installs in W7Toolkit, but better just after you install Windows, immediately install the first one, restart, and then the second one.
Currently all hotfixes that shows on WU after applying pack, can be safely hidden because they are superseeded.
Most likely for now... there may be a couple right before it is finalised that don't make it, as appeared to be the case with SP1 (but these were released later for SP1 I believe). Be interesting to see where they are at in terms of intended release date, whether it is in internal beta etc. The main reason why there hasn't been much info on it is because SP2 has been overshadowed greatly by Windows 8.
I've been looking for that script for months, it's no where to be found. This bug is really annoying.
Sadly it does not work, SharePoint Workspace get installed anyway. The only thing that works is to install Office 2010 without SP1 slipstreamed. Then you must install SP1 via a chain command, WSUS or a script of your own and finally all the hotfixes. This will works but your deployment time will clearly increase.