Tim: I believe the issue here is that fact that you are suppressing the required reboot after the upgrade. Many of the AFS libraries are loaded by the Explorer shell and Winlogon. As a result, they can't be replaced until a reboot occurs.
Jeffrey Altman Tim Czerwonka wrote: > I'm trying to upgrade from OpenAFS 1.4.1 (installed via the MSI, not as > an upgrade) to OpenAFS 1.5.2 on a Windows XP SP2 workstation. I'm not > having any luck; I'm wondering if anyone can point out what I'm missing here. > > OpenAFS 1.4.1 installed via: > > msiexec /q /i \\server\install.xp\postinst\msi\afs-1.4.1\afs.msi ALLUSERS=1 > REBOOT=Suppress TARGETDIR=C:\ > TRANSFORMS=\\server\install.xp\postinst\msi\afs-1.4.1\FILES\openafs-transform.mst > > afs.msi is a symlink to openafs-en_US-1-4-1.msi. The transform sets the cell > name, sets an option or two -- nothing clever or complex. > > This works fine -- I get a functioning 1.4.1 client with the changes in > the transform applied as anticipated. > > > > For the upgrade, I try: > > msiexec /q /fvomus c:\temp\openafs-en_US-1.5.2.msi /l*v c:\afs1.log > ALLUSERS=1 REBOOT=Suppress TARGETDIR=C:\ > TRANSFORMS=c:\temp\openafs-transform.mst > > (The transform was done against the 1.5.2 msi and sets the same options as > the 1.4.1 msi.) > > The logfile shows that the installation was successful. > (/afs/cs.wisc.edu/u/t/i/timc/public/afs1.txt) > > However, after a reboot it appears as if the 1.5.2 AFS client was never > actually installed. rxdebug still shows that I'm running 1.4.0008. > > > > The 1.5.2 msi and transform work just fine (the client behaves better than > 1.4.1 for our purposes) if it's a clean install without prior AFS client. > > > Any insight as to what I'm doing wrong is appreciated! > > Thanks-- > --Tim > > > Tim Czerwonka, [EMAIL PROTECTED] > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info
smime.p7s
Description: S/MIME Cryptographic Signature
