Monday, July 22, 2013

Unable to add new Veeam proxy server with the error: “Failed to install deployment service.”

Problem

You attempt to add a new Veeam proxy server that is located in your DR site that will be used as a target proxy for replication but receive the following error:

[serverName] Failed to install deployment service.

Access is denied.

--tr:Failed to create persistent connection to ADMIN$ shared folder on host [IP Address].

--tr:Failed to install service [VeeamDeploymentService] was not installed on the host [IP address].

image

image

The service account you’re using is a local account on the proxy server that is a part of the local administrators group.

Solution

This error ended up being more Windows related than Veeam as when I tested connectivity to the server, I was able to RDP but could not UNC to the admin$ or c$ administrative shares.  What I realized after troubleshooting the issue was that UAC was turned on for the proxy server with Windows 2008 R2 as the operating system and this was denying access for accounts that try to remotely access these shares.  There are 2 ways to correct this:

  1. Turn off UAC
  2. Modify a registry key to allow remote access

I ended up opting for turning off UAC since this environment has most servers configured as such.

6 comments:

Anonymous said...

thanks your article helped me with the same issue !

Julia David said...

I read your article and get very important information in addition if you have any query you can click here.
ExtraTorrent UK proxy

Anonymous said...

Firewall was problem on my Windows 2012 servers.



I had same issue:


Veeam Backup and Replication

The network path was not found.

--tr:Failed to create persistent connection to ADMIN$ shared folders on host [172.16.xyz.xyz].

--tr:Failed to install service [VeeamDeploymentService] was not installed on the host [172.16.xyz.xyz]

I tried different users, but the resolution was firewall-related.

Anonymous said...

I had the same problem but I could browse to the admin$ folder. I ended up typing the username manually (DOMAIN\username) rather than selecting from the Browse button and that worked!

I was using Server 2012, Veeam v8.0.0.2084 trying to add Server 2008 R2 as a target proxy.

Anonymous said...

Yup, DOMAIN\username worked for me too!

Anonymous said...

Thanks DOMAIN\username worked for me too!