This content has been marked as final. Show 9 replies
Check the Agent log files
Mine use FQDN (EPOSERVER.DOMAINAME)
so as long as DNS is working the machines should have no issues contacting the ePO server.
I'm sure l have read in the past that ePO does not like IP address changes.
As cheesestraws suggested..
As you have altered the sitelist.xml its newer than that on pc's then when the DNS redirects the agents they pick up the new sitelist.xml and use this with the new entries.
when do l alter the sitelist.xml?
when you alter the servers IP it will be altered automatically
The agent will try to contact the epo by its IP adress 6 times and if unsuccessful, it will try to use the DNS name of the ePO server. (Also in the sitelist). I suggest you examine the sitelist on a client to see what it looks like. In my environment I only see the NetBIOS name of the EPO server. so in that case if you are in a multidomain environment, you need to make sure that all clients will find the server by its NetBIOS name.
Try looking into the DNS suffix of your clients or maybe you have a working WINS infrastructure. Why do we always com back to that? happy nobody like WINS!
had a look at my sitelist.xml on a vista client and it has the following
So looks like l should be ok.
Sounds good pryorn.
I moved a large ePO3.6.1 installation this spring, but I could also move the subnet where the ePO was placed so I did not have this issue. I suppose since my ePO is not in a AD domain that is why the FQDN is not in my sitelist.
Good luck //Ronny
sadly we are not using AD, still stuck with NT4 Domains. Please don't laugh.