Unable to add the RD Virtualization Host server:

Question

Essentially, I’m unable to add a RD Virtualization Host Server to a Remote Desktop Connection Manager.  Below I’ve laid-out my server configuration(s), their roles within the network and other items I deemed necessary to trouble shoot this problem.

 

VDC1 – Domain Controller

·         Hosts RD Licensing Manager (Activated)

VSERVICER1 – Various RD Roles

·         Remote Desktop Connection Manager

·         Remote Desktop Session Host (This is only being used for RD redirection)

VBROKER1 – Frontend Web Server

·         RD Web

·         RD Gateway

IHOSTNODE1 – Hyper-V

·         Remote Desktop Virtualization Host Agent

 

So when I attempt to add IHOSTNODE1 to the Remote Desktop Connection Manager I get the following error message “Unable to add the RD Virtualization Host server”.   The trouble shooting methods I’ve employed s far have consisted of the following.

 

1 – Temporarily turned off the Windows Firewall across all servers previously mentioned.

2 – Search all the Event Logs for more descriptive messages.  Unfortunately, there isn’t the slightest hint of a problem.

 

Has anyone else ever experienced this issue?  Any insight or guidance will be greatly appreciated.

---

Chris Felpel Blog: http://www.yahoogler.com Email: [e-mail]

Answer 1

Well, the lack of responses lead me to believe that no one else ran into this problem...  Well, this lack of direction forced me to start at the ground floor on this one.  Sooo I downloaded Process Monitor and started from there and quickly discovered this problem was due to the server VSERVICER1 and the domain controller VDC1 having the same PID.  Ran sysprep, rebooted and rejoined to the domain.  Problem solved.  You got to love pointless error messages.

---

Chris Felpel Blog: http://www.yahoogler.com Email: [e-mail]

Answer 2

Well, the lack of responses lead me to believe that no one else ran into this problem...  Well, this lack of direction forced me to start at the ground floor on this one.  Sooo I downloaded Process Monitor and started from there and quickly discovered this problem was due to the serv rer VSERVICER1 and the domain controller VDC1 having the same PID.  Ran sysprep, rebooted and rejoined to the domain.  Problem solved.  You got to love pointless error messages.

---

Chris Felpel Blog: http://www.yahoogler.com Email: [e-mail]

So, the problem was caused by the conflict of the PID? It will be much more convenient if this is told directly in the error message. It should be impossible to me to find out the reason in two days.

Answer 3

Hello , 

I tried the sysprep but it does work. Can you explain how did you do with the process monitor if my problem is the same as you.

Answer 4

Thanks for the help... my problem was in a single domain and it turned out to be an incorrect dns config- but the lack of ad authorization was the prob still