docs/docbook/faq/clientapp.sgml

   1 <chapter id="FAQ-ClientApp">
   2 <title>Specific client application problems</title>
   3
   4 <sect1>
   5 <title>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</title>
   6 <para>
   7 When installing MS Office on a Samba drive for which you have admin
   8 user permissions, ie. admin users = username, you will find the
   9 setup program unable to complete the installation.
  10 </para>
  11
  12 <para>
  13 To get around this problem, do the installation without admin user
  14 permissions The problem is that MS Office Setup checks that a file is
  15 rdonly by trying to open it for writing.
  16 </para>
  17
  18 <para>
  19 Admin users can always open a file for writing, as they run as root.
  20 You just have to install as a non-admin user and then use "chown -R"
  21 to fix the owner.
  22 </para>
  23
  24 </sect1>
  25
  26 <sect1>
  27 <title>How to use a Samba share as an administrative share for MS Office, etc.</title>
  28
  29 <para>
  30 Microsoft Office products can be installed as an administrative installation
  31 from which the application can either be run off the administratively installed
  32 product that resides on a shared resource, or from which that product can be
  33 installed onto workstation clients.
  34 </para>
  35
  36 <para>
  37 The general mechanism for implementing an adminstrative installation involves
  38 running <command>X:\setup /A</command>, where X is the drive letter of either CDROM or floppy.
  39 </para>
  40
  41 <para>
  42 This installation process will NOT install the product for use per se, but
  43 rather results in unpacking of the compressed distribution files into a target
  44 shared folder. For this process you need write privilidge to the share and it
  45 is desirable to enable file locking and share mode operation during this
  46 process.
  47 </para>
  48
  49 <para>
  50 Subsequent installation of MS Office from this share will FAIL unless certain
  51 precautions are taken. This failure will be caused by share mode operation
  52 which will prevent the MS Office installation process from re-opening various
  53 dynamic link library files and will cause sporadic file not found problems.
  54 </para>
  55
  56 <itemizedlist>
  57 <listitem><para>
  58 As soon as the administrative installation (unpacking) has completed
  59 set the following parameters on the share containing it:
  60 </para>
  61
  62 <para><programlisting>
  63 [MSOP95]
  64         path = /where_you_put_it
  65         comment = Your comment
  66         volume = "The_CD_ROM_Label"
  67         read only = yes
  68         available = yes
  69         share modes = no
  70         locking = no
  71         browseable = yes
  72         public = yes
  73 </programlisting></para>
  74
  75 </listitem>
  76
  77 <listitem>
  78 <para>Now you are ready to run the setup program from the Microsoft Windows
  79 workstation as follows: <command>\\"Server_Name"\MSOP95\msoffice\setup</command>
  80 </para>
  81 </listitem>
  82 </itemizedlist>
  83
  84 </sect1>
  85
  86 <sect1>
  87 <title>Microsoft Access database opening errors</title>
  88
  89 <para>
  90 Here are some notes on running MS-Access on a Samba drive from <ulink url="stefank@esi.com.au">Stefan Kjellberg</ulink>
  91 </para>
  92
  93 <para><simplelist>
  94 <member>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</member>
  95 <member>Make sure that you open the database as 'shared' and to 'lock modified records'</member>
  96 <member>Of course locking must be enabled for the particular share (smb.conf)</member>
  97 </simplelist>
  98 </para>
  99
 100 </sect1>
 101 </chapter>