Deployment when previous application is manual install.
My network have around 150 client, all client application is install by manual and have various version.
Applicaion that manual installed on the client is:
Winzip7,8,9
Acrobat Reader 4,5,6,7
Office2000 , XP
Symantec Antivurus Corp 7,8,9
The applicaion that I want to deploy via GPO is Winzip9, Acrobat Reader 7, Office XP, Symantec Antivirus Corp 9.
The question is
1. What happen when I deploy the new application over the existing application(different version and same version)?
2. The previous version applicaion will auto uninstall and replace with the new version or not?
3. If the previous version will not auto uninstall, what is the best way to uninstall previous version and deploy the new version via GPO?
Applicaion that manual installed on the client is:
Winzip7,8,9
Acrobat Reader 4,5,6,7
Office2000 , XP
Symantec Antivurus Corp 7,8,9
The applicaion that I want to deploy via GPO is Winzip9, Acrobat Reader 7, Office XP, Symantec Antivirus Corp 9.
The question is
1. What happen when I deploy the new application over the existing application(different version and same version)?
2. The previous version applicaion will auto uninstall and replace with the new version or not?
3. If the previous version will not auto uninstall, what is the best way to uninstall previous version and deploy the new version via GPO?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
nmi
19 years ago
Personally, I believe that it will depend on the application itself. If you install a newer version to the same directory, then it is unlikely to deinstall the old version (some setups will detect and remove prior versions but they are the exception). Overwriting the existing version with the same version should not pose an issue although what will happen when you remove it is indeterminable.
Since most of your apps have been deployed manually, you will likely find that they will have to also be removed manually.
I suspect the easiest answer to your questions is to build a test machine with some of the existing apps then deploy your new versions by GPO and see what happens.
nmi
Since most of your apps have been deployed manually, you will likely find that they will have to also be removed manually.
I suspect the easiest answer to your questions is to build a test machine with some of the existing apps then deploy your new versions by GPO and see what happens.
nmi
Posted by:
Bladerun
19 years ago
This is the same problem that I'm facing. We have about 300 manual installs of the Blackberry software, and I need to deploy a packaged version of 4.0.
The bottom line is that we'll need to do manual removals, and then installs via policy. The transition from manual to managed in GPO deployment is a pain.
I've been theorizing that you COULD create an msi that installs a wise script (or any other script for that matter, i'm just familiar w/ wise) and then has a custom action to run it. I've built uninstall wisescripts that have logic built in to detect what version of what product is installed, and then to run either static uninstall commands, or I've even had them parse the reg setting with the uninstall string and run that.
I'd LOVE to test this theory, but my new job only has Install Shield Admin Studio [:'(]
The bottom line is that we'll need to do manual removals, and then installs via policy. The transition from manual to managed in GPO deployment is a pain.
I've been theorizing that you COULD create an msi that installs a wise script (or any other script for that matter, i'm just familiar w/ wise) and then has a custom action to run it. I've built uninstall wisescripts that have logic built in to detect what version of what product is installed, and then to run either static uninstall commands, or I've even had them parse the reg setting with the uninstall string and run that.
I'd LOVE to test this theory, but my new job only has Install Shield Admin Studio [:'(]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.