Remote Desktop Services Primary and Secondary Failover

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #7659
    Avatardragon3303
    Member
    • Total Post: 5
    • Newbie

    Ok…I’m new to the whole thin client experience and am running into this issue. We’re using the T10 thin client, and have two servers set up with the Remote Desktop Services (formerly Terminal Services) role on each, and the thin clients connect up to remote desktop sessions great. Is there a way, in the thin client config to define one of the servers as primary and the other as secondary, and have the thin clients connect automatically to the other server if the one they’re on goes down? Or do we have to something like the remote desktop service connection broker in Windows or something similar. So far all we’ve been able to have them do is create an rdp connection to server 1, and another to server 2 and they then connect using one or the other. Ideally, we’d like to have the new connection initiated automatically if they’re connected to server one and it goes down, and not have the users have to initiate the new connection to server 2. Thanks for any info.

    #23295
    ConfGenConfGen
    Keymaster
    • Total Post: 9813
    • Jedi Master
    • ★★★★★★★

    Why not use a Network load balancer like the NLA from MS.

    CG

    #23298
    Avatardragon3303
    Member
    • Total Post: 5
    • Newbie

    Well, I was hoping it could be done on the thin clients themselves, because the servers that they’ll be connecting to for the remote desktop sessions are going to be moving into a domain at a customer site, and we’re not sure what type of settings are going to be in place as far as group policy, security, etc., and we don’t have control over anything except for the couple servers that we’re implementing for this project. I was thinking if we could handle it at the thin client level, that would make it as easy as possible for the operators of those thin clients, while also not complicating the server side of things if something were to go wrong in the future. If it can’t be done at the thin client level, then I guess it may be that we need to handle it through some sort of software once everything is implemented into the domain

    #23300
    Avatarslc71
    Participant
    • Total Post: 6
    • Newbie

    I have 2 RDP Servers with a Session Broker Server, it was fairly easy to setup and has been working just fine. Here is the link I used to set it up. The Broker server I just setup in a Virtual Machine. The broker server also holds the user logon profiles.

    http://technet.microsoft.com/en-us/library/cc772418%28v=ws.10%29.aspx

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.