I just updated my RDWeb web client to version 1.0.18.0. The upgrade went smoothly, but I'm experiencing a strange issue. My RDweb is in a load-balanced cluster using NLB. When I connect through the NLB cluster, some of the text in the interface appears to use placeholder values as in this screenshot:
However, when I connect directly to one of the nodes, the text displays as expected.
Can anyone offer a suggestion to fix this?
Good day, can I use Windows Server CAL English 1pk DSP OEI 5Clt User CAL for my RDS?
Hi All,
How to continue use the remote desktop services manager, TSADMIN.msc in win2016 server OS ? Is there a alternative solution for this request ? Thanks.
Hi,
have a hard time right now. My setup is a Windows Server 2016 on a HP DL380p Gen8 Server with a Nvidia Quadro K4000 GPU. My goal was to create a VDI with user based Windows 10 Enterprise desktops my users can connect to with RemoteFX enabled.
Unfortunately I cant get it to work. As soon as I enable the RemoteFX GPU within the Hyper-V settings of any of the VM's I cant connect via RDP from another Windows 10 with MSTSC anymore.
- I get the user/password promt and enter both. (I now the authentication works because if I enter wrong credentials I get an password error)
- I see the "Remote Connection is being secured..." message and a second later the error message: "Your Remote Session has ended, possibly for one of these reasons:. The Administrator ended, the session Network Error...
BUT:
If I RDP into the Hyper-V Server (RDVSH) and open the Hyper-V Manager I can click on the same machines console and login - with RemoteFX enabled (as I can see within device manager "Microsoft RemoteFX Graphics Adapter WDDM...")
If I remove the GPU using Hyper-V Manager I can connect from the Windows 10 client with MSTSC to my VM Windows 10 just fine.
Other things I checked:
- Using Windows Server 2019 (same effect)
- clean non-domain windows 10 machine (same effect)
- MSTSC with the 10 MBit LAN option and not automatic detection (same effect)
We have deployed windows 2019 terminal servers and found that user were return to parent windows of defferent session when closing child window. For example,
Session 1: User logged in to the server using published application. Opens child window from the same session.
Session 2: Same User logged in to published application (which gives the same session on the server), launch the windows. Opens child windows.
Issue: when user closes child windows from session 2, it takes him to parent windows of session 1.
We never had this issue for windows 2008 terminal server session.
So is there any settings in the window server 2019 that should activate parent windows of the same session.
Thanks
Hi,
I'm running +10 Windows Server 2019 machine as virtual machines in Hyper-V.
I'm facing the issue that when logged on with RDC to these servers, that my keyboard and mouse frequently stop working on the remote machine, on the local machine all works normal.
Sometimes this is every couple minutes, sometimes it take 30-60 minutes.
Best solution so far is close the RDC connection and re-open the remote desktop. However sometimes the input is responding again after a minute or a couple of minutes.
I've tested with the task manager open on CPU screen, when the mouse/keyboard isn't responding, you can see that the task manager refresh the CPU screen as normal.
This is happening when logged on as administrator, and ALSO as client in my RDS Host.
Server: Windows Server 2019 Standard 1809, 8GB RAM, 4x CPU
Client: Windows 10 Pro 1903, RDC 15-Bit Color
I believe this is a bug in Windows, as i can't reproduce this behaviour when logged in from a Windows 7 client machine.
Do other users see similar situations?
Has someone found a solution for this?
I have a Server 2012R2 VM hosted on hyper-v.
I can manage the VM, but not the hyper-v.
I want to connect to the VM with RDP (from a windows 10 computer), and redirect a local USB (some license dongle). And I hoped remoteFX could do that.
HOW do I get remoteFX to work? I have trawled througt a lot of guides and blogs, without luck.
It seems that the VM, being 2012R2, does not require vGPU, and hence the hyper-v host does not need to be able to provide that. I cannot determine if the hyper-v host MUST have the RD Virtualization Server role installed or not (I hope not)
It seems that all it takes on server VM is to enable remoteFX/USB direction, and to install Desktop Experience.
And to disable "do not allow supported plug and play device redirection" on on the server" and enable "Allow RDP redirection of other supported RemoteFX USB devices from this computer.” on the client.
Yet, it seems not to work. Any help is appreciated.
/nikolaj
In the early morning and occasionally during the working day we are experiencing lots of 4 minute freezes in our Remote Desktop Session Hosts (Windows Server 2016) running in Azure. The servers are quite big as they are serving Windows 10 like general desktop sessions to 30+ users.
Only some of RDSH VMs are affected on each occasion. Different hosts on different occasions. One host may be hit twice in a single period. A period of freezes may be spread out up to an hour. There are more VMs affected in the early morning after they all power on than during the day.
I have a background script running on the VMs watching for Audio service hang ups and its logging indicates the 4 minute freezes involve the CPU pausing. Essentially if the CPU wasn't pausing the script would be logging a message after just 1 minute. My guess is the Azure Hyper-V hosts are automatically rebalancing on changes in load and to do so are migrating VMs between hosts. As our VMs use a lot of memory I believe the 4 minutes is mostly the time taken to copy the RAM contents to the other Hyper-V host.
Is this a reasonable conclusion? Are there other possible causes?
Has anyone managed to prevent their VMs from being moved?
Hi,
i am trying to find out if it is possible to add more remote desktop/terminal server licenses to a windows server, 2003 version. We currently have 2 licenses for the server, but are looking to increase this.
is it still possible to even buy more of these licenses for windows server 2003?
thanks
Hi all,
After the Collection Security settings on Windows Servers 2016 RDS, has been configured to -
Security Layer: RDP Security Layer,
Encryption Level: Client Compatible,
no check on "allow connections only from computer running..."
that changed was made in order to enable users to change their password when expired.
now users have to enter their password twice in order to login,
the GPO is configured with 'Always prompt for password upon connection‘ to disabled.
any ideas ?
thanks a lot!
Hi Everyone,
Im new to this forum and unfortunately i do not have enough experience to move past the issue that im currently facing.
To give you an overview on the current task at hand. I have a domain controller(2016) with RDS installed on one of the domain joined windows servers(2016). Basically to protect myself from any unexpected issues i have cloned the servers into an isolated environment to test on the renaming process before actually performing on production.
I have went through multiple articles and blogs on the process of renaming a domain name ie. ABC.local to ABZ.local.
The main issue is when the domain name is renamed(completed successfully), the RDS deployment breaks as it still detects the old server vm1.abc.local instead of the updated vm1.abz.local.
Most of the blogs available mention that it might be necessary to completely remove the roles and then re-add them back, however from my understanding it looks like the issue is primarily the server not updating its fqdn in the RDS deployment
I would really appreciate any advice on this matter and in the mean time i will continue to try and solve it.
Thank you.
Hi,
I have a win server 2016 standard (no cloud).
I can connect using rdp/wifi from windows 10 laptop.
A win ce terminal (unitech), connected on the same wifi, can not with the same credentials (ip, user, domain, password).
Any hint?
Alain Bourgeois
Hello all,
We have been transitioning some of our remote servers from 2012 R2 or 2016 to 2019 when we recently saw this issue. We have an application that is installed on the server and published as a RemoteApp for the users. When the application launches,
there is a Splash Screen that shows the version and information about the app while it is loading. As the Login dialog box for the app is opened, the Splash Screen is closed several seconds before it opens. The problem is that the Splash Screen is stuck on
the screen. If the Advanced RemoteFX setting in Group Policy is active, the screen will remain in full and if it is disabled, it will leave a Black Box in the exact location that the Splash Screen had been.
There is another thread about this in Terminal Services and there are no answers or responses since May (except what I have recently added). This is exactly what we are also seeing. (I cannot post the link as the system will not allow me)
Really do not want to have to pay Microsoft for an incident to get an answer as to why this is not working as it does in 2012 R2 and 2016 without any issues. The version of 2019 is Version 1809 Build 17763.652. For the Client PC, this happens with Windows 10 Version 1809 Build 17763.503 and Windows 7 Version 6.1 Build 7601 SP1.
Any help would be appreciated.
Thank you,
Stephen
Hi everyone,
we are currently having a RDS 2012 R2 deployment and want to switch to Azure App Proxy.
My idea was to deploy a second rdweb/gateway server and configure it with my poc group and then my pilot users.
I do not want to build a new RDS deployment from scratch to test if all my settings work.
Is this even possible? I only find HA configurations (which i do not want because it is a different config for each gateway server) or "It should work" posts.
Or is there an even better preferred way to migrate to Azure App Proxy with RDS?
<h3>Regards Stephan</h3>
Hi,
We have an issue with Remote Desktop Services on Windows Server 2016 servers (RD Virtualization Host).
There are personal unmanaged Windows 10 machines running on these servers.
When you log on the RD Web website it gives an error:
There are no available computers in the pool. Try connecting again, or contact your network administrator.
The user can login with mstsc onto their machine, but through the RD Web website doesn't work.
Normally the website works fine, but once in a while this issue happens.
This issue is fixed when we reboot the RD Website server.
There are no related errors in the eventlogs.
Anybody any idea?
Thanks,
My desktop is running Windows 10 v1803. My servers are running Windows Server 2016. All devices are connected through the same switch. All devices are patched, running the latest supported drivers and have the Windows Firewall disabled.
Ping latency is <1ms and file transfers are hitting gigabit speeds between Windows 10 and Server 2016.
I can successfully initiate an RDP connection (using MSTSC / no 3rd party software) from Windows 10 to Server 2016. However, the responsiveness of that connection is disturbingly sluggish. 1 mouse click takes 3-5 seconds to register.
In comparison, if I RDP between servers (2016 to 2016) I can stream YouTube smoothly This is not achievable from Windows 10.
Any ideas on what might be causing this behavior?
Hello colleagues,
I'm facing a weird scenario in which I'd like to set up a new Windows service that must use a specific domain account. This server is a Azure Server 2016 that acts as RD Session Host configured for User Profile Disks (UPD).
In other words, I have one RD Session Host and every time a user logs out, Windows unmounts the VHD and its profile disappears.
Then, I've configured a service with a specific domain account. However, its profile does not exist on C:\Users, due to the UPD feature. Consequently, when the service starts, it fires the eventid 1511 "Windows cannot find the local profile and is logging you on with a temporary profile".
Could you help me to find a workaround?
For me, the service can even use a temporary profile, but Windows never deletes them and flooding C:\Users with folders like "temp.001.002.003.nnn..."
Best
pf