Hi,
I am currently facing an issue with unattended deployment of the RD Session Host 2012 R2 role. My current setup looks like this:
1 x RD Session Host
1 x RD Connection Broker
1 x RD Web
What I am currently working on is to deploy another RD Session Host to my deployment using MDT 2013. I have the OS deployment and RD Session Host role deployment running and working, the issue is joining the ned RD Session Host to the deployment and collection.
I use this powershell command as a part of the MDT deployment process:
Add-RDServer -Server "$env:COMPUTERNAME.test.lan" -Role RDS-RD-SERVER -ConnectionBroker "rdcb.test.lan"
When I monitor the deployment process I can see that the above command gets executed on the server, however nothing happens other than that.
I suspect that because MDT runs in local admin/system context the above command doesn't work. The reason for my suspicion is that if I execute the above command as a domain admin on the server, it joins the deployment and Collection without any issues.
As MDT doesn't have any native support for running a deployment process or parts of the process as a domain admin, I have tried a few approaches to run the above command in some kind of domain admin context, I have however not been able to find a working solution.
Does anyone have some experience with automated installation and configuration of RD Session Host 2012 R2 using MDT 2013?