From 502a960354717bb1d7a2d001cbd1ad918a2f7a33 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Fri, 4 Oct 2002 16:11:31 +0000 Subject: 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) --- docs/docbook/faq/clientapp.sgml | 59 +++++++++++++++++++++++++++++++++ docs/faq/clientapp.html | 62 +++++++++++++++++++++++++++++++++++ docs/faq/samba-faq.html | 5 +++ docs/textdocs/Application_Serving.txt | 56 ------------------------------- 4 files changed, 126 insertions(+), 56 deletions(-) delete mode 100644 docs/textdocs/Application_Serving.txt 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. + +How to use a Samba share as an administrative share for MS Office, etc. + + +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. + + + + +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 + + + + + +Now you are ready to run the setup program from the Microsoft Windows +workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup + + + + + 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.

3.2. How to use a Samba share as an administrative share for MS Office, etc.

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.

MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"
3.2. How to use a Samba share as an administrative share for MS Office, etc.
- 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. -- cgit