summaryrefslogtreecommitdiffstats
path: root/docs/textdocs/Application_Serving.txt
diff options
context:
space:
mode:
authorcvs2svn Import User <samba-bugs@samba.org>1997-10-10 14:46:44 +0000
committercvs2svn Import User <samba-bugs@samba.org>1997-10-10 14:46:44 +0000
commit4480ee713f3ebaaf6852c2e3a5967b30e587f7db (patch)
tree70a8a34fa622fd9adef3dd7f65da299bf6c3e48a /docs/textdocs/Application_Serving.txt
parent3590a783338defa4ff1385b2d5bb095c5051ac82 (diff)
downloadsamba-4480ee713f3ebaaf6852c2e3a5967b30e587f7db.tar.gz
samba-4480ee713f3ebaaf6852c2e3a5967b30e587f7db.tar.xz
samba-4480ee713f3ebaaf6852c2e3a5967b30e587f7db.zip
This commit was manufactured by cvs2svn to create tag 'samba'.samba-misc-tags/samba
Diffstat (limited to 'docs/textdocs/Application_Serving.txt')
-rw-r--r--docs/textdocs/Application_Serving.txt50
1 files changed, 0 insertions, 50 deletions
diff --git a/docs/textdocs/Application_Serving.txt b/docs/textdocs/Application_Serving.txt
deleted file mode 100644
index 5a17b64b030..00000000000
--- a/docs/textdocs/Application_Serving.txt
+++ /dev/null
@@ -1,50 +0,0 @@
-January 7, 1997
-Updated: June 27, 1997
-Contributor: John H Terpstra <samba-bugs@samba.anu.edu.au>
- 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
-