JHT ==> Fixed typo in DOMAIN_CONTROL.txt, added Application_Serving.txt

	to help those wishing to run MS Office Application Servers.
(This used to be commit 3ecc94a7a3daeb6cc0cf4df83c6179f09670b663)

diff --git a/docs/textdocs/Application_Serving.txt b/docs/textdocs/Application_Serving.txt
new file mode 100644 (file)
index 0000000..ea8f129
--- /dev/null
+++ b/docs/textdocs/Application_Serving.txt
@@ -0,0 +1,45 @@
+January 7, 1997
+Contributor: John H Terpstra
+
+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
+procautions are taken. The failure will be caused by share mode operation
+which will prevent the MS Office installation process from re-opening various
+dynamic link library files. Some other files will also NOT be found at times.
+
+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 workstation as follows:-
+       \\"Server_Name"\MSOP95\msoffice\setup
+

diff --git a/docs/textdocs/DOMAIN_CONTROL.txt b/docs/textdocs/DOMAIN_CONTROL.txt
index b7f32e5f73e93990ad2bb14aa900efe289b2a44a..5804d151296b0033531a4e2e2f03a927b898e261 100644 (file)
--- a/docs/textdocs/DOMAIN_CONTROL.txt
+++ b/docs/textdocs/DOMAIN_CONTROL.txt
@@ -22,7 +22,7 @@ In fact, the registry contains entries that describes everything that anything
 may need to know to interact with the rest of the system.
 
 The Microsoft Windows NT system is structured within a security model that
-says that all applications and services much authenticate themselves before
+says that all applications and services must authenticate themselves before
 they can obtain permission from the security manager to do what they set out
 to do.