[Release] Office Integrator v0.6

[Siginet]

Office Integrator v0.6
Office integrator will allow you to slipstream all of the Office Hotfixes into your install disk and create an admin install for you. It will read the mysql database of http://SiginetSoftware.com to get any registry settings needed for the hotfixes.


Ever since I wrote the RVM Integrator I have had a ton of people ask me to make an Office SlipStreamer. So I have decided to create one. What it basically does is automate the slipstreaming of ServicePacks and Hotfixes into your Office Install disks.

The only reason I never actually made this simple tool is for the fact that microsoft has been pretty buggy at making their hotfixes for office. One hotfix you have to manually use a tool called orca to fix an error they put in it and also Microsoft Update was made in a way that is not compatable with detecting slipstreamed hotfixes.

You can download v0.6 Beta in this thread now.

You need to download the hotfixes from microsoft one at a time.
Or you can get an Office "HotPack" from www.SiginetSoftware.com. Hotpacks are a package of all needed hotfixes wrapped into one archive.

*Note* You should be connected to the internet while integrating because the Office integrator will check the mysql database on siginetsoftware.com for information needed to compile the reg file you can use so that microsoft update does not complain.


Download and Rate Office Integrator (http://fileforum.betanews.com/detail/Siginets_Office_Integrator/1175329925/1) v0.6
Download Office Integrator (http://siginetsoftware.com/files/OfficeIntegrator_0.6.zip) v0.6

1. Open the Office Integrator and choose your office install setup.exe (Source). This is optional... you only need to select your office setup.exe if you are using a fresh office source and it is not allready an admin source. If you have allready created an admin source then you can skip the first box and move on to the next step.

2. Now you can point to the second input box and choose your destination. If you allready have made an admin install of office 2003 using the /a switch then you can point to that admin install and the Office Integrator will recognize it as the destination. Your office admin install will then have the choosen hotfixes slipstreamed to it once the integration is started.

3. The third box you can select a servicepack to slipstream.

4. In the fourth inputbox you can choose the hotfix files or the new Office "HotPack" you want to slipstream. You can hold the CTRL button while selecting hotfixes/hotpacks to select more than one.

5. Now just click on "Integrate" and sit back and wait until it finishes.

... After each hotfix is slipstreamed the Office Integrator will read the DataBase file that was downloaded from http://SiginetSoftware.com, when you first opened OfficeIntegrator.exe, to grab the registry information for the hotfix you integrated. It has been verified to work with all of the hotfixes that are currently in the database.

If you integrate a hotfix that is not in the database please post any registry info here that should be added to our database.

This software is in beta so there may be issues. But it has been tested and does do the job so far. I need help from the users to build the database and make the program even more efficient. ;)

Thanks to Viva for all of his help with this project as well!


Changes:
v0.6
1. Fixed ServicePack Slipstream bug. The OWC11*.msp file was not getting slipstreamed. (Thanks Wimb for pointing it out)
2. Fixed a typo in the code for SETUP_OI.EXE
3. FILES\SETUP\KB_KEYS.REG is now renamed to FILES\SETUP\KB_KEYS.OI because it is no longer a reg file. It just holds the reg info needed for SETUP_OI.EXE to use to add the entries to the registry.
4. SETUP_OI.EXE now finds the Office 2003 Language after installation and uses that info to create the correct registry keys that are placed into the registry.

v0.5
1. The database is downloaded to the hard drive upon opening OfficeIntegrator.exe now.
2. It automatically checks the OS Lang to get the key info for each registry entry.
3. It now places the KB_KEYS.REG file inside FILES\SETUP so that it doesn't reside at the root.
4. It creates a new SETUP_OI.EXE that will be used instead of the original setup.exe.
5. The new SETUP_OI.EXE will run the original setup.exe and it will pass any parameters as well. It will install KB_KEYS.REG and it will create the AllPatches reg entry as each entry is installed. It will not overwrite any AllPatches entries. It specifically adds new entries to the list.
I've added more to the log file so that it will help better when trying to debug any errors.

v0.4
1. Fixed numerous small bugs.
2. Fixed compatability for the entire Office 2003 Suite.
3. Added better logging.
4. Added a donate option upon finishing an integration. You can select "Yes" to be taken to a place to donate or "No" if you wish not too. Hint Hint... ;)

v0.3
1. Fixed ServicePack slipstreaming bug.
2. Changed the way the database is read so that it is much more suffecient.
3. Now the Office Integrator will create a Log file named OfficeIntegrator.log in it's executable directory which will log important info in it.
4. Added support for the brand new Office "HotPacks".
5. Many new KB entries have been added to the database (Mainly for english and dutch registry entries).

v0.2:
1. In this version I pretty much re-wrote a lot of the coding structure. The database is read in a different way now which should allow for more expandability. I still have to add a lot of the reg entries to the database. And a lot of the reg entries that were submitted need to be placed into the database again. I put a bunch of them in... but I still have to get more of them inputed.
2. Now you can slipstream ServicePacks as well. :)
3. The Office Integrator will detect your Office source as well now.
4. You can use the integrator on the entire office suite now. Like OneNote, FrontPage... and so on. (Allthough certain hotfixes may need to be added to the database as well.)
5. Needed dll files for the online database are now compiled inside of the exe... so there is no longer a need to install them seperatly.

[ViVa]

Outch... :oops: sorry Sigi, didn't mean to steal/continue your ideas, I didn't see this note.

[Siginet]

No way viva. We just both started on the project around the same time. I'm actually glad you were working on one. ;) Now we can put our heads together and make this project even better. :D

When this project is released I'll make you a mod of it's forum and we'll bring it to life together.

It really shouldn't be a difficult tool to make.

[ViVa]

It'll be great, and time saving. :)

[ricktendo64]

Good one Sigi and Viva, cant wait for the final...

[Replika]

Ever since I wrote the RVM Integrator I have had a ton of people ask me to make an Office SlipStreamer. So I have decided to create one. What it basically does is automate the slipstreaming of ServicePacks and Hotfixes into your Office Install disks.
Great. That is i'm waiting for.
And could you please make Visual Studio Slipstreamer?

Heath Stewart on his blog made a how to slipstream Visual Studio 2005 SP1.
http://blogs.msdn.com/heaths/archive/2006/12/16/slipstreaming-visual-studio-2005-service-pack-1.aspx
But after slipstreaming, the installer expands to 3.0GB (from ~1.5GB)
I'm only a beginner and can not understand what Heath Stewart's comments to compress it myself.
You do re-CAB the installer in RVM Integrator, don't you? Please make the soft like that :).
Thank you.

--
Replika

[Siginet]

I am going to do my best. Office and Windows are completley different on how they are packaged. When the office integrator is first released it will only slipstream the hotfixes... but there are plans for me to try to make an option to direct integrate them as well. Which will save hundreds of megabytes.

[arabianhorse]

thanks it`s good topic
Best Regards

[ProfessorCPU]

I finally got a release together for everybody. :D

[BrainDedd]

I can only download 0.1? Or is 0.1 = 0.4? :confused:

[Siginet]

sorry that was a typo. We are still at 0.1. I'm waiting for feedback before I do any further development. So far I don't see much interest in this project.

A lot of people downloading... but no feedback. :(

I can't make the program better if nobody is willing to give me any feedback. Is it working for you guys... or not?

[jongent]

All updates integrated OK but when I tried to install office2003 from the freshly burned cd, it fails when copying the file:

Microsoft.Office.Interop.Infopath.SemiTrust.dll

asking me to insert the MS Office Professional Edition

jon

[Siginet]

That is a normal error. It is not caused by the Office Integrator. That error happens when integrating one of the hotfixes. If you install dot net to your system first I have heard it gets rid of the issue. Or there is a modification you can do to your msi with orca.exe. You can search msfn for the fix. This is one of the issues I want to have the office integrator fix automatically. I may add the possability in the next version.

[Siginet]

hi all,
I have a solution, I'll explain you how I did:

The problem is Update for InfoPath 2003 (KB920103):

you don't need Office 2003 PIA
you need Windows Installer SDK (x86) v1.1


After slipstreaming Update for InfoPath 2003 (KB920103) into Office 2003 Professional with SP2 there are two errors in PRO11.MSI.
To fix:

download Windows Installer SDK (x86) v1.1:
double click downloaded IntelSDK.msi and follow the instruction to install
go in the folder where you have install to (default D:\MsiIntel.SDK) then under folder Tools (D:\MsiIntel.SDK\Tools)
double click Orca.msi and install it
backup PRO11.MSI slipstreamed with Update for InfoPath 2003 (KB920103)
run Orca
with Orca open PRO11.MSI slipstreamed with Update for InfoPath 2003 (KB920103)
then in the Tables column (left) click on File, scroll down the rigth column until end, at the bottom you will see the last two rows like:

File Component_ Sequence
IPCLRWRP.DLL_0001 Global_PIA_XDocsWrapper2 4550
INFOPATH.CFG Global_PIA_XDocsWrapper2 4551

change the numbers under Sequence into:

File Component_ Sequence
IPCLRWRP.DLL_0001 Global_PIA_XDocsWrapper2 270
INFOPATH.CFG Global_PIA_XDocsWrapper2 271


[attachment=14192:attachment]
save PRO11.MSI
create image, burn it and try...

[jongent]

Worked perfectly. MS office update site says no updates needed.

Thanks a lot

jon

[Siginet]

:D Thanks for the feedback.

[Windoos]

Hai tnx for making the Office 2003 Integrator.
It don't work at my place and I get the following error by slipstreaming Hotfix no.1

Line 0 (file "c:\Officeintegrator.exe")
with $VF61663A30082E013
With $ ERROR

Error: Only Object-type variables allowed in an "With" statement.

I hope you know what the error is and can give me the solution.

With Regards,

Siebe B.

[Siginet]

Are you connected to the internet during the integration? Also... make sure no firewall is blocking Office Integrator from getting to the internet.

[Windoos]

Tnx for reply, ofcaurse I'm connected to the internet.
I'm behind a proxyserver. I have my own server. So if you can tell me wicht port I'll have to open I will trie again.

With regards,

Siebe

[Siginet]

Actually you will get that error if you did not install the included msi that came with the package. That msi installs some dll files that are needed to allow your computer to access the mysql database. ;)

I also saw on a website that says this:

Do you have a firewall on your Windows PC that may be blocking either outgoing or incoming data on port 3306?


Please let me know if any of this fixes your issue. This is the type of stuff I need to learn during the beta testing stages. I was curious to know what would happen on someones computer that was using a firewall or proxy etc. ;)

Thanks for any input.

[Windoos]

Several path were not riht.
That was de problem.

But there is an other strange problem. Ik have no sp2 slipstreamed. So i had first slipstream sp2.
Then i slipstream the hotfixes.
When I go MS update there are all to update.

Strange.

[neo]

i used to do this same thing using about 4 .cmd files that automatted the whole process start to finish. but I wanted to try this out since when I slipstream via my method, MS Updates says I am still missing patches. Office updates says I have them all...weird.

anyway, im just try to slip service pack 2 in and it starts, a looks like its done is under 10 seconds. is this normal? how can I tell that the integration was competed?

Thanks.

(if you ever need MSI's for your installs, let me know. thats what I do for a living)

[ProfessorCPU]

OK... The current version of Office Integrator does not slipstream the service pack for you. But the next beta version will give that option. Also the next version will allow you to slipstream servicepacks and hotfixes to the other disks for office 2k3. Like Frontpage, Project, Visio, etc...

On Office update you will not ever have an issue with it not seeing your updates. It is Microsoft Update that has the issue. ;) But if you install the .reg file that the office integrator makes then you will not have the issue with Microsoft Update not detecting your slipstreamed updates. ;)

Unless Microsoft actually fixed their MS Update bug you will need that reg file. It would make things much easier if they did fix the bug... but I haven't heard of the fix yet.

[TheSickman]

tanks a lot for the wurk

but 1 question

when i slip sp2 in me office2003

and i run office update
i get

KB894542
KB907417
KB913571
KB914455
KB919029
KB920103
KB920813
KB923097
KB924085
KB924424
KB924885
KB924886
KB925251
KB929057
KB929058
KB929060
KB929064

[ProfessorCPU]

If there are any hotfixes missing from the database then post the reg entries and I will gladly add them to the database. ;)

[TheSickman]

k

dis is ( i beleive ) what's bin added after MS update

after clean install

btw
me is a dutchie
me talkin bout Office2003 NL

[ProfessorCPU]

Thanks for posting your reg file. :) I've added any to the database that do not exist allready.

I notice in yours there are some that allready exist but yours are a little different because of dutch. So I was compairing the EN and the NL and I think I have a better idea on how to organise the Database so that we can use any language reg entries in the database. So I am going to hold off before I release Office integrator v0.2 until I can recode the way it will work with the database. It should open a lot of doors and make things much simpler. ;) So stay tuned.

I did only add the English versions of the hotfixes to the database for now... because the v0.1 Office integrator can only support 1 lang so far. But everybody please keep posting your reg files. Without your help this project won't work as well.

Thanks a lot for your help TheSickMan!

[j4gg3r]

Here ya go champ, updates to 4th March 2007 attached.

Slipped my Office from the cabs in \WINDOWS\Sofware Distribution\Download
manually and patched with Orca.
Hope your baby helps lots of people not have to do the same. :)

[wimb]

Not all selected Hotfixes from a list, are processed by the integrator.
Often the first and / or the last item of a list are actually not processed.

It is also important to integrate the SP2 update first separatedly, prior to the other hotfixes. Otherwise a revers update history can be the result.

The Office Integrator is a promising product, but is giving at the moment not always the desired and expected result.

[Siginet]

Yes it is still in Beta. ;) Actually it is very beta right now. Basically this release was really a practice. Just to see if the concept would work. I am very pleased with it's output and I have come up with a much better way to make it work. I plan on making a new version soon... but I have been putting my time in the RVM Integrator latley. Once I get a good release of the RVM Integrator released I should also be releasing a long awaited newer Windows XP PowerPacker. Then I will get back to coding the Office Integrator. :D

Just keep the reg entries comming in in the meantime. :D

[wimb]

The concept of the Office Integrator is very good and I hope that you can remove the processing errors.
The RVM Integrator is very valuable for all of us, so I can understand that you first focus on that.

In the mean time I will use semi-manual processing for integrating the hotfixes in Office as described in the MSFN site

unattended.msfn.org/unattended.xp/view/web/48/

[shurzota]

Please ignore me.

[LaMaKiNa]

fantastica utilidad, pero me pregunto cuando saldra la version para office 2007

[Siginet]

fantastica utilidad, pero me pregunto cuando saldra la version para office 2007

Google Spanish to English Translated:

fantastic utility, but I ask myself when saldra the version for office 2007

It is still very much in beta. Everything so far is only based on 2k3... but I do plan on making it work with other versions of office as well. Once I am satisfied with the 2k3 portion of it then I will work on 2k7 support. ;)

Google English to Spanish Translation:

Todavía está mucho en beta. Todo se basa hasta ahora solamente en 2k3… pero planeo en la fabricación te del trabajo con otras versiones de la oficina también. Una vez que esté satisfecho con la porción 2k3 de ella entonces trabajaré en la ayuda 2k7. ;)

[Makave2345]

Siginet.... Another outstanding tool...

Here is my reg entries for some new hotfixes...

KB920813
KB929064
KB929057
KB929058 *** OGA required
KB925251 *** OGA required
KB924885 *** Replaces KB925534
KB929060 *** OGA required
KB931764 *** Replaces KB924885 & OGA Required

I was also bored and thought it might help you out a little, so I updated
the database list (the webpage part) and added these to them. NOTE: I did not remove KB925534 or KB924885.

The edited database is also attached. If you can use it. Great... Just thought it might save you some time...

Anyways, thanks for such a great tool...

[j4gg3r]

Not all selected Hotfixes from a list, are processed by the integrator.
Often the first and / or the last item of a list are actually not processed.

It is also important to integrate the SP2 update first separatedly, prior to the other hotfixes. Otherwise a revers update history can be the result.

The Office Integrator is a promising product, but is giving at the moment not always the desired and expected result.

Hey wimb, You can use the tools and info in this MSFN thread to do it untill the intergartor is better.
http://www.msfn.org/board/index.php?showtopic=89038
You can then use that .reg I posted if you don't have access to your own to make the Office updates visible to MU.

[wimb]

Thanks a lot j4gg3r for your link to this interesting MSFN thread.
I was not aware of it, and it is very helpfull.

For the Registry Patch I have been using the path file given previously by TheSickman, which corresponds exactly to what was needed for my Dutch version of Office 2003. Also his list of post-SP2 updates for Office 2003 is correct for ultimo february 2007. So I would like thank him too for his contribution.

The slipstreamed Office 2003 is installed in less than a minute from the external USB harddisk. Everything works perfect.

[the_guy]

Siginet.... Another outstanding tool...

Here is my reg entries for some new hotfixes...

KB920813
KB929064
KB929057
KB929058 *** OGA required
KB925251 *** OGA required
KB924885 *** Replaces KB925534
KB929060 *** OGA required
KB931764 *** Replaces KB924885 & OGA Required

I was also bored and thought it might help you out a little, so I updated
the database list (the webpage part) and added these to them. NOTE: I did not remove KB925534 or KB924885.

The edited database is also attached. If you can use it. Great... Just thought it might save you some time...

Anyways, thanks for such a great tool...

There are a few more replaced updates. KB923091 is replaced by KB929060, KB923094 is replaced by KB929057, KB925257 is replaced by KB929058, and KB923272 is replaced by KB929064.

the_guy

[khan]

Siginet, I am just curious about the compatibility with Office 2003 Sp1.
I just want to Patch Office 2003 Sp2 with all Hotfixes/Updates into it...

Does it work with Office2003 Sp1 to Integrate SP2 etc....?

[Siginet]

Siginet, I am just curious about the compatibility with Office 2003 Sp1.
I just want to Patch Office 2003 Sp2 with all Hotfixes/Updates into it...

Does it work with Office2003 Sp1 to Integrate SP2 etc....?

Not yet no. Because for my beta testing I have only been concentrating on Office2k3 with SP2 at the moment. Once this project is fully working the database will be able to hold all of the registry info needed for every hotfix SP1 or SP2 and so on.

The next beta will also allow you to slipstream ServicePacks into it as well as hotfixes. ;)

[khan]

Not yet no. Because for my beta testing I have only been concentrating on Office2k3 with SP2 at the moment. Once this project is fully working the database will be able to hold all of the registry info needed for every hotfix SP1 or SP2 and so on.

The next beta will also allow you to slipstream ServicePacks into it as well as hotfixes. ;)

Sigi,I will wait for Next release....


thanks....:)

[khan]

Not yet no. Because for my beta testing I have only been concentrating on Office2k3 with SP2 at the moment. Once this project is fully working the database will be able to hold all of the registry info needed for every hotfix SP1 or SP2 and so on.

The next beta will also allow you to slipstream ServicePacks into it as well as hotfixes. ;)

Hey signet...There is a good news for Me...:)

I just successfully Slipstreamed Office 2003 Sp2 into Office 2003,I used your integrator and selected SP2 as an Hotfix....

Now I have Admin Source of Office2003 [*SP2] integrated 'Size=644 Mb'
I also installed and checked it...It is saying Office 2003 Sp2 in every office application about box...

Now I am looking for Integraing more update packs which I have in Office 2003 Sp2 Only CD...

ONENOTE2003SP2-KB887619-FULLFILE-ENU.EXE
PTK2003SP2-KB887618-FULLFILE-ENU.EXE
FRREFORM.EXE

Plus VIVA managed a link of most of the Hotfixes....

Is it safe to use the same admin source [D:\office2003\]to slipstreamed the hotfixes ? Or I have to integrate all at the sametime....

[mara-]

Hi Signet! This tool is great! I used to slipstream all post SP2 hotfixes, and after that, I went to Windows update and I found update that I already integrated:Security Update for Office 2003 (KB929064), so I'm posting here registry entry, so you can update your database.
There was one more update, but I forgot to integate it at all, but when I check I will post it here!!!

Greetings!!!

[khan]

Goody...:D

Thankyou Signet you did a really impressive work...Thanks buddy...;)

[Mandarin]

Signet - tried this for the first time today and all was going well until I get the attached error message and the Office Integrator crashed out. Any ideas?

[Siginet]

Signet - tried this for the first time today and all was going well until I get the attached error message and the Office Integrator crashed out. Any ideas?

Are you connected to the internet while you are using it? Do you have a firewall that may be blocking it?

[khan]

..................:)

[mara-]

Hi Siginet!

I know that question which I will ask now is not totaly related to this topic but, you may help me! I recently made unattended installation of Windows which will install Office 2003 with SP2 silently from SVCPACK pack! My installation was perfectly, but then I discovered your tool, and I integrated following updates:
KB894542
KB907417
KB914455
KB919029
KB920103
KB920813
KB923097
KB924085
KB924424
KB925251
KB929057
KB929058
KB929060
KB929064
KB931764

Then I made everything again (because of error I didnt make office now silently, I left it so installatio setup apears on Windows installation), and I get error:
Error 1935. An error occurred during the installation of
assembly component {53EB5CFB-3DAF-4890-ABCD
4895D28EAAAF}. HRESULT: -214702486

I searched little on google, and i think that is something related to net framewok, that some update need it installed, so can you tell me which office update causes this, so I can exclude it?

[Mandarin]

Are you connected to the internet while you are using it? Do you have a firewall that may be blocking it?

Connected to the net all the time. The first two hotfixes installed just fine then it threw up this error. Will have a go later on and try just a few at a time to see how it handles it.

I use Zone Alarm PRO and it asked for permission to access your server to check the sql database and I let it have permission and set it so it didn't need to ask again so it shouldn't be the firewall.

Will try again and report back. :D

[khan]

Yeah,...I also have a slow Internet connection which often disconnects while integrating the O2K3 hotfixes,this is irritating for me to start everything from the beginning...:(

@ Siginet,...Office 2003 Integrator works well but it will be more appriciating if you provide a download link of Hotfixes database which used as a PLUGIN inside O2K3 Integrator....
I don't know if you have all these Hotfixes in your database so please consider this page as a reference of your entire databese....I will update it time by time with more Hotfixes + Other Updates Like (Word Viewer 2003)
http://www40.brinkster.com/hivelocity/office_2003_post-sp2_updates.html

Do you guys have a LOG file generated by O2K3 Integrator ? what is inside that?

[Mandarin]

OK - another failure.

This time tried just integrating SP2 with no other hotfixes. It appears to go through the motions and puts up the "installing SP2" message at the top of the screen (or however it is worded) and when it gets to the end I get the first error box. Closing the Office integrator then gives the second error message. :confused:

[Mandarin]

Downloaded a new copy of SP2 for Office 2003 last night and tried just slipstreaming that and got exactly the same failure again. I can do the whole slipstream thing manually with no problems and it is odd that it just doesn't seem to like the Office Integrator.

[Siginet]

Downloaded a new copy of SP2 for Office 2003 last night and tried just slipstreaming that and got exactly the same failure again. I can do the whole slipstream thing manually with no problems and it is odd that it just doesn't seem to like the Office Integrator.

OK I will look into this issue. Thx for the feedback. :)

I also think in the next beta I will have the office integrator download the database to the computer upon opening the program. Then have it read the database from the computer instead. ;)

[khan]

OK I will look into this issue. Thx for the feedback. :)

I also think in the next beta I will have the office integrator download the database to the computer upon opening the program. Then have it read the database from the computer instead. ;)

Thank God....

Now you are carying for your O2K3 Beta Testers...:D
We are Waiting for the Next version....;)

[khan]

Sigi.....

Does this new version of O2K3 Integrator can slipstream these packs...?This will be awesome if O2K3 integrator handles these updates,Addins....

Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats
http://www.microsoft.com/downloads/details.aspx?FamilyID=941b3470-3ae9-4aee-8f43-c6bb74cd1466&DisplayLang=en

Office XP/2003 Add-in: Office Sounds
http://www.microsoft.com/downloads/details.aspx?FamilyID=C8BB981D-2A23-4D1A-8310-457C733BE290&displaylang=en

Plus I am manually adding some PowerPoints Templetes in the O2K3 Admin install Source and also Replacing the old USP10.DLL with the Latest VISTA RTM which I always do after installing office 2k3...

I don't know if the Integrator repacks the Admin source into CAB files...I reallize that the Entire Office2003 becomes larger and may be it will not fit in a single CD....

[Siginet]

When I have some spare time I will look into compatability with all of these. These are good ideas. If you post the steps you use to repack that stuff in there I will look into adding the possability. :D

[khan]

I also got the same error integrated with O2k3 Integrator 0.2...

What I did wrong ?
Connected with Internet all the time....!

1)Open O2K3 Integrator.
2)Browse for O2K3 Backup source [Original].
3)Make a new folder C:\Office11 as Destination folder...
Press the Integrate button....

O2K3 Successfully create the O2K3 ADMIN Source in C:\Office11

then I Connected to Internet and Open O2K3 Integrator...

1)Browse the path C:\OFFICE11 as Office2k3 source...[O2k3 Detected with Admin source]
2)Browse for O2K3 SP2 [Leave the Destination and Hotfixes]
3)Press Integrate button...

got the following errors...

49

[romsempire]

Hi, I am using your tool: Office Integrator.
I have integrated Office 2003 SP2+hotfixes with localize version of Office 2003: italian version.

Your tool seem integrate SP2 well.
At the end of integration process a windows appear.
I don't remembrer message it contain but it says: "A patch don't exist, etc."
After I click on OK button.
Your tool start hotfixes integration. The integration is slow and to the 5th hotfixes my system crach with a bluescreen: Machine Check Error.

So I have reported my error here.
I hope in future these problems will be fixed.

[Siginet]

Hi, I am using your tool: Office Integrator.
I have integrated Office 2003 SP2+hotfixes with localize version of Office 2003: italian version.

Your tool seem integrate SP2 well.
At the end of integration process a windows appear.
I don't remembrer message it contain but it says: "A patch don't exist, etc."
After I click on OK button.
Your tool start hotfixes integration. The integration is slow and to the 5th hotfixes my system crach with a bluescreen: Machine Check Error.

So I have reported my error here.
I hope in future these problems will be fixed.

I do not think your issues are related to the office integrator because there are no extra processes made by the office integrator other than the normal microsoft method of slipstreaming the files. If you are slipstreaming a lot of hotfixes + SP2 then it will take a while. There is no way around that. If your are getting a "Machine Check Error" it is more likely a hardware issue. Probably faulty memory which was accessed during the integration process.

[khan]

What about the error i got...:confused:

[khan]

I just Manually integrated Office2003 Sp2.....


office2003 Admin source in C:\Office2003 and Office2003Sp2 C:\Office2003sp2...

by entering this Command....


msiexec /p C:\Office2003Sp2\MAINSP2ff.msp /a C:\Office2003\PRO11.MSI shortfilenames=true /qb

I don't know why Office integrator did not patch sp2...:(

[Siginet]

I will look into this too. I think you can do what you want by leaving the source blank and point to your admin files in the destination box. ;) Try that and let me know if it works.

[khan]

I will look into this too. I think you can do what you want by leaving the source blank and point to your admin files in the destination box. ;) Try that and let me know if it works.


Yes, You are right....:)

By leaving the Source box blank it is 100% working ...:D


Sigi,,,Do we need to install these hotfixes over to O2k3 Sp2...?
http://support.microsoft.com/kb/910473/

http://download.microsoft.com/download/A/3/7/A37DD717-A3F4-4B9A-9F5F-D2342CB7FA32/office2003-kb910473-fullfile-enu.exe

[Mandarin]

Signet - tried again today using the girlfriend's PC and still can't get this to integrate SP2.

Tried your suggestion for Khan and that didn't help either.

I have tried pointing the integrator to my 2003 CD and also tried making a manual admin install to a folder on the root of C and pointing the integrator directly to that as well. Neither method will let SP2 integrate - I get the failures that I attached previously (the same ones in attachment 49 that Khan put up).

Either I am missing a step somewhere or this is glitchy, but I did follow the instructions to the letter.

[Siginet]

Hmmm... well I must have messed something up then. As soon as I get the spare time I will fix it and finish v0.3. Hopefully v0.3 will be a much more stable release.

[khan]

Mandarin...Don't try it directly at your Girlfriend's system :D
You should have install the Latest Windows Installer....
http://www.softpedia.com/get/Authoring-tools/Setup-creators/Microsoft-Windows-Installer.shtml

Siginet O2K3 Integrator working for me.

For Manual integration you can do it your self....
The best way I found was to make an Admin Install Source in C:\Office2003.
Now I just Put Office2003 SP2 inside the same folder C:\Office2003,By using WinRar Extracted all files in the same folder....they were 4/5 files...

In Startmenu > RUN , copy paste this command and run...

msiexec /p C:\Office2003\MAINSP2ff.msp /a C:\Office2003\PRO11.MSI shortfilenames=true /qb

I also do the same thing with the KB910473 Hotfix which Upgrade the [word.exe,Excel.exe,Powerpoint.exe] File version...;)


You can also see the complete Step by step tutorial here...
http://www.petri.co.il/office_system_2003_sp_slipstreaming.htm

[Mandarin]

I'll give 0.3 a go when it comes out and give you some feedback. Thanks for the quick response.

[khan]

Siginet....

If we do the manual integration for other Hotfixes,Does it also create the Registry info inside O2k3 ...? : I think it will only patch and replace the old files...
Then it may not satisfy microsoft but we will have an updated office 2003 CD. ;)

[Mandarin]

Just had this work correctly and integrated 11 hotfixes (I still have to download the other 4 that need to go in). But that was only by slipstreaming SP2 into an admin install manually so it looks like only the SP2 integration part is broken.

[Siginet]

Yes I found the typo in the sp2 integration. It is fixed in 0.3 now. ;) I should be releasing it very soon. I am working on the first HotPack. Once I have it working completely I will be releasing 0.3. I ran a test with the hotpack I made and there were 3 hotfixes that were still needed afterwards. :( So I need to fix that.

Today is my birthday though... and I am still hung over from last night... so this weekend I should have something together. ;)

If any of you have used the office integrator and had any of the hotfixes not recognized by Microsoft Update... please remember which ones aren't recognized before you update them and then get the reg info and post it here. ;)
Thx.

[Mandarin]

Good news on identifying the SP2 issue. :)

I know this is an early beta but could you think about having something that tells you when the whole process is completed. When I ran my test yesterday with the 11 hotfixes I could see each being installed but wasn't really sure it had actually finished. Just a suggestion. :D

[Siginet]

Good news on identifying the SP2 issue. :)

I know this is an early beta but could you think about having something that tells you when the whole process is completed. When I ran my test yesterday with the 11 hotfixes I could see each being installed but wasn't really sure it had actually finished. Just a suggestion. :D

Yeah I allready added that in the next version too. ;)

I also got rid of all the splash screens as well and am now using balloon tray messages instead. ;)

[Siginet]

v0.3 is now online and ready. :) Many fixes! This may be the first "Stable" release. I'll be uploading the first "HotPack" as well. :)

[Mandarin]

Will give this a go later on tonight and report back. I have all the hotfixes downloaded so probably won't try the hotfix pack first off.

I'll start again from scratch and see how it handles SP2 as well. :)

[mara-]

Hi Siginet!

I just tested 0.3 version. Admin creation went fine, SP2 slipstream went fine, but on hotfiexes integration I got some errors (I selected about 15 post SP2 hotfixes to integrate).You can see screenshoot of error and my log file. Any ide what went wrong?

P.S. I was conected to internet while was doing integration.

[Siginet]

Hmmm... all I can think is it didn't properly install the mysql plugin for some reason. Can you try again and see if the same thing happens?

Edit: Actually after looking at your log it looks like the mysql plugin was successfully working. I wonder if my website went tempararily down at that time? If that's the case I need to add some sort of check if it is online so you don't get an error like that. I do plan on having the OIntegrator download the entire db upon executing OIntegrator so that when hotfixes are integrated they get their info from the db on your hd instead. That should prevent stuff like this from happening. Last night after I released this I realized that the way I set things up it still isn't possible to completely integrate hotfixes for other office 2k3 products like FrontPage, OneNote and so on. So I am going to change a few more things in 0.4. ;)

[Mandarin]

Good news!

Just finished a complete integration of SP2 and all 15 hotfixes listed by Fragbert over at Ryan's forums.

I didn't make an admin install and let the Office Integrator take care of the whole process and it worked perfectly. My firewall is set to ask me whenever anything tries to access the net and I could see the integrator accessing the database now and again - it doesn't seem to do it after each and every hotfix though. Maybe it doesn't need to?

Like the balloon tips - much neater than the boxes at the top of the screen in the 0.2 beta. Got the final message saying the process had comleted which is an improvement too.

Tomorrow I will give it a go with the office update pack and see how it handles that. So far so good - nice work.

[Siginet]

I think in v0.3 it should look at the database for each hotfix. But in v0.4 it will not go to the database if a hotfix is not integrated due to incorrect hotfix for your source and so on. ;) That way you don't get reg entries made for a hotfix that isn't really integrated.

I am now coding into the OIntegrator to check if you are using FrontPage 2003, OneNote 2003, Project 2003, Visio 2003, or Office 2003. Depending on which one you are using it will change the reg entries according to the code it should be using for the registry. ;)

[Mandarin]

Tried the process using the office update pack instead of my individually downloaded hotfixes and got an error. Screenshot and comments made in the update pack thread.

[wimb]

In preparing a HotPack for the Dutch version of Office Prof. 2003,
I observerd that the MessageTitle in the ohotfix.ini files of the *.msp Updates
is always in Dutch.
However Microsoft Update produces in the Registry most Patches in English,
but strange enough some are in Dutch: namely KB914455 and KB924085.

To get rid off this language mismatch problem, it might be better
to describe the ohotfix.ini file of the HotPack in another way.
Maybe it is possible to give a 3-letter language code in the first rule after [DBInfo]
and then no language info in the following rules, where the
*.msp files are only identified by there KB-number.

The Attached file is the Registry Patch produced by Microsoft Update for
the Dutch version of Office Professional 2003 on April 18th 2007

[Siginet]

We had this same type of issue with the Polish HotPack. But we found out that it depends on how the hotfixes were integrated. It seems to be yet another bug from microsoft update that causes this. So I feel it would be much better to have the integrator correctly hold the entries in the database and not feed into the microsoft bugs if possible. Could you uninstall your office suite and reinstall it with no hotfixes... then install each hotfix manually? Then export the reg entries.

This would be much cleaner and would serve the database much better.

I will however add a way that the office integrator can look for the alternate english reg entry if the original language's entry does not exist in the database.

For instance instead of:
GPFILTff.msp=Office 2003-beveiligingsupdate (KB914455)

You will be able to alternatively use:
GPFILTff.msp=Office 2003-beveiligingsupdate (KB914455)|Security Update for Office 2003 (KB914455)

[wimb]

The Attached file is the Registry Patch produced by Microsoft Update for
the Dutch version of Office Professional 2003 on April 18th 2007

I did the uninstall of Office first and then a fresh Office Setup and let Microsoft update produce the Registry Patch. So there is no Integrator involded in making the given Registry Patch file !

[wimb]

Siginet, I will make another Registry Patch file, where I will manually install the hotfixes. I understand now that the manual install of the hotfixes is required for your database, although the result will be different from what Microsoft Update is producing.

It would be simpler if all language differences in the DisplayName in the registry could be avoided by simply using in the registry only the English naming.

[Mandarin]

Signet - another failure unfortunatley - this is using the new office update pack and the new office integrator v0.4. It was running nicely, integrated SP2 with no problems and was working its way through the hotfixes in the update pack then it just stopped for ages before throwing up the attched error message.

Log file included for you to take a look at too.;)

[Siginet]

I know for some reason my host (Dreamhost) was going up and down periodically today. :( That may be the reason why. In v0.5 I'll make sure to ping my site before accessing it to download the entire database to the hard drive.

It looks as if it were trying to query the db when it had an issue, according to the log.

Please try again and see if it still has issues.

Thanks for the help.

[Siginet]

Siginet, I will make another Registry Patch file, where I will manually install the hotfixes. I understand now that the manual install of the hotfixes is required for your database, although the result will be different from what Microsoft Update is producing.

It would be simpler if all language differences in the DisplayName in the registry could be avoided by simply using in the registry only the English naming.

I understand the result will be different... but that is a bug on MU side. I'd rather have people know that when they use the office integrator that the correct entries are placed in the registry. ;) Their own hotfix lists it in another language like it should... but MU is incorrect. In v0.5 I'll go ahead and add the extra option of getting the english reg entrie if the current language fails. I reccomend that HotPack creators try their best to submit the correct language for their reg files though. ;)

It should be simple to do with what you have...
You allready have the correct info in your ohotfix.ini. You can simply just replace the english string in the reg file with the Dutch one instead of installing each hotfix. Or if you want to use the english info in your hotpack you can make sure the english is in your ohotfix.ini file when you create it. Because whatever is in your ohotfix.ini is what is used to get the reg entry from the database. As long as the info in the database matches then all is well.

[wimb]

First I have disabled Microsoft Update and Office 2003 was uninstalled.
Then after Setup of Office Prof. 2003 NL, SP2 was installed manually.
Finally the for the Dutch version required 17 Hotfix Updates were installed manually.

April 19th, 2007
Hotfixes: KB894542, KB907417, KB914455, KB919029, KB920103, KB920813, KB923097,
KB924085, KB924424, KB925251, KB929057, KB929058, KB929060, KB929064, KB932330,
plus extra for Dutch version: KB913571, KB924886

Attached you will find the Registry Patches thus obtained for the Dutch version of Office 2003. :)

[Siginet]

Nice job Wimb! I am sure many will appreciate it. :D

So do you need any hosting for your HotPack?

[wimb]

Using the Integrator 0.4 gives an Error after Integrating SP2:

Warning! Query "AllPatches" Was not found in the DB or the DB was unreachable.

The AutoIt Error Info and the log are given as Attachment.

Before presenting the Dutch HotPack, I would like to have it first tested on my own computer. That was not possible, because of the given Error :(

I hope you can solve this issue :)

[wimb]

And the log as txt file ...;)

[Corkey]

I get the same error as Wimb.

My log file also attached

(Trying to slipstream SP2 into Office on a Win XP SP2 machine with more than enough disk space)
I did notice an error on initial load of the Integrator program - it was missing a .dll (sorry, missed the name) but when I restarted the prog, the mesage did not appear again.

regards
Corkey

[wimb]

I did notice an error on initial load of the Integrator program - it was missing a .dll (sorry, missed the name) but when I restarted the prog, the mesage did not appear again.



Here the same occurred:

myodbc3i.exe cannot finf MSVCR71.dll (at first run only)

[Siginet]

Are you guys still getting these errors? It may be that my site was down. :( As for the dll error. Searching google for MSVCR71.dll shows me a lot of programs that have issues with MSVCR71.dll for weird reasons. :( Mostly java stuff.

I seen a couple sites that recommend having the file placed in system32 if it does not allready exist. So that is what I will do in v0.5. MSVCR71.dll is actually needed for a lot of stuff so it won't be bad for me to include it. I didn't see any real reason for the errors though.

Sorry guys. I'll try to get a release out shortly.

[wimb]

OK, thanks a lot. We are looking forward for version 0.5

The interface of version 0.4 is very nice.

[mara-]

Hi Siginet!

I tested 0.4 version and integration went perfect, no any error. But I must ask you something. Maybe it is stupid question, but here it is: When I install office with integrated hotfixes do I manualy need to merge KB_Keys.reg or it will be merged automatically?

[Siginet]

you manually add them for now. Untill I can find a way to have it done automatically. :( Anybody have any ideas?

[wimb]

Unattended Install of Office 2003 made with ork.exe is described here:

http://unattended.msfn.org/unattended.xp/view/web/50/SESSID=51538ad02653852efd94da378b4f62d2/

One can add to the Office 2003 Batch Command a rule for automatic installation of the KB_Keys.reg:

start /wait regedt32.exe /S KB_Keys.reg

Instead of the Batch Command, one can use WPI for Unattended Install: http://wpiw.net/

[wimb]

After using ork.exe for preparing Unattended Install of Office 2003,
a file OF3SP_UNATTENDED.MST is obtained in the OF3_SLIP folder with your Slipstreamed Office 2003 Setup files. :cool:

Copy the OF3_SLIP folder in the folder Install of your WPI setup.
Now in the WPI folder WPIScripts you can edit file config.js and make a new entry for Office 2003.

Add the following rules to the config.js file:
cmd1[pn]=['%wpipath%\\Install\\OF3_SLIP\\setup.exe TRANSFORMS=OF3SP_UNATTENDED.MST /qb-'];
rega[pn]=['%wpipath%\\Install\\OF3_SLIP\\KB_Keys.reg'];

In this way the KB_Keys.reg file is automatically installed after the Setup of Office 2003. ;)

Running the WPI.hta file gives the desired result ! :)

[wimb]

The Office Integrator 0.4 does not install MSVCR71.dll in the C:\WINDOWS\system32 folder, so that the database was unreachable.

This problem was overcome bij installing mysql_odbc.msi provided in the version 0.1 as a plugin. So people who were just upgrading did not have the problem. But on a fresh XP installation the MSVCR71.dll file was missing.

This explains the ERRORS that we encountered. :D

Now after installing mysql_odbc.msi everything is running properly ! :)

However, in the KB_Keys.reg file that was made I see that the Products code used is 9040110900063D11C8EF10054038389C (= English) in combination with Dutch DisplayName.

The Dutch Products code should be: 3140110900063D11C8EF10054038389C
So there is still some confusion in the Database :???:

[wimb]

Also the All Patches given by the Database is not according to the
All Pathes for the Dutch version of Office 2003 !

[ElSid]

Just tried the integrator, 0.4. Made office (Office, Visio, Project, OneNote, Frontpage) install complete. This was installed in a VM environment with XPSP2 all patches installed (clean XPSP2 no slipstream or RVM integrated). I ran Office Update and SP2 download was requested. I then noticed that I forgot to import the reg files created in the folders :rolleyes: . Imported all regfiles and rebooted. Now the problems:

Office update still requests that I need to install SP2, which was slipstreamed. There are a host of other updates greyed out below it.
Windows update shows 7 required updates (SP2, KB920813, KB929064, KB925251, KB924424, KB919029, KB914455)
Previous manual slipstreams would NOT allow me to update certain components (i.e. outlook junk mail filter) after I slipstreamed. Any one have this problem?:confused:

Hope this helps with debugging.

[Siginet]

If you post your log file I can look into it better. I am thinking it may not have been slipstreamed... because if it wasn't slipstreamed the other hotfixes would have failed to slipstream as well.

@Wimb I am aware of those methods to be able to have the reg file imported... but that would not be an efficient way to include it with the integrator. That would make it so the user would have to manually do that stuff. I need a way from within the normal install that would work.

As for the reg keys not being correct... I was afraid of that. :( That means I have to make a change to our ohotfix.ini to allow us to provide the correct key.

I'm thinking we will have an area to specify, for instance:


[OHotfix]
MessageTitle=Siginet's Office2K3 HotPack April 20, 2007
Office=9040110900063D11C8EF10054038389C
OneNote=9040B30900063D11C8EF10054038389C
Project=9040B30900063D11C8EF10054038389C
FrontPage=9040710900063D11C8EF10054038389C
Visio=9040150900063D11C8EF10054038389C

I am also thinking to add a way for people to be able to rename the .msp files. Just in case there iof the same named .msp files.

For instance:

MSO_Project.msp,MSO.msp=Security Update for Office 2003 (KB929064)
Green = Name used in hotpack.
Red= Original name used used for reg entry.

[wimb]

Providing in the ohotfix.ini file of a HotPack a 3-letter language code (NLD for Dutch Updates), like used by Microsoft to identify their KB-Update files (office2003-KB894542-FullFile-NLD.exe) might be simpler and sufficient for you to provide the correct Products code in the reg keys.

[Siginet]

No that would be much more difficult because then I would have to know every single reg key and put that info direcctly in the OfficeIntegrator.exe. It would be much simpler to ask the HotPack creator to provide the needed info inside the ohotfix.ini. NLD would not give me any specific info on what the reg key is.

[ElSid]

Small issue with the log file. I used the integrator to slipstream each component individually. My last ini file is only for Frontpage.
I am thinking it may not have been slipstreamed... because if it wasn't slipstreamed the other hotfixes would have failed to slipstream as well. When I open word, excel, project ... they all register as SP2:confused: This to me indicates that SP2 was slipstreamed.
For my install, I had my source, SP2 on the D drive, HotPack on the D drive in another folder, and my output to my E drive. Don't know if this matters. I am posting my Frontpage officeintegrator.log, but it doesn't really show anything .

[ElSid]

Didn't realize I had to change the extension from .log to .txt

[Siginet]

According to your log file you never selected any ServicePack file for integration nor did you select any Hotfixes or Hotpacks.


;- 04/18/2007 22:59:02 - Source: "E:\Programs\_XP\Office2003\FRONTPAGE\SETUP.EXE"
;- 04/18/2007 22:59:02 - Destination: "E:\SLIPSTREAM\Office2003\FRONTPAGE"
;- 04/18/2007 22:59:02 - ServicePack: ""
;- 04/18/2007 22:59:02 - Hotfixes/HotPacks: ""

The only thing that was done according to this log is you created an admin install of Microsoft Office FrontPage 2003.

[wimb]

No that would be much more difficult because then I would have to know every single reg key and put that info direcctly in the OfficeIntegrator.exe. It would be much simpler to ask the HotPack creator to provide the needed info inside the ohotfix.ini. NLD would not give me any specific info on what the reg key is.

Ok, people can find the Products code in the registry Patches provided by Microsoft Update
and use this in the ohotfix.ini file of the HotPack,
so that you can use this value automatically in the database for making the correct KB_Keys.reg file.

The value of the AllPatches key provided by the database refers to 14 Patches ( from which only 6 are correct )
instead of referring to the 23 Patches given for the Dutch version of Office 2003.

[ElSid]

Frontpage does not have any service packs. That was the last thing I integrated/ran through the integrator to include my serial #. I'll re-run it again next week, I'm going on vacation for the first time in 2 yrs. :mrgreen:

[Siginet]

The AllPatches section is going to be changed. The way it does it now it only does it for looks. ;) I have to come up with a method that will add each patch to the AllPatches reg entry as it integrates them. But the issue is... if someone does not integrate all of the patches to their Office files then not all of the patches will be added and that can cause the reg key to be overwritten without all of the patches in the AllPatches section. As far as I can tell... the AllPatches entry doesn't do anything anyways. Except list the patches that have reg entries.

[wimb]

Good to hear that you are looking already for a good solution for the AllPatches entry. :)

My idea was also that this entry is not the most important one, but anyway it is better that the AllPatches value corresponds to the reg keys for the actually integrated Patches. :cool:

[Siginet]

Great news! I figured out how to find out what key is used in the registry depending on the OS Language. :)

What I mean is this:

In an english reg file we would use:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C
In Polish we would use:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\5140110900063D11C8EF10054038389C
In Dutch we would use:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\3140110900063D11C8EF10054038389C

The keys in red are what I am talking about.

The first 6 characters are what is important. The rest is the same on any.

It took me all day to figure it out. :(

The 5th and 6th characters were easy. They represent the part of the office suite. 11 = Office, 15 = Visio, 71 = Frontpage, 1A = OneNote, and B3 = Project.

The first 4 characters were the tricky part. Once I figured it out I felt stupid. All it is is the OS Language code... backwards.

OS Lang codes can be found here:
http://www.microsoft.com/globaldev/reference/win2k/setup/lcid.mspx

So with this in mind here is what all of the english keys are:
Office=9040110900063D11C8EF10054038389C
Visio=9040150900063D11C8EF10054038389C
FrontPage=9040710900063D11C8EF10054038389C
OneNote=90401A0900063D11C8EF10054038389C
Project=9040B30900063D11C8EF10054038389C

Polish Keys are:
Office=5140110900063D11C8EF10054038389C
Visio=5140150900063D11C8EF10054038389C
FrontPage=5140710900063D11C8EF10054038389C
OneNote=5140B30900063D11C8EF10054038389C
Project=5140B30900063D11C8EF10054038389C

Dutch keys are:
Office=3140110900063D11C8EF10054038389C
Visio=3140150900063D11C8EF10054038389C
FrontPage=3140710900063D11C8EF10054038389C
OneNote=3140B30900063D11C8EF10054038389C
Project=3140B30900063D11C8EF10054038389C

so now what I plan on doing is have the office integrator find the current OS Lang during integration and reverse it and use it in the key. I also plan on making a SETUP_OI.EXE to be used instead of the original SETUP.EXE. This SETUP_OI.EXE will run the original setup.exe and then it will import the KB_Keys.reg file with the current OS Lang being used in the keys.

If this works the way I think it will there will not be a need to have the keys represented in the ohotfix.ini file in your hotpacks. ;)

[wimb]

Siginet, this is all Great News ! :D

Your proposal is an elegant solution to be able to provide the correct registry keys for each Langugage and for all Products. :D

Also your idea for making a SETUP_OI.EXE file, so that after running SETUP.EXE the KB_Keys.reg are automatically imported, is very interesting :D

[wimb]

First I have disabled Microsoft Update and Office 2003 was uninstalled.
Then after Setup of Office Prof. 2003 NL, SP2 was installed manually.
Finally the for the Dutch version required 17 Hotfix Updates were installed manually.

April 19th, 2007
Hotfixes: KB894542, KB907417, KB914455, KB919029, KB920103, KB920813, KB923097,
KB924085, KB924424, KB925251, KB929057, KB929058, KB929060, KB929064, KB932330,
plus extra for Dutch version: KB913571, KB924886

Attached you will find the Registry Patches thus obtained for the Dutch version of Office 2003. :)

On April 23rd, 2007 a revision of the Registry Patches for the Dutch version of Office 2003 was made ( see Attachment ). :cool:

Only the DisplayName has changed in 5 occurrences, and all DisplayName entries are now in Dutch. :D

OLD: "DisplayName"="Update for Outlook 2003: Junk E-mail Filter (KB932330): OUTLFLTR"

NEW: "DisplayName"="Update voor E-mailfilter voor ongewenste post van Outlook 2003 (KB932330): OUTLFLTR"

Further: 4x "voor" instead of "for"

[Siginet]

All of the reg entries you submitted were allready in the database. ;)

Expect Office Integrator v0.5 out later today, :D

The database is downloaded to the hard drive upon opening OfficeIntegrator.exe now.
It automatically checks the OS Lang to get the key info for each registry entry.
It now places the KB_KEYS.REG file inside FILES\SETUP so that it doesn't reside at the root.
It creates a new SETUP_OI.EXE that will be used instead of the original setup.exe.
The new SETUP_OI.EXE will run the original setup.exe and it will pass any parameters as well. It will install KB_KEYS.REG and it will create the AllPatches reg entry as each entry is installed. It will not overwrite any AllPatches entries. It specifically adds new entries to the list.
I've added more to the log file so that it will help better when trying to debug any errors.

[odyn1982]

I tested new 0.5 Integrator and found 3 errors:
1. Only 9 of 18 hotfixes entries are in "KB_KEYS.REG" but Database file is full. Reg file in "Setup" folder looks like this:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\92B139F9099A8A74CAC13CAA075ABBF5]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu Office 2003 (KB925251): EUROTOOL"
"MoreInfoURL"="http://support.microsoft.com/kb/925251"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\D326130434CA14B40AFD857479196848]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu Excel 2003 (KB929058): EXCEL"
"MoreInfoURL"="http://support.microsoft.com/kb/929058"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\D71BB1914BB79E34C889A789E18FAA34]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu InfoPath 2003 (KB920103): INFOPATH"
"MoreInfoURL"="http://support.microsoft.com/kb/920103"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\79757D0B9FCD24846B9CA229B82718B0]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu Office 2003 (KB919029): LCCWIZ"
"MoreInfoURL"="http://support.microsoft.com/kb/919029"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\94AB56D3199EF3945B27012AF54C1EB1]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu Office 2003 (KB924886): MSGRGE32"
"MoreInfoURL"="http://support.microsoft.com/kb/924886"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\221F08EC4C174F84B9EFA094EB0F056A]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu Office 2003 (KB924886): MSSP3GE"
"MoreInfoURL"="http://support.microsoft.com/kb/924886"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\D78E1F6C1E3F478479CE8FD7BAD68687]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu Office 2003 (KB907417): OTKLOADR"
"MoreInfoURL"="http://support.microsoft.com/kb/907417"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\F81D2D10124B54D46986B33C209AA1DC]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu PowerPoint 2003 (KB929060): POWERPNT"
"MoreInfoURL"="http://support.microsoft.com/kb/929060"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patch es\BC6FC0DDCBDA26043BC05DB3128AA3BF]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000000
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20070423"
"DisplayName"="Aktualizacja produktu Office 2003 (KB923097): STLIST"
"MoreInfoURL"="http://support.microsoft.com/kb/923097"
2. Entries are for english office not polish. I'm using eng XP and polish Office. I think that Integrator checks only OS not Office.

3. When I run SETUP_OI.EXE I've got AutoIt error. See attached image

[Siginet]

I will look into this.

OK... so then I need to figure out how to get the Lang code of the Office version. :( I thought it was looking for the OS Lang. :(

Hmmm... I wonder why it did not find all of the reg entries?

[wimb]

Version 0.5 of the OfficeIntegrator was tested for the Dutch version of Office 2003. :cool:

I have found two Errors, documented in the Attachment.

1. The first entry OTKLOADR.msp of my NLD Hotpack does not occur as an entry in the KB_KEYS.REG file.
2. The same AutoIt Error as found by odyn1982, occurred when running SETUP_OI.EXE

The KB_KEYS.REG entries as far as I have seen are OK for the Dutch version of Office 2003.
This version 0.5 of the OfficeIntegrator is a great improvement.
I hope you can remove the final Errors :)

[mara-]

Integration went without any error!
But I'm getting same error as two members posted before me, when runing SETUP_OI!

Log and screenshot in attachement

[wimb]

Great news! I figured out how to find out what key is used in the registry depending on the OS Language. :)

The 5th and 6th characters were easy. They represent the part of the office suite. 11 = Office, 15 = Visio, 71 = Frontpage, 1A = OneNote, and B3 = Project.

The first 4 characters were the tricky part. Once I figured it out I felt stupid. All it is is the OS Language code... backwards.

OS Lang codes can be found here:
http://www.microsoft.com/globaldev/reference/win2k/setup/lcid.mspx

So with this in mind here is what all of the english keys are:
Office=9040110900063D11C8EF10054038389C
Visio=9040150900063D11C8EF10054038389C
FrontPage=9040710900063D11C8EF10054038389C
OneNote=90401A0900063D11C8EF10054038389C
Project=9040B30900063D11C8EF10054038389C

Polish Keys are:
Office=5140110900063D11C8EF10054038389C
Visio=5140150900063D11C8EF10054038389C
FrontPage=5140710900063D11C8EF10054038389C
OneNote=5140B30900063D11C8EF10054038389C
Project=5140B30900063D11C8EF10054038389C

Dutch keys are:
Office=3140110900063D11C8EF10054038389C
Visio=3140150900063D11C8EF10054038389C
FrontPage=3140710900063D11C8EF10054038389C
OneNote=3140B30900063D11C8EF10054038389C
Project=3140B30900063D11C8EF10054038389C

;)

The OneNote code in Polish and Dutch should contain 1A instead of B3 ;)
A typo Error at the 5th and 6th character, I think.

[wimb]

According to MSFN site:
http://unattended.msfn.org/unattended.xp/view/web/48/

the Manual Integration of SP2 involves two commands:

msiexec /p C:\SP2\MAINSP2ff.msp /a C:\Office2003\PRO11.msi SHORTFILENAMES=TRUE /qb
msiexec /p C:\SP2\OWC11SP2ff.msp /a C:\Office2003\OWC11.MSI SHORTFILENAMES=TRUE /qb

A command similar to the first command is visible in the log file of the OfficeIntegrator,
but something like the second command is not mentioned there.

Is the second command only absent in the log file, or is such a second command not executed by the OfficeIntegrator ?

[Siginet]

Hmm... it looks like you are right. I do have code in there to execute the OWC*.msp file though. For some reason it is completley bypassing it. :( I'll have to find where the code is messed up. Shouldn't be hard.

The only part that is gonna be hard is finding out the language of office. :( If guys can help me that would be great. I need to know what file(s) in the Office install source I can look at to find out what language code it uses.

[Siginet]

The only part that is gonna be hard is finding out the language of office. :( If guys can help me that would be great. I need to know what file(s) in the Office install source I can look at to find out what language code it uses.

I think I have an idea how I can accomplish this. Basically the SETUP_OI.exe file will check the registry and read a reg key on the system just after office is installed. It will be able to find the correct language. Then setup_oi.exe will re-write the KB_KEYS.REG file with the correct settings before adding them to the registry.

hopefully I will have a release put together later today. ;)

[wimb]

According to MSFN site:
http://unattended.msfn.org/unattended.xp/view/web/48/

the Manual Integration of Updates involves a command like:

FOR %%f IN (*.msp) DO msiexec /p %%f /a C:\OF3_SLIP\pro11.msi SHORTFILENAMES=TRUE /qb

whereas in the OfficeIntegrator log I see commands like:

;- 04/24/2007 06:37:03 - msiexec /passive /update "C:\DOCUME~1\UserA\LOCALS~1\Temp\Working\EXCEL.msp" /a "C:\OF3_SLIP_704\PRO11.MSI" /li! "C:\DOCUME~1\UserA\LOCALS~1\Temp\Working\EXCEL.msp. log"

The switch /update is not used in the Slipstream command of MSFN,

and SHORTFILENAMES=TRUE is added in the MSFN command :???:

[Siginet]

new release. :D

[wimb]

Siginet, Congratulations with version 0.6 of the OfficeIntegrator. :D

Almost perfect, but for the Registry Patches I am still missing the entry for OTKLOADR.msp ( the same Error as in version 0.5 ). :(

Is it possible that the absence of SHORTFILENAMES=TRUE in the command for integrating the Updates can cause this Error ?

Or is it a matter of timing and that something like start /wait can help ...

Office 2003 NL as far as I have seen is running perfect ! :)

As Attachment I sent you the log file ;)

My HotPack for the Dutch version of Office 2003 is ready for Upload !
How and where can I deliver it ?

[odyn1982]

Only one error, the same as in version 0.5; missing 9 reg entries.

[odyn1982]

Log:

ADDED:

Entry Added: Aktualizacja produktu Office 2003 (KB925251): EUROTOOL
Entry Added: Aktualizacja produktu Excel 2003 (KB929058): EXCEL
etc.

MISSING:

Integrating: Aktualizacja zabezpieczeń produktu Office 2003 (KB914455): GPFILTff
Integrating: Aktualizacja produktu Filtr wiadomości-śmieci programu Outlook 2003 (KB932330): OUTLFLTR
etc.

Missing entries founded in database:

"DisplayName"="Aktualizacja zabezpieczen produktu Office 2003 (KB914455): GPFILTff"
"DisplayName"="Aktualizacja produktu Filtr wiadomosci-smieci programu Outlook 2003 (KB932330): OUTLFLTR"
Database:
So when I compare them I saw that polish symbols (ą, ę, ł, ń, etc.) are missing. Hoftixes names are incorrect in database so they can't be added to final KB_KEYS.OI.

PS. Today first time I installed Office via SETUP_OI.EXE with unnatended.mst. All hotfixes were integrated and Office Update doesn't show any new.

[Siginet]

OK. Thanks for figuring that out. What you can do then is change your ohotfix.ini to be the same as it is in the database and that should work.

As for the Dutch key that isn't working... maybe it isn't in the database?

[odyn1982]

It won't be good solution because reg entries still be incorrect :( We must have correct, polish names so the database should be changed. That what I think ;)

[Siginet]

For now it will work if you change the ohotfix.ini to either the english entries or so that they match what is in the database now. Because I need to research and find out what would be a good setting for the database to be compatable with all characters. what is put into the registry doesn't seem to make a difference... so for now it will be fine. I will look into changing it .. but it may take some time. We have allready confirmed that Microsoft Update actually places english entries into the registry anyways. Also the SETUP_OI.EXE will make sure that your registry entries are placed in the correct area of your os.

I agree... it needs to be correct in the database... but I may not get a chance to fix that for a little while. I have a computer business to run and it has gotten very busy. Plus I need to begin working on the next RVM Integrator and a Maintenance program me and Vier have been creating.

[wimb]

Almost perfect, but for the Registry Patches I am still missing the entry for OTKLOADR.msp ( the same Error as in version 0.5 ). :(


The Error is caused by a wrong entry in the SiginetSoftware.com.DB database for the Dutch DisplayName of OTKLOADR.msp

In the database is written:
"DisplayName"="Office 2003-beveiligingsupdate (KB907417): OTKLOADR"

whereas it should be:
"DisplayName"="Update voor Office 2003 (KB907417): OTKLOADR"

After changing the ohotfix.ini file of my HotPack, so that it corresponds to the incorrect value in the database,
the OfficeIntegrator was able to process all the registry entries.

Now Office 2003 NL is running and MicrosoftUpdate is satisfied :D

[Siginet]

That's great news. :D

I was trying to figure out how to setup the database to allow different characters from languages like polish but no matter what I tried it didn't work. So for now when anyone creates a HotPack try to make sure there are no crazy characters in the reg file for the database. ;)

If you need hosting for your hotpacks let me know.

[wimb]

That's great news. :D

If you need hosting for your hotpacks let me know.

My HotPack for the Dutch version of Office 2003 is ready for Upload !
How and where can I deliver it ?

[Siginet]

Just go ahead and upload it anywhere like rapidshare or anything and I'll put it on my hosting.

[wimb]

This HotPack will integrate all hotfixes for the Dutch version of Office 2003.

April 27th, 2007
Hotfixes: KB894542, KB907417, KB914455, KB919029, KB920103, KB920813, KB923097,
KB924085, KB924424, KB925251, KB929057, KB929058, KB929060, KB929064, KB932330,
plus extra for Dutch version: KB913571, KB924886

Download Link: Office 2003 HotPack - Dutch 7.04.27 (http://rapidshare.com/files/28148059/Office2003-HotPack-NLD-704.rar.html)

Siginet, will you please change the value for the Dutch DisplayName for the OTKLOADR.msp hotfix in your database:

correct value: "DisplayName"="Update voor Office 2003 (KB907417): OTKLOADR"

so that the database corresponds to my Dutch HotPack and the Integrator can run Error Free.

A new Thread for Downloading this HotPack was started.

Enjoy !

[Siginet]

Your entry is now fixed. ;)

[wimb]

Thank you for fixing the Dutch entry for OTKLOADR in the database :D

By the way, leaving the Integrator with Cancel button gives an ERROR.
The DoExit function is Unknown ( see Attachment ).

[Siginet]

Thank you for fixing the Dutch entry for OTKLOADR in the database :D

By the way, leaving the Integrator with Cancel button gives an ERROR.
The DoExit function is Unknown ( see Attachment ).

Woops... I forgot to fix that one. It's fixed now.

It will be in v0.7. ;)

[MrAnon]

First, thanks for all the hard work you're doing for us! And thanks to the folks helping you so much!

My request is that you stop OI from pinging your mySQL server and just try to connect. The reason is that some network administrators (like mine....*sigh*...folks with 10-year old CCNAs should not be let near MS Server 2003 networks...) block ICMP activity but not actual traffic. The result is that I can't ping, but I can connect. Since OI aborts the database access if a ping doesn't go through, I can't get an update.

Much obliged! We've got 200+ PC's comprising our school's LAN and tools like OI are a godsend when trying to keep them updated. Between Office, Windows and the apps, doing manual updates is a full-time job in iteself!

Dean

"Who knows what eeeeevvvviiiilllll lurks in the hearts of Micro$oft?"

[Nameless Mofo]

My request is that you stop OI from pinging your mySQL server and just try to connect. The reason is that some network administrators (like mine....*sigh*...folks with 10-year old CCNAs should not be let near MS Server 2003 networks...) block ICMP activity but not actual traffic. The result is that I can't ping, but I can connect. Since OI aborts the database access if a ping doesn't go through, I can't get an update.


I have the same issue, the integrator complains that it can't ping so it refuses to download the reg data file.

One other request for 0.7: can the integrator window tail the log file like the RVM
integrator does during integration? The bubbles down in the tray is a nice touch,
but if a log file widget could be there it'd be cool. Maybe it's not possible given
the integrator's reliance on M$ msi installer stuff, but figured it's worth asking.

Cool program though, much better than using M$ update for half a day!

[Mandarin]

Not been able to do some testing for a while (since 0.4 actually) but just ran ver 0.6 with the hotfix pack and it has gone through perfectly with no errors.
I don't get any error trying to close the office integrator with the cancel button or the "X" - it just doesn't close. If I right click the system tray icon and pick exit it exits with no issues.
Will give 0.7 a go when it comes out and give some more feedback.

[benners]

Just started using this program and it works great, thanks Siginet. I would just like to suggest a few improvements\ideas.

1. Save the settings to an ini file like the RVMIntegrator.
2. Enable the OI to run unattendedly like RVM, add options to the OI for the serial, a tick box to agree to the MS license, these can then be passed to setup.exe when the integrate button is pressed.

I have skimmed\read through the posts and haven't seen these requests so thought I would ask.

Thanks again

[Siginet]

@Everyone I will fix the ping issue. I didn't even think of that... sorry.

@Benners Both of your ideas are definatly in the plan. I just haven't implemented it yet because I was trying to get the program functioning to it's full potential first. ;) You can expect those features to be in the next release.

[benners]

@Benners Both of your ideas are definatly in the plan. I just haven't implemented it yet because I was trying to get the program functioning to it's full potential first. ;) You can expect those features to be in the next release.

Nice, thanks. When you are happy with the programs performance and if you are not to busy what about also checking in the script directory for your hotfix rar file and auto adding it to the "Select Hotfixes" box, maybe check the version number at start up along with the registry entries?.

[Nameless Mofo]

Two more observations/requests:

1. I get the same error as wimb when I exit via the Cancel button, ie. DoExit: Unknown function name. The window title says "AutoIt error".

2. Maybe I don't understand the integration process well enough, but is it possible to make the hotpack self-sufficient, so it doesn't have to access the database? Some posts indicated there is reg data in ohotfix.ini, but database access still required? :confused:

[Siginet]

1. Allready fixed in the next release. ;)

2. The database is needed. The ohotfix.ini has the info needed to get the registry info from the database but it does not have the registry info in it.

[Nameless Mofo]

Hi Siginet, one more question: can the integrator be run piecemeal? ie. can I create the admin install in one run, exit out, bring the integrator back up, apply the SP, exit out, bring it back up, apply the hotpack?

Also, (ok 2 more questions) what stage(s) need the database connection? Just the hotpack, hotpack+SP, etc?

[ElSid]

Wow,
Siginet, you are the man, a version a week (since my last post) :cool: (0.4 to 0.6)
I am going to give this a go again this weekend. :rolleyes:

I ran into a slipstream bug and believe it to be Microsofts issue. Has ANYONE run into the Outlook "Junk E-mail Filter" error? In short, if I manually slipstream the "Junk E-mail Filter", Office Update and Windows Update will NOT allow me to update to newer filters as they become available.

Has anyone run into this problem using the integrator? :confused:

[Mandarin]

In my earlier reply I said everything worked perfectly, which was based on running the Office Integrator and then testing in VM Ware.

But today I have tried burning an ISO and installing on a real laptop and get an error about OPA11.bak not being available. It then asks me to put the souce media in the drive (which of course it is already in!!).

Seems that OPA11.bak is the activation details for Office 2003 which is odd cos I use a volume license version of O2K3 which does not require activation.

I tried a version with just SP2 slipstreamed and get the same error.

I tried the version that I made using v0.4 of the Integrator and that also throws up the same error.

It may be something to do wtih the way I have made the CD? Or is it something that others have experienced and not yet reported?

If I ignore the file error and let the install continue it completes fine but when I try to open Word it then tells me that the file is missing and just goes into an endless loop looking for it even when I point it back to the install CD. Pointing it back to my original souce CD doesn't help either which kind of proves it is not an integrator problem as such but a problem with the process I am using.

Any ideas how to get round this cos otherwise I have a great program to slipstream SP2 and add all the new hotfixes but end up with something that can't actually be installed.

[Siginet]

@Namless Mofo Yes the OI can definatly do that. Once you have your admin install source you no longer need to point to the setup.exe anymore. So leave the first input box blank. Then the OI will just perform the slipstream and/or Hotfixes/HotPack seperately. You can also add more hotfixes/hotpacks later as they come out. ;)

@Elsid I have not experienced that issue myself.

@Mandrin I am sure this is not caused by the integrator. I have never heard of this myself. I am thinking somewhere along the line you must have messed up your source. Is it possible to go back to your original source and start fresh? Try your original and use the OI for everything.

[Mandarin]

@Mandrin I am sure this is not caused by the integrator. I have never heard of this myself. I am thinking somewhere along the line you must have messed up your source. Is it possible to go back to your original source and start fresh? Try your original and use the OI for everything.

I think I agree Signet.
I did use the OI for everything in one go though so it is probably something odd about the system I used. The first CD I tried used ver 0.4 of the OI and I pointed it to my folder where I had downloaded all 15 of the individual hotfixes.

The second CD used ver 0.6 and the updated version of the office update pack.

I should be able to test it on another real system and see what happens.

Odd that they both work perfectly in VM Ware though.

[rhumes]

First off, thanks for this awesome tool! It looks like it will be a huge time saver for me....

Unfortunately, I am having the ping issue described earlier in the thread, as well.

I don't mean to sound pushy at all, but do you have an ETA on when you will release the version that takes out the ping test? Just a ballpark figure is more than adequate.


Thanks again!

[JanSamson]

Sofar this tool has already proofen worth..and I have seen the progress from the 0.3 version. Now the info states to run setup_oi.exe to install the Office 2003. But how to use this installation by installing the software via a GPO and installation of the software by the MSI and a MST to configure settings for outlook?

[Siginet]

setup_oi.exe will pass all parameters given to it to the original setup file. So The same way you would do it with the original setup file is how you would do it with setup_oi.exe

ETA for next release will be as soon as I can. Probably any time within this week. ;)

[JanSamson]

Thanx for your quick response, but I am not sure if I understand your explanation. As far as I can tell the packages I can use in a software rollout via a GPO in Windows Server 2003 are allways via the MSI installation file, and a MST if needed. Any suggestions here how to addres the installation to use setup_oi.exe instead :)

[HJW]

Hey Siginet,

What about HotfixPacks for Office2007 too. So making the office integrator multi-office compitable. Office07 is a much easier concept so I guess not very hard to add support for it. Just copy the contents of the pack to the Updates directory..
And I believe all updates by microsoft for office07 are multilanguage compitable ;)

gr
HJW

[TheSickman]

There are updates

KB933666 replacing KB929058
KB933669 replacing KB929060
KB934180 replacing KB929064
KB934181 replacing KB929057
KB934708 replacing KB932330


when i do on clean install with just sp2 slipped

updates are

KB933666
KB934181
KB934180
KB934708
KB933669
KB920813
KB925251
KB924085
KB924886
KB924424
KB919029
KB923097
KB894542
KB920103
KB914455
KB913571
KB907417


when i do update office2003 Dutch

see attachement for reg

i made Office2003-HotPack-NLD-905.rar

here is link

can be used as you updated database

http://rapidshare.com/files/30479304/Office2003-HotPack-NLD-905.rar.html

[wimb]

The ohotfix.ini file in the Office2003-HotPack-NLD-905.rar of TheSickman
has an incorrect value for the MessageTitle of the EXCEL.msp patchfile.

The correct value as derived from the office2003-KB933666-FullFile-NLD.exe download is:
EXCEL.msp=Excel 2003-beveiligingsupdate (KB933666)

TheSickman's Attachment Patches is missing the entry for sp2 update
"Office 2003 Service Pack 2 (SP2): MAINSP2ff" and the MessageTitle's in his file are mostly in English,
as given by the automatic update's of Microsoft Update.

[wimb]

For a Clean System without any history of Office 2003, when using SETUP_OI.EXE
there is in the Registry no value produced for the All Patches.

On a system where Office 2003 was first Uninstalled, SETUP_OI.EXE produces the correct value for the All Pathes entry !

In both cases the entries for the Update Patches are correctly produced by SETUP_OI.EXE

In other words the value for the All Patches entry is missing, when SETUP_OI.EXE is used on a Clean System ! ;)

[TwoJ]

Great news! I figured out how to find out what key is used in the registry depending on the OS Language. :)

What I mean is this:

In an english reg file we would use:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C
In Polish we would use:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\5140110900063D11C8EF10054038389C
In Dutch we would use:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\3140110900063D11C8EF10054038389C

The keys in red are what I am talking about.

The first 6 characters are what is important. The rest is the same on any.

It took me all day to figure it out. :(

The 5th and 6th characters were easy. They represent the part of the office suite. 11 = Office, 15 = Visio, 71 = Frontpage, 1A = OneNote, and B3 = Project.

The first 4 characters were the tricky part. Once I figured it out I felt stupid. All it is is the OS Language code... backwards.

OS Lang codes can be found here:
http://www.microsoft.com/globaldev/reference/win2k/setup/lcid.mspx

So with this in mind here is what all of the english keys are:
Office=9040110900063D11C8EF10054038389C
Visio=9040150900063D11C8EF10054038389C
FrontPage=9040710900063D11C8EF10054038389C
OneNote=90401A0900063D11C8EF10054038389C
Project=9040B30900063D11C8EF10054038389C

Polish Keys are:
Office=5140110900063D11C8EF10054038389C
Visio=5140150900063D11C8EF10054038389C
FrontPage=5140710900063D11C8EF10054038389C
OneNote=5140B30900063D11C8EF10054038389C
Project=5140B30900063D11C8EF10054038389C

Dutch keys are:
Office=3140110900063D11C8EF10054038389C
Visio=3140150900063D11C8EF10054038389C
FrontPage=3140710900063D11C8EF10054038389C
OneNote=3140B30900063D11C8EF10054038389C
Project=3140B30900063D11C8EF10054038389C

so now what I plan on doing is have the office integrator find the current OS Lang during integration and reverse it and use it in the key. I also plan on making a SETUP_OI.EXE to be used instead of the original SETUP.EXE. This SETUP_OI.EXE will run the original setup.exe and then it will import the KB_Keys.reg file with the current OS Lang being used in the keys.

If this works the way I think it will there will not be a need to have the keys represented in the ohotfix.ini file in your hotpacks. ;)

Hi Siginet

Thanks for this post, this is great to figure out, but i have something to add to this. I have just done an upgrade Office 2003 Professional edition and i get the following registry code;
9040111900063D11C8EF10054038389C
It seems that the first 7 can be different, the 7th is a 1 instead of the normal 0.
I can only imangine this seems to indicate that this is an Upgrade version instead of a normal retail, OEM, VLK version that doesn't need a previous office version.
I was wondering if you know any way of verifing this information?

Thanks

[Siginet]

Well... the only way we can verify is if more people post different variations. I don't think the office integrator currently works on upgrade versions anyways. Does it? Can you create an admin install with the upgrade version?

[TwoJ]

I was going to post a more complete post on the subject - hopefully later, normally the answer would be no, you would get the error;
"Creation of administrative installation images is only supported in enterprise versions of microsoft office 2003"

But;
i did find a post on msfn on how to modify the msi file (pro11n.msi in this case) with ORCA to switch certain values which then will allow an administrative install point. After that it is possible to slipstream the installation point, and that is reflected in the Office update stating that no updates are need. However microsoft update only verifies through the registry so i wanted to enter the registry values to indicate that these updates are in fact applied.

This is what brought me to the fact that the key is slightly different from the normal one posted, the 0 instead of 1 at the 7th location. However if you google 9040111900063D11C8EF10054038389C, you will see that it is a key that is posted a few places but i can't see anywhere where people talk about which version.

I guess i can try a normal 2003 install and an upgrade and see if i can re-verify that these are seperate keys.

Edit:
I found this website from microsoft for office xp a little while ago;
http://support.microsoft.com/kb/814087
If it keeps the same structure the first 7 numbers seem to be the ones to determine the version
again the first 4 as siginet was able to find are the language
the next 2 are the version
and the 7th number is a retail (1) or Enterprise (0)
I will try office 2003 with a retail version or OEM and see what key i get

[TwoJ]

Well i believe that 7th digit follows the same structure as indicated for office xp on that website,
The 1 indicates a retail, or OEM, or Upgrade version or basically a non-enterprise version.
The 0 indicates an enterprise version
Probably the reason why the 0 appears here for slipstreaming is because the 1 versions are "officially" not able to create an administrative installation point (/a), hense they cannot "officially" be slipstreamed.

So siginet if you are planning that the integrator can slipstream a non-enterprise office version it will need the patches to be applied at that different key (the 1 instead of the 0).

As i mentioned i have taken an upgrade CD and created an administrative installation point, thanks to the msfn post, i have been able to slipstream it, persumably it can also be transformed but i have not attempted to do that (yet?). I can do a network install of the upgrade CD without a prior XP install on the machine.

More later

[Siginet]

If anyone can find a method other than orca to make those changes then please post them. Because I want to do a lot of things with the integrator but I do not want to use orca. If there is some sort of cmdline utility that will do it or if it is possible with hex editing that would be the best method. I will be looking into this more myself once a new release of the RVM Integrator is finished.

[Nameless Mofo]

Hi Siginet, any idea when we can expect a new OI to play with? I read somewhere OI is queued up behind RVMI 1.5, but not sure when that was supposed to happen.

Sorry if this is a taboo question here, it sure is one over on RyanVM's board. ;) :mrgreen:

[Siginet]

RVM 1.5 is coming together pretty well. But it is not clear yet when it will be finished. It shouldn't be much longer. v1.5 has been basically re-written twice due to changes in autoit3's developement.

[dolivas27]

Well i believe that 7th digit follows the same structure as indicated for office xp on that website,
The 1 indicates a retail, or OEM, or Upgrade version or basically a non-enterprise version.
The 0 indicates an enterprise version
Probably the reason why the 0 appears here for slipstreaming is because the 1 versions are "officially" not able to create an administrative installation point (/a), hense they cannot "officially" be slipstreamed.

So siginet if you are planning that the integrator can slipstream a non-enterprise office version it will need the patches to be applied at that different key (the 1 instead of the 0).

As i mentioned i have taken an upgrade CD and created an administrative installation point, thanks to the msfn post, i have been able to slipstream it, persumably it can also be transformed but i have not attempted to do that (yet?). I can do a network install of the upgrade CD without a prior XP install on the machine.

More later

Do you have a link to the msfn post I have tried the one I found there to modify the msi file and still can not get the upgrade cd or the OEM cd to do an administrative install.

Thanks for any help on this I have been working on it for a few days now with no success or if you have any other pointers to make this work that would be excellent.

Thanks,
Dean

[Nameless Mofo]

Sigi, about the ping issue in 0.6: I know you're busy with RVMI, but would it be possible to release an OI 0.61 or something like that with the ping issue fixed?

If not, can I run OI 0.6 on a computer with unrestricted net access, then copy the siginetsoftware.com.db file to the computer that I would be doing the integration on, which has only restricted net access? Will OI 0.6 running on the restricted computer pick up whatever it finds in the copied siginetsoftware.com.db file?

Thanks!

[Siginet]

I think that would work.

[TwoJ]

@dolivas27

Sorry about not posting that info yet - always more to do;
anyways the link to the article is here;
http://www.msfn.org/board/index.php?showtopic=39750&mode=linear
This is the post that really started the ball rolling,
Copy the disc onto your HD, then use ORCA to modify the msi file according to the msfn post. From there you should be able to perform an administrative install point. After that then you can slipstream SPs and hotfixes.
I ended up writing an batch file that installs the slipstream version, updates the registry with the post-sp hotfixes, removes the product key for the install (since non-enterprise versions should all have different product keys).

This can be installed on a computer with no previous version of Office (even for the upgrade version) however the only minor issue is that in my script i do a silent install of XP (VLK) and then a silent install of Office 2003 (Upgrade CD). But when i start up Office on the machine it still asks for the original office XP installation CD, not a big deal but I thought by doing the initial office XP install it would be sufficient for the office 2003 install. Also when it asks for the CD it only gives access to the local drives, so you can't point it to a network install point.

Anyways let me know what and where your problems are happening and hopefully we can sort it out, or maybe there is enough info here.

[dolivas27]

@TwoJ

Thanks for the link and information that seems to work. I was looking at another posting on that site and it did not work for me but the link you provide worked. I still have some problems I did the slipstream and hotfixes using the Office Integrator v0.6 and that seems to work fine. I then did a test install using the install file that the Integrator created but after the install was completed and I checked for all updated none of the slipstreamed service packs or the hotfixes were applied? The update site still said I needed all the same patches I installed? I have used the Integrator before on the VLK and that one worked fine do you have any idea why it would not work on this version it is a OEM small business version (Not an upgrade) Also if you don’t mind could you send me your batch file I probably don’t need to install the office XP version first but I could just remove that from the batch. (No reason to recreate the wheel if you have a batch file that works and I like the fact that you remove the product key so I can add the correct key for the install)

Anyways thanks again for your help with this.
dolivas27

[Siginet]

@TwoJ

Thanks for the link and information that seems to work. I was looking at another posting on that site and it did not work for me but the link you provide worked. I still have some problems I did the slipstream and hotfixes using the Office Integrator v0.6 and that seems to work fine. I then did a test install using the install file that the Integrator created but after the install was completed and I checked for all updated none of the slipstreamed service packs or the hotfixes were applied? The update site still said I needed all the same patches I installed? I have used the Integrator before on the VLK and that one worked fine do you have any idea why it would not work on this version it is a OEM small business version (Not an upgrade) Also if you don’t mind could you send me your batch file I probably don’t need to install the office XP version first but I could just remove that from the batch. (No reason to recreate the wheel if you have a batch file that works and I like the fact that you remove the product key so I can add the correct key for the install)

Anyways thanks again for your help with this.
dolivas27

It very well may be posible that one digit in the reg entries are different for oem. Here's what I need you to do. Install your oem copy normally without the ointegrator. Then perform Microsoft Updates on it. When it finishes export the reg entries here for me so I can see what is different. ;)

[TwoJ]

Hi Guys

Well i'm happy things are starting to work for you, I ended up doing the slipsteaming and hotfixes updates manually, at that point i think siginet hadn't added the reg keys to the XP database so at that point it wouldn't have worked for me.

I think for you, you need to check 2 things, one is which update you are using, the Office update or the Microsoft update (the office update you go to the office page on MS website and it is a smaller link to just check for updates to office - the normal one takes you to the MS update page). When I did the updates the Office updates did an actual scan of the system and found the post-sp3 hotfixes, the Microsoft update only scans the registry to determine if the updates are applied. So unless you apply the registry entries for those hotfixes it will appear to Microsoft updates as if those hotfixes are not applied.

The second is as signet suggests is to copy the registry keys with those updates, look back a few posts to find the key we are talking about. Siginet i think designed his office update originally with enterprise (or aka slipstreamable) office CDs and now that we know a non-enterprise office (aka retail, oem, upgrade) can also be slipstreamed it is a question of finding out if those types (non-enterprise) have the same registry keys as the enterprise or whether as i suspect that they are different on the 7th digit as mentioned before.

I will post that batch file soon, i need to find it in my computer mess of which was the last version.

Siginet - you mentioned you updated the database with the XP keys, i haven't had a chance yet to try it, but i assume those are for the enterprise reg keys?

[dolivas27]

It very well may be posible that one digit in the reg entries are different for oem. Here's what I need you to do. Install your oem copy normally without the ointegrator. Then perform Microsoft Updates on it. When it finishes export the reg entries here for me so I can see what is different. ;)

Hi Siginet

Here are reg entries you wanted to see I hope I exported the correct keys for you if not please let me know which ones you need. There are two reg keys in the 7z file one is for Office OEM Basic Edition the other if for what I think is a full version of Office OEM but it could be a Retail version I don't know for sure as Microsoft sent it to me free for some promo a while back.

Anyways look them over and let me know what you think and if you need anything else from me. You will notice that the reg keys are different for both of these keys and different than the VLK key.

I just added another reg file this one it for the Student and Teacher addition.

I also have a question about your HotPack if I want to add the new updates to it do I just modify the ohotfix.ini with the new updates? and does one update just replace the other? (i.e. KB929058 is for Excel and is in the HotPack and KB933666 is out for Excel does the newer version just replace the older one or in there more to it?) I know there might be a newer version out from yesterday I was just using those as a example.

Thanks for the help,
Dolivas27

[TwoJ]

I think we are reverse engineering MS stuff - better lock them doors!
Well - thanks to Siginet & dolivas27 i think i can throw some more light on the GUIDs for the office products

Under the registry key;
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\

will be the Globally Unique IDentifier (GUID) for your office product, it will be a 32 digit value, i will assign it x1 as the first digit, x2 as the second, etc. So there should be
x1x2x3...x31x32
This code will determine what type of office product you have.

As Siginet found out the first 4 digits determine the language
x1x2x3x4
So for English it is 9040 or in reverse 0409 which is the typical language Identifier or LCID (see Siginet's previous post for more detail).

Next is the 2 digit office sku (Stock Keeping Unit) value
x5x6
I will come back to this.

Next is the 1 digit edition value
x7
This can have 3 values
0=Enterprise licence (including VLK, etc)
1=Retail licence (including OEM, Retail, Upgrade, etc)
2=Trial

The next series of x8 to x20 seems static as;
900063D11C8EF

Next is the version digit value;
X21
This seems to have 2 values
0=Office XP
1=Office 2003

Next the digits from x22 to x32 also seem static as;
0054038389C

This gives us
[x1x2x3x4][x5x6][x7]900063D11C8EF[x21]0054038389C
as
[Language][SKU][Edition]900063D11C8EF[Version]0054038389C
where language=LCID value backwards (ie english = 0409 -> 9040)
SKU= coming
Edition= (0-Enterprise/1-retail/2-trial)
Version=(0-office xp/1-office 2003)

ok - now the SKU's
i put this later because it seems to depend on the version digit value, ie it depends if you are talking about office xp or office 2003. For example if you had x5x6=21 then for office xp (x21=0) this would be Office XP Standard Edition, likewise for office 2003 (x21=1) this would be Office 2003 Standard Edition, however now if x5x6=31, then for office xp (x21=0) this would be Office XP Small Business Edition, while for Office 2003 (x21=1) it would actually be Office 2003 Basic edition.
So to determine which office type is installed we need first to know if we are working with Office XP or 2003 which is determined by x21 because the SKUs are not equivalent between the two.

Now the best part, as siginet found the x1-x4 is the language value in reverse, ie if the value is 9040 then in reverse we have 0409 which is the LCID for English.
Well for x5x6 it is just the SKU number in reverse so a x5x6 value of 21 is a SKU of 12!! which is either Microsoft Office XP Standard or Microsoft Office Standard Edition 2003 depending on the value of x21.

So the SKUs for office XP and other info can be found here;
http://office.microsoft.com/en-ca/help/HA011364611033.aspx
and the SKUs and stuff for office 2003 can be found here;
http://support.microsoft.com/kb/832672

here's the info;
Office XP SKUs
10 = Microsoft Office XP Premium
11 = Microsoft Office XP Professional
12 = Microsoft Office XP Standard
13 = Microsoft Office XP Small Business
14 = Microsoft Office XP Web Server
15 = Microsoft Access 2002
16 = Microsoft Excel 2002
17 = Microsoft FrontPage® 2002
18 = Microsoft PowerPoint® 2002
19 = Microsoft Publisher 2002
1A = Microsoft Outlook 2002
1B = Microsoft Word 2002
1C = Microsoft Access 2002 Runtime
1D = Microsoft FrontPage Server Extensions 2002
1E = Microsoft Office Multilingual User Interface Pack
1F = Microsoft Office Proofing Tools Kit
20 = System Files Update
22 = Microsoft PhotoDraw® 2002
23 = Microsoft Office Multilingual User Interface Pack Wizard
24 = Microsoft Office XP Resource Kit
25 = Microsoft Office XP Resource Kit Tools
26 = Microsoft Office Web Components
27 = Microsoft Project 2002
28 = Microsoft Office XP Professional with FrontPage
29 = Microsoft Office XP Professional Annuity
2A = Microsoft Office XP Small Business Edition Annuity
2B = Microsoft Publisher 2002 Deluxe Edition
2F = Standalone IME (JPN Only)
30 = Microsoft Office XP Media Content
31 = Microsoft Project 2002 Web Client
32 = Microsoft Project 2002 Web Server
33 = Microsoft Office XP PIPC1 (Pre Installed PC) (JPN Only)
34 = Microsoft Office XP PIPC2 (Pre Installed PC) (JPN Only)
35 = Microsoft Office XP Media Content Deluxe

And the SKUs for office 2003;
11 Microsoft Office Professional Enterprise Edition 2003
12 Microsoft Office Standard Edition 2003
13 Microsoft Office Basic Edition 2003
14 Microsoft Windows SharePoint Services 2.0
15 Microsoft Office Access 2003
16 Microsoft Office Excel 2003
17 Microsoft Office FrontPage 2003
18 Microsoft Office PowerPoint 2003
19 Microsoft Office Publisher 2003
1A Microsoft Office Outlook Professional 2003
1B Microsoft Office Word 2003
1C Microsoft Office Access 2003 Runtime
1E Microsoft Office 2003 User Interface Pack
1F Microsoft Office 2003 Proofing Tools
23 Microsoft Office 2003 Multilingual User Interface Pack
24 Microsoft Office 2003 Resource Kit
26 Microsoft Office XP Web Components
2E Microsoft Office 2003 Research Service SDK
44 Microsoft Office InfoPath 2003
83 Microsoft Office 2003 HTML Viewer
92 Windows SharePoint Services 2.0 English Template Pack
93 Microsoft Office 2003 English Web Parts and Components
A1 Microsoft Office OneNote 2003
A4 Microsoft Office 2003 Web Components
A5 Microsoft SharePoint Migration Tool 2003
AA Microsoft Office PowerPoint 2003 Presentation Broadcast
AB Microsoft Office PowerPoint 2003 Template Pack 1
AC Microsoft Office PowerPoint 2003 Template Pack 2
AD Microsoft Office PowerPoint 2003 Template Pack 3
AE Microsoft Organization Chart 2.0
CA Microsoft Office Small Business Edition 2003
D0 Microsoft Office Access 2003 Developer Extensions
DC Microsoft Office 2003 Smart Document SDK
E0 Microsoft Office Outlook Standard 2003
E3 Microsoft Office Professional Edition 2003 (with InfoPath 2003)
FD Microsoft Office Outlook 2003 (distributed by MSN)
FF Microsoft Office 2003 Edition Language Interface Pack
F8 Remove Hidden Data Tool
3A Microsoft Office Project Standard 2003
3B Microsoft Office Project Professional 2003
32 Microsoft Office Project Server 2003
51 Microsoft Office Visio Professional 2003
53 Microsoft Office Visio Standard 2003
5E Microsoft Office Visio 2003 Multilingual User Interface Pack
52 Microsoft Office Visio Viewer 2003

So we should now be able to look up the GUID and determine exactly what office products are installed and where to write the registry keys in order to have Microsoft Update recognize the slipstreamed hotfixes.

Siginet- i hope this helps you set up the database in order to support XP as well as 2003 :-)

The thing i would like to know is concerning the "AllPatches" key - the large hex value that doesn't seem to affect things, yet it would be nice to know how and why MS writes and modifies that key when patches are applied. Any ideas on that?

Hope this is helping some people!

[Siginet]

This will help a lot! Thanks for all of the research.

The thing i would like to know is concerning the "AllPatches" key - the large hex value that doesn't seem to affect things, yet it would be nice to know how and why MS writes and modifies that key when patches are applied. Any ideas on that?
I think that the ALLPATCHES key is just a list of the regkeys that are installed. So each update that is added is listed in the allpatches key. The OI_Setup.exe that I make will actually create the ALLPATCHES key as it installs new updates. ;)

[dolivas27]

Siginet any update for a possible fix for the OEM versions I know you have been busy with the RVMIntegrator beta. If there is anything else you need let me know.

Thanks,
Dolivas27 :smile:

[Siginet]

Sorry... I can't work on the OIntegrator at the moment. When I do I will create a quick fix for minor issues ... then I will work on adding new features.

[TwoJ]

A little more info;

I've been working on my office 2003 upgrade slipstream installation source, as i mentioned before this is an upgrade CD of office 2003 which through modification of the msi file can now be slipstreamed and can use the CIW or transforms.

One problem i am still experiencing is that once i delete the key for the office registration;
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\ Registration
When any office product is started it pops up the window for the user information and the Product Key. However since it is an upgrade CD i also get another window for the "Product Compliance Check" which is to determine a previous office installation, which can be office 97, 2000, or XP. I have tried doing a local install however i can't seem to get it to detect a local install and so it says to select the drive where office is located. However it only gives access to the local drives A, C, and D. In an attempt to determine what exactly it is looking for i've used office 97, 2000 and XP.

So i believe when it is trying to determine if you "own" a copy of Microsoft Office on CD-ROM it will try to locate the following files on the CD-ROM;

Office 97: OF97SPEC.INI (on root of Microsoft Office 97 CD)

Office 2000: POWERPNT.EXE (in /PFILES/MSOFFICE/OFFICE of Microsoft Office 2000 CD)

Office XP: STD.msi (on root of Microsoft Office XP CD)

Note that i was using office XP standard (STD.msi) the validation check probably also checks for pro.msi, proplus.msi, etc.
So i think if one had the OF97SPEC.ini from office 97 you can burn it to the root of a CD and the office 2003 should accept it as a valid upgrade CD.

If the setup does not find a valid version of office it will generate a Error 1608. Setup could not locate a version of Microsoft Office 97, 2000 or XP on the selected drive. etc

If anyone has any suggestions on what i can do to find a bypass for this Product Compliance Check i would be very thankful.
It seems that most of the validation rests on the DigitalProductID key which if it is deleted will cause office to request the Product Key again plus the Product Compliance Check for the upgrade CD.

thanks

[cworkman]

When I First Run The Office Integrater I Recieve The Attached Error:confused:

[Siginet]

When I First Run The Office Integrater I Recieve The Attached Error:confused:

This is cause by either your network blocks pings, your intenet is down or SiginetSoftware.com is down.

In the next version i will get rid of the pinging and just check for connectivity to the website.

[TwoJ]

Still trying to find a method of having a fully slipstreamed installation of Office 2003 upgrade, i actually wonder if the office 2007 upgrade can be modified in the same way?

Anyhow i was hoping that somehow the msi file would also be modifiable so that it does not look for a previous version, i guess my understanding of msi is pretty limited. The Product Compliance Check seems to be a function within the office programs (word, excel, etc) or perhaps it calls another program to verify that the digitalproductId in the registry is valid. It seems that it is the product key itself which determines if it is an upgrade or full version. I don't think there is anything in the msi file to modify that would change an upgrade version to a full version or to bypass the product compliance check.


At this point i can think of two ways to try to avoid the "product compliance check", I believe that the upgrade installation automatically looks for an installed previous version, which even if i install XP when i run the upgrade it doesn't automaically find the installation, nor in the Product Compliance Check does it find the installation when you choose the local drive. So the first way would be to find if its possible to find what files or registry settings are necessary for it to find a local source.
The 2nd choice would be to be able to take a product key for office and generate the DigitalProductID and ProductID, if thats possible?, and write that into the registry and see if it will accept that it is fully installed.

I guess some more information and testing is necessary at this point!

[Siginet]

Those are some great ideas TwoJ. But... I won't add support to hack an upgrade disk to become a retail and so on. ;) I have to be careful when it comes to that kind of stuff. I don't want Siginet Software to get flagged.

I'm not asking you to stop research... I am just letting you know I won't directly add support to do something like that.

[TwoJ]

I completly understand and support that position, I am kind of using this as a forum just to keep track on my "progress" if you can call it that.

I am an IT person, and of course one of the usual stuff during the course of the day is to reformat-reinstall computers, and also to comply with MS licensing so that one computer= 1 license XP + 1 license office + 1 license acrobat , etc, etc.

The windows xp is slipstreamed and is a corporate version so everything is cool, but i've got a mess of corp, oem, retail, and upgrade liceses for office. If MS offered an upgrade of taking an OEM + $$ = volume license conversion i think i would jump on it. however to take an office 2003 install, apply SP2, then apply post sp2 updates takes some time, especially if you have to go to the machine to put in the disc since there are remote locations.

So all i want to do is have my upgrade CD act like my corp version for office, i have no desire to crack the upgrade in the way to avoid paying for a retail version but just so that i can launch my script that can install the office XP then lauch office 2003 which will detect the xp install and not bring up this validation check for a previous version. Perhaps it breaks the EULA of not suppose to slipstream a retail version, but MS is still getting their $$ for the software, and if i can simplify the installation (not bypass the security) of office then i consider that fair play (even if it may be agaist their EULA).

[Siginet]

I definatly am on the same page as you. ;) That is exactly what I aim to do. Like I said... you are welcome to track your findings here. :D

[TwoJ]

At this point i can think of two ways to try to avoid the "product compliance check", I believe that the upgrade installation automatically looks for an installed previous version, which even if i install XP when i run the upgrade it doesn't automaically find the installation, nor in the Product Compliance Check does it find the installation when you choose the local drive. So the first way would be to find if its possible to find what files or registry settings are necessary for it to find a local source.
The 2nd choice would be to be able to take a product key for office and generate the DigitalProductID and ProductID, if thats possible?, and write that into the registry and see if it will accept that it is fully installed.

I guess some more information and testing is necessary at this point!

Well i opted for solution #1, the second choice of producing the DigitalProductID and ProductID seem to lay in the same realm as windows that it does a hardware scan to produce a hash which is combined with the office key. while it does seem that it is possible to reverse engineer this process i think it is a little beyond my time limits at the moment, plus the fact i have no desire to start IP legal affairs with MS.

Good news on solution #1, is i believe i have narrowed down which registry key the office 2003 upgrade checks for a previous office installation. Before i post my script and hopefully confirm that everything works as i am hoping with the registry key, i want to test the original problem i was having with the upgrade slipstream installation not recognising an office xp installation.
I will hopefully test this at work on monday and report after that

cheers!

[TwoJ]

Some more info;

These are 2 links for numbering scheme of Office XP and 2003 for their GUID;
Office XP;
http://support.microsoft.com/kb/302663
Office 203;
http://support.microsoft.com/kb/832672

Next is the Good news, i believe i have confirmed that the Office 2003 Upgrade CD does NOT check if there are any actual files on the hard drive before it pops up with its product compliance check window.
What it does check is the uninstall information for Office XP (and probably 97 & 2000 - but i haven't checked).
It checks this key;
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall
for the previous office installation, in my case it was the subkey;
{90120409-6000-11D3-8CFE-0050048383C9} which given the links from above will tell you that this was a Office XP (9-RTM version) (0-Enterprise) (12- Standard Edition) (0409-English).
As an extra bonus - it doesn't seem to verify all the keys but just one, which is the help link - ie HelpLink = http://www.microsoft.com/support
I've attached the key in this post.
So if you take an Office 2003 Upgrade CD and install this registry key, then install office, it should accept that you had a previous installation of Office XP installed.
Now its possible that it scans different keys for deifferent versions of office but it seems that is the key for the version that i was using as a legit upgrade.

So if you have an upgrade CD you can now install an administrative install point, slipstream updates, apply transforms, and install the necessary registry key to avoid the product compliance check.

I was just trying to see if i can change the product key in the setup.ini file or in the setup.exe PIDKEY={Product Key} but it seems that if you are installing from an administrative install point that the install uses that key regardless of whether you entered another key in the setup.ini file.

At this point i was trying to determine if there is an easier way of pre-entering the key (ie into setup.ini or by defining it in the PIDKEY= command line) to avoid deleting the "volume" key to re-enter a normal "retail" key.

I will take a look later, perhaps the best way may be to write an autoit script to take care of it?

If anyone has ideas for that part....

[wimb]

If you point in the second input box to an admin install already slipstreamed with the Service Pack, then after integrating the HotPack, the KB_KEYS.OI registry file will not get an entry for MAINSP2ff

In order to be correct, an entry for MAINSP2ff should be present in the KB_KEYS.OI file, also when the destination was already slipstreamed with the SP2 Service Pack.

It would be nice if the program was able to recognise the presence of the SP2 Service Pack in the destination,
so that the correct KB_KEYS.OI file can be produced.

[searcher101]

anybody know why I'm getting this.
thanks.:confused:

[Kelsenellenelvian]

Corrupted update file?

[Siginet]

That would be my first guess as well. Thanks Kel... I didn't see his post in here. ;)

[ENU_user]

wha' wrong window

[Colinzim]

where's the dl link for office integrator ??

[skinnyJM]

Siginet,
Please see the quoted post (http://www.siginetsoftware.com/forum/showthread.php?p=3147#post3147) below,

I've noticed that SiginetSoftware.com.DB does not contain post SP3 registry entries. As a result after Office 2003 integration Microsoft Update wants to install correctly integrated updates. This is due to a fact that Kb_keys.oi does not contain necessary registry updates.

skinnyJM
Please start jour job with update of SiginetSoftware.com.DB.

Additionally downloaded SiginetSoftware.com.DB has extra spaces in every registry path as shown below:
[HKEY_LOCAL_MACHINE\...\Curr entVersion\...\Patch es\...

Every time I want to use Office Integrator I need to:
a) remove spaces shown above
b) manually add all post SP3 updates.

Anyway after this everything works as expected.

as I think it would probably have been better posted in this thread, rather than the Office 2003 Service Pack 3 released (http://www.siginetsoftware.com/forum/showthread.php?t=226) thread.
But then again, what do I know? :D
Thanks,
skinnyJM

[Siginet]

I think I have fixed all of the spaces that I found in the database. ;) Thanks for pointing this out gjack!

[awkward]

Can someone please tell me how to make microsoft update recognise that I have slipstreamed the updates - I read about installing the .reg file that integrater creates but cannot find it or even know where to put it!!
Thanks

[Siginet]

Just use the SETUP_OI.EXE when you install from files integrated with the OFFICE INTEGRATOR. ;)

[awkward]

Ahh ! I wondered what that file was all about - ok, I will uninstall and reinstall using the setup_OI file.

Is there a way I can incororate that file into the normall setup so it just autoruns and next next etc?

Thanks for your quick response

[Siginet]

You should be able to pass any parameters to this file as you would pass to the original setup file. ;) Basically the setup_oi.exe passes all of these parameters to the original setup file. ;) We are in the process of testing another method where we can move the original setup file into the setup folder where setup.ini resides. Then name setup_oi.exe the same name as the original setup file. It has been said to work... so we are testing everything to ensure it is stable.

[awkward]

Ok thanks, I am trying that now - m u did not ask for the 10 updates this time but a new one is there KB943985 v2 - I believe it was only released today but I'v never seen one with v2 after it! - and I'v just managed to find a fullfile to download here http://www.microsoft.com/downloads/details.aspx?FamilyId=296E5F2C-F594-41C8-A20A-3E4C40AE3948&displaylang=en
I couldn't get office to autorun from _oi file! I will wait for the experts!!
Will slipstream this new update now.
Thanks again.

[ZaForD]

@awkward,
I'm no expert. But I think I can help ya. ;)
I edited the "Autorun.inf" to point to "Setup_oi.exe" instead off "Setup.exe"
then burnt it to disk.

[Siginet]

The next version of the OI will no longer use SETUP_OI.EXE. :D It will actually replace the original setup file... using the same name and move the original setup file into files\setup. Which works exactly the same. :thumbsup:

[ZaForD]

Hi Siginet,

Could you leave your icon as the default in the new "Setup.exe" or add it so it can be used instead of the Office11 one.

I've got used to picking my disks by icons, rather than going to all the trouble of reading the "Label". :p

[Siginet]

Yes it will use the same icon.. or possibly a new one. ;)

[jfcarbel]

If I wanted to use the integrated version with an unattended install, then should I change this:

REG ADD %KEY%\065 /VE /D "MS Office 2003 Professional" /f
REG ADD %KEY%\065 /V 1 /D "%CDROM%\Office\setup.exe TRANSFORMS=%CDROM%\Office\Unattended.MST /qb-" /f

To this:

REG ADD %KEY%\065 /VE /D "MS Office 2003 Professional" /f
REG ADD %KEY%\065 /V 1 /D "%CDROM%\Office\setup_OI.exe TRANSFORMS=%CDROM%\Office\Unattended.MST /qb-" /f

Will this work?

ALSO:

When SP or hotfixes are slipstreamed into an administrative installation, are there any changes made to the MSI file?

I ask because of 2 reasons:

1) I noticed that after running the office integrator the file date on the MSI file (PRO11.MSI) changed to todays date

2) It seems the serial/key is embedded in the MSI file and I do not have the original source only this administrative installation version. But I want to change the key and the PIDKEY setting in the INI file is not overridding the MSI one. How do I override or remove the key from my Office MSI?