Response indicates relay is part of a different deployment

Usage and Config Platform
1

(imported topic written by murtasma91)

We are in the process of migrating clients over from our pilot site to our production site. One area is left to migrate the masthead file on however all the clients in this area are having trouble reporting back to the BigFix pilot site to receive actions. I have attached the log from the client with the most current last report time.

At 09:17:00 -0400 - BES Support (http://sync.bigfix.com/cgi-bin/bfgather/bessupport)

Fixed - BES Clients’ Licenses Will Expire Soon - BES 7.0 (fixlet:482)

Relevant - BES Clients in License Expiration Grace Period - BES 7.0 (fixlet:483)

At 09:22:51 -0400 -

RegisterOnce: Attempting to register with ‘http://pilotrelay5.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=7.1.8.13&Body=12593128&SequenceNumber=434&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&Root=http://bes.bf.umich.edu:52311&AdapterInfo=00-21-70-14-46-d2_141.211.152.0%2F24_141.211.152.73_1’

At 09:22:54 -0400 -

RegisterOnce: GetURL failed

At 09:23:36 -0400 -

RegisterOnce: Attempting to register with ‘http://pilotrelay4.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=7.1.8.13&Body=12593128&SequenceNumber=435&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&Root=http://bes.bf.umich.edu:52311&AdapterInfo=00-21-70-14-46-d2_141.211.152.0%2F24_141.211.152.73_1’

At 09:23:38 -0400 -

RegisterOnce: GetURL failed

At 09:23:50 -0400 -

RegisterOnce: Attempting to register with ‘http://pilotrelay2.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=7.1.8.13&Body=12593128&SequenceNumber=436&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&MinHops=3&MaxHops=3&Root=http://bes.bf.umich.edu:52311&AdapterInfo=00-21-70-14-46-d2_141.211.152.0%2F24_141.211.152.73_1’

RegisterOnce: Response indicates relay is part of a different deployment.

At 09:24:29 -0400 -

RegisterOnce: Attempting to register with ‘http://pilotrelay3.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=7.1.8.13&Body=12593128&SequenceNumber=437&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&MinHops=3&MaxHops=3&Root=http://bes.bf.umich.edu:52311&AdapterInfo=00-21-70-14-46-d2_141.211.152.0%2F24_141.211.152.73_1’

RegisterOnce: Response indicates relay is part of a different deployment.

At 09:24:33 -0400 -

RegisterOnce: Attempting to register with ‘http://pilotrelay1.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=7.1.8.13&Body=12593128&SequenceNumber=438&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&MinHops=3&MaxHops=3&Root=http://bes.bf.umich.edu:52311&AdapterInfo=00-21-70-14-46-d2_141.211.152.0%2F24_141.211.152.73_1’

RegisterOnce: Response indicates relay is part of a different deployment.

At 09:25:25 -0400 -

RegisterOnce: Attempting to register with ‘http://pilotsite.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=7.1.8.13&Body=12593128&SequenceNumber=439&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&Root=http://bes.bf.umich.edu:52311&AdapterInfo=00-21-70-14-46-d2_141.211.152.0%2F24_141.211.152.73_1’

RegisterOnce: Response indicates relay is part of a different deployment.

Unrestricted mode

Configuring listener failed to initialize as wake-on-lan forwarder(AdapterInfo=).

ShutdownListener

SetupListener completed successfully

Here is the masthead for the pilot site

IME-Version: 1.0

Content-Type: multipart/signed; protocol=“application/x-pkcs7-signature”; micalg=sha1; boundary="----645E4D0805E41018DDDDB673BEAE4A1E"

This is an S/MIME signed message

------645E4D0805E41018DDDDB673BEAE4A1E

MIME-Version: 1.0

Content-Type: multipart/related; boundary = “VLSY+”;

type=“Application/x-Fixlet-Site-Masthead”

Organization: University of Michigan

LicenseAllocation: 10000

LicenseExpiration: 31 Jul 2009 00:00:00 GMT

From: acwilson@bf.umich.edu

Subject: Action Site Masthead

X-Fixlet-Site-Masthead-Version: 2

X-Fixlet-Site-Name: actionsite

X-Fixlet-Site-Gather-URL: http://bes.bf.umich.edu:52311/cgi-bin/bfgather.exe/actionsite

X-Fixlet-Site-Report-URL: http://bes.bf.umich.edu:52311/cgi-bin/bfenterprise/PostResults.exe

X-Fixlet-Site-Registration-URL: http://bes.bf.umich.edu:52311/cgi-bin/bfenterprise/clientregister.exe

X-BES-Mirror-Gather-URL: http://bes.bf.umich.edu:52311/cgi-bin/bfenterprise/besgathermirror.exe

X-BES-Mirror-Download-URL: http://bes.bf.umich.edu:52311/bfmirror/downloads/

X-Fixlet-Site-Serial-Number: 10818

X-Fixlet-Site-Update-Frequency: Day

x-bes-action-lock-controller: console

x-bes-action-lock-initial: off

x-bes-action-lock-omit-site: http://sync.bigfix.com/cgi-bin/bfgather/bessupport

Why am I getting the “Response indicates relay is part of a different deployment” when the client attempts to register with the pilotsite? Is it becuase our license appears to be expired for the pilot site right now?

2

(imported comment written by BenKus)

Each Agent/Relay/Server share the masthead file and they all need to have the same exact masthead or they will not be able to communicate effectively… The error message you posted indicates the agent is complaining that the relay’s masthead (and potentially the BigFix Server’s masthead) is different from the BigFix Agent’s masthead.

So if you installed a new server or installed a relay pointing to a different server, the agents that were installed pointing to the old server won’t be able to use this new relay.

Ben

3

(imported comment written by murtasma91)

Is there a way to manually update the masthead for a client using another software deployment platform, such as running a batch file that replaces the masthead file and reset’s the BigFix client configuration on the workstation?

Our pilot site license has no expired on us. Just try to see if there is another possible workaround without having to remove then redeploy the clients to workstation still waiting to get migrated?

4

(imported comment written by BenKus)

Hi murtasma,

You can use the Task in the BES Support site to switch the masthead… alternately you can run the BigFix Client installer with the new masthead (using any tool you want) and it will install the agent as part of the new deployment.

Ben

5

Hey, very old post… but i just solved the same issue.

during our migration from the otd to new infrastructure:

  • copy masthead.afxm to ActionSite.afxm
  • delete [KEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\EnterpriseClient\Settings] reg key
  • restart besclient service

it worked great!

GIovanni