Jump to content


Sign in to follow this  
milemar

Direct Collection and app deployment

Recommended Posts

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,

Share this post


Link to post
Share on other sites

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.

  • Like 1

Share this post


Link to post
Share on other sites
Ath3na

What 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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

My mistake, as you didn't mention ConfigMgr 2007 and you did mention application, I assumed you were using ConfigMgr 2012. In ConfigMgr 2007 you can't configure detection methods. The only method to prevent the installation on system that already have that software is to create a custom script or filter them out of your collections.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...