Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Interesting Office 2000 Challenge (hoenst!)

Status
Not open for further replies.

Hutton

IS-IT--Management
Apr 10, 2001
6
US
I have taken over a site where I have found the Office installation on every machine is corrupted.

We were getting calls for all types of problems (Dr. Watsons, templates not working, macros not recording) so I took a vanilla NT build, added Sp6a and installed Office 2000 Std using the MST file that the workstation build was built with. Doing this simplified the build and eliminated other applications.

All the reported problems appeared on the above configuration.

So I then created another vanilla machine, Sp6a with Office 2000 (from the same source) but without the .MST file and all was fine.

As each machine stands now the "Detect And Repair" feature does not work, as files are under the wrong location.

Opening the .MST file does not provide any answers - it looks fine.

So, my options are as follows:

1) Repair
Nope, doesn't work from GUI or cmd line
2) De-install & Reinstall
From the cmd line. Initial tests showed that Office
wasn't installed 100%.
3) Attempt to jusr re-install
Hasn't worked successfully yet.

It looks like option 2 is required but this is a problem as >300Mb to 1,000's of clients will be a killer on the network.

So in short I am wondering if there are any tools or techniques that could get me to repair/re-install office without having to run the std setup program. I know this is a long shot but could save our network bandwidth!!!

I'm gonna post this on the NT Workstation forum as well.
Thanks in advance,
Hutton.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top