We have had ESet Remote Server and Console (V 188.8.131.52) installed on a Windows 2003 Enterprise Server which acts as a Domain Controller. Clients are pointed to that server and show up in the console, the console connects to the ERA server, no problem. We are now going to replace that Domain Controller with a new machine running Windows 2012 Essentials. The new DC is on a new domain but we've established a trust relationship between the old and new domains, temporarily, as a means of transitioning from one to the other. I've installed ESET Remote Server and Console (V 184.108.40.206) on the new DC and tried, as a test, to switch one or two workstations from the old to the new ERA Server by opening up NOD32 AV on the clients and updating the IP of the Remote Administration server. Unfortunately, even after a day, neither of the two w/s I switched show up in the new console's list. Further, the new server doesn't show in the upper (Server) pane, even though it says "Connected" in the lower right-hand corner of the window. I've double-checked the IPs and the ports, the Remote Server service is running, I just don't know where to go from here. I've examined the ESET KB but every article I've found seems to address peripheral issues. I would very much appreciate any pointers to KB articles or ESET site resources that would outline the appropriate procedure for switching servers. Thanks in advance.