Hi to all,
I have a problem after migrating a client from SEC to Central, the problem is that the client as a message relay stays connected to the old SUM and fails to communicate with the Central Dashboard.Even if I uninstall and reinstall it it remains connected to the old SUM.Is there any way to force a specific message relay?
I appear that your SUM server is also configured as an Update cache/Message relay hence those machines are trying to queue to the shortest route. If that is the case, you can remove the Update cache/Messagerelay…
When you mentioned forced connect to your old SUM. does it mean that you are still not fully migrated all your systems to central? By default, once you have migrated your license from on-prem to cloud, automatically the update path of your endpoint will be directed right away to Central and will bypass any active SUM server in your environment and will connect to your new Message relay if you have set-up one in your central dashboard.
yes I haven't completely migrated yet, but there is already a new message-relay, the problem is that some clients after the migration continue to connect to the old SUM. While I would like them to go to the new message-relay, is there no way to specify the message-relay at installation time?
I appear that your SUM server is also configured as an Update cache/Message relay hence those machines are trying to queue to the shortest route. If that is the case, you can remove the Update cache/Messagerelay on your SUM server and proceed with the migration.For those machines that are currently pointing to SUM, You can manually assign them to the new Update cache/Message relay that you've set up on your central by following the steps on this KB article.For your question about a way to specify an update cache through a migration tool, there is no way to do that as this is not applicable.
I can install the agent by specifying the message relay.