surfincow Posted April 25, 2014 Report post Posted April 25, 2014 As I test, I removed my computer from the collection that this task sequence is deployed to. Updated machine policy and ran Application Deployment Eval Cycle and the rogue application no longer shows up. So it is something with this application being in this TS which is deployed to this collection that is definatly causing the problem. How and why an application within a TS is able to be detected and ran when the TS itself is not is a mystery.. Quote Share this post Link to post Share on other sites More sharing options...
