The (third-party) SSL certificate on our RDS server expired. I replaced it with a new one (from same company with same server name). If I connect with a Remote Desktop Connection, and specify the server name and rd gateway, it connects fine. If I connect using the web client, when I select the application to run (after logging in) it says,

Oops, we couldn't connect to "application"

Your session ended because an unexpected server authentication certificate was received from the remote PC. Ask your admin or tech support for help.

Certificate information:
Server Name: CN= name.domain.local
Certificate thumbprint (SHA1):
<hex number string>

Does anyone know what i can check to fix this?

have a new deployment of server 2019 terminal services.  We are sharing just the applications, not the full vdi, also i have the session host and the gateway/broker as two separate virtual machines using hyper-v.  The session host is using a direct attached graphics card.  The gateway/broker is configured w/ two nics, one internal, and the other in a DMZ.  The session host just has the one internal nic.  

The issues is that when i connect from my internal network, that is when the performance is awful.  The best i can describe it is that it's lagging behind.  For example the calculator app, after i move the mouse over it and click some numbers, over the course of the next 30 seconds i can see just where i moved my mouse all over the app and click the numbers.  Also when i move the app's windows it moves about 30 seconds after i move it.  However if i remote in from the outside world it works perfect.  Hardware performance is not getting taxed at all, it feels very much like a connection thing.  I had meraki verify that all the traffic was staying local on that switch, and the there was no lag coming from the switch, but he did note that he felt there was an excessive amount of udp traffic given the task at hand. 

Any idea's on where else i could even look to trouble shoot this, or better yet a solution>?

many thanks! 

IT guy

QUESTION 1: I setup a Server 2019 single server that serves RD connections. Purchased per DEVICE RD CAL's, more than 3 remote connections work but the RD Licensing Manager does not show the licenses as ISSUED. I know if it is setup as per USER that the counter will not change by design but I have everything set to per DEVICE as I am only using a WORKGROUP and not a DOMAIN.

I followed these directions: https://support.microsoft.com/en-sg/help/2833839/guidelines-for-installing-the-remote-desktop-session-host-role-service

RD Licensing Diagnoser doesn't show any issues. It shows licensing type as per DEVICE

Server 2019 is activated and Online

I tried to upload screenshots but Microsoft says I can't do this until my account is verified. Checked my email but nothing to verify was sent. ???

QUESTION 2: Another peculiarity is on the welcome screen, all I see is OTHER USER and I have to manually type in the username and password of a particular user. I went through all the local security and group policy settings as described elsewhere and everything is defaulted to show usernames. I'm stumped. This behavior only changed after installing the RD Session Host and RD Licensing Manager after reboot.

Much Appreciated during these trying times.

Hi all,

I get the following error when trying to activate an RDS Licensing server.

The specifications...

• Brand new Windows Server 2019 Standard VM
• Domain joined
• Server Activated with MAK key via telephone method as this environment is not allowed to get general internet.
• Proxy configured to allow server access to https://clearinghouse.one.microsoft.com

The error...

I can't find any event logs that correspond to this error message popping up? The only thing I can think is wrong here is the proxy config and or I am missing additional URLs required for successful RDS licensing loading / activation tasks?

P.S> I am also correct in believing I can have many RDS licensing servers in many networks so long as I do not exceed my enterprise agreement RDS user CAL limit as assigned to my agreement?

E.G. when you activate an RDS License server it asks you how many CALS do you want to load into the server...

Thanks in advance...

durrie.

Hello,

for my Windows Server 2016 I installed RDS via Server Manager, roles based installation. The server is deactivated, but still without a license, I first use the grace period. The Windows Server 2016 is used as a workgroup server, Active Directory  is not installed.

At the Local Group Policy Editor I  set  "Use the specified Remote Desktop license server" and the "Set the Remote Desktop licensing mode".



But the RD Licensing Diagnoser indicates an error.

What is missing?

Thanks,

Ottilie

Hi,

This is my first post here and I'm also doing my first Powershell script.

Small background to the project. As everyone knows COVID-19 is spreading around the globe and we are suggested to work from home. With this my manger asked me if I could do a dashboard for VPN users. Which I've done in python and php.

But we also have a couple of Direct Access servers which I would like to monitor aswell.

I've found the following cmdlet which does what I want Get-RemoteAccessConnectionthe question I have now is. What privledges does require for me to run this command on a remote server.

I want to set up a Service Account that only have read rights to get the remote access information.

Best Regards,

Robin

Hi!

I've installed a Remote Desktop Gateway on Windows Server 2016, it worked perfectly last week. Today some users are having issues trying to connect to their workstations through RDG, but when they try to connect rdp directly (connected to the VPN) it works, and then became available and starts to work trough RDG again. 

Any ideas? 

Thanks!

Hi,

We are using windows service 2019 with RDS CAL 2019. The session host is windows server 2016. This microsoft page shows Windows Server 2016 session host can use RDS CAL 2019. After RDS license server setup and license imported. Notice the windows server 2016 session host check out the license, however the available number under 2019 doesn't get count down shown as below. Should I see available 9 because one is issued out? Is there something configured wrong?

Appreciate someone can help.

Jun



We have OpenGL application working on a server computer.  If later we connect via RDP to this server, OpenGL application continues to function without any problems. Obviously RDP just transfers image from server to remote computer.

If we start the same OpenGL application on the same server from RDP session, it runs OpenGL not on server but on the remote computer. Application crashes on operations that require OpenGL 2.0 or higher.

Is there any way to force RDP to run OpenGL code always on server no matter how it was started, directly on server or from remote computer?

Hey Guys,

I have a RDS Broker HA setup and wanted to upgrade the first broker to Server 2019. 
I removed the broker from the farm. Maybe i didnt have to do that, but i saw an article telling me to remove the broker from the farm in order to maintain availability to the RDS environment. So i did.
Once removed i upgraded the server to Server 2019. Now, when i try to readd the server to the farm i get a failure message saying "The list of joined servers could not be retrieved on server <servername of 2019>. Priviledge not held".

I wonder what priviledge its talking about? 
Did i brake the setup with the removal of the broker from the farm? I know, once broken, i have to rebuild everything. Is that the case?

Hi,

I am accessing to company VPN to work from home and I need to remote to a desktop in the company before I could rdweb to a application.I am unable to see the USB device through this method even if I enabled smart card in rdp or using mstsc /admin or mstsc / console.

summary

1 - VPN to the company network
2 - rdp to the specific company desktop
3 - launched the rdweb
4 - clicked on the URL that application which needs the USB for authentication 
however, even if at pt2 when I checked it also did not detect the usb

Need any advise on how I can detect the USB device

many tks

Hi,

we're facing the following issue while trying to add new Remote Desktop Session Hosts into
a session host collection  : "Unable to retrieve the session collection properties".

The server can be added into the deployment but can't be added into the session host collection and the message above
is returned. This error never happened before and is ennoying as we need to deploy more Servers/Collections.

A collegue noticed that adding a couple of servers at once (from the GUI) succeeded ...
I can't find anything related on EventViewer (Brokers / DataBase server)

Is this a known bug ? I can't find anything related on Microsoft support.microsoft.com
Any help would be much appreciated, Thanks.

MCTS Windows Server Virtualization, Configuration

I have a RDS server in domain installed with Licensing role as well (RDSH and Licensing role on same server) with Per User CAL installed.
Licensing report revealed that multiple CAL's allocate to single domain user.
Total 2 CAL's against one user name - one of yesterday and two of today with same time.

I can see he only running one session as per "quser"

Domain User account is not modified like user account is not recreated or renamed.

I could not find reasons or clue how this can happen with Per User CAL's

Appreciate if someone can shed some light or what next I can do to avoid it.

Hi There

Hoping you can help

I have a remote desktop services 2016 farm which consists of a broker, gateway and several rds session hosts, when staff connect to a session there audio and recording audio is fine but when they connect to the HTML5 version the audio recording sources are empty, am i missing something, is this no supported in the HTML5 version

I am in the process of standing up an RDS 2019 environment along side our RDS 2016 environment. 2016 environment was thrown together in a hurry a couple years ago and I figured this would be a good chance to stand a new one up done halfway properly. No issues on the old environment, what few published RemoteApps are there work ok.

However, on the 2019 environment I seem to have issues connecting with my Surface Book 2.

Scenario:

GW01 - RD Gateway
WEB01 - RD Web
CB01 - RD Broker
LS01 - RD Licensing
SH01 - RD Session Host running Wordpad RemoteApp to test

Client:
Surface Book 2
Windows 10 Enterprise
3000x2000 with 200% scaling
2 x 1920x1080 monitors connected via Surface Dock

This client connected to our RDS 2016 farm does not have any issues running a RemoteApp. If I attempt to run the test Wordpad on the 2019 setup I get the following message:

Here are the scenarios I have tried:

On dock with external monitors with W10 scaling at 200%: Fails with error above

Off the dock with no external monitors but native resolution scaled to 200% - works

On the dock with native resolution scaled to 100% - works

The first scenario is going to be the most common use for me. This is really a niche issue at the moment since I am one of a few that are using a Surface device with a high resolution display. However we continue to roll out other Surface devices and laptop brands with high resolution screens so I could see this being more problematic down the line.

I haven't been able to find another reference to this error thru my Google searches so far. As long as scaling is the same across all monitors it appears to work ok but in this mixed scaling setup, the 2019 session host fights back where the 2016 session host appears to handle it with no issue.

Hi

I have RDS cluster on Windows 2016 Server and use User Profile Disk. Today when users login on one server when press start button menu start don't show myself. When logout this person and person log myself on different server menu start work correct. Person use this same User Profile Disk. This situation is for all users on this one server. Not was installed any updates.

Hello all,

We've been having an issue lately with a specific app we use over RemoteApp - it's essentially a program built inside of FileMaker.
When people launch the RemoteApp, the FileMaker client can sometimes take 10-15 seconds before it actually shows any GUI (but the process launches immediately). When running as a full Remote Session, or directly on the server, this is no problem. However, it seems when that GUI doesn't show fast enough, the RemoteApp Connection Times out (The icon in the System Tray that shows we're connected to a Remote App Session disappears as well). If they relaunch the RemoteApp (via the RDP file), the process is already running since the user session was just disconnected and not logged off, and the app is fine.

It's not really too much of an issue, but obviously it does cause some frustration with users. I've been searching for an answer, but I can't seem to find one. Is there a configurable timeout for the RemoteApps that I can set?

This is in a Domain Environment.
All the client machines are running Windows 10 Pro. Servers are running 2016 Standard in a Hyper-V environment.
The app is FileMaker Pro 17 Advanced.

Any thoughts?

Can't figure out why login through RDS Gateway is so slow...

I've setup a 2019 RDS environment.

It's all VM's
Server: Connection Broker and License Server
Server: Session Host (Server 2019)
Server: Gateway (in DMZ)

Using FSLogix.
MFA plugin through Azure.

When logging in from inside network it's fast. (Not asking for MFA)
When logging in from outside through gateway, it takes 1:40 minutes before desktop is ready. (Asking for MFA)

Using a RDP file.
MFA challenge comes ~11 seconds after password is entered.
After that: "Configuring remote session" in a long time.
Occasionally the login is way faster.
(after I wrote this, the MFA challenge took 4 seconds and was 100% logged in in about 10 seconds through gateway)

I can't see where to begin troubleshooting...

Sometimes the connection is lost, asking the MFA challenge again.
Tried using "Negotiate" and  "RDP Security Layer"

Tried looking Event Viewer on several servers with no luck

Sorry for the jumping in text.

Hello,

We have a new Server 2016 Remote Desktop environment set up (1 broker + 2 TS's).
We installed 50 RDS CALs (per user).

At first none of the CALs were being issued, but the remote desktop connections work fine nonetheless (published apps).
License configuration + License Diagnostics say everything is OK.

So we removed the licenses, reinitialized the database, reinstalled the licenses, reactivated license server.
After that we noticed that about 10% of the connections made had a corresponding CAL issued.
I have no idea why some are issued and most are not. The users for whom the CAL was issued are spread across both TS's.
Eventviewer shows nothing out of the ordinary regarding RDS licensing. License config + diagnostics still say everything is OK.

It also turns out that the grace period is still active when we check through WMI : 110 days left (10 days past since reactivating the licenses).

Any ideas on where to look next ? Thank you.

I have two nodes that I am trying to set up a virtual machine-based deployment with.

Node1 has RDCB, RDGW, RDWA, RDVH all installed properly, and seem to work as expected.

Node2 has only RDVH installed, and it is not working correctly.

From Node2, in Server Manager under Remote Desktop Services, I get the error:  

The server pool does not match the RD Connection Brokers that are in it. Errors:
1. Cannot connect to any of the specified RD Connection Broker servers. Ensure at least one server is available and that the Remote Desktop Management (rdms), RD Connection Broker (tssdis), or RemoteApp and Desktop Connection (tscpubrpc) services are running.

Node1 (which hosts the RDCB) is online, and all of the three services above are running on it.

I can ping Node1 from Node2 and vice versa.

Node2 is apart of the server pool on Node1 and vice versa. I even removed them and re-added them.

I followed threads suggesting to open the RDCms database in SQL Management Studio, bring it offline and then back online, but this makes no difference (probably because RDCms was not in a recovery or pending state in the first place for me).

Uninstalling RDVH and re-installing RDVH directly onto Node2 makes no difference.

Uninstalling RDVH and re-installing RDVH through "Add RD Virtualization Host Servers" under Deployment Overview on Node1 fails with this error in Event Viewer under Microsoft-Windows-Rdms-UI/Admin :

Event ID 4119

RD Virtualization Host Configuration Failed on <server-name> With Error: At least one of the required services is not running on the server <server-name>.

Searching this event ID pretty much only brings up results about firewall blockages. I have no firewall set up, and so this is not the issue. I found absolutely no results online about not having a required service.

On Node2, I have the following services installed and running:

- Remote Desktop Configuration

- Remote Desktop Services

- Remote Desktop Services UserMode Port Redirector

- Remote Desktop Virtualization Host Agent

What service am I missing? Is it Remote Desktop Management (rdms)? How do I go about installing it? And why was it not already installed?

Both these servers have just gone though fresh OS installations, are fully updated, and have identical OS specs. 

I have removed/installed/rebooted both servers countless times to try to get a proper RDVH installation on Node2.

It makes no sense as to why this wouldn't be working out of the box.