Staged Delivery of SCCM Packages
I'm looking for a best practice for deploying mandatory assignment SCCM applications in a staged fashion. The main goal is to catch exceptions missed in testing before the application borks every computer in the enterprise.
We have created collections starting with a small group of testing computers and IT dept then adding more computers to each subsequent collection. I like the idea of creating advertisements for each collection and setting the assignment time so each one starts a few hours after the previous. This does make the reporting a bit harder, checking and reconciling logs from each advertisement. The other method I'm considering is one advertisment in which we change the target collection every few hours. This has the disadvantage of not being able to schedule the entire deployment in advance. It does provide a single log file for the entire deployment.
Before VBSCAB suggest we do a better job of testing our packages, we don't manage the configuration of all our clients so there is some risk of a configuration unknown to us causing an exception in a package that was thoroughly tested. I'm interested if anyone knows of any caveats creating many advertisements that overlap somewhat in the target computers or changing the target collection on an active advertisement.