I have some clients that, through the miracle of several admins attempting to master the (inexplicably complicated) interface of the remote console, are lost to the system. They do not report to any console that exists. My question is, if I cannot alter those clients (by simply modifying that registry value, which seems like it would work, if I can shut down the serivces using the key or run the change as that service somehow), is there some way to hijack the standard setting for the update server, so that those clients end up pulling updates from my server instead of trying to pull directly from ESET? Can I fool them with a local DNS zone or something to get them connected? And if they pull updates from my server, will they show up as clients? Or does that require that the remote console setting be explicitly set. I suppose if I could at least have the clients pulling updates while I sort out recovering them via push installs, that would be something. So, can I just hijack the ESET domain name with my own DNS server, and get them updating at least?