RDS Web Client RemoteApp Default Language always en-US

%3CLINGO-SUB%20id%3D%22lingo-sub-1295133%22%20slang%3D%22en-US%22%3ERDS%20Web%20Client%20RemoteApp%20Default%20Language%20always%20en-US%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1295133%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20deployed%20an%20RDS%202019%20Farm%20with%20the%20WebClient%20enabled%20-%20it%20works%20great%2C%20apart%20from%20one%20thing%3A%3CBR%20%2F%3EWe're%20en-GB%2C%20and%20the%20RemoteApps%20via%20the%20WebClient%20launch%20with%20en-US%20as%20the%20default%20and%20show%20the%20language%20bar.%20(Where%20you%20can%20switch%20to%20en-GB)%3CBR%20%2F%3EThis%20is%20a%20problem%20for%20Word%2FOutlook%20as%20the%20proofing%20language%20is%20incorrect%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EThe%20Session%20Hosts%20are%20all%20en-GB%20all%20the%20way%20through%2C%20with%20that%20set%20to%20copy%20to%20new%20profiles.%3C%2FP%3E%3CP%3EI've%20even%20removed%20the%20en-US%20pack%20via%20lpksetup.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20same%20RemoteApps%20launched%20via%20mstsc%20using%20the%20downloaded%20.rdp%20files%20are%20perfect%2C%20it%20only%20affects%20browser%20based%20launches%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20am%20missing%20here%3F!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303217%22%20slang%3D%22en-US%22%3ERe%3A%20RDS%20Web%20Client%20RemoteApp%20Default%20Language%20always%20en-US%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303217%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F615569%22%20target%3D%22_blank%22%3E%40ChrisH0701%3C%2FA%3E%26nbsp%3Bthere%20is%20a%20bug%20with%20the%20web%20client%20where%20we%20send%20a%20default%20keyboard%20layout%20(ENG%20US)%20when%20initiating%20the%20connection.%20We%20are%20actively%20working%20to%20resolve%20this%20issue%20and%20will%20push%20an%20update%20to%20the%20client%20as%20soon%20as%20possible.%20We%20will%20have%20a%20more%20definitive%20ETA%20soon.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20meantime%2C%20keyboard%20input%20should%20work%20as%20expected%20as%20the%20client%20sends%20Unicode%20input%20by%20default.%20Until%20this%20fix%20makes%20it%20to%20production%2C%20the%20proofing%20language%2C%20etc.%20will%20be%20an%20issue.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1304847%22%20slang%3D%22en-US%22%3ERe%3A%20RDS%20Web%20Client%20RemoteApp%20Default%20Language%20always%20en-US%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1304847%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F284352%22%20target%3D%22_blank%22%3E%40briantaintor%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20-%20I'd%20eventually%20figured%20out%20it%20must%20be%20something%20like%20that%2C%20and%20the%20keyboards%20are%20correct%20like%20you%20say%2C%20it's%20the%20proofing%20that%20doesn't%20work.%3CBR%20%2F%3EI've%20'fixed'%20it%20temporarily%20by%20setting%20the%20ignnoreremotekeyboardlayout%20key%20in%20on%20the%20session%20hosts%20which%20is%20forcing%20everyone%20to%20en-GB%20for%20now%2C%20but%20I'll%20revert%20this%20when%20the%20new%20client%20is%20released%20as%20I%20do%20have%20people%20who%20will%20want%20different%20regional%20settings.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20good%20to%20know%20it%20wasn't%20an%20issue%20of%20my%20creation!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1665137%22%20slang%3D%22en-US%22%3ERe%3A%20RDS%20Web%20Client%20RemoteApp%20Default%20Language%20always%20en-US%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1665137%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F284352%22%20target%3D%22_blank%22%3E%40briantaintor%3C%2FA%3E%26nbsp%3Bis%20there%20any%20update%20on%20this%20issue%3F%20We've%20been%20working%20on%20using%20the%20RD%20Web%20Client%20and%20have%20faced%20exactly%20the%20same%20issue.%20Ultimately%20we%20will%20potentially%20have%20multi-country%20or%20locale%20users%20that%20will%20want%20different%20regional%20and%2For%20keyboard%20layout(s).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20deployed%20the%20IgnoreRemoteKeyboardLayout%20fix%20as%20described%2C%20but%20just%20wanted%20some%20kind%20of%20timeframe%20as%20to%20when%20a%20fix%20for%20this%20is%20likely%20to%20be%20issued%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Just deployed an RDS 2019 Farm with the WebClient enabled - it works great, apart from one thing:
We're en-GB, and the RemoteApps via the WebClient launch with en-US as the default and show the language bar. (Where you can switch to en-GB)
This is a problem for Word/Outlook as the proofing language is incorrect

The Session Hosts are all en-GB all the way through, with that set to copy to new profiles.

I've even removed the en-US pack via lpksetup.

 

The same RemoteApps launched via mstsc using the downloaded .rdp files are perfect, it only affects browser based launches

 

What I am missing here?!

3 Replies

@ChrisH0701 there is a bug with the web client where we send a default keyboard layout (ENG US) when initiating the connection. We are actively working to resolve this issue and will push an update to the client as soon as possible. We will have a more definitive ETA soon. 

 

In the meantime, keyboard input should work as expected as the client sends Unicode input by default. Until this fix makes it to production, the proofing language, etc. will be an issue. 

@briantaintor 

Thanks - I'd eventually figured out it must be something like that, and the keyboards are correct like you say, it's the proofing that doesn't work.
I've 'fixed' it temporarily by setting the ignnoreremotekeyboardlayout key in on the session hosts which is forcing everyone to en-GB for now, but I'll revert this when the new client is released as I do have people who will want different regional settings.

 

But good to know it wasn't an issue of my creation!

 

 

@briantaintor is there any update on this issue? We've been working on using the RD Web Client and have faced exactly the same issue. Ultimately we will potentially have multi-country or locale users that will want different regional and/or keyboard layout(s).

 

I've deployed the IgnoreRemoteKeyboardLayout fix as described, but just wanted some kind of timeframe as to when a fix for this is likely to be issued?