ACC Application migration from one instance to another Instance using the same mid server host.

[VinjiPrak]

Dear Colleagues,

The goal is to migrate the ACC (Agent Client Collector framework from one instance to another without altering the configuration on the agents. Currently, there's a host with a mid server installed that connects to Instance A and successfully collects data from the agents. The plan is to migrate everything to Instance B.

Here's what has been done so far:

1. New Mid Server Installation: A new mid server has been installed on the same host. The original mid server, which was connected to Instance A, has been turned off.

2. Stopping Services on Instance A: The listener and websocket endpoint on Instance A have been stopped to prevent further data collection.

3. Configuring ACC Listener on Instance B: The next step is to set up the ACC listener on Instance B. This involves configuring the mid server to connect to Instance B using port 443.

However, an error is occurring during the ACC listener on the Instance B 'Error - Failed to setup the agent client collector. MID web server creation didnt succeed'

[cassieb_]

Is the ACC Websocket Endpoint configured for the new MID Server to be the same as the old one?

[VinjiPrak]

Dear @cassieb_ 

Yes, the ACC Websocket endpoint configuration will be same because the host on which mid servers are installed are same. Post migration we will turn off the mid server instance 1 service and mid server instance 2 will be alive. (Both these mid instances are hosted on a single server. One is pointing to Instance A (which will be sunset soon), and instance B will live.

[Doci1]

I would start with MID machine restart. Not just the service 😉

[VinjiPrak]

Dear @Doci1 

Quick Background- 

I have two servicenow instances: Instance A and Instance B. Instance B is a newly created, fresh instance. Our goal is to migrate all data and configurations from Instance A to Instance B, as Instance A will eventually be phased out and decommissioned.

Currently, there are thousands of agents reporting to Instance A. To avoid modifying the agents' configurations, such as changing the MID server URL and API key, I plan to install an additional MID server on the same host that currently points to Instance A. This setup will result in two MID server instances running on a single host: one pointing to the older Instance A and the other pointing to the new Instance B.

As of now - Steps

I turn off the ACC listener on Instance A. To do this, I navigate to the MID web server record in the UI and select 'stop.' Additionally, I stop the WebSocket endpoint record to ensure the ACC listener is fully disabled. (Is there anything else I should consider to completely stop the listener?)

Next now, I proceed to Instance B to configure the ACC listener. However, when I attempt to enter the port during the ACC listener configuration, I encounter an error. - 'Failed to setup the agent client collector. MID web server creation didnt succeed'