Ask a questionAsk a question
 

AnswerBest practices for phased roll-outs for software distribution

  • Friday, November 06, 2009 10:14 PMfenster.sccm Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm rolling out an application to laptops only.  At present I have a collection that is based on an AD group and members of a laptop collection (WQL query).  This is my pilot group.  I plan on rolling the application out in phases so will start with 10%, 30%, 60% etc.  When that is complete I plan on pointing the advertisement to the laptop collection.  Here are my questions:

    1. To do the phased rollout is it best practice to use multiple collections and mulitple advertisements?
    2. When I finally point an advertisement to the laptop collection, how can I be sure the application won't reinstall on those machines that already have the application.  Note, I plan on setting Rerun if previous failed on all advertisements. 
    3. Or should I add the various phases in AD groups and then once I'm done remove all the groups from the collection and change it's membership to be the WQL query based on a laptops?

    So basically what are the best practices for doing phased rollouts and ensuring the applications don't get reinstalled?

    Thanks

Answers

  • Saturday, November 07, 2009 7:53 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    #1: There is no one-fits-all solution. You could use part of the computer name to limit the number of targeted clients (for example: ending with A, then ending with B; but that depends on your naming standard).
    #2: It won't reinstall if it was successfully installed the first time (given that you set it to "Rerun if previous failed")
    #3: no need to create various AD groups.

All Replies

  • Saturday, November 07, 2009 7:53 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    #1: There is no one-fits-all solution. You could use part of the computer name to limit the number of targeted clients (for example: ending with A, then ending with B; but that depends on your naming standard).
    #2: It won't reinstall if it was successfully installed the first time (given that you set it to "Rerun if previous failed")
    #3: no need to create various AD groups.