BigFix Excel Connector

Hi @Mojea, it is correct that you can only select one BES Properties.

Are you looking to extract different properties for computers?
Then you should select BES Computers instead.

I do have a question that I do not seem to find when I run a report on fixlets that need to be applied. When running the report I have a need to report on a “per server” basis. Right now it will list all the servers in one cell that need the fixlet. Is there a way to accomplish this. I need a report for all of our citrix servers. The only identifier is by name, but since they are all dumped into one cell a sort does not help either because I get all the servers that need this patch.

@roberteastman I might need a picture to understand the issue.
Have you seen this feature that will determine how “multi-valued” results are to be displayed?

Leewei, I did not notice that check box. I reran my report without the check box and I can get the report the way I needed it. Thank you.

I have been trying to figure out how to run this report with excel connector but am at a standstill on determining if this can be done. Management would like a report monthly of all the patches that were applied in the last 30 days. Since the connector is connecting to the DB I am sure that it can access this information but I am not seeing it in the choices when using it.

Thanks

Hello @leewei,thanks you for build a great tool.Could you know why my Excel Connector not display on Win2008 R2 Excel 2010 addon ?

Here is the log. ( I’m not sure do I have to restart server after install addon )
adxregistrator.log

==============================================
Add-in Express Registrator Log File: 01/16/2019 17:41:14

Installation directory: C:\Tivoli Endpoint Manager Excel Connector 3.3
Registrator version: 6.4.3056.0
Operating System: Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit
Process Owner: Administrator
Command Line: “C:\Tivoli Endpoint Manager Excel Connector 3.3\adxregistrator.exe” /Install=BigFixExcelConnector.dll /privileges=admin
Run ‘As Administrator’: Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): Off

17:41:14 0220 Starting the add-in registration process.
17:41:14 0220 Loading mscoree.dll
17:41:14 0220 Success.
17:41:14 0220 .NET Framework installation directory:
17:41:14 0220 The latest version of .NET Framework: 'v4.0.30319’
17:41:14 0220 Loading CLR: v4.0.30319.
17:41:14 0220 Calling CLRCreateInstance method.
17:41:14 0220 Success.
17:41:14 0220 Calling GetRuntime method.
17:41:14 0220 Success.
17:41:14 0220 Calling GetInterface method.
17:41:14 0220 Calling GetInterface method for the CorRuntimeHost interface.
17:41:14 0220 Success.
17:41:14 0220 Starting CLR…
17:41:14 0220 Success.
17:41:14 0220 The CLR v4.0.30319 has been initialized successfully.
17:41:14 0220 Creating a new domain setup.
17:41:14 0220 Success.
17:41:14 0220 Getting the add-in directory.
17:41:14 0220 Success. The directory is ‘C:\Tivoli Endpoint Manager Excel Connector 3.3’
17:41:14 0220 The ‘shadow copy’ is disabled.
17:41:14 0220 Creating a new application domain.
17:41:14 0220 Success.
17:41:14 0220 Getting the base directory for the domain.
17:41:14 0220 Success. The directory is ‘C:\Tivoli Endpoint Manager Excel Connector 3.3’.
17:41:14 0220 Searching for the Add-in Express core library.
17:41:14 0220 Success. The ‘AddinExpress.MSO.2005.dll’ file is found.
17:41:14 0220 Creating an instance of the ‘AddinExpress.Deployment.ADXRegistrator’ class.
17:41:14 0220 Assembly identity is ‘AddinExpress.MSO.2005’.
17:41:14 0220 Success.
17:41:14 0220 Unwrapping the instance of the ‘AddinExpress.Deployment.ADXRegistrator’ class.
17:41:14 0220 Success.
17:41:14 0220 Calling the managed registration procedure.
17:41:14 0676 Connecting to the application domain of the Add-in Express loader.
17:41:14 0676 Success.
17:41:14 0676 Loading the ‘bigfixexcelconnector.dll’ assembly.
17:41:15 0676 Success.
17:41:15 0676 Registering the ‘bigfixexcelconnector.dll’ assembly (administrator).
17:41:15 0676 The ’ bigfixexcelconnector.dll’ assembly has been registered successfully.
17:41:16 0220 Success.
17:41:16 0220 The add-in registration process is completed with HRESULT = 0.

adxloader.log

Add-in Express Loader Log File: 01/16/2019 17:56:40

Startup directory: C:\Tivoli Endpoint Manager Excel Connector 3.3
Loader version: 6.4.3056.0
Operating System: Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit
Process Owner: Administrator
Command Line: EXCEL.EXE
Run ‘As Administrator’: Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): Off

17:56:40 2076 9092 Starting the add-in registration process.
17:56:40 2076 9092 Loading mscoree.dll
17:56:40 2076 9092 Getting the latest CLR version.
17:56:40 2076 9092 The latest CLR version is ‘v4.0.30319’.
17:56:40 2076 9092 Loading CLR: v4.0.30319.
17:56:40 2076 9092 Calling CLRCreateInstance method.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Calling GetRuntime method.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Calling GetInterface method.
17:56:40 2076 9092 Calling GetInterface method for the CorRuntimeHost interface.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Starting CLR…
17:56:40 2076 9092 Success.
17:56:40 2076 9092 The CLR v4.0.30319 has been initialized successfully.
17:56:40 2076 9092 Creating a new domain setup.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Getting the add-in directory.
17:56:40 2076 9092 Success. The directory is 'C:\Tivoli Endpoint Manager Excel Connector 3.3’
17:56:40 2076 9092 The configuration file is ‘C:\Tivoli Endpoint Manager Excel Connector 3.3\app.config’
17:56:40 2076 9092 The ‘shadow copy’ is disabled.
17:56:40 2076 9092 Creating a new application domain.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Getting the base directory for the domain.
17:56:40 2076 9092 Success. The directory is ‘C:\Tivoli Endpoint Manager Excel Connector 3.3’.
17:56:40 2076 9092 Searching for the Add-in Express core library.
17:56:40 2076 9092 Success. The ‘AddinExpress.MSO.2005.dll’ file has been found.
17:56:40 2076 9092 Creating an instance of the ‘AddinExpress.MSO.ADXLoaderSupport’ class.
17:56:40 2076 9092 Assembly identity is ‘AddinExpress.MSO.2005’.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Unwrapping the instance of the ‘AddinExpress.MSO.ADXLoaderSupport’ class.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Creating an instance of the XML parser class.
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Loading the manifest file (C:\Tivoli Endpoint Manager Excel Connector 3.3\adxloader.dll.manifest).
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Getting the root element of the manifest (C:\Tivoli Endpoint Manager Excel Connector 3.3\adxloader.dll.manifest).
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Getting the ‘assemblyIdentity’ element of the manifest (C:\Tivoli Endpoint Manager Excel Connector 3.3\adxloader.dll.manifest).
17:56:40 2076 9092 Success.
17:56:40 2076 9092 Searching for the ‘name’ attribute of the ‘assemblyIdentity’ element.
17:56:40 2076 9092 Success. The name is ‘BigFixExcelConnector, PublicKeyToken=bef2983f1300af93’.
17:56:40 2076 9092 Calling the managed procedure to register the ‘BigFixExcelConnector, PublicKeyToken=bef2983f1300af93’ assembly.
17:56:40 1996 9092 Connecting to the application domain of the Add-in Express loader.
17:56:40 1996 9092 Success.
17:56:40 1996 9092 Loading the ‘BigFixExcelConnector, PublicKeyToken=bef2983f1300af93’ assembly.
17:56:40 1996 9092 Success.
17:56:40 1996 9092 Registering the ‘BigFixExcelConnector, PublicKeyToken=bef2983f1300af93’ assembly (user).
17:56:41 1996 9092 The ’ BigFixExcelConnector, PublicKeyToken=bef2983f1300af93’ assembly has been registered successfully.
17:56:41 1996 9092 The managed registration process is complete with HRESULT = 0.
17:56:41 2076 9092 The add-in registration process is completed with HRESULT = 0.

@teerapongpa, there are no errors in the logs, which is a good sign.
Can you please check the status of the addin from:
Excel menu File --> Options --> Add-ins -->
Scroll to bottom to Manage drop-list “COM Add-ins” --> Go button

We want to make sure that the BigFix Connector is checked and no errors from Excel.


They notify error as image shown

What I noticed

  1. In order to see addon,I have to run excel.exe as admin
  2. Current Excel is unregistratred version
  3. Is there any security policy block?

@teerapongpa, there are no security policy blocks that will impact this.
When you install the addin, it should have by default installed in c:\users[name]\appdata folder.
The fact that your say c:\Tivoli Endpoint Manager Excel Connector 3.3\ means that you changed it correct?
I wonder if because the user does not have permission in this folder structure.

Add-in Express Loader Log File: 01/29/2019 18:28:50:176

Startup directory: C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8
Loader version: 8.1.4350.0
Operating System: Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit
Process Owner: Administrator
Command Line: "C:\Program Files (x86)\Microsoft Office\Office14\EXCEL.EXE"
Run ‘As Administrator’: Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): Off

18:28:50:176 1356 6204 Starting the add-in registration process.
18:28:50:176 1356 6204 Loading mscoree.dll
18:28:50:176 1356 6204 Getting the latest CLR version.
18:28:50:176 1356 6204 The latest CLR version is ‘v4.0.30319’.
18:28:50:176 1356 6204 Loading CLR: v4.0.30319.
18:28:50:176 1356 6204 Calling CLRCreateInstance method.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Calling GetRuntime method.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Checking if the hosting API of .NET Framework v4.0 beta is installed.
18:28:50:176 1356 6204 The hosting API is up to date.
18:28:50:176 1356 6204 Calling GetInterface method for the CorRuntimeHost interface.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Starting CLR…
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the CLR version.
18:28:50:176 1356 6204 The CLR v4.0.30319 has been initialized successfully.
18:28:50:176 1356 6204 Creating a new domain setup.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the add-in directory.
18:28:50:176 1356 6204 Success. The directory is 'C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8’
18:28:50:176 1356 6204 The ‘shadow copy’ is disabled.
18:28:50:176 1356 6204 Creating a new application domain.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the base directory for the domain.
18:28:50:176 1356 6204 Success. The directory is ‘C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8’.
18:28:50:176 1356 6204 Searching for the Add-in Express core library.
18:28:50:176 1356 6204 Success. The ‘AddinExpress.MSO.2005.dll’ file has been found.
18:28:50:176 1356 6204 Creating an instance of the ‘AddinExpress.MSO.ADXLoaderSupport’ class.
18:28:50:176 1356 6204 Assembly identity is ‘AddinExpress.MSO.2005’.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Unwrapping the instance of the ‘AddinExpress.MSO.ADXLoaderSupport’ class.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Creating an instance of the XML parser class.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Loading the manifest file (C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8\adxloader.dll.manifest).
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the root element of the manifest (C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8\adxloader.dll.manifest).
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the ‘assemblyIdentity’ element of the manifest (C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8\adxloader.dll.manifest).
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Searching for the ‘name’ attribute of the ‘assemblyIdentity’ element.
18:28:50:176 1356 6204 Success. The name is ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’.
18:28:50:176 1356 6204 Calling the managed procedure to register the ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’ assembly.
18:28:50 1908 6204 Connecting to the application domain of the Add-in Express loader.
18:28:50 1908 6204 Success.
18:28:50 1908 6204 Loading the ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’ assembly.
18:28:50 1908 6204 Error: Could not load file or assembly ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
18:28:50 1908 6204 Inner Exception: The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
18:28:50 1908 6204 The managed registration process is complete with HRESULT = 2.
18:28:50:192 1356 6204 The system cannot find the file specified.

I found error on manual loading COM,Do you know what it is ? @leewei

Problem Solved : For every user , each of them have to run following cmd separately. (I install it on terminal server.)

“/adxregistrator.exe /install=“BigFixExcelConnector.dll” /privileges=user”

Then Bigfix Excel Addon Showup , :slight_smile:

Hi Leewei,
Amazing utility you created, it has been very helpful. Is there support for windows 10. The latest version uses .NET framework 2.0, wondering if it will be coded to use a more recent version.

Alex

Latest version uses 4.5.2 NET framework. Info is in the original post.

Change History

Changes in version 3.3.8.0

(2017/05/04) Switched to .NET Framework 4.5.2 from 2.0
(2017/05/04) Supported TLS 1.2

Hi everyone!

I have question about specification of BigFix Excel Connector.

I executed Query Wizard and create report of BES Computers. Then I showed Relevance Code.
I could show the code including bes property "<property name>".
Also I could show the code including bes property whose (name of it = "<property name>" and (item 0 of it = <property id> and item 1 of it = <property sub-id> and item 2 of it = 1) of id of it).

I can’t understand about these difference of relevance code involving bes property.
why it is occur these difference?
Please let me know.

thanks
Nobumitsu

Hi Lee Wei,
I’ve downloaded BigFix Excel Connector version 3.3.8, verified .Net Framework full is installed, when I run it I’m getting a message window “This setup requires the .NET Framework version 2.0. Please install the .Net Framework and run this setup again. The .Net Framework can be obtained from the web. Would you like to do this now?”

However .NET Framework version 2.0 has ended support long ago. As I understand it .Net Framework is the latest version and is compatible with .NET Framework 4.5.2, noted in the installation instructions. Am I missing something. Also, does the Excel Connector require any of the .Net Framework advanced services enabled?

Any help is appreciated. Thanks.

Chi

image

Did you try turning on the .NET Framework 3.5 feature? It includes the runtimes for .NET 2.0 and 3.0

I’ve tried but I think it’s blocked. Correct me if I’m wrong but I was under the impression that apps written to .Net Framework versions 3.5 and lower will require version 3.5 to be installed, and apps written to .Net Framework version 4 or higher will need version 4 installed. Also, Change History for version 3.3.8.0, “(2017/05/04) Switched to .NET Framework 4.5.2 from 2.0”, so why would it be asking for version 2.0? I’m a bit confused.

It’s that highlighted checkbox at the top of your “Turn Windows Features on and off” screenshot, not the download file referenced in the installer.