summaryrefslogtreecommitdiff
path: root/docs/docbook/faq
diff options
context:
space:
mode:
authorJelmer Vernooij <jelmer@samba.org>2002-10-04 16:11:31 +0000
committerJelmer Vernooij <jelmer@samba.org>2002-10-04 16:11:31 +0000
commit502a960354717bb1d7a2d001cbd1ad918a2f7a33 (patch)
tree83950707d9ba68217f8be1b6fbf114849cfd108b /docs/docbook/faq
parent6f8a1c20410b7eedd451fdd2b8e7da1818d36a0b (diff)
downloadsamba-502a960354717bb1d7a2d001cbd1ad918a2f7a33.tar.gz
samba-502a960354717bb1d7a2d001cbd1ad918a2f7a33.tar.bz2
samba-502a960354717bb1d7a2d001cbd1ad918a2f7a33.zip
Move Application_Serving.txt to FAQ question "How to use a samba share as a administrative share for MS Office, etc?"
(This used to be commit 5e96448348d3db232a9a9f273a16dcfc4f69aaab)
Diffstat (limited to 'docs/docbook/faq')
-rw-r--r--docs/docbook/faq/clientapp.sgml59
1 files changed, 59 insertions, 0 deletions
diff --git a/docs/docbook/faq/clientapp.sgml b/docs/docbook/faq/clientapp.sgml
index 9bb7cb320f..2077b230ce 100644
--- a/docs/docbook/faq/clientapp.sgml
+++ b/docs/docbook/faq/clientapp.sgml
@@ -23,4 +23,63 @@ to fix the owner.
</sect1>
+<sect1>
+<title>How to use a Samba share as an administrative share for MS Office, etc.</title>
+
+<para>
+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.
+</para>
+
+<para>
+The general mechanism for implementing an adminstrative installation involves
+running <command>X:\setup /A</command>, where X is the drive letter of either CDROM or floppy.
+</para>
+
+<para>
+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.
+</para>
+
+<para>
+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.
+</para>
+
+<itemizedlist>
+<listitem><para>
+As soon as the administrative installation (unpacking) has completed
+set the following parameters on the share containing it:
+</para>
+
+<para><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
+</programlisting></para>
+
+</listitem>
+
+<listitem>
+<para>Now you are ready to run the setup program from the Microsoft Windows
+workstation as follows: <command>\\"Server_Name"\MSOP95\msoffice\setup</command>
+</para>
+</listitem>
+</itemizedlist>
+
+</sect1>
</chapter>