MST problem with OutLook

[dpelletier]

Hello all.

I have been trying to set up a MST file to run and install OutLook 2003 with
a default profile but its not working. I am using the MS utility to build the
MST file.

Here are the system settings

The client Pcs ( about 180) have a mix of MS Office 2000 or MS Office 2003
installed.
They have the full suite except no one has OutLook. When the orignal IT guy
installed MS Office he did not install OutLook 2003 as we used Lotus Notes.

Now we want to install MS office 2003 on all computers and add OutLook
to the install base as we are moving away from Notes.

I am having 2 problems,

1. I can update or reinstall MS office with my MST file just fine over the
network with a remote installer, but it will not install OutLook for the life
of ME!

2. I have managed to get OutLook installed on some systems but when i do i
can not repeat it using the same MST file from the same Share drive.
Permissions are the same.

ps when Out Look is installed sometimes (50/50) the default profiles will be
changed how i want them and sometimes they wont take. i am putting in things
like the mail sever IP, and using %username% to capture the profile name
among others.

If you need more info please ask, this is driving me insane! I believe my
problem is when OutLook was first installed we told it not to install.
Because when i reinstall MS Office every program but OutLook installs right
and takes its settings.

 

[Roady [MVP]]

Which deployment method are you using?
If via Group Policy and assigned to machines, make sure that the computer
objects also have read access to the distribution share.
On the computers that fail, see if re-enforcing the policy solves it;
Start-> Run; gpupdate /force

 

[dpelletier via OfficeKB.com]

I am using a program called Remote Installer. While we are the admins at
this site we do not have the authority to change or do anything with Group
Policy. This is why i am using a 3rd party software.

But i know this is not the problem. Because I have tried running the setup.
exe in CMD with the MST file while signed in as a local admin on the the PCs
them selves by passing the remote access and i get the same result.

My current method of deployment, using the Remote Installer to run a Bat file
that starts the MST install located on the network with Administrator rights.

Which deployment method are you using?
If via Group Policy and assigned to machines, make sure that the computer
objects also have read access to the distribution share.
On the computers that fail, see if re-enforcing the policy solves it;
Start-> Run; gpupdate /force

Hello all.

[quoted text clipped - 39 lines]

right
and takes its settings.

 

[Roady [MVP]]

You can enable logging for the setup to see what is going on. There might
already be logged something about this in the Event Viewer.
Do all other modified settings you have specified for the other Office
applications get applied correctly?



-----

I am using a program called Remote Installer. While we are the admins at
this site we do not have the authority to change or do anything with Group
Policy. This is why i am using a 3rd party software.

But i know this is not the problem. Because I have tried running the
setup.
exe in CMD with the MST file while signed in as a local admin on the the
PCs
them selves by passing the remote access and i get the same result.

My current method of deployment, using the Remote Installer to run a Bat
file
that starts the MST install located on the network with Administrator
rights.

Which deployment method are you using?
If via Group Policy and assigned to machines, make sure that the computer
objects also have read access to the distribution share.
On the computers that fail, see if re-enforcing the policy solves it;
Start-> Run; gpupdate /force

Hello all.

[quoted text clipped - 39 lines]

right
and takes its settings.