[Samba] Samba share breaks msi-install process

[Jeremy Allison]

On Mon, Jan 03, 2005 at 05:00:07PM +0100, Samba list wrote:
> Hi,
> 
> I need advise by someone with knowledge about the inner workings of
> MS Installer to explain the behavioural difference between using a
> Samba share and a native Windows share.
> 
> I'm trying to install a (commercial) package on multiple
> Windows machines. This package shares several database-like files
> in a central directory on a central share. Using a share on a Windows
> XP-machine works OK leaving the central files intact, using a Samba share
> breaks things.
> 
> First I install the package on the first machine (say pcA).
> The central directory on the share is created and the files are installed.
> The package now works excellent.
> 
> Then I install the package on the second machine (say pcB).
> The central share is found, but on Samba the important "database" file is
> reinitialised, deleting all the information put into it using pcA.
> 
> The shares are mapped using the same account name and password (only
> one PC needs to be active at the same time).
> I have tried both Samba Version 2.0.5a, and Version 3.0.3pre2-2.pre2.
> Both behave exactly alike.

Can you retry this with the recently release 3.0.11pre release - if you
still get the problem we'll follow up.

Thanks,

	Jeremy.