TEM Client 8.2.1093 Windows Installation via TCM SPB

Usage and Config Platform
1

(imported topic written by LarryKlaus)

We are having a unique problem where the TEM Client installation hangs up at a certain point when using a TCM SPB install. When we install manually, without pushing via TCM, we have no problem. Our command line is:

C:\esd\swd\tem82193\img\us\BigFix-BES-Client-8.2.1093.0.exe /s

/v"/qn SETUPEXE=1 INSTALLDIR=""“C:\Program Files (x86)\BigFix Enterprise\BES Client”"" MASTHEADFILE="""\esd\custom\masthead.afxm""" CLIENTSETTINGSFILE=""“C:\esd\sdwork\clientsettings.cfg”"""

The last few lines in the log file are:

Action start 10:20:13: imm_isc_SetClientComplianceSiteURL.

MSI (s) (40:98)

10:20:14:757

: Invoking remote custom action. DLL: C:\Windows\Installer\MSIFCCF.tmp, Entrypoint: f2

InstallShield 10:20:14: Running InstallScript function f2

InstallShield 10:20:14: Opening stream of file C:\Windows\Installer\MSIFCCF.tmp

InstallShield 10:20:14: Extracting support file IsConfig.ini to C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}\IsConfig.ini

InstallShield 10:20:15: Extracted isconfig.ini to C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}\IsConfig.ini

InstallShield 10:20:15: Got ‘{B4781305-2D9E-402A-B720-541439C1CD81}’ for TempPathGuid from isconfig.ini

InstallShield 10:20:15: Attempting to use temp path ‘C:\Users\ADMINI~1\AppData\Local\Temp{B4781305-2D9E-402A-B720-541439C1CD81}’

InstallShield 10:20:15: Using temp folder C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}

InstallShield 10:20:15: Installing engine…

InstallShield 10:20:15: Using product language 1033

InstallShield 10:20:15: Extracting support file setup.inx to C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}\setup.inx

InstallShield 10:20:15: Extracting support file ISRT.dll to C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}\ISRT.dll

InstallShield 10:20:15: Detected X64 OS

InstallShield 10:20:15: Extracting support file ISBEWX64.exe to C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}\ISBEW64.exe

InstallShield 10:20:15: Extracting support file _isres_0x0409.dll to C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}_isres_0x0409.dll

InstallShield 10:20:15: Extracting support file String1033.txt to C:\Users\ADMINI~1\AppData\Local\Temp{8D35EA8C-A88F-46DC-B82E-8A818AAC778E}\String1033.txt

InstallShield 10:20:15: Skipping optional support file _isuser_0x0409.dll

InstallShield 10:20:15: Setting script cmdline…

InstallShield 10:20:15: ProductCode is {02EB5871-4DC4-4126-91D6-F1FA82166313}

InstallShield 10:20:15: Initializing Engine

InstallShield 10:20:18: Done Initializing…

InstallShield 10:20:18: Registering Msi Server…

InstallShield 10:20:18: Invoking script function SetClientComplianceSiteURL

It always hangs on the last

SetClientComplianceSiteURL

function. On a manual install the log continues with the following:

MSI (s) (18!A4)

10:00:15:992

: PROPERTY CHANGE: Adding CLIENTCOMPLIANCE_SITEURL property. Its value is ‘http://esdbes01.usnc.ibm.com:52311/cgi-bin/bfgather.exe/actionsite’.

InstallShield 10:00:16: CallScriptFunctionFromMsiCA() ends

InstallShield 10:00:16: Cleaning up temp file C:\Users\ADMINI~1\AppData\Local\Temp{01964226-0777-45E0-B7CF-3A84EC2F5572}\ISBEW64.exe

InstallShield 10:00:16: Cleaning up temp file C:\Users\ADMINI~1\AppData\Local\Temp{01964226-0777-45E0-B7CF-3A84EC2F5572}\ISRT.dll

InstallShield 10:00:16: Cleaning up temp file C:\Users\ADMINI~1\AppData\Local\Temp{01964226-0777-45E0-B7CF-3A84EC2F5572}\IsConfig.ini

InstallShield 10:00:16: Cleaning up temp file C:\Users\ADMINI~1\AppData\Local\Temp{01964226-0777-45E0-B7CF-3A84EC2F5572}\String1033.txt

InstallShield 10:00:16: Cleaning up temp file C:\Users\ADMINI~1\AppData\Local\Temp{01964226-0777-45E0-B7CF-3A84EC2F5572}_isres_0x0409.dll

InstallShield 10:00:16: Cleaning up temp file C:\Users\ADMINI~1\AppData\Local\Temp{01964226-0777-45E0-B7CF-3A84EC2F5572}\setup.inx

Action ended 10:00:16: imm_isc_SetClientComplianceSiteURL. Return value 1.

And then there are several more pages of log output until the normal end.

Has anyone else been successful creating a TCM SPB and installing it to Windows servers?

Larry

2

(imported comment written by BenKus)

Can you explain more about what you mean by the TCM SPB? Are you trying to repackage the BigFix Agent?

Ben

3

(imported comment written by LarryKlaus)

Ben,

Yes, we packaged the TEM Client for Windows setup as a Software Package Block in Tivoli Configuration Manager. When we use TCM to install the SPB to a Windows server, it hangs at the point indicated in the log file segment I posted. No pop-up dialog occurs on the Windows server target and eventually the Tivoli distribution times out.

When we run the exact same installation script in a standalone fashion (without TCM), the TEM Client install .exe does not hang up.

-Larry

4

(imported comment written by BenKus)

Hi Larry,

Does the SPB package extract and run the native installer? If it instead tries to copy the registry/files manually, it might be problematic…

Ben

5

(imported comment written by LarryKlaus)

Ben,

Yes, our SPB runs the Client installer BigFix-BES-Client-8.2.1093.0.exe.

-Larry

6

(imported comment written by BenKus)

Is the path to the masthead file correct? You might try specifying a full path to help figure out if there is a current-working-directory problem.

Ben

7

(imported comment written by LarryKlaus)

Ben,

Thanks for pointing that out, I did not notice it before, we’re checking on it. However, that syntax should evaluate to the “current working drive”, which in our case should be the System Drive. That path from the root of C: does exist, but we are going to test with %systemdrive% specified.

Larry