Jump to content

WBlank

Members
  • Posts

    1
  • Joined

  • Last visited

About WBlank

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. We are in the process of virtualizing our servers, and I have created a new ESET server on my network, so at this time I have two. Once the migration actually works, we'll only have the new one. My problem is when I log into the old server and use its ESET Remote Admin Console, I select every computer on it's client list and create a configuration task. In this task, I put in the address of the new server for the Remote Administration field, and also for the Update Server. Upon activating this task, the most confounding clusterf has occurred. About 50% of the clients packed up their belongings and moved over to the client list for the new server. 100% of them also stayed behind on the old server, which is fine, when that server is turned off, it'll sort itself out. Secondly, of those 50% that it actually worked for, some decided to switch update servers, and some didn't. So I've compiled a list to check one by one, to see why they won't listen to the voice of reason and migrate to the new server. I can ping these machines from both servers just fine. When I activate the task to make the clients move over, it just says Waiting for the State, it never activates. What's the deal?
×
×
  • Create New...