milemar Posted March 25, 2015 Report post Posted March 25, 2015 Hi Guys, Maybe you can point me to the right directions. I have old SCCM server which is faulty and I am building a new one. The company choose to deploy application to the users not computer accounts. I have created a test collection "Deploy test app" with a direct membership rule to include AD security group "Test APP users". I have created advertisement to deploy application to that collection. As this is a deployment of new SCCM to production environment lots of the PCs already has that application installed. My question is how to prevent that application be deployed to those PCs? Thanks, Quote Share this post Link to post Share on other sites More sharing options...
Ath3na Posted March 25, 2015 Report post Posted March 25, 2015 If you are using the application model to deploy applications then if the application is already on the machine the application detection rule will detect the software already present. This will then mark the deployment as success but the application will not attempt to re-install the software. You can migrate from SCCM 2007 / 2012 to 2012. You could migrate all your applications/packages/images/collections, then clients.This way all your old figures for deployment would be carried across to the new SCCM installation and you can continue from where you left off. 1 Quote Share this post Link to post Share on other sites More sharing options...
milemar Posted March 26, 2015 Report post Posted March 26, 2015 Thanks for the quick reply Quote Share this post Link to post Share on other sites More sharing options...
milemar Posted April 30, 2015 Report post Posted April 30, 2015 Ath3naWhat do you mean "If you are using application model"? I have pushed SCCM clients install from new SCCM server to assign those system to new SCCM and I see that many applications are deployed again even if that application is already installed. Why is that? Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 30, 2015 Report post Posted April 30, 2015 That's an indication that the detection method is not correct. Quote Share this post Link to post Share on other sites More sharing options...
milemar Posted May 1, 2015 Report post Posted May 1, 2015 OK. How can I change that? Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted May 1, 2015 Report post Posted May 1, 2015 I would start by checking the AppEnforce.log to see if that's indeed the problem. Quote Share this post Link to post Share on other sites More sharing options...
milemar Posted May 6, 2015 Report post Posted May 6, 2015 Isn't the log present only in SCCM 2012? Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted May 6, 2015 Report post Posted May 6, 2015 The log file I mentioned is a client log file, which can be found on the client in C:\Windows\CCM\Logs. Quote Share this post Link to post Share on other sites More sharing options...
milemar Posted May 7, 2015 Report post Posted May 7, 2015 There is no such a log in SCCM 2007. I have checked both users (C:\Windows\System32\CCM\Logs) and server location. Even if you try to Google it all results are related to SCCM 2012. Quote Share this post Link to post Share on other sites More sharing options...
