Hi All, I'm changing our SCCM environment to install applications from AD Security groups. What process/procedure do I need to follow to speed up the deployment - from a servicedesk advisor putting a machine in a group to the software appearing on the machines, and the same for removal of software. For removal of software I used a query based collection which interrogates a machine, if the software displayname appears in Add/Remove programs but the machine is not in the relevant AD group, the software will be uninstalled. Therefore, I think I need to 'tweak'; AD System Group Discovery, AD System Discovery, Hardware Inventory... not sure what else. What is a good time period for this? I would think that from a PC being put in a group to installation starting on client should be no longer than 30 minutes? Is this a good time? Thanks in advance. Peter

I do the AD system group discovery to run every 30 min for discovering the computers that are added to AD sec group. and all of my query based colllections will update their membership for every 30 min which suffice to install the applications on the requested computers. It depends on the organisation sometimes they dont want to schdule it for every 30 min (collection and discovery) bcz of network bandwith issues. AD system discovery and Heartbeat will not impact on Deploying applications Via AD sec group but again they are required for discovering the computer and refreshing/updating the database. //Eswar Koneti @ www.eskonr.com

If you are targetting only new machines which are not present in the DB. Then you can try installing SCCM SP2 R3. R3 will provide options to do delta discovery and delta eval cycle for collection.Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

What is a good time period for this? I would think that from a PC being put in a group to installation starting on client should be no longer than 30 minutes? Is this a good time? That doesn't work for each and every environment. Discovery + collection update + policy polling have to be less than 30min. That's not realistic for larger environments. 3rd party tools like http://www.systemcentertools.com/esd2007.html or http://sccmspeedup.codeplex.com/ can help in that situationTorsten Meringer | http://www.mssccmfaq.de

An00p, this will be for all machines, including ones already in the database. Torsten, Are you saying it should be a shorter period than 30 mins or longer? What service/client method send the add/remove program data back to sccm?

Longer periods, because the load on the ConfigMgr server is pretty high if you set such "aggressive" schedules, but that depends on many factors (# of clients reporting to a site, hardware specs and setup etc)Torsten Meringer | http://www.mssccmfaq.de