I have made sure that the baseline is set to use latest revision, and even redeployed the baseline to some test machines, but they all still show and old revision.

I have deployed another baseline with the same behavior. In both cases the initial revision is the one listed.

Can anyone explain why?

We are on 2012 SP1 CU4.

Cheers

did you initiate the machine policy action ?review the logs DCMagent.log and CIagent.log ?

addition info about troubleshooting http://blogs.msdn.com/b/scom_2012_upgrade_process__lessons_learned_during_my_upgrade_process/archive/2012/09/21/compliance-settings-sccm-2012.aspx

did you initiate the machine policy action ?review the logs DCMagent.log and CIagent.log ?

addition info about troubleshooting http://blogs.msdn.com/b/scom_2012_upgrade_process__lessons_learned_during_my_upgrade_process/archive/2012/09/21/compliance-settings-sccm-2012.as

Hi,

Have you tried to remove the old deployment, wait for the baseline disappear from the client? Then re-deploy the baseline.

Best Regards,

Joyce

Hi,

Have you tried to remove the old deployment, wait for the baseline disappear from the client? Then re-deploy the baseline.

Best Regards,

ok,it now makes little sense about the issue. Changing the version of CI do not change the CB Version until you do some modifications to CB.

By Default,the CB always use the latest version of CI(Which you set via CB Properties).

I looked at the client WMI to find if there is any info about what CI Version did the client receive but no info. May be you can try verbose logging if that track any additional info into logs.

try to look at CIStatestore.log ,it will tell you the CI version with Priority .I believe,the priority is nothing but the CI Version.you should see something when New CB applied with any CI changes with line An existing CI state is changed