ITOM Cloud Core Services + Pointing ACC agent to different ServiceNow instance

[Todd Berry]

Has anyone successfully been able to point your ACC agent to a different ServiceNow instance via the ITOM Cloud Core (mid server less architecture)?

For example, we installed our ACC agent on a windows laptop and configured it via the out of the box instructions to point to our ServiceNow Dev instance.  We are now manually want to point this to our ServiceNow test instance so we can verify and test.  We have not been able to get it to work, but executing the following steps

- stop ACC agent

- delete certs in the /cache/cnc folder

- update URL and registration key in the acc.yml

It won't connect properly so i feel like we are missing a step.

Any luck yet?

[Derek Kitzelman]

@Todd Berry , Can you try deleting the value of the "agent-key-id" parameter. It should be at the bottom of the acc.yml. This should be re-populated once connectivity has been established to the new instance.

[Todd Berry]

Yes, i tried that and it didn't work.

[dougw]

I got it to work and didn't even clear the cache, lol.

Do you have ADCv2 enabled on your instance?  That has to be enabled in order for MID-Less ACC to work.  And be aware that PDIs do not support ADCv2 

[SK Chand Basha]

Hi @Todd Berry 

Can you try to clear the cache as well. 

KB :- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1182043

Mark it helpful and Accept Solution!! If it helps to understand.