summaryrefslogtreecommitdiff
path: root/docs/textdocs
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/textdocs
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/textdocs')
-rw-r--r--docs/textdocs/Application_Serving.txt56
1 files changed, 0 insertions, 56 deletions
diff --git a/docs/textdocs/Application_Serving.txt b/docs/textdocs/Application_Serving.txt
deleted file mode 100644
index 6a61a99d7e..0000000000
--- a/docs/textdocs/Application_Serving.txt
+++ /dev/null
@@ -1,56 +0,0 @@
-Contributed: January 7, 1997
-Updated: March 24, 1998
-Contributor: John H Terpstra <samba@samba.org>
- Copyright (C) 1997 - John H Terpstra
-Status: Current
-
-Subject: Using a Samba share as an administrative share for MS Office, etc.
-==============================================================================
-
-Problem:
-========
-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.
-
-The general mechanism for implementing an adminstrative installation involves
-running:
- X:\setup /A, where X is the drive letter of either CDROM or floppy
-
-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.
-
-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.
-
-Solution:
-=========
-1. As soon as the administrative installation (unpacking) has completed
- set the following parameters on the share containing it:
- [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
-
-2. Now you are ready to run the setup program from the Microsoft Windows
-workstation as follows:-
- \\"Server_Name"\MSOP95\msoffice\setup
-
-MS Office Sharing - Please note:
-================================
-
-Workgroup Templates should be stored on an ordinary writable or read-only share
-but USER templates MUST be stored on a writable share _OR_ on the users' local
-machine.