Re-Installing MSO2k3

[AnOddName]

Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks!

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

The Custom Installation Wizard created MST is only used for an initial installation.
After that use the Custom Maintenance Wizard (CMW) files to make changes.
http://microsoft.com/office/ork/2003

==========
Hello,

We have installed Office 2003 with LIS using .MST the way we thought we
wanted it. We changed our minds and decided we wanted to lower Exel's
Maco Security. After modifying the MST to reflect our change, we tried
reinstalling it. The install runs for awhile but doesn't actually seem
to do anything, it certainly didn't change the Macro Security.

REINSTALL=ALL
ENFORCECACHE=1

Any ideas what may or may not be going on?

Thanks! >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill

 

[AnOddName]

Hi Bob, thanks for replying! Yes, I agree that the CMW is the ideal
solution. I'm actually helping somebody do this, and the person won't
be present for several days. My solution would be to use the CMW to
design the changes and then deploy them to the clients, and that's what
I'm going to propose. (That along with an OPS file)

Even though this should solve the issue, my task was to find out 'how
to reinstall office'.

Is it safe to say that you cannot reinstall office using MST,
setup.ini., command line params, but rather uninstall it first and then
reinstall it? I believe that REINSTALL=ALL will mearly pull update
files from an administrative source. Is this correct?

Bill