An agent from Environment A was downloaded and installed on servers that should actually be in Environment B. Now I have seen that you can change the environment via oneagentctl.exe:
--set-tenant and --set-tenant-token
Since the cluster nodes are the same for Environment A and Environment B, they should still be accessible when changing the environment (we have of course other Environment ActiveGates for A and B but the same Cluster nodes). So, my thought is to use these two options from oneagentctl to change the environment. This then looks something like this:
.\oneagentctl.exe --set-tenant=TENANT-B --set-tenant-token=TENANTTOKENOFB --restart-service
After this is run, does it automatically also Update the configuration for the ActiveGates so that those of the Environment will take place? I thought that because the cluster nodes are the same, it will probably update those automatically?
For my understanding, it should somehow update it because if I add an extra ActiveGate to an Environment, this should also be deployed to the existing OneAgents... or are I wrong?
Solved! Go to Solution.
If the OneAgent has access to the cluster nodes, or Cluster ActiveGate (if deployed), it will update the configuration. If you environment disallows such connections and oneagents can only connect using the Environmnet ActiveGates, then you must also set the endpoint using --set-server to a valid address for the B environment.
The endpoints are updated as soon as the OneAgent connects to the environment.