I have a laptop here I recently reloaded with W10 for a user. I am trying to deploy ESET antivirus through the admin console. ESET is installed on our backup DC (DC02). The agent deploy task kept failing so I went to the machine and was able to ping the DC hostname from the laptop but from the DC, I can't ping the laptop if I use the hostname, it fails because it is trying to ping the wrong address (192.168.1.136). The IP of the laptop is 192.168.1.122 and when I ping that, I do get a response (this is the network adapter address, not wifi).
I flushed the DNS on both DCs and tried again but it is still seeing the laptop with the wrong IP. 192.168.1.136 isn't a used IP right now, it is nowhere on the network. I removed the laptop from the domain, removed it from AD and from ESET, shut it down, flushed the DNS on the DCs again. Started the laptop up, joined the domain (it pulled the same 192.168.1.122 address from the network adapter), moved the laptop into the correct folder in AD, sync'd AD with ESET, tried to push the agent again but it failed.
I went back to the DC and it is still associating the hostname of the laptop to 192.168.1.136.
Any ideas on what else to try? I can't deploy the laptop until I have ESET on it.