I looked into dependencies with another deployment (Lync Basic to Lync Enterprise), and I don't think my logic is working.
The systems already have Lync Basic installed. So I have a Lync Enterprise Installer which works fine alone. I have a Lync Basic Uninstaller which works fine on its own. So I decided to use dependencies, but I don't have the logic to tell the system "If you detect Lync Basic, Uninstall then Install Lync Enterprise" I only have the ability to say " Install Lync Enterprise, then uninstall Lync Basic" but this is when it automatically does it. Stephen's idea worked for the Winzip and 7-zip, but it didn't work for my Lync 2013 deployment. So I thought maybe I will give dependencies a try. I am still looking into it, as I think I need to get it for first detect Basic THEN do the uninstall THEN do the Install of Enterprise. It is too bad this cannot be an upgrade, would be much easier. Thanks From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Sent: Tuesday, September 03, 2013 1:48 PM To: [email protected] Subject: Re: [mssms] When creating an install and uninstall package it runs automatically? Wait, why aren't you using a dependency? On Tue, Sep 3, 2013 at 9:33 AM, Kevin Johnston <[email protected]<mailto:[email protected]>> wrote: I have done this a few times and the results are always the same. I have created a 7-zip install Application and I created a winzip uninstall Application. Both are set as available and both work perfectly OK when they are separate. But then I wanted to get fancy and have it so that it uninstalls winzip first then installs 7-zip. In 7-zip I have the Winzip uninstall as supersedence, where I think the issue happens, because when I add this to a collection it instantly starts the uninstall (almost like it becomes required), when I am hoping that a user can choose to kick start the uninstall/install themselves. I assume that most CM admins do this so it takes the work away from the end user having to have 2 tasks to complete? Thanks, Kevin Johnston
