Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, February 18, 2016 2:48 PM
Hello,
I'm trying to uninstall an application, which I have targeted to three differen't collections with computers in. I've removed any references, such as dependencies and requirements for the application - including any revisions that might have the older references in as well.
The compliance was high and a lot of the clients were uninstalling, except for the odd one which I checked myself manually. However, we had to re-add the application back into the Task Sequence for an image previously use and suddenly we've got errors stating "Conflicts with another application deployment" "Rule is in conflict with other rules".
The computers that are targeted from the uninstall are in a collection which is then included in a collection we've assigned the task sequences to.
Am I right in saying that once the task sequence has been completed it wouldn't have any further rules or enforcement i.e. installs/uninstalls post deployment.
Ollie
All replies (1)
Friday, April 29, 2016 6:25 PM
If I understand correctly, you have an application deployed to UNINSTALL, and a task sequence deployed to the same target collection to INSTALL the same application.
If the application to UNINSTALL is still deployed to the collection with REQUIRED deployment purpose, then the post deployment behavior after task sequence would be the re-discovery where the application would automatically get detected again, and the UNINSTALL deployment will get reinforced.
If possible, I would change the deployment purpose for the UNINSTALL deployment to Available or remove the uninstall deployment if not needed any more, and also ensure to select the option for the application to be assigned to task sequence without being deployed to a collection.