Error: The remote session could not be established from remote desktop client WR_XxXXxXXX because its temporary license has expired. Event id 1028. User may be unable to launch app.

You may only see spinning wheel on user's machine when they attempt to launch an app and no error is displayed.
Log Name:      System
Source:        Microsoft-Windows-TerminalServices-RemoteConnectionManager
Date:          mm/dd/yyyy hr:mm:ss am/pm
Event ID:      1028
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:     Computer name.domain name
Description:
The remote session could not be established from remote desktop client WR_XXxxXXXXxxxXX because its license could not be renewed.

You would see following information in BrokerAgent trace:
       LaunchManager.ValidateConnection: Connection Protocol: ProtocolTypeIca, Session Key: 00000000-0000-0000-0000-000000000000
       ticket        <GUID>
       launch ref    <GUID>
       client h/w id <Hexadecimal>
       client addr   xxx.xxx.xxx.xxx
       client name   WR_XXxxXXXXxxxXX

Turned off "overrideIcaClientName" in web.config file. 

Follow the instruction give in this article:  https://support.citrix.com/article/CTX136271

Problem Cause

The “WR_XXxxXXXXxxxXX” name, is generated when using Receiver for Web to launch application. This is because JavaScript can’t get the real host computer name, in normal case this “WR_XXX” client name should be just used between StoreFront and Broker through NFuse. When client connects to VDA, it actually will use the real host computer name and send the information to VDA.

We can see client fills this “WR_XXX” name instead of the real host computer name and  this causes the failure before RDS session setup and later we see the application not launching.

The client name filed is filled with WR_XXxxXXXXxxxXX breaks the RDS rule for the client name length limitation for RDS

If we launch an app through Receiver for web, during ticket verification we will see below BrokerAgent trace:
      LaunchManager.ValidateConnection: Connection Protocol: ProtocolTypeIca, Session Key: 00000000-0000-0000-0000-000000000000
       ticket        <GUID>
      launch ref    <GUID>
      client h/w id <Hexadecinmal>
      client addr   xxx.xxx.xxx.xxx
      client name   <client machine name>

We will see the client name filed is the host computer name, this matches Microsoft’s RDS rule. However, looking at the non-working trace from customer’s environment, we will see below trace:
      LaunchManager.ValidateConnection: Connection Protocol: ProtocolTypeIca, Session Key: 00000000-0000-0000-0000-000000000000
      ticket        <GUID>
      launch ref    <GUID>
      client h/w id <Hexadecinmal>
      client addr   xxx.xxx.xxx.xxx
       client name   WR_XXxxXXXXxxxXX