03-27-2018 11:12 AM - edited 02-21-2020 10:52 AM
Hello All,
2 Weekends ago we upgraded our ISE Servers from 2.0 to 2.3.
Prior to the upgrade I had to modify the Hostnames of the 2 ISE Servers. Because of the change, each client's "ConnectionData.xml" file was still showing the old Policy Node's Hostname. So I modified one ConnnectionData.xml file to show the 2 new FQDNs of the Policy Nodes. Then, we pushed this new XML config file with PDQ to all client machines.
*FYI, I already have new Certs on both of the ISE servers for their new hostnames which were signed by our Internal Windows CA Server...
One of the Windows 7 PCs that this was pushed to, is still showing the Policy Server's OLD hostname in the System Scan tab of the AnyConnect settings window, even though the ConnectionData.xml file is showing the correct hostname.
I've tried starting and stopping each of the AnyConnect services for all the modules, including the ISE Posture Module. When that didn't work, I rebooted... Even after the Reboot I am still getting the pop-up error message from AnyConnect that shows the Security Warning that the cert doesn't match the Hostname. Since the ConnectionData.xml file is showing the correct hostname, I'm not sure why the Security Warning message is still displaying the old hostname..? Screenshot below...
It almost seems as though its getting the hostname from a cached config file somewhere on this PC. But, I'm not sure where else the PSN's Hostname would be defined, other then ConnectionData.xml?
Any thoughts or suggestions would be greatly appreciated!
Thanks in Advance,
Matt
03-27-2018 12:01 PM
03-27-2018 12:35 PM
04-04-2018 08:52 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide