Hi guys,
if some Kind of strange behavior where I´am not 100% sure what is causing this... So here is the Situation: I´ve created an application "Nvidia Drivers" with 4 deployments types. Each DT uses a global condition as requirement to decide, based on the Video controller, which DT is used. The application is deployed as available AND I´ve also added the same application to a task sequence. This TS is still the one which was used to install these and most of all our clients. The TS is also deployed as available to these Clients (PXE and media only). After all that stuff we have seen some unexpected installations in the field, even after removing the deployment. So what is going on here? Is there some sort of "loopback" where the clients geht the application from the TS where they once installed from? I´ve found some blog and other forum posts
- http://blogs.technet.com/b/umairkhan/archive/2014/03/08/configmgr-2012-application-supersedence-behavior-with-task-sequence-deployments.aspx
- https://social.technet.microsoft.com/Forums/en-US/935c3556-e8a1-4146-95f2-6e6822dbb2f8/application-dependencies-installing-with-no-deployment-of-parent-application?forum=configmanagerapps#d98eaf8c-df65-403c-9204-713b4a5547a9
- https://social.technet.microsoft.com/Forums/en-US/c9cd7953-35a2-46eb-bedc-6427c15e92c4/applications-in-a-task-sequence-reinstall-when-app-changes?forum=configmanagerapps
with similar issues, but always related do supersedence. I don´t have supersedence used here. Can anybody confirm or refute my speculation. I can provide log files shots in about ~8 hours since it is 11pm for me now, but you guys sure have some great ideas until I´am back in the Office ;)
Thank´s a lot...