fragbert
Content Type
Profiles
Forums
Events
Posts posted by fragbert
-
-
Hi,
I've done an Administrative Installation Point from my Office 2003 CD and slipstreamed SP2 & all office updates needed as it's explained here.
That is what we have all done. Have you checked your installation via *microsoft update*, not *office update*? And when I mean *microsoft update*, that means you have upgraded *windows update* to *microsoft update*.
0 -
Same here, I used the CMD office updater from msfn and still Micro$h!t says I need to update.
And yet if you go to Office Update on MS's site, it works properly and state you have 0 downloads required. Go figure...
I've opened a case with MS specifically on this issue, I will update this thread if MS responds with a solution.
0 -
but i want to see 0
Same here, following the MSFN UWXP guide verbatim.
MS needs to fix their MS update site to recognized O2K3 SP2 w/ integrated hotfixes. It is inexcusable that they do not!
0 -
I tried MS's official newsgroups and surprisingly nobody there had an answer. Anybody still have these problems like me?
0 -
[quote name='glent' post='473130' date='Mar 2 2006, 03:54 PM']did you use nlite to remove something?[/quote]
No. I used a standard corp volume XP w/ SP2 slipstreamed, installed the latest RyanVM update pack, and latest BTS driver packs (I've been doing this without error for the past 6 months). Usually if there is an update remaining to install, I will just use the INTEGRATE: method without issue. I seems that KB912945 is causing this, however I'm not entirely certain.0 -
Bump - this is happening to me now after integrating the latest ActiveX update from MSupdate (optional fix). Any ideas? I deleted the entire display section of my WINNT.SIF and still no dice.0
-
The latest MSRT was released today and I want to integrate it into my unattended XP install DVD. Is it as simple as using /integrate ?
0 -
Hello I have been following threads about this odd issue where a seemingly perfect unattended XP install for whatever reason will prompt on certain machines (hence no longer be unattented) for a "Plug and Play Monitor" driver. I see this is an issue that affects Dell Optiplex machines with integrated Intel graphics (GX520 here). Both suggested fixes in this forum do not fix this annoying prompt (editing the WINNT.SIF to 800x600x60hz and installing MS hotfix 883667).
I am at a loss, any help is appreciated.
0 -
I believe that they ARE slipstreaming. I think the problem is either a bug in MS Update or the slipstreaming process isn't importing the registry entries to indicate that they're installed. Testing all of this out has been on my to do list for a while now, but it's just always being shoved aside.
PROBLEM SOLVED - editing the .ini for each hotfix so that IsNormalUpdate=0 fixed the issue. It seems with these new post SP2 hotfixes that you must specify that these are being integrated into administrative install points, else the hotfix will install in "normal" mode.
Problem NOT solved. Crap still happens.
0 -
Hello, after following the instructions on the unattended guide to integrate SP2 into Office 2003 (which works and installs fine) the last steps to integrate any hotfixes (in this case, three patches released after SP2) fail to slipstream. I even extracted each hotfix and slipstreamed them one by one rather than using the .cmd's offered on the Office 2003 section of the guide and it still would not integrate (MS update still marks these three fixes as critical updates to download).
The three post-SP2 hotfixes are:
KB892843
KB905648
KB907417
Any ideas? Is there a new method to install O2K3 hotfixes post-SP2?
Thanks.
0
Slipstreamed all office updates in the Office 2003 install
in Microsoft Office
Posted
Welcome to the club.
Update - I have opened several cases with Microsoft, with one finally reaching somebody who understands english properly and recognizes our very specific problem with *MU*. So far it looks like the bug with MU is that it will list the updates for download if these hotfixes are not listed in add/remove programs when "show updates" is checked. Since these are integrated before installation, the hotfixes will of course not be listed under Office 2003. Office Update clearly uses a different (and correct!) method in detecting previously installed/integrated hotfixes.
I'll update as this case continues.