Troubleshooting Azure Virtual Desktop RDS Feed Connection Issues

Steps to Resolve Azure Virtual Desktop RDS Feed Connection Issues

Question

In your company, the end-users access Azure virtual desktop from personal devices.

The support desk reports a significantly high number of calls because the users get trouble with connecting to their published RDS feed due to mistyped feed URLs.

Which of the following steps would you take?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Correct Answer: B

You should publish the feed URL for email discovery by creating a new TXT record with the host _msradc and the text rdweb.wvd.microsoft.com/api/arm/feeddiscovery.

Option A is incorrect.

Adding a CANME in DNS will not resolve the issue.

Option B is correct.

You need to set up email discovery by adding a new DNS record with properties host, text, and TTL.

Option C is incorrect.

You need to add a TXT record, not a AAA record in DNS.

Option D is incorrect.

Creating a new URL with a URL shortener is not the best solution to the given problem.

Option E is incorrect.

Creating a Host record in DNS is not the right solution.

To know more about how to Set up email discovery to subscribe to your RDS feed, please visit the below-given link:

In this scenario, end-users are having trouble connecting to their published RDS feed due to mistyped feed URLs, which is causing a high number of support desk calls. To resolve this issue, one of the following steps can be taken:

A. Add a CNAME record in DNS: This step involves creating a CNAME (Canonical Name) record in the DNS (Domain Name System). The CNAME record maps an alias name to a canonical (real) name. In this case, the CNAME record can be used to create an alias name for the RDS feed URL that is easier for end-users to remember and type correctly. For example, a CNAME record can be created for "rdsh.company.com" that points to the actual RDS feed URL.

B. Add a new TXT record in DNS: This step involves creating a new TXT (Text) record in the DNS. The TXT record can be used to provide additional information about the RDS feed URL, such as instructions for end-users on how to correctly type the URL. However, this step alone may not be effective in reducing the number of support desk calls.

C. Add a new AAA record in DNS: This step involves creating a new AAAA (IPv6 Address) record in the DNS. The AAAA record is used to map a hostname to an IPv6 address. However, this step is not relevant to resolving the issue of mistyped RDS feed URLs.

D. Create a new URL with a URL shortener: This step involves creating a new URL with a URL shortening service. However, this step may not be effective in reducing the number of support desk calls, as end-users may still mistype the shortened URL.

E. Create a Host record in DNS: This step involves creating a new Host (A) record in the DNS. The Host record maps a hostname to an IPv4 address. However, this step is not relevant to resolving the issue of mistyped RDS feed URLs.

Therefore, the most appropriate step to take to reduce the number of support desk calls would be to add a CNAME record in DNS.