1969 is some sort of epoch system time. i would re-install the agent and try again, because it sounds like your installed agent is at fault.
Did greatscott's suggestion correct your issue?
sdelvecchio and greatscott,
No it dosnt seem to be helping, weve reinstalled the agent manually on this machine several times. When we open the status monitor, we can see it is communicating with the ePO, even pulling the task to install point products. Its just not installing the point products.
Now, i must note that we have to manually install the agent on this computer to get the ePO to pick it up. Using the "new system" selection from the ePO server does not work, as when we browse for the system after selecting the workgroup or domain, it will not appear in the list of selectable clients. Im not sure if this have anything to do with it.
Time to start doing some further digging.
- RDP to the client machine and open a cmd window can you ping the ePO server?
- RDP to the ePO server and are you able to get to the admin$ of the client?
- From the ePO server open a cmd window, and do a forward and reverse nslookup on the client machine? Does the IP address and DNS match?
- From the client machine look at the sitelist.xml file is the correct ePO server listed?
- Is there a firewall (either corp-wide or local) preventing communication between ePO on ports 80,443 and 8081?