Post migrate RADIUS server from Windows 2012 R2 to Windows Server 2019, Windows 10 Client facing RADIUS Authentication failure for 802.1x protocol

Question

I had one W2K12R2 WDC+NPS server. I build a new server with different name, configure the server as per our environment. Then I've demoted the old DC and promoted new server as DC with same name & IP address. Also, I export & import NPS configuration from old server to new server. Now new W2K19 DC is working fine but in NPS log I can see so many 6273 Audit failure events. Office users are reporting they are unable connect wither through Wired or Wireless network.
Our environment is either system will connect through wired or wireless, first it will go to RADIUS server for authentication (certificate based EAP 802.1x protocol), once system will be authenticated, it will get IP address and can enter our office network else it will take guest network (only internet). Wireless access points are Cisco Merarki.
When users are coming office after DC upgrade, they are unable to authenticated by RADIUS, as a workaround we are connecting those system through gest network, then connect VPN, then updating group policy, rebooting the laptop, after that users are getting authentication from RADIUS server.
I'm looking for some urgent help or solution on this issue as there are so many users, we won't be able to provide this workaround to all users one by one. Not sure do we need to modify group policy or not for 802.1x or we need to modify something else in new DC+NPS server. If someone can help me out from this worst situation.