Troubleshooting Office 2000 Install
Novell Cool Solutions: Tip
By Peter Riesett
Digg This -
Posted: 5 Sep 2001
Version: ZENworks for Desktops 3
During the installation of Office 2000, using ZFD3, we got the error message,
"Problem: Install failed. Could be due to insufficient disk space."
on our Windows 9x computers.
It turns out that we had a custom Start menu in the policies, and the users only had RF rights to the directory where the custom Start menu was created, and the installer was trying to create the "New Office Document" shortcuts into the Start menu. We temporarily gave the users create rights, and the problem went away.
Any other gotchas and workarounds you'd like to share about installing Office 2000? Let us know what you've learned the hard way.
Rather than give users rights to the shared menu, we temporarily changed where the Start menu was to c:\windows\temp. The office install then happily put the shortcuts there, then we changed it back.
That way, we don't get those unwanted shortcuts in the shared Start menu, and don't need to give users rights we don't want them to have.
I would like to chime in on the "Troubleshooting Office 2000 Install" article. In most cases corporate policy dictates a "common" Start menu and therefore requires that "network users" not have rights to write shortcuts to the Start menu. In this case you can use the "Custom Installation Wizard" utility provided by Microsoft in the Office Resource Kit 2000 (ORK2K) to preconfigure your installation of Office 2000 without these Start menu shortcuts.
You can then give the "network user" a simple application object on the application launcher that runs the local executable office file(s). (ie. C:\PROGRAM FILES\MS OFFICE\OFFICE\WORD.EXE. You can do this for each Office program you want the "network user" to be able to run.
This maintains company policy and protects your common Start menu.
To prevent this error use create a custom .MST file that does not create shortcuts on the custom Start menu. Add them in later if they are on a Network volume. Then there is no need to change the file rights as the shortcuts do not get created! To create a custom MST file get hold of the MSI admin kit from Microsoft.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com