[Release] Office12 (2007) Post SP3 HotPack Multilanguage (GL

[adric]

Hi Twoj, I just tried building a new hotpack for June and noticed that OI considers outlookloc2007-kb2687404-fullfile-x86-glb.exe as Obsoleted by outlook2007-kb2863811-fullfile-x86-glb.exe. There are 4 files in kb2687404 that are missing in kb2863811 so I'm wondering if this is an OI error. When I updated your last hotpack. I didn't see kb2687404 as being considered obsolete when updating with kb2863811. Ohotfix .ini after updating had both

[KB2687404_outlook-x-none.msp]
KB=KB2687404
and
[outlook-x-none.msp]
KB=KB2863811

So it looks like there is a difference when building a new hotpack from the previous fixes or if you simply update the previous hotpack. Is [KB2687404_outlook-x-none.msp] a special case?

[TwoJ]

Hi Adric
Yes, unfortunately the OI has problems with keeping up with all the non-standard updates coming out of Microsoft.
You should use my Office Updates Downloader http://cpu.reboot.pro/viewtopic.php?f=20&t=759 , to get the necessary updates for 2007 (or any others that you want) and in those downloads is a small batch file to extract and rename if necessary all patches into a folder called updates, then you just need to copy those into the updates folder in your source of 2007.
Until there is some active maintenance of the OI I have found this method the best workaround until siginet can get the OI updated.
Hope that helps

[adric]

Hi TwoJ, I was aware of the downloader, but I wanted to update Office 2007 with the June updates and I noticed the batch file wasn't set up to handle the new updates. Anyway, I was able to use OI with the update hotpack function for the new fixes.
KB2878233 O2007-S ( ) * MS14-036 Office Suite replaces KB2817641
KB2881069 O2007-S ( ) * MS14-036 Office Suite
KB2880513 O2007-S ( ) * MS14-034 Office Suite replaces KB2878236
KB2880515 O2007-S ( ) * MS14-034 Office Word replaces KB2878237
KB2881065 O2007-U ( ) * Outlook 2007 Junk eMail Filter replaces KB2880505

[TwoJ]

To tell the truth, I've only been using my little batch file, now that 2003 has hit end-of-life, 2007 and up only do post-patching, so its a lot easier to manipulate the batch file then to try to fiddle around with renaming or fooling the OI to integrate 2 fixes it wouldn't normally integrate.
Also as I mentioned else where, I just don't have the time to keep up every month, I've already shaved off quite a bit of time due to the batch file, but it would be great to find some more automatic way.
If you know which hotfixes replace other hotfixes and with some basic knowledge of scripting you can modify my script, it is very basic.
Hope that helps

[bigbloke]

Is this project dead now?

[TwoJ]

Maybe not dead - but very dormant
Since Office 2003 the idea of integrating hotpacks or hotfixes has been a moot point since starting with 2007 and future office versions you can't 'integrate' hotfixes, you just post-installation patch them. Since Microsoft was continuously changing their 'spec' on hotfix structure it was a continuous problem to keep the OI updated for every monthly patch release where they would change something that wouldn't work. So eventually I just went back to a batch script to do the installs of the hotfixes.
So the only thing you really need to do is keep a constant list of Office hotfixes and modify the script every month. Since Office 2007 I think is EOL or near, there is 2010, 2013, and now 2016, in 32 and 64 flavors, so keeping these all up to date every month is more effort than I have time and interest in at this point. Since my job has changed I don't do office (software) installations like I used to so I have moved onto other stuff.
However the script is fairly simple and it shouldn't take too long to modify it for the current needs.
Hope that helps and updates people
thanks

[adric]

HI Twoj, glad to see you still stopping in now and then. As of January, I can no longer get OI to run on W7, so I may need to revert to the script you mentioned. I haven't found out why the OI GUI will no longer appear. Seems to be related to the OI.dll that gets placed (along with other files) in system32 when you launch OI. Still works on XP and W8.1 with Dec. Updates though.

If I already have the updates I need and don't want to use the downloader, will the batch file and copy to source instalation be enough? Also, I don't see _ExtractMSPs.bat anywhere in the download package. How do I get to the batch file?

On second thought, if I just run <fn>.exe /extract:z:\tmp /quiet on each update, that should give me the files I need correct?

[TwoJ]

Hi adric

Yes, I still monitor the forum from time to time.
The OI still should work in Win7, I know that my anti-virus was starting not to like it at one point, you might want to check if your AV is stopping it.
Yup if you run that command you should be able to extract the files, you can use the script to cycle through the updates to get the msp's out by replacing that command instead of the integration command.
Just as I mentioned the issue is that every month you need to modify it to get the new hotfixes if you are dealing with office 2010 or newer.
hope that helps

[bigbloke]

Nice one thanks for replying. I just assumed no one looked at these threads anymore due to the date of the post prior to my previous.

[Williamrek]

Can we post M-Rated stuff here as long as we put a warning or somthing?
Im not planing on writing anything M-rated, but it would be nice to know what we can and can not post here.

.