Hi Everyone,
I don't know if this is already a Known issue, But, wanted to share with everybody.
Scenario: Superseding (ONE of the suite of appplications) which were deployed onto the User machines with a (Newer version of one particular Application among the suite).
To be more clear, we are only replacing one of the application with a newer version among a suite of applications.
Problem:
The detection method of this (older version which was already deployed onto prod) has been to set to check the file version in the [INSTALLDIR]. Now, the newer version of that application has the (same files and folder structure) as the older one.
When we supersede, everything is fine, until after the installation of the new version of the application. When the Policy cycles run after some time for a different deployment then the (Supersedence logic to "uninstall" again kicks in thinking that it still haven't uninstalled the previous version because of the ("same files and folder structure") it uninstalls the newer version of the application.
Note: when I say, "same files & folder structure above", I mean the File version of that Particular file set to be detected in the older version of the application is the same in the newer version of the application too.
- Edited by Tightend 13 hours 23 minutes ago