Quantcast
Channel: Ivanti User Community : All Content - Endpoint Manager and Endpoint Security (EPM) (Powered by LANDESK)
Viewing all articles
Browse latest Browse all 1714

1165 - The agent setup program started but communication is lost

$
0
0

Problem:

Unable to install a LANDESK agent. When pushing an agent, the status never succeeds or fails, but remains active. The status may show 1165 The agent setup program started, but communication is lost.

 

Process:

When installing an agent, you will need some elevated permissions in order to do so.

First, the account will need permission to create a folder on the intended target. On windows, this will be C:\$ldcfg$.

Second, the account will need permission to copy the agent installer into the created folder.

Third, the account will need permission to remote execute the agent installer.

 

Many times this issue may be temporarily network related, and may resolve itself.

Sometimes, it is network related and may require some help, such as rebooting a router or switch.

Other times, this may be caused by permissions issues, which may have inadvertently changed, even if the account is a Domain Admin.

Solution:

  1. Make sure that the agent installer is being copied over to the target machine.
  2. Ensure that the specified scheduler account has remote execute permissions.

 

Check Remote Execution Permissions:

  1. Download PsTools from Microsoft TechNet Windows Sysinternals. (https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx)
  2. Extract PSTools either into your execution path or something short off the root such as C:\Temp\PsTools.
  3. Open a Command Prompt.
  4. If you do not have PsTools in your execution path, then change directory to where PsTools was extracted. (ie. "cd C:\Temp\PsTools").
  5. Issue a simple command with PsExec calling an executable on the remote machine. You may be prompted to accept the End User License Agreement.
    1. Example: Remotely create c:\$ldcfg$
      1. psexec \\ComputerNameOrIP -u Domain\SvcAcct cmd /c md c:\$ldcfg$
    2. Example: Remotely execute a command on target machine
      1. psexec \\MachineOrIP -u Domain\SvcAcct ipconfig
      2. 41650-1.jpg
  6. The command should run. If you receive "access denied", then you may need to investigate why the account does not have the correct permissions for remote execution.

 

NOTE: Please be careful with PsExec and other PsTools as they are very powerful and can inflict damage upon your computer systems if used incorrectly. Because of this danger, some AV and security products may block the usage of PsTools or flag them as a vulnerability. The AV and security products may need to be temporarily disabled while investigating permissions.


Viewing all articles
Browse latest Browse all 1714

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>