1 2 Previous Next 11 Replies Latest reply on Oct 13, 2015 9:26 AM by c.estes

    EPO 5.1.1 failed agent deploy

    c.estes

      Hello,

       

      I am actually have two issues at once.  I am trying to use EPO 5.1.1 to deploy the agent client on domain PCs.  I have around 60 PC listed within EPO and about a 1/3 of them actually completed the deployment successfully.  1/3 of them say they are completed but the machines status never changes from unmanaged to managed and when I click on the systemname for one of these computers it shows no indication that is actually has the client installed.  The 1/3 straight up fail and give me a error like below:

       

      Starting deployment to computer "systemname" through the Agent Handler servername.domain.local 

      Failed to authenticate with remote system, system error: The network path was not found. 

      Failed to authenticate with remote system, system error: The network path was not found. 

      Expired. The task will be stopped.

       

      these are all domain computers and I am using domain admin credentials so I am not sure why it is failing? 

       

      Any ideas?

       

      Thank you

      Colin

        • 1. Re: EPO 5.1.1 failed agent deploy
          Peter M

          Moved to ePO for better support.

          ---

          Peter

          Moderator

          • 2. Re: EPO 5.1.1 failed agent deploy
            Richard Carpenter

            Hi c.estes

             

            The log you have provided indicates that the Network Path cannot be found. This is normally down to either Name Resolution of the system name by the ePO server, or that TCP 139 & 445 are not open from the ePO server to the System to copy the Windows Agent exe file to the system.

             

            Try using nslookup from your ePO server to resolve the system name using NetBIOS (unqualified name), if this fails check the DNS settings on the IP configurations of the ePO server and the FQDN suffix list.

             

            If name resolution works, check that the ePO server can get to the remote system on port TCP 445.

             

            Regards

            Rich

            McAfee Volunteer Moderator

            Certified McAfee Product Specialist - ePO

            • 3. Re: EPO 5.1.1 failed agent deploy
              Daniel_S

              Maybe you also check the firewall-settings on your clients.

              It´s an often to see problem for the ePO not being able to contact the clients.

               

              Regards

              Dan

              • 4. Re: EPO 5.1.1 failed agent deploy
                c.estes

                As it turns out I confused myself a bit before creating this thread.  The message I posted was for about 24 works stations that the server can't contact.  It is possible that these are laptops that are being used by off-site users and I wont be able to verify until later this week.  there are a couple of other computers that I can contact and I can get the Admin$ but still get this error message:

                 

                Starting deployment to computer hostname through the Agent Handler server.domain.local

                Failed to access remote system registry, system error: The network path was not found

                Deploy agent installation package to target system was successful

                • 5. Re: EPO 5.1.1 failed agent deploy
                  Daniel_S

                  In the ePO-settings you can configure how and in which order ePO is trying to contact the systems. This can be DNS, IP etc.

                  So it´s quite possible and normal that you get such messages when the first method fails.

                   

                  Regards

                  Dan

                  • 6. Re: EPO 5.1.1 failed agent deploy
                    avinash34

                    check this link  before pushing the agent to the client systems.

                    My guess is may be remote registry service is not running on the client machines.

                     

                    Thanks,

                    Avin

                    • 7. Re: EPO 5.1.1 failed agent deploy
                      c.estes

                      Thanks.  I was able to load the remote computers services.  I did notice that remote registry service was started but I stop and restarted it and the installation went through successfully with no errors.  Unfortunately now they still show up as unmanaged despite have the installer run.  I have about 10 other computers sitting in the same boat and ideas?  Sorry for all the diferent issues it feels like as soon as i fix one issue another pops up.

                       

                      thanks for your help so far.

                      • 8. Re: EPO 5.1.1 failed agent deploy
                        Daniel_S

                        What does you ePO say, when you ping the system? Is it reachable?

                        • 9. Re: EPO 5.1.1 failed agent deploy
                          c.estes

                          Yes EPO Says the system is pingable.

                          1 2 Previous Next