Database SCCM Scan displays same count of x86 and x64 for an inventoried product

[TimothyG]

Hello,

We are in the initial stage of configuring our recently-purchased Enterprise Plus subscription.

When accessing the Database Scan option to query our existing SCCM database, the results show that for the majority (but not all) of the products that PatchMyPC supports that are also in our inventory, there are the exact same number of x86 installations as x64 installations.  See, for comparison, Google Earth and JAWS v. IrfanView in the attached screenshot.  Looking at a report in our console shows 21 total installations of Google Earth, not 42.

Is this Database Scan result expected? And if so, how will it impact which products we Select and Enable in order to have PatchMyPC update these products going forward?

Thank you for your assistance.

[Justin Chalfant (Patch My PC)]

Hey!

Thanks for the post, today, not all products are perfect when it comes to differentiating between 32-bit and 64-bit installations. Today, we are using the view: dbo.v_Add_Remove_Programs that contains both installed programs from the 32-bit and 64-bit registry hives. We can differentiate between some programs based on their Application Title name, but not all.

With that said, we do plan to split the product queries to the v_GS_ADD_REMOVE_PROGRAMS and v_GS_ADD_REMOVE_PROGRAMS_64 for products that install in the correct registry hive. This will help improve the 32/64-bit counts to be more accurate. We've had it on the radar internally for a few months. If you have a minute, I would recommend posting this feedback as an idea on https://ideas.patchmypc.com/ to make sure it stays on the radar.

[CharlieD]

1st off - Things are going swimmingly.  Love this product, recommendation to my CTO for purchase coming before the budget cycle ends. 

I just noticed the that applications being created in SCCM have comments that say "created with v1.5.8.4" vs the v1.5.9 that the installer I used says it contains.  Control Panel and the application GUI itself both state 1.5.9 as well.

could this be a relic from my 1st attempt at installation (which could very well have been on 1.5.8.4) before I had a chance to fully implement and request the demo license just this week.  I did install v1.5.9 earlier this week (2019-12-04), but did not check to see if I was installing over the top of a previous 1.5.8.4 attempt.  Again, not of grave concern, as things are running and generating just fine.  Just a oddity note to pass along.

[Justin Chalfant (Patch My PC)]

This was actually related to the core DLL being build 1.5.8.4 even on the 1.5.9 build. Note, we are on build 1.6.4 now do you not have self-update enabled?

1st off - Things are going swimmingly.  Love this product, recommendation to my CTO for purchase coming before the budget cycle ends. 

I just noticed the that applications being created in SCCM have comments that say "created with v1.5.8.4" vs the v1.5.9 that the installer I used says it contains.  Control Panel and the application GUI itself both state 1.5.9 as well.

could this be a relic from my 1st attempt at installation (which could very well have been on 1.5.8.4) before I had a chance to fully implement and request the demo license just this week.  I did install v1.5.9 earlier this week (2019-12-04), but did not check to see if I was installing over the top of a previous 1.5.8.4 attempt.  Again, not of grave concern, as things are running and generating just fine.  Just a oddity note to pass along.