Desktop Central Agent installation, Patch Scan , Asset Scan and Remote Control fail with error message - "Network Path was not found."
This error will be shown if,
You can resolve this issue as follows:
Check the client computer is switched on and connected in the network properly to install agent and carry operations like Patch Scan/Remote Control/Asset Scan. Also, ensure that you have specified the computer name correctly. The following steps will help you confirm the client machine's accessibility:
Goto Start > Run > Type computer name prefixed by "\\" and hit the Enter key
Enable this in all the client computers as below to carry out remote operations like Agent Installation/ Patch Scan/ Inventory Scan/ Remote Control in the client machines.
For computers using Operating System released before Windows 7, follow the steps mentioned below;
For computers using Windows 7 as Operating System, follow the steps mentioned below;
Firewall has to be configured for a problem-free agent-server communication. Enable the Microsoft Firewall settings in the Desktop Central application as follows and try doing the desired opeartion.
Goto Admin tab > Agent Settings > General Settings > Select Enable Firewall Settings
The settings will get applied during the subsequent refresh cycle. To apply the steps immediately, follow the steps mentioned below:
Note: You will still have problems related to Windows firewall in case, the Group Policy is configured to not allow exceptions. To overcome this, you will need to modify the GPO accordingly to allow the Desktop Central Server to communicate the Desktop Central Agents via the 135 and 445 ports.
Run the script as explained below in all the client machines to configure the Firewall to carry out remote operations like Agent Installation/ Patch Scan/ Inventory Scan in the client machines:
Running the above script will open the following ports in the client computers and installs the Desktop Central Agent:
To run the script in multiple computers, you can either use the PsExec utility or add this script as a startup script in the GPO of Active Directory.
Desktop Central aplication copies the Agent binaries to the Admin$ of the client machine prior to triggering Agent Installation. Therefore it is essential to have the Admin$ enabled in the client machines for smooth Agent Installation. You will need to edit the registry to enable the default administrative share.
For Windows Server 2008 R2: In case you have a Windows Server 2008 R2 based domain environment you can enable the Admin$ in your client machine using a Start-Up script. Please refer to this document for details.
Applies to: Agent Installation Failure, Desktop Central Agent Installation, Patch Scan Failure, Asset Scan Failure
Keywords: Agent Installation, Desktop Central Agent Installation Failure, Patch Scan Fails, Asset Scan Fails, Installation Failure
|Unable to resolve this issue?|
If you feel this KB article is incomplete or does not contain the information required to help you resolve your issue, upload the required logs, fill up and submit the form given below. Include details of the issue along with your correct e-mail ID and phone number. Our support team will contact you shortly and give you priority assistance and a resolution for the issue you are facing.
|Other KB articles||24/5 Support|
Support will be available 24hrs a day and five days a week (Monday through Friday), excluding USA & India public holidays.
Tel : +1-888-720-9500
Speak to us