Is it possible that these machines did actually move across domains at any point (Travelling laptops for example ?).
Have a look at the local sitelist.xml some of these machines, as this eventually defines which AH a client will actually be talking to.
It''ll be towards the end, lsited as an 'SpipeSite'.
As to the reason, that may require a lot more analysis, it might be better to open a support case to have it investigated.
Thanks for the reply Rob. They are fixed servers in each domain so they shouldn't have moved domains.
I'll have a look at the sitelist.xml file and compare between a rogue server and a working server and look at what AH is listed.
It may happen wen the AH is unable talk to ePO server or else the AH is unable to send and collect the properties from ePO servers.
if still the problem exist kindly recreate the FramePkg.exe with exact sitelist.XML.hopefully after tat the AH will be able to collect and send the properties successfully from the ePO server