Ask a questionAsk a question
 

AnswerFrequently updated applications and advice on how NOT to reset my baseline

  • Wednesday, September 16, 2009 11:17 PMTonyMusor Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

      I release new baselines and images every quarter worldwide. The image includes items like shockwave, flash, quicktime, etc. The release period is one month for ~2500 computers. During the one month period, if any updates for these products are released or zero days are released then they are slipstreamed into my deployment. 

      My problem is updating the CI's to reflect these new versions, resets the baseline, and then I have to wait 1-3 days for evaluation to complete and all systems to report. This totally messes up my reporting, and I essentially lose two days of reporting any time a zero day is released. No too mention my heart sinks when my compliancy drops back down to zero again.

      I was thinking of creating the CI so it would look for the version number with a greater than or equal to. So that when the new version comes out, it will show up as compliant. Problem being most of my CI's reference the registry and versions in the registry are string based, so greater than or equal to is not an option. I will probably switch most of them to file versions to support this. 

      How is everyone else dealing with their baselines and products that update very often? Do you put them into a seperate baseline or just reset the whole thing. I don't want to reset the baseline for the whole month if possible.

     Thanks guys,
            The Moose

Answers

  • Wednesday, September 23, 2009 11:15 PMKevinM [MSFT]MSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Personally I would put things that are known to be updated often in the same baseline, or each in their own baseline, knowing that it will be reset each time there is an update.
    This posting is provided "AS IS", provides no warranties, and confers no rights. -- Kevin

All Replies

  • Wednesday, September 23, 2009 11:15 PMKevinM [MSFT]MSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Personally I would put things that are known to be updated often in the same baseline, or each in their own baseline, knowing that it will be reset each time there is an update.
    This posting is provided "AS IS", provides no warranties, and confers no rights. -- Kevin