Seen this before, for me it involved a DNS issue; system had two IPs (cable & wifi) - cable was active yet wifi held the DNS record: disabled wifi flushed DNS and after that deployment worked...Perhaps it's the same issue for you.
I tried this out and it did not work
Does anyone have any other ideas?
Check the logs. %temp%\McAfeeLogs\
Are you sure the account credentials are valid on failed computers? Windows firewall is on?
Are you able to open the admin$ share of the client system from the ePO server using the same credentials used when using Deploy Agent
One way you could determine it is a network related traffic blocking is by taking the FramePkg.exe and manually install it on one workstation, then see if it can communicate to ePO - if it can't, you will get an error in the Agent_error.log within C:\ProgramData\McAfee\Common Framework\DB
I ran into similar issue. Just to rule out it was DNS issue I set epo to communicate using NetBIOS with the remote system. It worked fine
Double check the IP address of the remote system. Do an nslookup from the epo server if it resolving to right DNS hostname.