Moved to ePO for better handling.
Are all the clients on the same domain?
What credentials are you suppling for the install?
Do you do anything funky like remapping temporary folders to network shares?
All clients that I get this issue with are on the same domain.
The credentials that I am supplying are the same ones that have worked with all 1000+ clients that I have successfully deployed to.
I am not aware of any remapping like that.
Do you mean the faulty clients are on a different domain to the ones that work?
No they are all on the same domain.
mmmm....Do you know anything about these machines that would be different from all the others. Has the OS been deployed using an image?
Are you able to confirm that the agent is actually installed or not.
Are you able to get the agent status monitor to open and have a green band at the top with 'Agent Service is now running'?
I'm actually running into something similar. The actual server task log reports the "Deploy Agent" action as successfully completing. When you drill-down and review the log, though, you get the "Failed to access remote system registry, system error: The network path was not found." message.
Haven't identified the cause on my issue, either - in my case, I believe multiple issues are compounded. One of which, is multiple domains. I also believe UAC configurations and potentially Windows Firewall are adding to the headache.
What's annoying, though, is I can see the in the ePO server logs where it is successfully connecting to the target endpoint, authenticating, copying the McAgent to the ADMIN$, and executing the FramePkg installer.
The agent isn't installing, I get no system tray icon or system process running.
I can't be sure if the OS was out of the box or an image, but it is likely a ghost image that wasn't sysprep'd as our legacy systems are still out there.
Could if be a SSID or similar issue?
Try to turn the Windows Firewall off and then redeploy.
Also make sure you can connect to the hidden share of the target host.