diff options
Diffstat (limited to 'docs/faq/clientapp.html')
| -rw-r--r-- | docs/faq/clientapp.html | 62 |
1 files changed, 62 insertions, 0 deletions
diff --git a/docs/faq/clientapp.html b/docs/faq/clientapp.html index d2ba0a08b5..0081891331 100644 --- a/docs/faq/clientapp.html +++ b/docs/faq/clientapp.html @@ -86,6 +86,68 @@ rdonly by trying to open it for writing.</P You just have to install as a non-admin user and then use "chown -R" to fix the owner.</P ></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN175" +></A +>3.2. How to use a Samba share as an administrative share for MS Office, etc.</H1 +><P +>Microsoft Office products can be installed as an administrative installation +from which the application can either be run off the administratively installed +product that resides on a shared resource, or from which that product can be +installed onto workstation clients.</P +><P +>The general mechanism for implementing an adminstrative installation involves +running <B +CLASS="COMMAND" +>X:\setup /A</B +>, where X is the drive letter of either CDROM or floppy.</P +><P +>This installation process will NOT install the product for use per se, but +rather results in unpacking of the compressed distribution files into a target +shared folder. For this process you need write privilidge to the share and it +is desirable to enable file locking and share mode operation during this +process.</P +><P +>Subsequent installation of MS Office from this share will FAIL unless certain +precautions are taken. This failure will be caused by share mode operation +which will prevent the MS Office installation process from re-opening various +dynamic link library files and will cause sporadic file not found problems.</P +><P +></P +><UL +><LI +><P +>As soon as the administrative installation (unpacking) has completed +set the following parameters on the share containing it:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> [MSOP95] + path = /where_you_put_it + comment = Your comment + volume = "The_CD_ROM_Label" + read only = yes + available = yes + share modes = no + locking = no + browseable = yes + public = yes</PRE +></P +></LI +><LI +><P +>Now you are ready to run the setup program from the Microsoft Windows +workstation as follows: <B +CLASS="COMMAND" +>\\"Server_Name"\MSOP95\msoffice\setup</B +></P +></LI +></UL +></DIV ></DIV ><DIV CLASS="NAVFOOTER" |