Pinned topic Making a BigFix MSI
I know that it also does not help that I am not the one who normally works with bigfix.
SystemAdmin 110000D4XK2038 PostsACCEPTED ANSWER
Re: Making a BigFix MSI2011-10-12T15:10:24Z in response to DavidMS91on your BigFix server there should be a directory - \BESInstallers\ClientMSI - which already contains a BESClientMSI.msi for installs. I would start with that as I know it works when using group policy.Updated on 2011-10-12T15:10:24Z at 2011-10-12T15:10:24Z by SystemAdmin
DavidMS91 270004W38H2 Posts
JCope 2700070NA81 PostACCEPTED ANSWER
Re: Making a BigFix MSI2014-03-31T14:02:19Z in response to DavidMS91
David, did you ever find an answer to the question of whether the Masthead was included in the \BESInstallers\ClientMSI\BESClient.msi file?
I have been gleaning through the IEM Administrators manual and several websites on GPO and I cannot find any indication of how the masthead or config files get connected to the MSI.
jgstew 270004VDPE47 PostsACCEPTED ANSWER
Re: Making a BigFix MSI2014-04-02T14:16:20Z in response to JCope
I believe that the MSI from BigFix/IBM's websites do not include the Masthead.
I am not certain about the MSI's referenced as residing here: \BESInstallers\ClientMSI on the root server.
It has been my understanding that you must have the MSI and masthead in the same folder when running the MSI in order for the masthead to be set properly, otherwise you would need a 3rd party tool to package the MSI to include it.
I'd recommend creating an MSI that ONLY installs the masthead and push out both MSIs using Group Policy.Updated on 2014-04-02T14:18:12Z at 2014-04-02T14:18:12Z by jgstew
BigFixNinja 270003VJ1213 PostsACCEPTED ANSWER
Re: Making a BigFix MSI2014-04-03T20:02:23Z in response to jgstew
See the following documentation:
The client msi does not contain the actionsite.afxm masthead but the client can be deployed without it. However, before starting and running the client, the actionsite.afxm needs to be placed in the C:\Program Files (x86)\BigFix Enterprise\BES Client folder.
IBM Endpoint Manager Support
nberger91 270004W6A034 PostsACCEPTED ANSWER
Re: Making a BigFix MSI2011-10-12T16:33:11Z in response to DavidMS91create a system startup script which executes a simple bat file. create a folder, copy the setup.exe, masthead, and the bat file ... run !
if exist "%ProgramFiles(x86)%\BigFix Enterprise\BES Client\BESClient.exe" goto AgentFound
if exist "%ProgramFiles%\BigFix Enterprise\BES Client\BESClient.exe" goto AgentFound
%LOGONSERVER%\netlogon\BigFix\setup.exe /s /v"/qn /l*voicewarmup "C:\BigFixInstallLog.log"
MBARTOSH 2000002HB636 PostsACCEPTED ANSWER
Re: Making a BigFix MSI2014-04-02T14:30:02Z in response to nberger91
In our environment a login script is not a good idea because of bandwidth contraints. A logon script ill at least download the batch file everytime a user logs on. I am not sure but it may also copy setup.exe also.
Bigfix needs discovery with automatic client installation, like SCCM.