Uninstall of msi corrupts machines with Blue Screen of Death
We have an msi package (for Lotus Notes 6.5.4) that does not uninstall cleanly. When you attempt to uninstall this package it results in a blue screen of death and corrupts the machine making it a bit of a mess. This msi is deployed right now and used by almost 240 staff. Lotus Notes is a core application here so we can not afford to have 240 computers not functioning correctly.
I will call this msi --> Package A.
We have built a "new" msi for Lotus Notes 6.5.4 (Package B) that we want to replace Package A with. Package B installs and uninstalls cleanly with no corruption and BSOD.
We are using Active Directory and Group Policy to deploy software. We are using Windows 2000 server and workstations.
My question(s):,
1. How do we remove Package A from these 240 workstations without "actually" performing an uninstall of Package A from these workstations (because of the corruption and Blue Screen of Death outlined above).
2. We want to use Package B for all "new" workstation builds and any new staff that come on board.
Any thoughts or ideas on how to tackle this issue are most welcome.
John Falloon
I will call this msi --> Package A.
We have built a "new" msi for Lotus Notes 6.5.4 (Package B) that we want to replace Package A with. Package B installs and uninstalls cleanly with no corruption and BSOD.
We are using Active Directory and Group Policy to deploy software. We are using Windows 2000 server and workstations.
My question(s):,
1. How do we remove Package A from these 240 workstations without "actually" performing an uninstall of Package A from these workstations (because of the corruption and Blue Screen of Death outlined above).
2. We want to use Package B for all "new" workstation builds and any new staff that come on board.
Any thoughts or ideas on how to tackle this issue are most welcome.
John Falloon
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
aogilmor
18 years ago
if you know what is causing the bsod you could correct that after doing the removal of Package A. As part of the upgrade.
just thinking out loud here. if you add the "cure" for the bsod to the new "good" package, Package B, and add package A to the upgrade table of Package B it should remove package A and install Package B without the BSOD. You should then be able to install Package B and it'll remove Package A as part of the upgrade process.
Is there a way to cleanly get rid of package "A" without removing it? doubt it. you have a bad package and have to deal with it some way.
This kind of thing should be caught in QA. Learn from the bad experience and go over your QA procedures. If you don't have any, now is the time to do create them.
just thinking out loud here. if you add the "cure" for the bsod to the new "good" package, Package B, and add package A to the upgrade table of Package B it should remove package A and install Package B without the BSOD. You should then be able to install Package B and it'll remove Package A as part of the upgrade process.
Is there a way to cleanly get rid of package "A" without removing it? doubt it. you have a bad package and have to deal with it some way.
This kind of thing should be caught in QA. Learn from the bad experience and go over your QA procedures. If you don't have any, now is the time to do create them.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
