MSI installs to floppy
We use Zenworks to deploy our apps and Wise to package them. We noticed last year that one of our applications would fail if a user installed or verified it with a floppy present. As we have deployed more msi packages the problem appeared more frequently but not consistently enough to troubleshoot.
This has occured with Wise PS and vendor msi's. I just installed approx 15 applications from the Novel application launcher with a floppy in the drive and it happened with two: Groupwise and Visual Manufacturing (an ERP program.)
The unfortunate part is that when it does happen the app will never install properly again and the machine often has to be reimaged. It has also happened with zips and as I said it is not consistent.
I did note that when running any msi, either via Zenworks or locally, the installer "talks" to the floppy but only rarely does it attempt to write there.
I am not sure if this is a Zenworks or msi issue. I have checked the apps I created and there is no reference to the floppy nor was there was a floppy in the drive when I created it. Can't vouch for the vendor packages.
Any help would be appreciated.
Thanks,
Steve
This has occured with Wise PS and vendor msi's. I just installed approx 15 applications from the Novel application launcher with a floppy in the drive and it happened with two: Groupwise and Visual Manufacturing (an ERP program.)
The unfortunate part is that when it does happen the app will never install properly again and the machine often has to be reimaged. It has also happened with zips and as I said it is not consistent.
I did note that when running any msi, either via Zenworks or locally, the installer "talks" to the floppy but only rarely does it attempt to write there.
I am not sure if this is a Zenworks or msi issue. I have checked the apps I created and there is no reference to the floppy nor was there was a floppy in the drive when I created it. Can't vouch for the vendor packages.
Any help would be appreciated.
Thanks,
Steve
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
ewall
18 years ago
A couple thoughts...
1) You could add the property ROOTDRIVE=C:\ to the MSIs to force them to go to the C:-drive (otherwise Windows Installer will pick the drive with the most free space normally). You can add this to the MSI's Property table, or just specify it on the command line like so:
2) To remove the broken installs that sent parts to the floppy drives, I'd recommend using the program MSIZAP.EXE from the Windows Installer resource kit. During packaging, I often make myself a "force_uninstall.bat" file with the following commands:
Good luck!
1) You could add the property ROOTDRIVE=C:\ to the MSIs to force them to go to the C:-drive (otherwise Windows Installer will pick the drive with the most free space normally). You can add this to the MSI's Property table, or just specify it on the command line like so:
msiexec.exe /i My_Program.msi ROOTDRIVE="C:\" /qb!-2) To remove the broken installs that sent parts to the floppy drives, I'd recommend using the program MSIZAP.EXE from the Windows Installer resource kit. During packaging, I often make myself a "force_uninstall.bat" file with the following commands:
msiexec.exe /x {MY_MSI_GUID} REMOVE=ALL /qb!-
msizap.exe TW! {MY_MSI_GUID}Good luck!
Posted by:
BobTheBuilder
18 years ago
Good stuff ewall,
Additionally there is this Microsoft MSI cleanup utility (<click link) which you can use to clean up a bad MSI installation.
So rather than rebuilding the workstation you could run this util and clean up the mess and then re-run the install (sans floppy disk). It might save a little time!
Additionally there is this Microsoft MSI cleanup utility (<click link) which you can use to clean up a bad MSI installation.
So rather than rebuilding the workstation you could run this util and clean up the mess and then re-run the install (sans floppy disk). It might save a little time!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
