Quantcast
Channel: Ivanti User Community : Document List - Inventory
Viewing all articles
Browse latest Browse all 397

How to check for Microsoft Office version 32-bit or 64-bit in inventory

$
0
0

Description:

          This document's purpose is to assist in adding the Microsoft Office bitness to custom data in Inventory, where it then can be queried once reported in a client's inventory.

 

Resolution:

          Essentially what is described in the process below is adding a registry key that contains the bit version of office to custom data. Once it's reported by Inventory you can build a query that will display that custom data and help the user determine what version is being run.

 

Checking the registry item:

This step is not necessary to the overall resolution, but rather to illustrate what information we will be adding to the inventory.

               1. Type Windows Key + R or type "run" in the start menu and launch to open the Run interface

               2. Type "regedit" in the provided command line

                    explorer_2017-09-27_09-30-41.png

                3. This will open Registry Editor, where we will want to navigate to HKLM\Software\Microsoft\Office\15.0\Outlook\bitness

For different versions of Office, check 14.0, 16.0, etc. depending on what version you are looking for.

                    bitness.PNG

               4. As we can see from the above image, that registry item tells us that this devices contains a 64-bit version of Outlook. We can now add that information to be scanned into inventory.

 

Adding the registry item to custom data:

               1. Open Ivanti Management Console and click Tools> Reporting / Monitoring> Manage software list

                         RemoteDesktopManagerFree_2017-09-28_11-05-55.png

               2. When the Manage Software List snap-in opens:

                    a) Expand Custom Data

                    b) Highlight Registry Items

                    c) Click the green New button on the toolbar

                         RemoteDesktopManagerFree_2017-09-28_11-17-13.png

               3. Add the following information to the dialogue box:

                    a) Root Key (generally HKLM)

                    b) Key - this is path to the key you want to scan

                    c) Value - the attribute you want pulled into inventory

                    d) Attribute Name - this is what the data will be named in the inventory and how it will be nested

                         RemoteDesktopManagerFree_2017-09-28_11-30-06.png

               4. Click OK to save and create the custom data

WARNING:The above image is an example of what adding a custom registry item looks like. Your environment may differ and require different input.

               5. Now that the new item has been created, you will notice that (Unpublished)(1) will appear next to Manage Software List. To publish the list, you need to click the Make Available to Clients(2) button.

                         RemoteDesktopManagerFree_2017-09-28_11-41-12.png

               6. After you make the update available to clients, future inventory scans should report that registry item

It may take up to two inventory cycles (48 hours by default) to report the custom data.

               The official help documentation for this process can be found here: Add custom registry items to inventory scans

Creating a custom query:

               - Now that the registry item is being reported into custom data on the inventory, you can create a query to display that information.

               - The documentation on building custom queries can be found here: Custom Database Queries: How they work, guidelines on creating them, and examples of them in action

Ivanti Support is not able to help with creating custom queries but the document above and others in help.ivanti.com and throughout the community can help with creating them.

Viewing all articles
Browse latest Browse all 397

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>