Office 2000 network installs cannot access original install share anymore

[Gerry Hickman]

Hi Grol,

It's a bit worrying that you don't know how to do this, since it's
required to integrate patches into your build...

If you read the KB articles for the administrative "full file" patches,
they explain the command line options.

Here's a quick example of what you might use, this will "reinstall" the
Word files. Replace d:\Office\o2kadm with your UNC path to your share.
This command will attempt to re-install a feature from your share, so if
there's a problem with the share, it should crash with a bad ErrorLevel
and you should see some annoyance in the log file.

LOOK OUT FOR LINE WRAP - the MSIEXEC command is all on one line...

echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "D:\Office\o2kadm\data1.msi" /qn /l*v c:\wordv3.txt
REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE REINSTALLMODE=vomu
REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%

 

[Gerry Hickman]

Hi Grol,

It's a bit worrying that you don't know how to do this, since it's
required to integrate patches into your build...

If you read the KB articles for the administrative "full file" patches,
they explain the command line options.

Here's a quick example of what you might use, this will "reinstall" the
Word files. Replace d:\Office\o2kadm with your UNC path to your share.
This command will attempt to re-install a feature from your share, so if
there's a problem with the share, it should crash with a bad ErrorLevel
and you should see some annoyance in the log file.

LOOK OUT FOR LINE WRAP - the MSIEXEC command is all on one line...

echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "D:\Office\o2kadm\data1.msi" /qn /l*v c:\wordv3.txt
REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE REINSTALLMODE=vomu
REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[grolschie]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.
grol

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.

 

[Gerry Hickman]

Well the thing is, I can browse the share manually and reinstall at will.
The WI doesn't fail with access denied then. It only fails when the system
calls WI for some reason at boot-time. I will try your script, but I suspect
it might not trigger the problem.

Well the script will trigger the install process almost as if you're
installing a "feature" from within Office itself. The only difference is
that you're passing the share path manually. You've already checked the
paths in the reg, so this is a very good simulation excercise.

The time you've spent writing this message you could have already run
the script and analysed the log file.

We have not installed any Office2k service packs until now as everything has
been running smoothly since day one until now.

OK, but that's crazy. Any document you open from outside your
organization could easily exploit your systems.