Azure Virtual Desktop - .rdpw file expires - Error Code: 0x1608

Question

Hello,
4 months ago I downloaded a .rdpw file from https://client.wvd.microsoft.com/arm/webclient/v2/index.html
and distributed the file to all user like a standard old rdp file.

What I didnt know back then that the file expires after around 4 Months.

The following error message appears when I try to connect with the file:

[Window Title] Remote Desktop

[Content] The connection has been blocked because the certificate in the connection information has expired. Please either update your workspace or contact support for assistance.

[^] Hide Details [OK]

[Expanded Information] Error Code: 0x1608 Extended Error Code: 0x0 Timestamp (UTC): 2023-09-18T05:27:20.543Z Activity ID: 00000000-0000-0000-0000-000000000000

I dont want to distribute the file every 4 months.

How can I fix this?
Can I set a time limit to the file ?
Do I really have to replace the file every 4 months.

There has to be a way that the users can keep the connection file that doesnt expire.

Thanks for your help!

Answer 1

Hello Leonard Schwenk

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

The error message you are seeing is related to the certificate in the .rdpw file that has expired. Unfortunately, there is no way to set a time limit to the file or prevent the certificate from expiring.

However, there are a few options you can consider to avoid having to distribute a new .rdpw file every 4 months:

Use Azure AD Application Proxy: You can use Azure AD Application Proxy to publish the Remote Desktop web client and allow users to access it through a secure URL. This way, you can avoid distributing the .rdpw file altogether.

Use Azure Virtual Desktop feed URL: You can use the Azure Virtual Desktop feed URL to distribute the Remote Desktop web client to your users. This URL is unique to your Azure Virtual Desktop deployment and does not expire. You can find the feed URL in the Azure portal under the "Overview" section of your Azure Virtual Desktop deployment.

Use PowerShell to automate the distribution of new .rdpw files: You can use PowerShell to automate the process of distributing new .rdpw files to your users every 4 months. This way, you can avoid having to manually distribute the files.

I hope this helps!

Answer 2

Even in my environment facing the same issue. Since client wanted to use Offline package from user machines, we are getting this type of challenges.

I don't know what MS is doing to fix this type of issues.

Answer 3

I reached out to support and they confirmed with me that it's not supported and suggested a feature request idea be submitted. Here it is: https://feedback.azure.com/d365community/idea/762c86b5-68fe-ee11-a73c-0022485313bb