If the Pulseway agent deployment fails then please check the following:
- Can you ping the remote system from the probe?
- Is the system which is marked as 'Probe' into the same subnet as the system on which you are planning to install the Pulseway agent(target system)? If the target system and the probe are on different subnets, then installation will fail. The probe an target system should be into the same subnet.
- Check if the admin share on the remote system is accessible please run this command from the elevated Terminal window and enter correct credentials: \\ip-address\admin$
- Check whether the .Net Framework version 4.0 or higher is installed on the remote system.
Also, please make sure that you are using the correct Domain Administrator credentials (username and password).
But if this doesn't help, then enable the diagnostic logging on the agent (probe) from the Pulseway Manager -> Settings -> Diagnostics. And then send the deploy command once again and then look for the errors into the trace.log file. This file is located in the Pulseway's installation directory.
If you cant resolve this issue, then please send the trace.log file to the support@pulseway.com so we can investigate the issue.
Comments
1 comment
Another vital step to check is making sure Network Discovery is enabled on target systems. Simply open target system's File Explorer > Navigate left hand panel to "Network" > Click on it > If disabled, banner message will show up towards top of window > Click Enable (you must have Admin credentials to enable if UAC is in effect, depending on your local policy)
Or use this alternate method to enable https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/cannot-turn-on-network-discovery
Please sign in to leave a comment.