Deploying Office 2003 Silent Install - Problem with Outlook

I

Inoffensive

Hello, this is how I'm trying to deploy Office 2003:

Create an admin install point, slipstream SP1 and related updates, create
MST file using ORK tools, and finally create a silent install package using
PackageForTheWeb. In the MST file, I'm creating a local installation source.
This has been successful in the initial upgrades without any issues
whatsoever.

However, in certain cases, when Outlook tries to configure itself upon
initial start, it asks for the pro11.msi file. Since a local installation
source has been created, why does Outlook ask for the MSI file?

Anyone know of a workaround for this issue? Thanks for any and all help.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
I

Inoffensive

After a day of researching, I found out that the admin install process does
not create the MSOCACHE folder. So, either you install from admin install
point with service packs slipstreamed or you can install it using setup.exe
with a modified MST, setup.ini and ohotfix (with its own modified ini) for
chained updates. This wasn't easy with a few issues with the ohotfix issues.
But I finally got it fixed.

Hope this helps anyone in a corporate setting.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 
R

RodeCa

I think (*not* sure at all) that you must use a "compresed CD image" (not an
Admin Install Point) if you wish to get a local installation source.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Deploying Office 2003 Pro 2
office 2003 0
deploying outlook 2003 with office xp using ciw 0
MST, MSI, Deploying via GPO - how to silent install 18
Office 2003 rollout - workstations need the install after every re 0
Question about Office/Access 2003 installation 0
Office 2003 silent install problems 0
deploy office 2003 0

Top