mirror of
https://github.com/samba-team/samba.git
synced 2025-02-01 05:47:28 +03:00
-
52 lines
5.6 KiB
HTML
52 lines
5.6 KiB
HTML
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter 2. Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-errors.html" title="Chapter 4. Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter 3. Specific client application problems</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2815105">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2815137">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2882001">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815105"></a>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</h2></div></div><div></div></div><p>
|
||
When installing MS Office on a Samba drive for which you have admin
|
||
user permissions, ie. admin users = username, you will find the
|
||
setup program unable to complete the installation.
|
||
</p><p>
|
||
To get around this problem, do the installation without admin user
|
||
permissions The problem is that MS Office Setup checks that a file is
|
||
rdonly by trying to open it for writing.
|
||
</p><p>
|
||
Admin users can always open a file for writing, as they run as root.
|
||
You just have to install as a non-admin user and then use "chown -R"
|
||
to fix the owner.
|
||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815137"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><div></div></div><p>
|
||
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.
|
||
</p><p>
|
||
The general mechanism for implementing an adminstrative installation involves
|
||
running <b class="command">X:\setup /A</b>, where X is the drive letter of either CDROM or floppy.
|
||
</p><p>
|
||
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.
|
||
</p><p>
|
||
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.
|
||
</p><div class="itemizedlist"><ul type="disc"><li><p>
|
||
As soon as the administrative installation (unpacking) has completed
|
||
set the following parameters on the share containing it:
|
||
</p><pre class="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
|
||
</pre></li><li><p>Now you are ready to run the setup program from the Microsoft Windows
|
||
workstation as follows: <b class="command">\\"Server_Name"\MSOP95\msoffice\setup</b>
|
||
</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882001"></a>Microsoft Access database opening errors</h2></div></div><div></div></div><p>
|
||
Here are some notes on running MS-Access on a Samba drive from <a href="stefank@esi.com.au" target="_top">Stefan Kjellberg</a>
|
||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</td></tr><tr><td>Make sure that you open the database as 'shared' and to 'lock modified records'</td></tr><tr><td>Of course locking must be enabled for the particular share (smb.conf)</td></tr></table><p>
|
||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Compiling and installing Samba on a Unix host </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Common errors</td></tr></table></div></body></html>
|