Issues after changing the AP Name on Wireless LAN Controller

Question

I recently changed the AP Name of all the Wireless Access Points in my branch office (which are all associated to the branch office Wireless LAN Controller(s)). After that I noticed that all branch office employees are unable to connect to the employee SSID. The employee SSID uses web authentication and employees are authenticated using Head Office AD via Cisco ACS, both located at the Head Office.
There are other SSID's on the WLC which all work fine, but only employee SSID which uses AD authentication does not work. AD authenticaion is working fine because employee's in HO are successfully able to connect to the employee SSID at HO.
The branch office is connected to the HO via a tunnel link. We noticed that if we restart both the ASA at either ends of the tunnel. The employee SSID starts working again but only temporarily for a day or so... what could be the issue? Can renaming the AP's cause issues? How can I fix this problem?
Thanks in advance

Answer 1

Thanks Elliott,
        I did the debug like you said and I am getting the following debug messages:
*apfMsConnTask_0: Jun 20 08:18:14.580: Deleting the client immediatly since WLAN is changed
and also
*apfReceiveTask: Jun 20 05:25:11.857: 00:1f:3c:86:af:15 Orphan Packet from 192.168.52.34
The logging on the WLC shows
*apfReceiveTask: Jun 18 17:56:41.788: %MM-1-ANCHOR_UNAVAILABLE: mm_mobile.c:2155
All export anchors are down. Cannot anchor the client.00:c0:a8:f3:cd:ae
The DHCP pool for the employee users are configured on a guest WLC which sits behind an ASA