I think this is a pretty easy question. I have a few SCCM sites that have a lot of collections and advertisements. I'm trying to convince them it is a bad idea to have so many. I need microsoft documentation on why it is a bad idea to have a lot of collections and advertisements.

That is just it. I'm trying to configure our environment appropriately. We have many software packages, collections, and advertisements. I'd like to give my admins guidance on general house cleaning. There are a number of things we are doing that I think we shouldn't but I would like some official guidance to back me up.

There are a number of things we are doing that I think we shouldn't but I would like some official guidance to back me up. There's no official guideline or one fits all solution. You are the only one that knows what's going on in your ConfigMgr infrastructure. So how should we help you without being able to analyse your environment? One suggestion is always right (stolen from Sherry's signature): "Standardize. Simplify. Automate."

Microsoft only says that you shouldn't have more than 10 levels of Collections since it could take days to update all the way down due to different schedules you might have setup on each collection. The only limitation to how many packages/collections/adv is the SQL database speed/disk size/DP needed to push all the packages to all the machines so really it is hard to judge the best size. Really you don't need to focus on so man but rather on Folders and groups. You know you can create a collection with nothing in it and call it Adobe (no update schedule) and then make all the sub collections like adobe reader/pro etc. This allows you to manage the enviroment.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com