A
AJ
Hello All
Can someone confirm that this is expected behaviour . We want to
acheive the following:
Deploy Outlook 2003 SP2 on all machines.
Some of the machines already have olders versions of Office and some
have nothing at all. I am not particularly concerned about Office,
only the Outlook component. Office is out of scope but if it all gets
upgraded with the Outlook work, then fine - double bonus.
Here is what I have done:
Created an installation point for Office on a network share
Patched the installation point with SP2
Created an MST file which contains some Outlook profile settings. The
MST file does not do anything with the other Office applications, they
are configured as not available with a red cross next to them.
Here is what happens when I run setup.exe with the TRANSFORMS option:
1. On machines that don't have Office installed Outlook SP2 is
deployed and the customisations in the MST file work- Great all fine.
2. Machines that do have Office installed (including Outlook) but an
older version the complete version of Office is upgraded to SP2 and
the Outlook customisations work. - Great all fine even though I only
expected Outlook to get upgraded?????
3. For machines that have the current version of Office (SP2)
installed nothing appears to happen and the Outlook profile
customisations are not applied. - Not good
4. For machines that have Office but no Outlook becuase it was
uninstalled again nothing happens. I was expecting Outlook to get
deployed and added to the existing offuce install as per the per the
MST file - Not good but we can live with this as it will be so few
machines
Can someone try and explain this lot for me, is this expected
behaviour I am seeing?
Should I just create an Outlook administrative point and take office
out of the equaion??
Thoughts, advice
Thanks
AJ
Can someone confirm that this is expected behaviour . We want to
acheive the following:
Deploy Outlook 2003 SP2 on all machines.
Some of the machines already have olders versions of Office and some
have nothing at all. I am not particularly concerned about Office,
only the Outlook component. Office is out of scope but if it all gets
upgraded with the Outlook work, then fine - double bonus.
Here is what I have done:
Created an installation point for Office on a network share
Patched the installation point with SP2
Created an MST file which contains some Outlook profile settings. The
MST file does not do anything with the other Office applications, they
are configured as not available with a red cross next to them.
Here is what happens when I run setup.exe with the TRANSFORMS option:
1. On machines that don't have Office installed Outlook SP2 is
deployed and the customisations in the MST file work- Great all fine.
2. Machines that do have Office installed (including Outlook) but an
older version the complete version of Office is upgraded to SP2 and
the Outlook customisations work. - Great all fine even though I only
expected Outlook to get upgraded?????
3. For machines that have the current version of Office (SP2)
installed nothing appears to happen and the Outlook profile
customisations are not applied. - Not good
4. For machines that have Office but no Outlook becuase it was
uninstalled again nothing happens. I was expecting Outlook to get
deployed and added to the existing offuce install as per the per the
MST file - Not good but we can live with this as it will be so few
machines
Can someone try and explain this lot for me, is this expected
behaviour I am seeing?
Should I just create an Outlook administrative point and take office
out of the equaion??
Thoughts, advice
Thanks
AJ