Office 2003, Custom Installation Wizard, MST

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Tom Felts]

That is weird. I have a similar job to upgrade Outlook XP to Outlook 2003,
and it works fine.

Have you tried using a Custom Maintenance Wizard job? Set everything to
"Leave Unchanged" except Publisher, which would be set to install?

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy F.]

Tom,

I haven't tried the Custom Maintenance Wizard, but from looking at it,
it would seem that it would defeat the purpose of me deploying the
install through Group Policy because I would then need to visit the
stations to run the Maintenance file. I think I might contact
Microsoft directly and have them explain to me why the .MST file is
being ignored. If I get anywhere, I will certainly post an answer to
this thread for others.

Thanks for your time,
Troy.

 

[Troy]

Update: Microsoft wants $350.00 to troubleshoot the problem which seems
rather like extortion to me. In any case, after paying for the Office
licenses and associated Software Assurance, there is no way I'll be spending
an additional $350.00 to troubleshoot the issue. If I ever find the solution
on my own I will post it here so that others don't get suckered for a $350.00
charge.

Troy.

 

[Troy]

Update: Microsoft wants $350.00 to troubleshoot the problem which seems
rather like extortion to me. In any case, after paying for the Office
licenses and associated Software Assurance, there is no way I'll be spending
an additional $350.00 to troubleshoot the issue. If I ever find the solution
on my own I will post it here so that others don't get suckered for a $350.00
charge.

Troy.

 

[Troy]

Update: Microsoft wants $350.00 to troubleshoot the problem which seems
rather like extortion to me. In any case, after paying for the Office
licenses and associated Software Assurance, there is no way I'll be spending
an additional $350.00 to troubleshoot the issue. If I ever find the solution
on my own I will post it here so that others don't get suckered for a $350.00
charge.

Troy.