Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 164
  • Last Modified:

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-E36C693DC07D} /passive /norestart
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?
0
kwatt562
Asked:
kwatt562
  • 7
  • 5
1 Solution
 
Vadim RappCommented:
The answer is in your deployment tool. You probably have to tell it to ignore the failure of pre-deployment task.
0
 
kwatt562Author Commented:
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?
0
 
Vadim RappCommented:
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.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
kwatt562Author Commented:
there is no documentation in the tool, checked with the provider too :(
0
 
Vadim RappCommented:
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?
0
 
kwatt562Author Commented:
Desktop Central
The only numerical error value in the logs was 1605, tried that but didn't affect anything
0
 
Vadim RappCommented:
I would write a script that encapsulated calling msiexec, so the script would return 0 in any case.  You probably can make it as easy as to call not msiexec <parameters> but cmd /c msiexec <parameters> .
0
 
Vadim RappCommented:
...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.
0
 
kwatt562Author Commented:
thanks again, encapsulating the msi did the trick, can you explain more about what it does?
0
 
Vadim RappCommented:
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.
0
 
Vadim RappCommented:
>The drawback is black window showing on the screen.

...here's freeware that overcomes this, and more:

http://www.ntwind.com/software/hstart.html
0
 
kwatt562Author Commented:
great thanks a lot
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now