Article ID: 135466
Article Last Modified on 7/18/2007
APPLIES TO
- Microsoft Office 95 Standard Edition
- Microsoft Excel 95 Standard Edition
- Microsoft PowerPoint 95 Standard Edition
- Microsoft Word 95 Standard Edition
- Microsoft Project 4.1 Standard Edition
- Microsoft Access 95 Standard Edition
- Microsoft Works 4.0 Standard Edition
- Microsoft Works 4.0 Standard Edition
This article was previously published under Q135466
SYMPTOMS
When you perform a Workstation installation of your Windows 95 application,
the shared files may be installed to the following folder on your local
workstation
c:\Program Files\Microsoft Shared\Common Files
even if you chose to have the shared files installed on the network server
during Setup.
CAUSE
This behavior occurs when Setup cannot resolve the path to the Microsoft
shared files on the network server during the Workstation installation. In
this case, Setup copies the files to your local workstation instead.
You do not receive any indication that the files are being installed
locally, even though you chose to have them installed on the network
server.
WORKAROUND
During the administrative installation (Setup /a) for the applications
listed above, you have the option to specify how the user is going to
access the shared files; namely, by using the server name or drive letter.
In general, this problem only occurs when you enter a Universal Naming
Convention (UNC) path during the administrative installation.
To work around this problem, select the Drive Letter option in the Network
Server Confirmation dialog box (during the administrative installation) so
that Setup does not have to resolve a UNC path to the server during the
workstation installation.
Additional query words: 1.20 word6 powerpt w_works off7 xl7
Keywords: kbprb kbsetup KB135466