Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

Question

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence.  I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml.  The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
 <Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
 <Setting Id="Reboot" Value="Never" />
 <Setting Id="SETUP_REBOOT" Value="NEVER" />
 <OptionState Id="ProductFiles" State="Local" Children="force" />
 </Configuration>
The detection method is the folder path to see that office 14 exists.  When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue. 
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall.  The application is in the supersedence tab for Office 365 2013. This never installs.  If I create a softare distribution and deploy it on its own it uninstalls without issue. 
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this.  The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool.  I can install this with the application I created using the appv5 package created with the click to run tool.  The issue is we need Office 2010 and Lync 2010 uninstalled first. 
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013. 
I have looked at many articles and so far it is not working for us.  Any help appreciated to get us to the cloud.
Thanks,
Brit

Answer 1

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do.  The detection method seems to be hanging things up.  On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com