Cancel msiexec application removal if not found
Hi
I am setting up a deployment of skype 7 via our deployment tool. We previously managed and deployed Skype 6.18 via GPO, so I have set a pre-deployment task to remove 6.18 via the application GUID.
cmd file is MsiExec.exe /X{1845470B-EB14-4ABC-835B
Then Skype 7 deploys.
However if for some reason Skype has been uninstalled the whole thing fails as it cant find 6.18 to remove, anyway to set it to skip 6.18 removal should it not be found?
I am setting up a deployment of skype 7 via our deployment tool. We previously managed and deployed Skype 6.18 via GPO, so I have set a pre-deployment task to remove 6.18 via the application GUID.
cmd file is MsiExec.exe /X{1845470B-EB14-4ABC-835B
Then Skype 7 deploys.
However if for some reason Skype has been uninstalled the whole thing fails as it cant find 6.18 to remove, anyway to set it to skip 6.18 removal should it not be found?
Vadim Rapp
The answer is in your deployment tool. You probably have to tell it to ignore the failure of pre-deployment task.
ASKER
Hi, thanks for that
In the tool I have two text fields below my added script
Script Arguments :
Proceed if exit code is :
I am new to application deployment, can you help assist what I need to enter here to allow the install to run if the pre-deployment script is unable to locate 6.18 Skype?
In the tool I have two text fields below my added script
Script Arguments :
Proceed if exit code is :
I am new to application deployment, can you help assist what I need to enter here to allow the install to run if the pre-deployment script is unable to locate 6.18 Skype?
You need to tell it to "Proceed if exit code is : (anything)". How to do that probably can be found in documentation on the tool.
ASKER
there is no documentation in the tool, checked with the provider too :(
Then you probably have these 3 choices: (1) contact the real developer (2) experiment by trying some well-known values, like * or -1 (3) look in the log, if there's one, maybe it tells there what was expected (4) choose another deployment tool.
What is the tool, by the way?
What is the tool, by the way?
ASKER
Desktop Central
The only numerical error value in the logs was 1605, tried that but didn't affect anything
The only numerical error value in the logs was 1605, tried that but didn't affect anything
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
...also maybe ask on their forum at https://forums.manageengine.com/desktop-central; another way is to find real name of their developer from their blog, and try to call directly by name. Depending on their size, policies, and other factors, it may work.
ASKER
thanks again, encapsulating the msi did the trick, can you explain more about what it does?
it's a program (command shell) that in turn calls msiexec, waits for the completion, and quits. Regardless of the return code returned by msiexec, the shell always returns 0. The drawback is black window showing on the screen.
>The drawback is black window showing on the screen.
...here's freeware that overcomes this, and more:
http://www.ntwind.com/software/hstart.html
...here's freeware that overcomes this, and more:
http://www.ntwind.com/software/hstart.html
ASKER
great thanks a lot