You wish to report Chrome browsers in your organization based on bitness (requires PDQ Inventory Pro or Enterprise).
IMPORTANT: Starting with Chrome Version 56.x, this article no longer applies due to inconsistencies with upgrading existing installations with different Chrome architectures. We are looking into a broader solution for architecture detection and will update this, and other articles, as appropriate and when that solution becomes available.
Download and then import the attached files into PDQ Inventory (located at the end of this article) or create your own reports, collections, and scan profile using the instructions below.
I. Create the Scan Profile to collect Chrome information:
1. Go to File > Preferences > Scan Profiles. Click on New then Add in the new Window, and then select Registry.
2. In the Edit Registry Scanner Window, add the following registry patterns:
3. Click OK.
4. Back in the Scan Profile Window, change the name to something meaningful (e.g. Chrome Bitness Scan).
5. Click on the Triggers tab.
6. Set a reasonable Trigger (in this example, when the scan data reaches the ripe old age of two days).
7. Click OK to save the scan.
- Although the scanner should run since there is no scan data, it is advisable to manually run the scan on all computers from which you wish to collect Chrome bitness data. Bitness data may not be accurate until the scan is successfully run.
- It is also advisable to run an Application scan if you are using a Chrome collection. For example, I am only interested in doing an initial scan for machines that have Chrome installed. I have created a Dynamic Collection to include all machines with Chrome. I would run the Application scan on all machines in order to populate the Dynamic Collection with the latest and greatest information.
II. Create Basic reports to report Chrome bitness:
1. Click on New Report in the toolbar > Basic.
2. Name the report something meaningful.
3. For the 32-bit Chrome report, go to the Filters tab (the Columns tab can remain as-is) and add the following filters:
4. Save and run the report
5. For 64-bit Chrome, repeat steps 1 and 2 above and add the following filters (again, the Columns tab can remain as-is):
III. Create Chrome bitness collections:
Creating a collection is relatively easy once you’ve created the report (or vice-versa, creating a report from a collection). You can also download the collection in the Downloads section at the end of this page.
1. Right-click the Basic report you want to use to create a collection and select New Collection from Report.
2. Confirm the filtering, name, and any other aspect of the Dynamic Collection.
3. Click OK to create the Dynamic Collection.
Once complete, a header collection (no filters) was added with the converted Report > Collection for both 32 and 64-bit Chrome as subsections.
Filters for Collections and Reports
Create Collection from a Report
Admin Arsenal Live! : Mastering Collection and Report Filters
Advanced Collections and Report Filtering - Part I
Advanced Collections and Report Filtering - Part II
Advanced Reports in PDQ Inventory using SQL
Deploying Google Chrome Enterprise