Reader SCUP problem - detection logic issue?

Report · Feb 17, 2015

Sorry about crossposting, but frankly the Adobe forum navigation is atrocious, so when I originally posted this to the general Reader forum, I was unaware that this forum even existed.

Anyway...

I'm starting to test the deployment of Reader updates via SCUP.

What I'm seeing is that Config Manager says I have X number of clients that require Reader 11.0.n - fine.

It seems confused about what systems need which update, though. E.g. it says that my workstation requires 11.0.2, 11.0.5, and 11.0.8 even though I'm actually running 11.0.10.

SCUP 2011, SCCM 2012 SP1

Anyone know what's going on/what I need to look for, here?

Report · Mar 18, 2015

We are also seeing the same issue with 11.0.10 MUI. We have a mixed environment as far as versions. We have a lot of machines that are up to date already with 11.0.10. It appears on the machines with 11.0.10. MUI they are also getting 11.0.2, 11.0.5, and 11.0.8 and when the updates apply they are left with 11.0.2 installed? How is the installed version being detected?

Report · Mar 19, 2015

Yeah, I'm seeing similar.

I deployed just .08 as a test. My workstation, formerly on .10 got downgraded to .08. Reporting shows it as being in need of .05 and .02, but NOT in need of .09 or .10. This is a mess.

Report · Mar 19, 2015

...or maybe it didn't actually downgrade. Hard to tell.

Help-->About says it's 11.0.08. Programs and Features says it's 11.0.08. SCCM report says it's 11.0.08.

Properties of AcroRd32.exe say it's 11.0.10.32.

So the actual executable is the right version, but parts of the product itself are confused at to what version it is. Maybe some of the other 192 files are the wrong version, but Adobe only knows.