RDS 2012 Connection Broker HA - DNS RR or NLB?

I'm setting up a new RDS 2012 farm and I need very high availability. I'm deciding on how to configure the connection broker HA. I have 2 server VMs that will be the gateway, rdweb, and conn brokers. The Microsoft article you have probably seen
RD Connection Broker High Availability in Windows Server 2012  recommends using DNS RR. And the standard
recommendation for the rd gateway is to use Windows NLB.
I'm a little perplexed as to why you would use DNS RR when you have a much more robust solution available with NLB. You are already setting up NLB for the gateway, so why would you use what I would say is an inferior choice with dns rr for the conn broker?
The main issue I see is that if one of the cluster servers is offline, dns rr will at least 50% of the time point clients to a broker that's not available. With NLB, it's aware of the server being down and will point all clients to the one that's online.
Am I missing something? Does anyone using NLB for conn broker have any input good or bad? Thanks much in advance...

You need to read that:
http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/general/remote-desktop-server-farms-explained-part1.html
And when you said  "at least 50% of the time" don't forget the client DNS cache.

Similar Messages

  • RDS 2012 Connection Broker and round robin DNS?

    Hi,
    I have a set-up with three session host servers and one of them is also a connection broker. Round robin DNS is configured for the three servers and the clients, who are all on our internal networks, can connect just fine to the farm name. My
    questions is, is there any point in having round robin configured since the connections still need to go through the CB? Could i just have one DNS-record for the farm name pointing to the CB? My initial though was that round robin would add
    redundancy, but does it realy? I've tried to find answers on this but none of the articles and posts i've found are realy clear to me.
    Quite often the initial connection for clients is slow and my theory is that it's caused by the RR DNS records.

    Hi,
    Thank you for posting in Windows Server Forum.
    I think we need to have DNS RR entries for our RDS environment because DNS RR will be used by RDP clients to connect to the RD Connection Broker servers. Once when we allowed the entries of all server to DNS RR, when there is alternate connection need to capture
    for following server it will provided by DNS RR. 
    During the connection process, the end nodes (RDVH, RDSH, RDWA) will get configured with all the RD Connection Broker server names, and they will randomly choose one to connect to. The RDP clients will use the DNS Round Robin name configured to connect to the
    RD Connection Broker servers randomly.
    More information.
    RD Connection Broker High Availability in Windows Server 2012
    http://blogs.msdn.com/b/rds/archive/2012/06/27/rd-connection-broker-high-availability-in-windows-server-2012.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • RDS 2012 Connection Broker and Web Access in different domains

    Hello!
    I'm trying to add Web Access (WA) server to RDS 2012 Deployment. WA server and other servers in Deployment are in different domains (in different forests with 2-way forest trust).
    WA server was added to Deployment
    successfully without any warnings.
    We have many applications published but in this new WA server there are no application icons in Rdweb page at all.
    There is nothing interesting in logs on WA server as well as on Connection broker servers. 
    Is this design
    acceptable? Which additional actions are needed to make application icons visible?

    Hi,
    Please refer below links and cross verify the Web Acess server settings.
    http://blog.kristinlgriffin.com/2010/03/rd-web-access-is-emply.html
    http://social.technet.microsoft.com/wiki/contents/articles/5974.the-case-of-invisible-remoteapp-programs-a-k-a-no-remoteapp-programs-listed-on-rd-web-access-site.aspx
    Regards,
    Manjunath Sullad

  • Confused by RDS Connection Broker and DNS

    Hi,
    I'm setting up the following in my lab to test before a production deployment:
    RDSH01 - RD Session Host 1
    RDSH02 - RD Session Host 2
    RDSH03 - RD Session Host 3
    RDSBG - RD Connection Broker
    Everything seems to work great if I point my RDP client at one of the session hosts via a DNS round robin, it redirects me to whatever server has my disconnected sessions on and new sessions get put on servers with the least connections, great, however,
    I have the following questions...
    I've read on other threads that I should be pointing my RDP client at the Broker, not at a Round Robin DNS containing the Session hosts.  That said, its working just connecting to the hosts and redirecting and load balancing accordingly.  Is this
    the right approach?  (I've got RDS.domain.local pointing at RDSH01, RDSH02 and RDSH03)
    I'm currently using a Self Signed Cert for RDS.domain.local which is great when initially connecting, however when I get redirected to another host it comes up with a warning for eg. RDSH02.domain.local as the Session Hosts have no certs on them.
    From what I've read, you don't need to put certs on every Session Host as the connection goes via the broker but when I connect to the broker I get told I'm not authorised, I can only connect to the Session Hosts.
    What am I missing here?
    Many thanks,
    Dave

    Thanks, I'll do that when I get to the live environment.  The client has 10 thin clients already at a remote location using a single RDSH directly, they're Windows 7 Embedded with the RDP update so I'll tweak them with the load balance details.
    As for R2, unfortunately we put the order through too early for R2 and have no SA, I tried to blag an upgrade through our MS account manager but he couldn't help as the prices have gone up so we'd have to go back to distribution and re-order :(
    The client is coming from a very old physical 2003 environment which hasn't been touched in years, the current 2012 RDS is 100x better than their full far desktop experience so we'll be fine.  Its 80 users over 3 RDSH's with 32Gb RAM on each although
    I may increase that as we have more in the pot.  Basically 3 VMware hosts on the front of an Equallogic, each with 64Gb RAM.
    I will need to have a look at HA RDCB but that just introduces a single point of failure on the SQL box, so would have to do that too, seems overkill, can I just remove the RDSH's from the collection and run without the broker if it dies and rebuild the
    collection with a new broker?
    How many SAN's will I need on my cert, I've got memories of having to make multiple requests the first time I did exchange years ago.
    Think I'll write a step by step guide for this, I've looked at loads and most on the web don't cover the little details, just the main steps which are kinda obvious.

  • RDS 2012- connect to session collection trough mstsc.exe on XP SP3

    Hi!! i need to connect to a session collection based on rds 2012 directly trough mstsc.exe on xp sp3 clients... xp don't support remoteapp and desktop connection and my users can't use internet explorer to connect trough rd web Access..
    Thanks!

    Hi,
    What you could do is upgrade Windows XP with the latest Remote Desktop Client available for Windows XP (http://support.microsoft.com/kb/969084)
    Then extract the .RDP file you want from the RDS 2012 environment (or specify the properties manually in a .RDP) file.
    Recently I wrote on article on the distribution of Remote Apps and desktops in Windows Server 2012, that might be useful:
    http://virtualizationadmin.com/articles-tutorials/vdi-articles/general/distribution-of-remote-apps-and-desktops-in-windows-server-2012.html
    Also, more info on the .RDP properties specifically needed for RDS 2012:
    http://microsoftplatform.blogspot.nl/2012/04/rd-connection-broker-ha-and-rdp.html
    Kind regards,
    Freek Berson
    The Microsoft Platform
    Twitter
    Linked-in
    Wortell company website

  • RDS 2012 - Connection issues when selecting "This is a private Computer"

    We recently cutover our corporate RDS system the Windows 2012 version and it was pretty smooth, only  few issue that where resolved quickly.  In the last 3 weeks I nave had 4 differnet users working from home on personal WIndows 7 system that
    they use to connect to their computer in the office using Windows 2012 RDS telling me that they can't connect any longer.  Doing some basic troubleshooting I discovered that if they select the option on the RDS Webaccess page "This is a private computer'
    they can't connect to their computer in the office.  If they select "This is a public or shared computer" It works fine.
    Anyone seen this before???
    Joe Gomez

    Hello,
    Thanks for your response.
    1. Windows Server 2012
    2. it appears that  it is connecting then it times out after about 30-40 second.
    3. "Remote Desktop can't connect to the remote computer for one of the these resons:"
    Remote access to the server is not enabled.
    The remote computer is turned off.
    The remote computer is not avalible on the network.
    Make sure the remote computer is turned on and is connected to the network and that remote access is enabled.
    4. I will try the a non customized RDWEB page.
    5. Our users have a range of RDP clinet version, I will make sure that these having the problem are on 6.3.9600
    6. Yes they use the Connect to Remote PC feature to connect to a physical PC in the office.
    This worked fine in the Windows 2008R2 RDS environment.  The new RDS 2012 we started to see this.
    Thanks
    Joe
    Joe Gomez

  • Shadowing of Windows 7 clients from 2012 Connection broker.

    Hi All,
    In the 2012 Remote Desktop Services Applet, one has the ability to shadow virtual desktops. When I try to do this I get access denied (either viewing or controlling). I've turned on file and printer sharing and I'm logged on as an administrator. I can send
    a message to the Virtual Desktop and Log them off. I've also installed the 8.1 patches for Windows 7 SP1.
    Does the remote shadowing only work for Windows 8 clients??
    SP1 updates applied:
    KB 2574819: An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1
    KB 2857650: Update that improves the RemoteApp and Desktop Connections features is available for Windows 7
    KB 2830477: Update for RemoteApp and Desktop Connections feature is available for Windows
    KB 2913751: Smart card redirection in remote sessions fails in a Windows 7 SP1-based RDP 8.1 client
    Thanks,
    Kevin

    Hi,
    Yes, the Windows 7 client is not supported.
    Host (that the admin wants to shadow)
    Clients (that the admin is using)
    Windows 7 SP1 (guest)
    Windows 8.1 (guest)
    WS 2012 R2 RDSH
    Servermanager
    No
    Yes
    Yes
    Windows 8.1 mstsc
    No
    Yes
    Yes
    Windows 7.1 w/ 8IP update
    No
    Yes
    Yes
    Windows Store RD client
    No
    No
    No
    iOS
    No
    No
    No
    MacOS
    No
    No
    No
    Android
    No
    No
    No
    Quote from
    Remote Desktop Services Session Shadowing
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Rds 2012 r2 - Connection Broker - Round Robin DNS

    I am working on building a 2012 r2 RDS setup with 2 session hosts, a web app, and a CB.   We are currently using 2008 r2 in a rds farm setup that is working perfectly, but wanted to get some of the enhancements in 2012 r2.. so that is why i am going
    down this path. 
    It sounds like when doing reading, is that we can no longer just drop the fqdn of the dns rr of the session hosts in the RDP client and it will connect.  Instead we need to log onto the web access portal and connect that way?  I tried the DNS RR
    to point to the session hosts, and that seemed to work, but had issues when disconnecting and reconnecting it  would push me to another session host.
    Is there a way to get it back to using DNS RR and the session broker work like it did in 2008 r2? I feel like end users are going to struggle when working from home and setting up a RDP client.  Or do i just not use the connection broker and use a Load
    Balancer like HA PRoxy?
    The documentation is very lacking on RDS on the new os... 
    Thanks in advance for any advice

    Hi James,
    Thank you for posting in Windows Server Forum.
    From Server 2012\R2 we normally have initial connections going to the broker and not to our RDSH server directly as previously for server 2008 R2. Yeah we can use DNS RR for your RDS environment but with DNS RR is that it is unaware if the server is online
    or offline while my load balancer is service aware. So in case of a problem with a connection broker the request will be redirected to the active connection broker thanks to my load balancer. DNS RR does not have this feature. So it’s good idea if you can
    use NLB or any 3rd party Load balancer for web and gateway services. You can refer
    this thread for information.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Server 2012 R2 RDS- Only want the Session Host, Connection Broker and Licensing Server!

    Hi all,
    Wondering if anyone has experience with implementing Remote Desktop Services (RDS) on Windows Server 2012 R2.
    I am doing an RDS design for a platform where we only need an RDS Session Host, Licensing Server and Connection Broker. We do not need web access as these servers will simply be jump boxes internally!
    However, implementing this correctly in our test environment has proved to be tricky. The options are:
    Use the Server Manager and do a traditional install via Roles and Features ( specifically add the Session Host, Licensing Server and Connection Broker). The installation process seems to go through ok in this scenario but when I head over to the Remote
    Desktop Services section of the Server Manager I simply get the message 'An RDS Deployment does not exist in the server pool. To create a deployment head to Roles and Features'.
    Use the specific ‘Remote Desktop Services installation’ option on the Server Manager and do a Session Based Desktop deployment and Quick Start. This installation process seems to go through correctly and the Remote Desktop Section seems to be working
    correctly via the Server Manager. However this process is ‘hard locked’ i.e. it installs the session host, web access and connection broker. I can then remove the web access component later from Roles/ Features.
    Is there a best practice (if any) for installation? i.e. Will there be any issues down the line if I remove RDS Web Access from my server while following method 2?
    There is a complete lack of documentation from Microsoft here so not sure what to do! Just need a basic RDS session based deployment.

    Hi,
    As I know from server 2012\R2 the best deployment skill is to perform via “Remote Desktop Services” installation mode with Standard deployment and don’t let single role to install. Because when we install through RDS mode, there are specific extra tools and
    services activated along with that deployment which you can’t find with single role installation. And that is for sure, when we install RDS role as of this, by default we will get install RDCB, RDSH and RDWA role installed.
    Sorry don’t have any option to try to remove that role as that role basically needed for RemoteApp and Desktop purpose. But if you want then you can try it with help of “Remove-RDServer”Powershell command.
    https://technet.microsoft.com/en-us/library/jj215506.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Server 2012 RDS - Remote Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL

    Seeing the error listed here.
    The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
    Pooled virtual desktop collection name: NULL
    Error: Error code: 0xFFFFFFFF.
    Broker and Hyper-V are on the same physical machine.
    Any ideas on where to start troubleshooting this?
    Used the happy wizard to create everything, and got no errors.
    I have created a small pool collection, and given rights to domain users. Everything "looks" good.

    I have the same problem.
    (Making this long hand for those who come after)
    I have installed SQl Management Studio Express 2012 SP1
    http://www.microsoft.com/en-us/download/details.aspx?id=29062 
    (You only need the one file "SQLManagementStudio_x64_ENU.exe")
    Ran this as Administrator 
    And typed in the Server Name field
    \\.\pipe\MICROSOFT##WID\tsql\query
    Then hit connect.
    Expanded Databases (+sign)
    Expanded RDCms 
    Expanded Tables
    Right Clicked on rds.target, select Edit top 200 rows
    Right Clicked and copied, then pasted this into a notepad file on the desktop (As a backup)
    Right Clicked and selected Delete to delete the row with the data in it (and PoolID was set to Null in this row)
    Did the same for rds.pool
    Manually added Remote Desktop server into the MEMBER OF tab of
    “Windows Authorization Access Group” via Active Directory Users and Computers. As this domain was Windows 2003 Native when the RDS server was first installed.
    Rebooted server and same issue>
    Checked SQL again and rows had come back.
    Is that what you meant by "delete
    the rds.target and rds.pool with pool id = NULL"?
    Not a SQL guru, so any help appreciated.

  • RDS 2012 R2 Connection broker in HA mode SQL mirroring issue

    Hi,
    I have an issue where our two brokers will not connect to the failover database when the database fails over.
    Our setup:
    Database - 2 x SQL 2012 Standard with the RDCB database mirrored in high safety with automatic failover mode. 
    Brokers/Web gateways - 2 x server duel role servers in different subnets. They're configured in HA mode
    I won't include the session hosts as it's out of scope for this issue.
    So the RD database connection string has been set to:
    DatabaseConnectionString : DRIVER=SQL Server Native Client 11.0;SERVER=server2\instance2,5555;Failover_Partner=server1\instance1,5555;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=RDCB
    So when this was first set, the DB was failed over and it worked. It was then failed back to the correct principal but now when failed over to the Failover_Partner it will not connect.
    I've confirmed the SQL permissions and custom port aren't an issue.
    Has anyone else experienced this issue?
    Stephen Turner

    Hi Stephen,
    Thank you for posting in Windows Server Forum.
    Did you receive any specific error\Event ID for your issue?
    Apart it seems there is some misconfiguration issue for failover cluster. If connections are empty, that means broker servers are not connecting to the mirror server database, most common problem is database security in mirror server. So check all brokers have
    full access to the mirror database and mirror database saved folder.
    For more information to recheck the steps you can go through following articles.
    Window server 2012 | Remote Desktop Connection Broker high available with SQL Server Mirror
    https://asithadesilva.wordpress.com/tag/remote-desktop-connection-broker-high-availability-with-sql-mirror/
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • RDS 2012 - unable to connect to SH via webgateway

    Dear all,
    we have setup a RDS 2012 system following this article;
    rds8-standard-3-node-remoteapp-deployment-on-windows-server-2012
    It all went ok as far is I could see but Im running into the following problem.
    If I use MSTSC to connect through the gateway directly things work, I get the desired SH desktop without a problem. (eg connect to SH001.domain.local using the web url for the gateway/webserver).
    If I go to the external website and try to setup a connection it goes into somekind of loop. It first gives me a security warning stating it wants to connect to the connection broker, then I get a certificate error from the connection broker, which is correct
    in this case, I choose to ignore the certificate warning and continue anyway. RDP then continues; Securing external connection, checking bandwith, starting the external connection. And there it hangs, it doesnt go any further and tries to connect for ever.
    The external adres of the gateway is xxx.xxxx.nl and internally it xxx.xxxx.local not sure if this could be related. I noticed an article with a powershell script that would change the .local into .nl
    Strange thing it worked before. I even went as far as  trashing all 3 machines, removing the roles and removing them from the domain to run the install again on fresh machines with new DNS names. Still no luck.
    Not sure on how to troubleshoot this any further. Eventlogs on the GW and CB show nothing special, no errors. One thing that I do notice is a recurring WMI 5605 ID - The root\cimv2\RDMS namespace is marked with the requiresEncryption flag. Access to this
    namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again.
    Thanks for any thoughts on this.
    Best regards,
    Louis

    HI,
    Can you confirm everything works internally and your problems occur when trying to access resources externally.
    Firstly check the certificates and ensure you have configured self signed or trusted.
    Try turning of certificate authentication for testing only - this will answer your authentication level question.
    Have a look at the following post:
    http://ryanmangansitblog.com/2013/03/10/configuring-rds-2012-certificates-and-sso/
    It does sound like you are experencing issues with the Internal and external nameing of the gateway. There are a few ways round this. TP has written a script which will assist with the change.
    http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80/file/103829/2/Set-RDPublishedName.ps1 If you have questions
    around the use of this, reply in this post.
    Ryan Mangan | Ryanmangansitblog.wordpress.com | Help keep the forums tidy, if this has helped please mark it as an answer

  • Change Connection broker DNS suffix

    Hi all,
    I have VDI infrastructure inside local domain. I want to change DNS suffixes of VMs and RD servers to external domain name and attach external wildcard certificate to connection.
    Everithing is OK with VMs but when I tried to change DNS suffix for Connection Broker Server I got following error in sever manager:
    The following servers in this deployment are not part of the server pool:
    1. <Old FQDN of server>
    The server must be added to the server pool.
    If  I add server with old FQDN in All Servers section by DNS search even if it cannot find anything then I can view RD deployment properties but I can't change RD Connection Broker name.
    How to correctly change RD server's DNS suffix?

    Hi Sergey,
    When you need to change the name of the broker in a non-HA RDS deployment, you essentially need to wipe and re-create the RDS deployment.  For example, remove all RDS servers from the deployment (except broker) , remove RDCB Role Service (which
    effectively wipes out the deployment), rename the broker server, create a new RDS deployment, then add all the other RDS servers back into the deployment.
    In many cases people do not want to rename their internal servers, so what you can do is change the published FQDN using the script below:
    Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
    https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    -TP

  • Relation between RD Connection broker and RD session host farm in 2012 R2

    Good Day
    I have configured standard RDS session based deployment recently on 2012 R2 servers
    Everything is working as expected
    The setup has TWO RD Session host, 1 Session Broker, one RD Web access and one RD Gateway
    I have created 2 DNS records named Rdsfarm.domain.com for my RDS1 and RDS2 session host servers and if I connect to this
    rdsfarm.domain.com with RDP from TS clients, i am able to connect to any one of TWO rds servers without any problem
    However some part is not clear to me
    I have not added rdsfarm.domain.com any where except my RD Gateway server RAP policy
    Also I have added my RD Broker server in RAP allowed group above.
    I don't see any config where this farm name is associated with my RD Broker server
    I have tried to connect to RD broker server from client, but it didn't redirect me to RD session host servers
    If I try to connect to my RDS servers with their FQDN , it gives me error that I must connect thru farm name
    Can you please help me to understand relation between RD session host servers farm and RD broker server ?
    Also I would like to know what exactly happens in background when user start RDP session by entering RDS farm name
    Note that RDS farm name is generic DNS Host(A) record pointing to my both RD session host servers
    I wanted to know is there any command or configuration I missed out as I don't see any config where Generic RD Session Host Farm name (DNS Host(A) record) is associated with my RD Broker server ?
    Thanks
    Best Regards
    Mahesh

    Hi,
    If you are opening Remote Desktop Connection and manually connecting to the broker then it will not work properly because you have no way of specifying the target collection in the user interface.  If manually using the RD Client to connect is a requirement
    what you can do is set the default collection in the RD Connection Broker server's registry.
    To specify the default collection, please create the registry setting below in the broker's registry:
    HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings
    DefaultTsvUrl     REG_SZ     tsv://vmresource.1.<VDI pool ID>
    To determine the correct value for DefaultTsvUrl please open RDWeb in a non-IE web browser and click on the icon for the collection you would like to be the default, then edit the downloaded rdp file with Notepad and copy the portion of the loadbalanceinfo
    setting that is similar to the above.
    An alternative would be to download the .rdp file from RD Web Access and double-click it to connect.
    As I mentioned above it is generally intended to have users connect via RD Web Access or RemoteApp and Desktop Connections feed or Remote Resources (uses the feed) so that the client will obtain the proper .rdp file from the server.
    To configure the FQDN that is published in the .rdp files you can use the cmdlet below:
    Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
    http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    Below is a sample configuration based on what you have written:
    1. Published FQDN (using cmdlet above):  rdsfarm.domain.com  --> points to ip address of RDCB server.  When launching a RemoteApp or Full Desktop connection from RD Web Access, the prompt window will show this FQDN next to Remote computer.
    2. Gateway FQDN:  gateway.domain.com --> externally points to public ip address of your RD Gateway server.  TCP port 443 and UDP port 3391 need to be forwarded to the RDG's internal ip address.  When launching a RemoteApp or Full Desktop
    connection from RD Web Access, the prompt window will show this FQDN next to Gateway server.  This FQDN is set in Server Manager -- RDS -- Overview -- Deployment Properties -- RD Gateway tab.
    In RD Gateway Manager -- Properties of RD RAP -- Network Resources tab you should select Allow user to connect to any network resource or define a RD Gateway-managed group that has all of the FQDNs that the user will need to connect to.
    3. RD Web Access FQDN:  remote.domain.com --> internally points to the ip address of your RDWeb server, externally points to the public ip address of your RDWeb server.  This is the name you give users if they want to use RD Web, for example,
    https://remote.domain.com/rdweb
    If you want users to manually connect using Remote Desktop Client as well as use RDWeb it will be a bit confusing to them since they will need to use one FQDN when manually using the client and a different FQDN when using RDWeb.  You could fix this
    by having them only use one method or run RDWeb directly on the RDCB server, that way users would only need to know a single FQDN for both RDWeb and manual connections.
    4. You should have a wildcard certificate with subject of *.domain.com set for all RDS purposes in Deployment Properties.
    Thanks.
    -TP

  • Server 2012 R2 Remote Desktop Connection Broker

    I have installed RDS on a server named PLUTO on which Windows 2012 R2 datacenter is in. There is a domain controller (domain name: AGROSY) running on a Linux server. We have used Samba 3.6.6 to control the file sharing system.
    When I attempt to install RDS in Server Manager, it states as following: could not retrieve the deployment information from RD connection broker server pluto.AGROSY.
    Then, I searched a lot of solutions, e.g.  and tried as following:
    Enter-PSSession -ComputerName pluto   --> which works;
    but Enter-PSSession -ComputerName pluto.AGROSY   --> which gives the error message as: Enter-PSSession : Connecting to remote server pluto.AGROSY failed with the following error message : WinRM cannot process the request. The following
    error with errorcode 0x80090311  occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.
    If I ping the pluto.AGROSY, it works as well.
    I have no idea how it can be solved, please help me out. Thanks a lot!

    Hi,
    Thanks for your comment. Sorry for late reply.
    Initially please enable the PowerShell remoting in your case. 
    Enable-PSRemoting
    http://technet.microsoft.com/en-us/library/hh849694.aspx
    For FQDN name, please see that RDCB is properly configured and also certificate which you have used for RDS environment must be trusted with its private key and must match the FQDN name of the server. Did you seen the certificate has been properly used and
    configured. You can go through following article for certificate and also for configuring RDCB role.
    Configuring RDS 2012 Certificates and SSO
    Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

Maybe you are looking for