This is an issue again, and will be resolved in moments the problem is someone is adding a domain, and it is making the XML on the config malformed and having to be fixed.
We will be changing the nodes for win15 server tonight, I believe there is an issue on this node making the problems. We already have a new node setup and working to do it with as little outage as is possible, hopefully less than 10 minutes in total. We have it in control manually fixing ever 2-3 hours, but it is getting to be quite a pain.
Server is up now, didn't even reboot but did swap the primary and backup network adapters in settings and change some configs. Very glad to know not an issue on the new node hardware, but a rare issue indeed.
We will need to do a maintenance for adding a backup nic to this at some point now, as it seems this one has died(need to do a swap), but the server is up, without even a reboot at this time, and we have other means to take the backups for now. We will post notice in a planned manner to do the nic swap.
Wow wild, having some packetloss on this new NIC now, I am here in the datacenter with our tch in training, we are going to do a NIC swap in the next 15 minutes now to get this resolved for good.