Submit a request

Nerdio Help Center

Can RDS users automatically be assigned to an RDS server that is available?


Applies to: Nerdio for Azure (NFA)


Setting up a High Availability (HA) RDS architecture is a common request. A critical component of any RDS based virtual desktop architecture are the RDS session host servers. It is important to make sure that the RDS servers are redundant and uptime is as close to 100% as possible.

NFA Enterprise customers can take advantage of RDS Collections. With RDS Collections, the system will automatically assign additional RDS session hosts to the collection pool depending on workload, as determined by CPU threshold settings for the collection.

NFA Professional customers can take advantage of RDS clone-and-switch process. RDS session hosts in Nerdio are provisioned using Azure's managed disks. As a result, Microsoft Azure guarantees a 99.5% up-time for the RDS servers. If you are looking for additional redundancy, follow this clone-and-switch process:

I. Pre-setup

First, clone the RDS session host and keep it off to the side:

  1. Log in to Nerdio Admin Portal (NAP) and navigate to the Servers module.
  2. Locate the RDS session host server and click the Clone button.
    Settings4.PNG
  3. Once the cloned server has been provisioned, shut down the cloned server.

II. Switch users to cloned server when necessary

Should your primary RDS session host server become unavailable, you can activate the cloned RDS session host in place of the primary server:

  1. Log in to Nerdio Admin Portal (NAP) and navigate to the Servers module.
  2. Locate the cloned RDS session host server and click the Start button. Make sure the server starts successfully.
  3. Remote in to a publicly accessible server such as FS01.
    Settings1.PNG
  4. From FS01, remote in RDGW01.
    Settings2.PNG
  5. Open DNS Manager on RDGW01.
  6. Navigate to nerdio.net DNS zone, edit the RDSHXX.nerdio.net A record and change the FQDN of the server it points to so that it points to the cloned RDS session host.
    Settings3.PNG
  7. Refresh DNS (ipconfig /flushdns).

Remember to undo the changes once the primary server is back online.

 

Was this article helpful?
0 out of 0 found this helpful

Comments

Please sign in to leave a comment.