CelticWhisper

Urrrgg, not looking forward to that if it's more of the same for Office.

I'm trying to get our corporate Office 2010 installer fully patched via dropping .MSP files in the \Updates folder and am running into a peculiar problem - updates seem to conflict with each other and undo one another's application. For example, if I drop SP2's extracted .MSP files in the \Updates folder and install Office, I can then run Windows Update and get a list of patches for Office 2010 that doesn't include SP2. Great, makes sense, I pre-installed it via the Updates folder. However, when I drop the MSP files from another patch into the folder, even if I rename them so as not to overwrite like-named files from the SP2 application, when I run Windows Update it shows SP2 as an available installation. It's a reduced filesize, but it's still there. This suggests to me that some component of SP2 is no longer installing once other updates are added to the folder. Complicating matters further, re-integrating SP2 then undoes some of the other patches and they show up in the WU update list. Has anyone had success in getting a fully-patched installation of Office made using offline patching, such that a "Check for Updates" operation will yield no missing patches? How did you do it?

I'm sorry to resurrect such an old thread, I know it's terrible form, but I'm fighting with this very issue now. I've tried running setup.exe /a (as well as /A, with the uppercase a) and I get a "Preparing to install Office 2000" window, which stays up for a few minutes and then closes with a "Setup completed successfully" window. I can see no evidence of it creating another directory on the HDD to serve as an administrative install point and I am never prompted for any options. I did try running the Custom Install Wizard once before and there's an MST file in the directory. Do I need to delete this? Is there anything else I need to do in order to revert to a "clean" source? This is running from a folder "O2KSB" which contains the files on the Office 2000 Small Business install CD, as well as the install files for SP2 and SP3. I am extremely frustrated, I will admit that. I am not thinking clearly. I have been interrupted here at the office 12 times since I started trying to figure this out so it's a mess in my head. What am I doing wrong? Thank you and, again, I apologize for bringing back such an ancient thread. I figured it was better than spamming a new one.

This is essentially a follow-up to my "Dot Net Demystified" thread. I'm trying to get WMP11 and the WindowsXP-WindowsMedia-KBabc123 updates integrated into my install source. I found Boooggy's WMP11 slipstreamer and it seems to work well. My question is this: If I integrate WMP11 with this tool, as future updates are released can I just run them with the /integrate switch pointed to C:\XPCD or do I always have to use the WMP11 slipstreamer for all WMP11 updates?

Will check those out as soon as this test install is done. Thank you so much for this.

I've been doing unattended-install work for a few years now, focusing mostly on automation and driver integration, but I've hit the point where I think I've got that stuff down to a science. The .NET framework, though, vexes me more and more with each passing install. I've searched for information on this forum and elsewhere about automating the install of .NET framework components and while I know the information is available, it's not terribly approachable. A lot of the discussions are at a very low level, involving people who've had sleeves rolled up and hands dirty for a long time and are using terms quite alien to me. Other times I'll find one suggestion, see a reply that it didn't work, and see no further replies on how to continue forward. I've heard of RyanVM Integrators, extracting .NET installers, the different stages (T-13, cmdlines.txt, /integrate switches) to run them at, but a lot of this seems either contradictory, inconsistent in results, or incomplete (e.g. I use this installer at T-13...'kay, but do I extract it or not? If so, what do I run? The EXE? The MSI? What?) and it's all starting to run together in my head. I guess what I'm asking is this: Is there a recommended starting point for taming .NET installers? The ones I'm most concerned with automating are version 2.0 because nLite requires it, the stonking huge 3.5 Family Update because it takes forgoddamnever to install and that gets tiring over multiple test-runs, and 4.0 because...latest and greatest? I know from reading that these are not the easiest things in the world to install and it seems a lot of people are fighting with them. If it's just the nature of the beast that they're not intuitive at all to install, I completely respect that and don't expect special treatment. My concern, though, is that there IS an easy solution out there and I've just been missing it. TL;DR Version: Where can I go for simple, explicit, straightforward instructions on how to integrate as many versions as possible of the .NET framework and its updates? I'm drowning in information overload and don't want to chase tried-but-disproved solutions. Thanks in advance for any help you can give. You'll have saved my sanity and that's worth a lot to me.