none
Connection Broker only redirects to one entry in RRDNS cluster

    Pergunta

  • Hi all,

    Our Remote Desktop Gateways are configured to receive their remote apps from the connection broker.  On our connection broker ,in it's remote App sources in Remote Desktop Connection Manager there is "farm.local".

    Farm.local is a RRDNS entry comprised of 5 separate NLB Clusters, the TTL of Farm.Local is only 3 minutes.  Meaning the DNS entry should rotate every 3 minutes.  

    When people connect VIA the gateway, they get directed to one NLB cluster and the connection broker never rotates after that.  If I take farm.local out of the RemoteApp Sources in Remote Desktop Connection Manager on our connection broker, then re-add farm.local they are directed to a different NLB cluster.

    It seems Remote Desktop Connection Manager gets the initial IP that the RRDNS is currently on and never updates past that.  
    quinta-feira, 26 de setembro de 2013 21:50

Respostas

  • Hi All,

    I just thought I'd post a work around I created to overcome this issue.  I created a Powershell script that, removes the RRDNS cluster, then immediately re-adds the cluster back to the remote app sources.  Once I verified this performed in the way that I needed, I created a scheduled task to run the Powershell script which runs every 3 minutes.  This matches the TTL of the RRDNS entries.

    This is run on the connection broker.

    import-module RemoteDesktopServices

    remove-item RDS:\ConnectionBroker\RemoteAppSources\<farm_FQDN>

    new-item -Path RDS:\ConnectionBroker\RemoteAppSources -Name <farm_FQDN>



    • Marcado como Resposta Nathan Julsrud sexta-feira, 27 de setembro de 2013 16:54
    sexta-feira, 27 de setembro de 2013 16:53

Todas as Respostas

  • Hi All,

    I just thought I'd post a work around I created to overcome this issue.  I created a Powershell script that, removes the RRDNS cluster, then immediately re-adds the cluster back to the remote app sources.  Once I verified this performed in the way that I needed, I created a scheduled task to run the Powershell script which runs every 3 minutes.  This matches the TTL of the RRDNS entries.

    This is run on the connection broker.

    import-module RemoteDesktopServices

    remove-item RDS:\ConnectionBroker\RemoteAppSources\<farm_FQDN>

    new-item -Path RDS:\ConnectionBroker\RemoteAppSources -Name <farm_FQDN>



    • Marcado como Resposta Nathan Julsrud sexta-feira, 27 de setembro de 2013 16:54
    sexta-feira, 27 de setembro de 2013 16:53
  • Thanks for sharing the workaround. It is valuleable for other community members.

    Niki Han
    TechNet Community Support

    domingo, 29 de setembro de 2013 13:13