(imported comment written by brolly3391)
Hello Stacy,
The masthead is integrated into the MSI when you perform the initial BES Installer setup. That file is in your
c:\BESInstallers\ClientMSI
folder on your BES server. If you get a new masthead, you can regenerate that MSI by running the BES Installer on a workstation somewhere and tell it to use your current masthead.
The MST I did using Installshield Admin Studio but it could be done in Orca (free from MS) or any other tool that can create an MST.
Since Orca is a free MS tool I will give instructions on how to do this in Orca:
Open the BESClientMSI.msi in Orca.
Transforms>New Transform
_ Feature table - Add Row:_
Feature=Custom
Feature_Parent=
Title=Custom Relay reg key
Description=Custom Relay reg key to configure client to talk to a specific relay for its initial communication to the BES Server.
Display=0
Level=1
Directory_=
Attributes=0
Components table - Add Row:
Component=CustomReg
ComponentID= {3D0CB02D-B282-42D6-8567-2ADD8A37179A}
Directory=INSTALLDIR
Attrib=2
Condition=
KeyPath=
FeatureComponents table - Add Row:
Feature=Custom
Component=CustomReg
Registry table - Add Row:
Registry=InitialRelayReg
Root=2
Key=SOFTWARE\BigFix\EnterpriseClient\Settings\Client__RelayServer1
Name=value
Value=http://yourrelay.domain.com:52311/bfmirror/downloads/
Component=CustomReg
Registry table - Add Row:
Registry=InitialRelayRegDate
Root=2
Key=SOFTWARE\BigFix\EnterpriseClient\Settings\Client__RelayServer1
Name= effective date
Value= Wed, 18 Apr 2007 21:39:16 +0000
Component=CustomReg
Transform>Generate Transform
Save it as BESCustomRelay.MST
Notes for adding rows: Most entries are case sensitive. It would be easiest to use my entries verbatim and only change the yourrelay.domain.com string to your own relay and generate a new ComponentID GUID. Feature and Component names are keyword lookups for the MSI so if you change them in one row, cascade your changes to the other rows. The ComponentID can be left blank initially; once the row is created you can right click to generate a new one. It is a best practice to never re-use a GUID. If the component changes in any way, give it a new GUID.
Next, test your transform on a machine with the network disabled so that the BES client cannot talk to the server. Test using this command line and note that TRANSFORMS is all caps:
msiexec.exe /I BESClientMSI.msi /qn TRANSFORMS= BESCustomRelay.MST
Verify that the registry keys are present after the install. Add a bogus host entry in
C:\WINDOWS\system32\drivers\etc\hosts 127.0.0.1 yourBESserver.domain.com
so that the client cannot talk directly to the BES server. Then re-enable the network connection. Verify that the client does in fact use the relay to talk to the BES server. Restore your test machine from an earlier backup.
Once testing is complete you can simply set up your GPO to use the transform using a command line similar to the one you used in testing.
Orca: http://msdn2.microsoft.com/en-us/library/aa370557.aspx
One final note, this is all only for MSI rollouts of the BES client. If you are performing a normal setup.exe rollout you can use this KB for setting initial relay:
http://support.bigfix.com/cgi-bin/kbdirect.pl?id=244
Cheers,
Brolly