I am new in Bigfix. I am thinking about… how to create dynamic affiliation groups and I found this solution on Bigfix forum. I have many branch offices and one primary TEM server. I need to create dymanic affiliation action, which create local affiliation SeekLisk for branch computers(one branch one relay) and second affiliation location will be central TEM server.
—solution from Bigfix forum ----
Set the Relay settings to:
setting “_BESRelay_Register_Affiliation_AdvertisementList”="{(value of settings “Location By Subnet” of client)}" on “{now}” for client
Set the Client settings to :
setting “_BESClient_Register_Affiliation_SeekList”="{(value of settings “Location By Subnet” of client)}%3bPrimarySite" on “{now}” for client
This is good example of solution but I have one big problem. I do not know create action script which will by take value “Subnet Address” of BESClient and put it to the custom setting as “Location By Subnet”. Have anybody experience with this?
I am wondering about something like this…
setting “Location By Subnet”="…;PrimarySite" on “{now}” for client
If I understand you correctly, you need to group your computers by subnets, right? If yes - you can create automatic computer groups. No need for custom properties.
I need solution which will read subnet address from client computer and put it in to the action script. I have about 150 branch offices and I am searching for simple solution how to create action script to configure affiliation groups for relays/clients.
For example:
Local computer will try to connect to the branch relay. If branch relay is down then computers will be connect to the TEM server.
Action for Clients
setting “_BESClient_Register_Affiliation_SeekList”="{(value of settings “Location By Subnet” of client)}%3bPrimarySite" on “{now}” for client
As far as I understand, what you describe is the default Tivoli’s way to choose a relay when it’s “Relay selection method” is set to Automatic. You can set it either manually on each computer (Edit Computer Settings menu, untick “Assign relays manually”) or on a group of computers. You just need one relay for each local subnet.
There is no need to do this job for Tivoli Endpoint Manager. Tivoli can do it all alone.
But I have problem with this default behavior. Nearest relay ist choosen by nearest network hops. In my case is TEM server virtual machine in datacenter behind some routers. I don`t know how many. Than I have building1 (700 clients) and branch1(15 client)… My problem is… All clients from building1 catch to relay in branch1 instead to the TEM server in datacenter. Maybe problem ist in number of network hops. Branch1 relay could be closer that TEM server…
This is from Relay documentation.
How does the BigFix Client/BigFix Relay Auto Selection work?
• BigFix Clients will choose their closest BigFix Relay by periodically “pinging” each BigFix Relay to determine which relay is the closest based upon the number of network hops. The default BigFix Relay selection period is 6 hours and is configurable.
• Each BigFix Client will make a list of their closest BigFix Relays. If they cannot reach their closest BigFix Relay because it is off or down, they will try the second closest, and so on.
• If a BigFix Client cannot find any BigFix Relays or they are all down, the BigFix Client will connect directly with the main BigFix Server.
• If more than one BigFix Relays are the same distance away from a BigFix Client, the BigFix Client will randomly choose amongst them.
You bring me to idea. I set clients to manual relay selection in building1. All others will be automatic and I don`t use relay affiliation groups. I will see…
But I have problem with this default behavior. Nearest relay ist choosen by nearest network hops. In my case is TEM server virtual machine in datacenter behind some routers. I don`t know how many. Than I have building1 (700 clients) and branch1(15 client)… My problem is… All clients from building1 catch to relay in branch1 instead to the TEM server in datacenter. Maybe problem ist in number of network hops. Branch1 relay could be closer that TEM server…
This is from Relay documentation.
How does the BigFix Client/BigFix Relay Auto Selection work?
• BigFix Clients will choose their closest BigFix Relay by periodically “pinging” each BigFix Relay to determine which relay is the closest based upon the number of network hops. The default BigFix Relay selection period is 6 hours and is configurable.
• Each BigFix Client will make a list of their closest BigFix Relays. If they cannot reach their closest BigFix Relay because it is off or down, they will try the second closest, and so on.
• If a BigFix Client cannot find any BigFix Relays or they are all down, the BigFix Client will connect directly with the main BigFix Server.
• If more than one BigFix Relays are the same distance away from a BigFix Client, the BigFix Client will randomly choose amongst them.
You bring me to idea. I set clients to manual relay selection in building1. All others will be automatic and I don`t use relay affiliation groups. I will see…
I am creating action script but is not functional. Could anybody help me to correct them?
// Set parameter LocalSubnet to Subnet address
parameter “LocalSubnet” = “{value of keys “HKLM\Software\Network Associates\ePolicy Orchestrator\Agent” whose (exists value whose(name of it = “SubnetAddress”) of it) of native registry}”
// Set list of name for BESClient_Register_Affiliation_SeekList setting
"_BESClient_Register_Affiliation_SeekList"=
"{parameter "LocalSubnet
};*
" on "now
" for client
