Hi @Mohamed Raees - did you follow the Agent Management User Guide for install?

Hi @Mohamed Raees, since the manual installation works, then this is great. Next steps, you would need to check a couple of things such as reviewing the logs for any error messages relating to the agent deployment process. 

Also do not forget to check for network restrictions (Windows Firewall) by ensuring the right port is open for proper communication: https://helpcenter.veeam.com/docs/backup/agents/used_ports.html?ver=120

If you review the Windows event logs of the physical machine you’re trying to do the install on, can you see anything descriptive of what the issue might be? The User Guide shows some possible Agent Events you can look at. The VBR console may have some logs in the: C:\ProgramData\Veeam\Backup location as well.

What errors are you getting?

Are these machines joined to a domain?

Have you got firewall enabled? If so, have you got the appropriate ports opened as per the documentation?

its actually in machine rescan shows error

Click on the host within the rescan and it should provide error details

it shows network path error .i am facing this issue only for one server or pc in which i installed VBR

Can you send a screenshot please, is the PC domain joined?

I had this as well and it was firewall issues, the machines were in a different subnet and all the ports had not been opened by “Mr network”. Not my area networking but could be routes too? if maybe your not on your default gw. You can to a powershell test-netconnection with the port numbers to check https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection 

Looks like you can shorten that command to tnc , wow and I have been typing it out for years.. 

This is an important question.  If the PC is NOT domain joined, there is a service or setting (I have to look it up again) that is not running by default that you have to manually add/enable for the agent to authenticate or have access to the workstation.  I can’t remember what it is, but I’ll look it up again.

For reference (not sure if it applies to you or not), but the item that needs to be enabled is the LocalAccountTokenFilterPolicy.  You can view the two below links from the R&D Forums that reference this.

https://forums.veeam.com/servers-workstations-f49/pushing-agents-to-non-domain-computers-t69495.html

https://forums.veeam.com/veeam-agent-for-windows-f33/unable-to-install-backup-agent-t81785.html