docs/faq/FAQ-ClientApp.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
   2 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.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-Config.html" title="Chapter 3. Configuration problems"><link rel="next" href="FAQ-errors.html" title="Chapter 5. 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 4. Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Config.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><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter 4. Specific client application problems</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2808466">MS Office Setup reports &quot;Cannot change properties of '\\MSOFFICE\\SETUP.INI'&quot;</a></dt><dt><a href="FAQ-ClientApp.html#id2808495">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2808433">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808466"></a>MS Office Setup reports &quot;Cannot change properties of '\\MSOFFICE\\SETUP.INI'&quot;</h2></div></div><p>
   3 When installing MS Office on a Samba drive for which you have admin
   4 user permissions, ie. admin users = username, you will find the
   5 setup program unable to complete the installation.
   6 </p><p>
   7 To get around this problem, do the installation without admin user
   8 permissions The problem is that MS Office Setup checks that a file is
   9 rdonly by trying to open it for writing.
  10 </p><p>
  11 Admin users can always open a file for writing, as they run as root.
  12 You just have to install as a non-admin user and then use &quot;chown -R&quot;
  13 to fix the owner.
  14 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808495"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><p>
  15 Microsoft Office products can be installed as an administrative installation
  16 from which the application can either be run off the administratively installed
  17 product that resides on a shared resource, or from which that product can be
  18 installed onto workstation clients.
  19 </p><p>
  20 The general mechanism for implementing an adminstrative installation involves
  21 running <b>X:\setup /A</b>, where X is the drive letter of either CDROM or floppy.
  22 </p><p>
  23 This installation process will NOT install the product for use per se, but
  24 rather results in unpacking of the compressed distribution files into a target
  25 shared folder. For this process you need write privilidge to the share and it
  26 is desirable to enable file locking and share mode operation during this
  27 process.
  28 </p><p>
  29 Subsequent installation of MS Office from this share will FAIL unless certain
  30 precautions are taken. This failure will be caused by share mode operation
  31 which will prevent the MS Office installation process from re-opening various
  32 dynamic link library files and will cause sporadic file not found problems.
  33 </p><div class="itemizedlist"><ul type="disc"><li><p>
  34 As soon as the administrative installation (unpacking) has completed
  35 set the following parameters on the share containing it:
  36 </p><pre class="programlisting">
  37 [MSOP95]
  38         path = /where_you_put_it
  39         comment = Your comment
  40         volume = &quot;The_CD_ROM_Label&quot;
  41         read only = yes
  42         available = yes
  43         share modes = no
  44         locking = no
  45         browseable = yes
  46         public = yes
  47 </pre></li><li><p>Now you are ready to run the setup program from the Microsoft Windows
  48 workstation as follows: <b>\\&quot;Server_Name&quot;\MSOP95\msoffice\setup</b>
  49 </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808433"></a>Microsoft Access database opening errors</h2></div></div><p>
  50 Here are some notes on running MS-Access on a Samba drive from <a href="stefank@esi.com.au" target="_top">Stefan Kjellberg</a>
  51 </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>
  52 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Config.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 3. Configuration problems </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Common errors</td></tr></table></div></body></html>