/build/static/layout/Breadcrumb_cap_w.png

Office 2003 mst problem after install SP3

Hi,

I made one transformen file to Office 2003 with the office resource kit, and for Outlook i config the exchange settings. Everything works fine after the installation, and if i open the Outlook it open with my exchange mailbox.
But if I deploy the package like this (see 1 and 2), with the office 2003 sp3 after the installation, the Exchange settings disappear, and the outlook open with the mail config guide:

1. msiexec /i pro11.msi TRANSFORMS=Off2k3Pro.MST /qb
2. Office2003SP3-KB923618-FullFile-SVE.exe /q

So does anyone have an idea why my exchage settings get erased after deploy office 2003 sp3?

/SaiTech

0 Comments   [ + ] Show comments

Answers (3)

Posted by: dodgy 14 years ago
Orange Belt
0
Hi SaiTech,

I'd recommend that you slipstream the service pack 3 into the office source folder (haven't tried with non-english language version though should work for you).

http://www.petri.co.il/office-2003-sp-3-slipstreaming.htm
Posted by: SaiTech 14 years ago
Orange Senior Belt
0
Thanks dodgy,

It seems to be the most easy/smartest way, I will try it. One question: You need administrative version of SP3. Does all patches need to be a administrative version, so what about if you would like to patch the Office 2003 later ex. with WSUS?

/SaiTech
Posted by: SaiTech 14 years ago
Orange Senior Belt
0
Hummm,

it looks that I have been using the administative sp3 "Office2003SP3-KB923618-FullFile-SVE.exe", however I cant find the one used to call "client"

/SaiTech
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ