[Release] Office12 (2007) Post SP2 HotPack Multilanguage (GLB)

[TwoJ]

I do not know is it me or link in Downloads section for Office 2007 HotPack is not working...
And it's for last month, not for February.
Thanks anyway.

There seems to be an issue with the forum that posts are not getting updated automatically - Siginet if you read this, its been going on for some time where i need to manually refresh the page to see new & updated posts.

You should try doing a manual update on the page, if not here's the link;
http://rapidshare.com/files/34897159...ck-glb-0210.7z

[herc]

Yes, I need to manually refresh the page to see latest posts.
Links are ok now.

[TwoJ]

Project, SharePoint Designer, and Visio have no updates as of 2010-03-11

The 2007 Office i'll post tomorrow but i will likely post a newer version as well which will be the 'newer' update style for 2007 going forward.

[TwoJ]

Update to 2010-03-12

There are new types of downloads available so please read the post well to understand which one you want to download

Thanks

[thylacine]

TwoJ, am first timer here.

after reading post #1, am confused.


I have Office 2007 with SP2 source ISO. Do i need to download the SP2 Fullfile from Microsoft?

or do i just get Office12-PostSP2-HotPack-glb-0311.7z and using OI to "integrate" this hotpack with Office 2007 SP2 ISO?

[TwoJ]

- no worries that why we're here

You are correct that if your source already has the SP2 inclused you only need the hotpack.
The OI however is even smarter that it would know that you have a SP2 integrated source and skip the SP integration.

I'm obviously not up to date with all of MS releases but i'm not aware that MS has released any office products that come with integrated SPs, unlike their Windows releases, so thats why i take the assumption that the source has no SP integrated.
There are of course a lot of non-microsoft releases which integrate SPs into them but my experience has always been for Office that its better to start off with the orginal non-SP version.

[thylacine]

thx TwoJ

after looking at hte source, now i know it's actually pre-installed SP2 (MSPs) in the Updates folder.

[benners]

- no worries that why we're here

You are correct that if your source already has the SP2 inclused you only need the hotpack.
The OI however is even smarter that it would know that you have a SP2 integrated source and skip the SP integration.

I'm obviously not up to date with all of MS releases but i'm not aware that MS has released any office products that come with integrated SPs, unlike their Windows releases, so thats why i take the assumption that the source has no SP integrated.
There are of course a lot of non-microsoft releases which integrate SPs into them but my experience has always been for Office that its better to start off with the orginal non-SP version.

Currently the OI will only know the service pack level for Office 2007 if it has integrated it. With previous versions the main msi build number was updated after a slipstream but as 2007 has the updates folder instead it would have to scan each of the files until it found "Service Pack" in the msp description and then get the build number. It is something I am going to do but just trying to find a quick solution so as not to slow down the process.

[thylacine]

i've just been twiddling around the current OI, amazing work there benners

oh how i really wish Microsoft did allow direct hotflix slipstreaming instead of dumping their MSPs in just folder and only picked it up during install (sic!)

btw, benners, any chance of adding tweaking support on the custom.xml (Office12 Enterprise)?

e.g. features: adding/change product key/user name/company name, etc.

[benners]

i've just been twiddling around the current OI, amazing work there benners

oh how i really wish Microsoft did allow direct hotflix slipstreaming instead of dumping their MSPs in just folder and only picked it up during install (sic!)

btw, benners, any chance of adding tweaking support on the custom.xml (Office12 Enterprise)?

e.g. features: adding/change product key/user name/company name, etc.

The features (except the etc ) you have asked for are in the new build. I am currently testing it. I have had to change some code and shoehorn the new Office stuff into it. It's getting a bit messy, would love to have the time to rewrite it

It would be better if MS would stick to a method. Seems a waste of a users time when doing an install to wait for the updates as well