Hello,


FYI, I am using windows server 2019 Eval version. we want to work out the setup before acquiring licenses from MS.

All windows machines(servers, windows-10) described below are deployed as VM's on Dell server with VMware esxi.

We have a lab where in we need to log on to Jump-Server (WINDOWS-SERVER-2019) using RDP.

from this Jump-Server, I need to log on to 

1. Windows-Server using RDP client on Jump-Server.
2. Windows-10 machine using RDP client on Jump-Server

I understand we must install RDP services in the Jump-Server & Windows server. 

--------

what I have at the moment is:

Jump-Server has services:

1. Domain Controller
2. RD Gateway
3. RD Web Access
4. RD Connection Broker
5. RD Session HOST

Windows-Server has services:

> RD Licensing
> RD Session HOST.

After configuring the Session based RDP, I'm able to get into Jump-Server.

But when I try RDP client (inside Jump-Server) to connect to Windows-Server. I get error message "An internal error has occurred"

Query-1: how to configure Session based RDS host on Jump-Server & Windows-Server, so that with same user could login to Windows-Server after getting into Jump-Server?

---------

Configure RDP for Windows-10 VM's:

Theoritically I understand, I should:
Add windows-10 vm into same domain
add this vm into RD Session Host. 

Query-2: is this correct or do we need extra device cal AND/OR USER cal to connect via RDP client from Jump-server above?

Thanks in Advance,

I am looking for best practises when it comes to RDS License Servers in a greenfield environment.

If you build two I assume you put your full license count on both servers and they run as active/active? Or would you have one powered down and power on if required?

IF the RDS License server (configured for Per User licensing) went offline,is there a period where users will continute to log in or they can't until the License Server is back online?

I enabled Keep alive through Group policy and applied it to the Windows Server 2008 R2. User is trying to connect to another Windows Server 2008 standard server from an RDP through Win2K8 R2 server. My question is can I apply these RDP policies on the client side(which is my Windows server 2008 R2), as many places I read that you can apply the same on the client side also. 

Even though in the Group Policy it says REMOTE SESSION HOST (Host being the server that the client is getting connected to).

I applied the policy on the client side that would do the same on the Server side. Is this wrong? I wanted to ensure that even though we are not aware about the other side the timeout is present, I thought applying on my end at least would keep the session from not disconnecting. 

Based on this I see that it says apply this policy, but it does not restrict only to Server but also the client that the RDP session gets connected.

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754272(v=ws.11)?redirectedfrom=MSDN

AA2913

Hi,

Just wanted to share some knowledge, regarding the use of RemoteApps with Windows 10 1903 clients.

We have for the past 200+ days, been in dialog with Microsoft, regarding RemoteApp lag. 

When using / moving RemoteApps around the screen, there would be an delay in moving. You can simply see the mouse is seconds ahead of the window, that is being dragged.

The issue is only present in RemoteApps, but works in  Full desktop mode, using the same RDS collection.

We tested this on the following platforms:

Clients:

Windows 10 - 1709 - Works

Windows 10 - 1803 - Works

Windows 10 - 1809 - Works

Windows 10 - 1903 - Dont work

RemoteApp Servers (RDSGW, RDSCB, RDSH):

Windows server 2012 R2 - works with all clients, except for Windows 10 1903.

Windows server 2016 - works with all clients, except for Windows 10 1903.

Windows server 2019 - works with all clients, except for Windows 10 1903.

Just like in Windows 10 1803, Microsoft had some severe issues with RemoteApp, but replacing the mstsc.exe and mstscax.dll files, from a build prior to 1803, fixed the issue. This is also true in the Windows 10 1903 build.

https://social.technet.microsoft.com/Forums/en-US/f3e9852b-393c-4aa0-9d2f-961a82cfc603/remoteapp-after-windows-10-update-1803-are-slow-and-right-mouse-button-is-not-responding-it-reacts?forum=winserverTS

After alot of frustrations, we figured the root cause - the mouse!

If using an high-end mouse like Razor, Steelseries or Logitech gaming mouses, then the issue is present.

When changing to a regular mouse, like an standard Dell or HP, the problem disappears instantly.

After this finding, Microsoft have choosen to close the case...

According to Microsoft its not Windows 10 1903 that is the root cause, but instead several large and independent mouse manufacturers (Logitech, Razor, Steelseries, etc), that is the root cause. But using the same mouse on other Windows 10 versions, works perfectly... Also if replacing the mstsc.exe and mstscax.dll in the 1903 build, using the files from 1809, works with the high-end mouses.

Hopefully someone find this post, before spending enormous amount of time tracking this down... :)

I upgraded my desktop to Win 10 from Win 7 and now I can not access any Microsoft Office products on it when connecting from another computer using Remote Desktop Connection.

All MS Office products like Word, Excel, Powerpoint, when started on the RDC server system, displays only a white frame on the RDC client system.

It is a problem with the newly upgraded Win 10 server computer, as connecting to it with RDC on a Win 10 computer and a Win 7 computer produces the same white frames.

Other applications like Adobe Photoshop display normally in the RDC remote session.  It is only microsoft office that shows a white frame.  

Going back to the server computer and logging in locally shows the (for example) window with Word in it displaying completely normally locally, but as a white frame remotely.

I have seen other people posting with this problem.

I have deleted the graphics drivers on the server system then restarted to reinstall them - no change.

Does anyone know why all of a sudden MS Office applications running on a win 10 system upgraded from win 7 just display a white frame when viewed through a remote desktop connection?

Hi,

we have a Windows Server 2019 Std running as an RDP server in the cloud. Since April we have the problem that the RDP sessions are often disconnected (session freezes, RDP ends automatically between 1-10x a day).

The connection to the data center is established via VPN. There are no problems with the VPN.RDP licenses are assigned to all users, and the server also has enough free resources.The TS has been restarted every night since the beginning of last week. According to user reports, the RDP abortions have become fewer.It does not always affect all users working on the terminal server at the same time.Users are connected from different locations or from the homeoffice and use Windows 10 or MacBook (yes, it also gets caught).On April 29th, 2020 I finally got an error message in the log:

(error message translated from german to english):

Faulting application name: svchost.exe_TermService, version: 10.0.17763.1, timestamp: 0xb900eeff

Name of the faulty module: rdpnano.dll, version: 1.0.1910.10003, time stamp: 0x5d9fb8b3

Exception code: 0xc0000005

Error offset: 0x000000000007a054

Faulting process id: 0x490

Faulting application start time: 0x01d61cfc9b512c4c

Faulting application path: C: \ Windows \ System32 \ svchost.exe

Faulting module path: C: \ Windows \ System32 \ rdpnano.dllReport ID: 6c0ddb81-d8e6-4f0e-932c-344fe1af1559

Full name of the faulty package:Application ID that is relative to the bad package:

I hope someone can help me

Hi, I'm using Windows 10 Pro RDS and I'm trying to access it over WAN. I've turned RDS on, opened the ports on the firewall, and port forwarded my router, but I'm still unable to access it from the internet. The thing is, I've tested and Remote Desktop works on LAN, but not when on WAN over the internet.

Any help appreciated 

Thanks

Hello all!

I am trying to install Remote Desktop Services (Roles: RD Connection, RD Session Host, RD Web Access) on Server 2019 that was previouse installed on the same server, where at the time it was on Server 2008 R2. This is a part of a server upgrade. Before upgrading the server I uninstalled the RDS roles then upgraded it from 2008t2 -> 2012 ->2012r2-> 2019. Up running the RDS deployment I am stuck at what is shown in the screen shot. I don't have a background in RDS so I have just been following guides and blogs but can't see me to find anything on this error. I am guessing there is a specific group policy that I need to create? 

In case you can't see it full, the error reads as follows:

Phil Balderos

I have a Hyper-V cluster running Server 2016 Datacenter version 1607

This cluster is running multiple VMs, including 6 RDS Host servers for users to access both internally and externally through RDGateway. Everything has been running fine since last Summer, but in the last could of days, one of the 6 RDS hosts has started to experience a typing lag. This lag occurs whether you connect via an RDP connection or even if you connect via a console session in Hyper-V Manager (without running an Enhanced session)

The lag only occurs after you log in - i.e. at the username/password field, typing appears instantly, but as soon as the users desktop appears, anything you type (notepad, word, etc, Start Menu-> Run), any typing appears on the screen very lowly, one character every (roughly) 1 second, no matter how fast you typed in. no characters are lost though.

This occurs whether you log on as a domain user or a local administrator.

All 6 RDS hosts are in the same OU and have the same GPOs applied.

No relevant changes have occurred, and no windows updates have been applied in the last month.

All other VMs and the host servers typing is normal. Only this one RDS Host.

Has anyone seen anything similar before?

Anyone got a fix?

Thanks

Ken Z

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

Hi guys,

I am just seeing if anyone has got this working.

I have a VDI environment that is working well, I have external user connect via a gateway to the VDI environment using RSA authentication. 

What I am having an issue with is MAC OS, system. I have downloaded the Microsoft RDP client and installed on Mac Systems. The machine can connect to the Gateway and Webserver. Then can authenticate with RSA and logon to the VDI environment. Yet when they download the RDP file it ends up just connecting to the Gateway host name. Not to the VDI environment. So it looks like the VDI gateway is not being configured on the Microsoft MAC RDP client. 

Has anyone got this working, or know who to get MAC connecting directly to the VDI Desktop through a VDI Gateway with RSA. Please note if I manually configure that gateway I can get this working but that does not use RSA 2FA. 

Thanks for your time in Advance 

Craig 

Craig G

Hi there

I am having a problem whereby a USB webcam works fine on my local machine but when i connect to my RDS 2016 it doesn't pick up the webcam. I have enabled it through the Remote desktop Connection applet and I have enabled RemoteFX through GPO but the Camera still doesn't get picked up. 

Can you suggest what else i can do?

Kind regards

George

Hello,

We have a problem with the bin of our UPD profils.

Our farm : 

DCS01 and DCS02 : active directory 

MGM01 : management of the RDS farm and SQL database for broker HA.

BRK01 and BRK02 : brokers

RDS01, 02,...07 : RDS hosts

FLS01 : data + upd location

Diagnostic : 
User connects to the farm.
Randomly, users can delete, or not, files on their desktop, download, ... They are prompted for admin credentials.

We saw that when they cannot delete, the bin is empty, and their icon on c:\users is a yellow folder. When they can delete, their icon is the beautiful little hard drive, and the bin contains the previous deleted files :


Test : 

Delete from other location outside UPD, like C:\test\test.txt : ok no problem,

Files are not in the public folder 

regedit - profillist (in case of temp profil) : no temp profil 

delete $recycle.bin in the upd 

delete c:\$recycle.bin on each RDSH servers

disable the GPO with "Hide these specified drives in My Computer" and with the prevent access on my test user 

restart all servers except DCs 

Delete the $recycle.bin in the UVHD-template

shift + del : it's ok, no prompt for admin credentials, but we lose the bin..

Currently, we have these rights on the $recycle.bin of the UPD

I tried to add aclcls c:\users\%username%\$recycle.bin /grant %username%:F 

But :
- when we have the problem (yellow folder icon), we can delete files without credentials prompt, 2 files are added in c:\users\%username%\$recycle.bin for each file deleted (see with dir command) but the bin on the desktop is still empty.
- when the session is ok (hard drive icon), we don't have the file deleted, previously with the problem, in the bin on desktop.

We tried too to mount the UPD on the FLS server, unassigned the letter, unmount the UPD.

We don't have more ideas. If you can help us please. 

I hope I have been understandable

Thanks 

<style></style><style></style><style></style><style></style>

Hello,

I need to have a better understanding of Microsoft VDI.

My objective is to have 500 connections to the virtual desktops I have created in my VDI Host server.

What do I need to accomplish it?

Can I assign like 5 users to 1 virtual desktop that I have created?

We have 2 Connection broker server in a HA Environment, suddenly one server stopped working and we are getting the below error when we tried to query in powershell

Get-RDServer : To configure the Remote Desktop management server for a high availability deployment, provide an active
Remote Desktop management server name for the RD Connection Broker server.
At line:1 char:1
+ Get-RDServer
+ ~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDServer

Any Thoughts will be greatly appreciated 

Regards Niroshan Ezra Paulsingh My Blog | http://exchange2010info.wordpress.com/

From this article I am trying to understand that you can enable the Keep Alive on the client side also is that correct? Can you set the Keep Alive Interval and other settings on the client side through the GROUP POLICY. 

Next, when it says REMOTE DESKTOP HOST in the group policy, does this mean both on the client side and the server side or just the SERVER site since people can misunderstand Host being the host server hosting the terminal services.

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/troubleshoot/rdp-client-disconnects-cannot-reconnect-same-session

After Remote Desktop client loses its connection to the remote desktop, the client can't immediately reconnect. The user receives one of the following error messages:

• The client couldn't connect to the terminal server because of a security error. Make sure you are signed in to the network, then try connecting again.
• Remote Desktop disconnected. Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.

When the Remote Desktop client reconnects, the RDSH server reconnects the client to a new session instead of the original session. However, when you check the RDSH server, it says that the original session is still active and didn't enter a disconnected state.

To work around this issue, you can enable the Configure keep-alive connection interval policy in the Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections group policy folder. If you enable this policy, you must enter a keep-alive interval. The keep-alive interval determines how often, in minutes, the server checks the session state.

AA2913

Hi Evryone,

what is difference between quick start and standard deployment on rds Services.

Best regards,

AHL

AHL1988

Hi,

I deliberately let my SSL certificate expire because I got a new wildcard one. The new certificate is installed in Certificates - Local Computer / Personal / Certificates. "certlm" reports certificate is "OK". It's been there for a while.

Today, my clients started getting certificate warnings. 

I found this "quick fix" link:

https://support.microsoft.com/en-us/help/3042780/remote-desktop-listener-certificate-configurations-in-windows-server-2

The "quick fix" does not work .. I assume I cannot select it because it's not a "pfx" file but the page doesn't mention this is a requirement. It implies I just need the certificate, which is a .crt file. How do I make it into as "pfx??"

I also tried the manual fix with this "wmic" command but got a Invalid Parameter command which the page says can happen if the certificate is not installed, but IT IS INSTALLED!!!

What undocumented (thanks Microsoft) aspect of this am I missing?

Thanks,

Jeff