Ask the Community
Groups
Why are Agents not installing via LANWatch? - Connect IT Community | Kaseya
<main> <article class="userContent"> <p> </p> <p><strong>Question:</strong></p> <p>Why are Agents not installing via LANWatch ? An error "The network path was not found" is seen in the log</p> <p> </p> <p><strong>Answer:</strong></p> <p>You have entered apparently valid credentials and used a valid package to install agents on machines. However, after scanning the LAN using LANWatch, some you see some obvious error messages,e.g. wrong user name and password, no admin$ share, but some seemed to have just not installed.<br><br>When trying install the client you get this message "The network path was not found"</p> <p>The causes could include:</p> <ul><li>An attempt to connect to\\admin$ resulted in a failure.</li> <li>A possible combination of the windows firewall on the client and incorrect net bios name resolution on the server.</li> </ul><p> </p> <p><em>The following instructions only apply to Kaseya on-Premise VSA customers</em></p> <p>Run a manual instance of the LANWatch to assess the problem.</p> <p>LANWatch uses a program called KCONNECT to remotely connect to and install the agent on remote machines. It is this program you need to run to assess the issue.</p> <ol><li>Copy kconnect.exe from kaseya server e.g. c:\kaseya\webpages\ManagedFiles\VSAHiddenFiles to c:\ on the machine on which you have been running LANWatch.</li> <li>Copy a version of the agent that includes the /r (force reinstall) switch in the package (this will force the install to proceed if some part of a previously failed Agent install still exists) to c:\ as well.</li> <li>From a command line at the root (c:\) of the LANWatch machine type the following command with MACHINENAME being the target machine for the agent:</li> </ol><p>kconnect \ \MACHINENAME -c -u domain\username -p password kcssetup.exe<br>(If there is no name, you can leave out the domain, or try the target machine name)</p> <p>If successful, you will see error code 0. </p> <p>If you see any other error message, type the following command to find additional information on the error:</p> <p>net helpmsg <em>{error number}</em></p> <p>These error messages are windows error messages and not Kaseya or PSEXEC error messages.</p> <p> </p> <p><strong>APPLIES TO</strong></p> <p>On-Premise Customers only<br><br></p> </article> </main>