I have a new PC and Laptop both running Windows 10 PRO and have used Remote Desktop for years. I can connect using my Laptop to my Desktop but get a BLACK SCREEN when I do and have not Control.
Read lots of info, tried lots of stuff. Still no where. Even tried Microsoft Support, there was NO support.
Hello everyone,
I am tring to setup RDG with MFA on Windows 2016. I have followed countless instructions and cannot seem to get the NPS part work. I can log int the remote desktop without issue however it never authenticateswith Azure. When I look that the logs for NPS I see absolutley nothing, when I check the logs for the NPS extension its the same nothing. I just cant figure out what part I am doing wrong and there be nothing in the logs. Let me know if anyoe has some suggestions.
Hi guys,
I have Windows Server 2019 with Remote Desktop Gateway role and multiple servers with Remote Desktop Session Host role.
The issue is that sporadically users that are connected to some RDSH servers get disconnected. It doesn't happen on all RDSH servers but just few of them at the same time. For example out of 60 RDHS servers only 5-6 servers can be affected at the same time. Once it happens users can't re-connect in approximately the next 5 minutes.
I can't find anything neither in RDG logs not in RDSH logs.
What might be the reason of that?
I use RDP to connect to a Server12. It will work fine from the Win 7 Ultimate computer I use. I am setting up a Win 10Pro Enterprise computer (using the same hardware except for larger SSD hard drive). I am unable to connect from the new Win 10 setup, Hyper-V virtual Win 7pro, another Win 7Pro on my network , my Win 12 server or an Android app. I have disabled the Sophos UTM firewall on the remote system to test. I cannot find an error message in the event logs for any of the systems. The remote server does log"Listener RDP-Tcp received a connection" but nothing after that. If I use the incorrect credentials I get an authentication error but I don't see it logged. I have installed a new self signed cert. I am using a non-standard port but I use the same on my Server 12 and can remote in from anywhere. I have noticed that in the Sophos firewall log that the good connection results in first a TCP connection then a UDP. The incomplete connections do not have a UDP connection.
Any help would be appreciated.
Following testing scenario:
- All in one RDS Server (Broker, Host, Licensing and WebAccess)
- Two identical ThinClients with two connected USB audio devices (Lync Phone Edition and USB-Soundcard) - UserA and UserB
- RemoteFX USB redirection enabled
- no GPOs except RemoteFX are set for testing purposes
So if the first UserA logs in, everything seems fine. RemoteFX devices are redirected and both audio devices are set as default (soundcard as default audio and LPE as default communication device) After UserB logs in, his devices are also redirected and set as default - no problems at all. But at the same time as UserB logs in, the default Audiodevices of UserA are unset. If i set the default audio devices manually for UserA, they are unset for UserB.
I have made the same testing on Server 2016 - no such Problems.
We had the same scenario running in productive enviroment on Server 2012R2 for about 5 years, this issue didnt occure.
We have customers using Remote Desktop to log into a Windows 2019 Server running on AWS. Our EXE app starts up and runs just fine and uses DirectX for graphics and sound. But when customers close and reopen the Remote Desktop our app can no longer create DirectX surfaces. Here is the code that fails:
ZeroMemory(&ddsdCur, sizeint(ddsdCur));
ddsdCur.dwSize = sizeint(ddsdCur);
ddsdCur.dwFlags = DDSD_CAPS;
ddsdCur.ddsCaps.dwCaps = DDSCAPS_PRIMARYSURFACE;
res = IDirectDraw_CreateSurface((LPDIRECTDRAW)pdd, &ddsdCur, (LPDIRECTDRAWSURFACE *)&pddsback, NULL);
if (res != DD_OK) fatalerror();
The result code (res) is DDERR_UNSUPPORTEDMODE -- The display is currently in an unsupported mode
We have discovered if we check the new Windows 10 option to "disable full screen optimizations" then everything works as expected. The customers can open and close the Remote Desktop and the app is still there running fine. My questions is this: is there something we can do to be more compatible with full screen optimizations? We don't want to have all customers set this flag. What can we do to be compatible?
Thanks in advance
Hello,
We have a 2012 r2 server running RDS publishing a number of RemoteApps.
When we go to the Server Manager and drill down to the Remote Desktop Services area we are seeing a number of the sections that will not display their information and we can no longer manage RDS via Server Manager.
Starting at Server Manager\Remote Desktop Services\Overview the "Deployment Servers" window shows a red banner with "Could not refresh the list of servers"
Going to the Server Manager\Remote Desktop Services\Collections, all three of the windows, Collections, Host Servers, and Connections will eventually display the similar type of error message, stating to check the status of the services for Remove Desktop Connection, Windows Remote Management and Windows Internal Database.
The server is fully patched, event logs don't show anything of note.
We've rebooted the server and confirmed all those services and all "Remote Desktop *" services are running.
We're still able to access the RDWeb instance to use the published applications.
This had been working previously, not sure when it last was though as we don't always go into Server manager. We can manage the remoteapps via powershell, but are curious why Server Manager no longer functions.
Any assistance would be greatly appreciated.
thanks...
I am having issues with domain-joined client computers connecting to a RemoteApp or Remote Desktop session via the internet. I have the feed set up so that the shortcuts appear in a start menu folder. When the client (Win 10 or 8.1) is on our internal network, the shortcuts to RemoteApps and Desktops work immediately without the user being challenged for credentials. However, when connecting from the internet, the user is challenged for credentials. External access is via a Windows Server 2012 R2 machine running the Web Application Proxy role. The RD web interface is published via the web application proxy using pass-though. The gateway, web access and broker roles are all installed on the same Server 2016 Standard box. There are 2 distinct problems when clients try to connect externally:
1) On Win 8.1 the client can enter their credentials and connect. We want them to not be prompted - the user experience should be the same both within the internal network and externally.
2) On Windows 10, the client enters their credentials, which are then rejected - the user cannot access the RemoteApp or desktop externally, the credentials dialogue box simply opens again.
I have implemented group policies on the clients to enable caching of credentials and automatic pass through authentication. These policies include: "Allow delegating default credentials" for our terminal servers the "Set RD Gateway authentication method" policy set to "Use locally logged-on credentials".
I can't see anything logged on the broker/gateway to indicate why auth is failing on the Win 10 clients, either in the Security logs or the Remote Desktop specific Applications and Services Logs. Is there something I can enable to log and audit this information and help get to the bottom of this?
Thanks in advance!
Matt Nock
Hi,
We have a Remote desktop license server (Server 2016) and installed "RDS per user cals license".
We had a lot of user making use of this license so we deleted the C:\Windows\System32\lserver to rebuild the database. It all looked good but now only "new" (that never connected to the RDSH) users are issued a license and "old" users (that had a license issued before deleting the license folder) are not issued a license, they still can make contact to the RDSH
I cannot find any error on this (configuration and eventviewers are good according Microsoft) Is there any way to fix this?
Allready rebuild the database with the wizard (RD license manager) but this doesn't fix the problem
Thanks!
I have a hyper-v server with two server 2012 vm's
I can RDP to one VM on Win 7 client , but not the other VM.
I tried RDP from one VM to the other VM (which I can't connect to from Win 7). Error about Oracle ccpsd....
So I unchecked the Require Network Level Auth on the VM which I couldn't connect to with Win 7 client. Now I can RDP to the VM.
So, why can I connect to one VM with NLA [x] checked, but not able to connect to the other VM, unless I uncheck NLA?
Thinking of re-creating the vm...
Hello,
Does anyone know how to install Yammer notifier on RDS W2K12 R2 for all users?
Tried some things but its not working. Normal Yammer installation and the MSI both are not working in RDS.
Any help will be appreciated.
LEVD
Hi All,
As the title say, i deleted the Remote Desktop certificate store in "Cert:\LocalMachine\Remote Desktop\", How to re-generate or re-create this certificate auto-generate?.
EDIT:
For more detail, i followed this manual:
https://social.technet.microsoft.com/wiki/contents/articles/36151.renew-the-rdp-self-signed-certificate.aspx
When I stop and start the "Remote Desktop Configuration" service, In the Event Viewer appear this message: "The Terminal Server has failed to create a new self signed certificate yo be used for Terminal Server authentication on SSL connections. The relevat status core was Object alredy exists."
Thanks a lot.
Hello,
What would be the recommended hardware specs & Internet bandwidth for 400 concurrent users using RDS? If it is possible, it would be most helpful if there will be computation (supporting link for the steps etc.).
Thank you,
rolaine
Hi everyone, I'm pulling my hair out on this one...
In short, I easily got USB redirection working on our Win10 Workstations, but can't get it to work at all on Windows server 2016.
Set up:
- All workstations are on Windows 10.
- Servers are on Windows server 2016, we have bare metal boxes, and some VMware hosted servers as well (same behavior). Some are still on trial license, some on full fledged license.
- All Group Policies are set via Active Directory Domain Controller, and are the same for workstations and servers.
So I did all the recommended stuff:
- Enabled remoteFX for clients and hosts. (admins and users)
- Allowed all hardware.
- Enabled encoding for win 2008R2 (I'll remove this one since we dont have any win2008.)
- Do not allow supported P&P device redirection: Disabled.
- Running remote desktop client as admin.
- Enabling local devices and selecting the wanted device (usb joystick in our case).
That works great when connecting from a win10 workstations to a win10 workstation. We see the little computer in the RD title bar, the joystick redirection works, we can unplug the device, plug it back and get it working again.
When connecting to a windows server 2016 (bare metal, VM, trial or full license) the remoteFX computer icon doesn't even show up in the title bar. Again, the Group Policies are indentical and checked with GPresult.
What is different in windows server 2016 ??????
I saw a few people reporting the same issue on a few forums, but never any resolution...
HI, sorry for my english .
On a 2016 virtualized server domain member, I had a RDS working fine with one network interface.
For backup purpose to a private lan, I add a network card with a different ip network.
When this new network card is disabled, all is runing fine, I can as admin access to server manger and RDS services and rdp client cann have access to the session on the server.
When I activate this second network interface, access to RDS service configuration via server manger is unable (I get a "connection to server broker ...." with no resposn..) AND the client can't access to the terminal. RDP access become impossible.
Any ideas ?
I am going to distribute certain applications on the server using RDS (Remote APps)
It worked in an internal network, but I have a question about how to proceed with the external network.
RD Session Host / RD Web Access / RD Connection Broker / RD Gateway / AD DS, DNS Server
I want to know if I need all of these roles and how many servers I need to deploy.
RD Session Host / RD Connection Broker + RD Web Access / AD DS, DNS Server (three in total) has been isolated to complete the internal network test.
Help me where to add the RD Gateway and RD licenses.
++
Is it correct to use 443 ports on the RD Gateway and 3389 ports on the internal servers?
Hi,
i have a server in another point and i made a remote connection over internet with ip static and port forwarding
my redirected printer is available in remote server but when i want to use it, it send a print but nothing happend
anyone have this experience ?
Please Help me
i would be greatful if anybody help me , Thanks
Hello,
I haven't find any information about and I have just answered myself, but need to be sure about the answer :)
I have a RDS Farm with a Broker that hosts also UPD on dedicated virtual disk with Microsoft Dedupe Enable.
As I have migrated the Broker on a deduplicated storage, the Microsoft Dedupe is not needed anymore, so I want to disable it.
So the question is: is it possible to disable it (Windows 2012) without service disruption (considering that this is a 24/7 production server)?
I've been looking through the RDS event logs and I can clearly see that the licenses have been granted to X, Y or Z device. But I want to find out which RD Session Host they accessed to get the license. Is this logged somewhere (maybe if you enable verbose logging)?