Right now we are seeing an issue with RDP were the user profile service hangs on logging in. Port 3389 is showing up fine.
I wanted to see if anyone has a script or tool that would try to login all the way to multiple servers and make sure they get a desktop. That way I could check on those servers.
I have SCOM 2016 Available if that can be used to do this as well.
Hi, I've this issue after migration of RDS server from 2012 R2 to 2016 and client have Windows 10 1709 but with Windows 10 1703 no issue.
Any suggestions?
Hi
i like when user use rds service and will export any file from program remote only can save on local computer they remote to server.in save as show the local computer folder
Hi,
In our environment we have a number of Linux, Ubuntu, servers (hosted on Azure) that admins need remote access to. When a Linux desktop is needed we use X2Go opened to a XFCE session, the X2Go application is a published app on the RDS environment. This works great when the “thick” RDP client is used however we’d like to use the new HTML5 web client and this is where we seem to hit the issue. The X2Go application opens up nicely in the browser (Edge) and we can connect to the server where the Linux desktop appears. However although the mouse works the keyboard does not, the only key that works is “enter”. To check this wasn’t a X2go/XFCE issue we’ve also tried XRDP using the standard Windows RDP client and this produces the same result, although in this case it is not possible to enter anything into the XRDP login screen. As a final sanity check we’ve also deployed a new Ubuntu server with nothing additional installed other than XRDP and the result was the same.
Anyone else using the new HTML5 web client and seeing anything like this behaviour?
Hi all,
putting together a HA RDS farm design - and im having trouble finding guidance on sizing for RD Connection brokers, RD Web and RD Gateway servers.
I get the for the session hosts, it is very dependant on what is running within the sessions and hence, the lack of hardware sizing guidance.
For the other roles it would be nice to have some sort of general advice - i.e. 1 connection broker per 1000 users, 1 RDGateway per 200 users etc....
Does anyone know if sizing guidance such as this exists? (and I just haven't been able to find it)
Atradius
Atradius
Hello
We have been running RDS for years and years without issue. Back in march we decided to hold of on all patches for this credssp patches to smooth out. We just recently started testing out fully patched clients however now we are receiving a double prompt trying to log into anything with RDS. I am only ever seeing this on patched clients. We tried patching 1 TS box but that did not help.
Any ideas?
Hello,
I set up an RDP farm with Broker. We are running server 2008 R2.
I tried to make a SAN cert in our Enterprise CA but every time I adopt the cert for the RDP connection it still says Certificate Mismatch. It shows the server name on the RDP Cert and not the farm name.
https://blogs.technet.microsoft.com/isablog/2011/10/09/how-to-generate-a-certificate-with-subject-alternative-names-san/
This is the article I used. Has anyone else had this problem before?
Thanks,
Jason
Jason Munsterteiger
RDS 2012
Remote app server 2012 - approx. 20 clients - get these errors in event viewer repeatedly. Some users report they must restart PC after returning from being away in order for remote app to allow them to reconnect.
How could I get rid of these event viewer errors?
RDS Log File
Log Name: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational
Source: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS
Date: 3/3/2015 7:47:51 PM
Event ID: 97
Task Category: RemoteFX module
Level: Warning
Keywords:
User: NETWORK SERVICE
Computer: REMOTE1.XXX.local
Description:
The RDP protocol component X.224 detected an error (0) in the protocol stream and the client was disconnected.
System Log Error
Log Name: System
Source: Schannel
Date: 3/4/2015 10:42:02 AM
Event ID: 36887
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: REMOTE1.XXX.Local
Description:
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 49.
The colors are off (yellow text & black back ground in Windows Explorer) on some users when they log into a Windows 2012 server via RDP & using the Remote App.. It only happens from a Windows 7 machine, and only on that particular Server, and only certain users. When I use RDP or the Remote App from a Windows 10 machine (same user), no issues.
I've tried updating the registry key via GPO to go with the Aero theme
I've tried deleting everything in the C:\Windows\Resources\Themes\aero\VSCache folder to let the server rebuild, but there was nothing there.
I've changed the C:\Windows\Resources\Ease of Access Themes\basic.theme file to only go with the Aero theme not the Aero.lite theme.
I've done this "SFC /scannow" and "DISM /online /cleanup-image /resorehealth"." -
Nothing has worked.. I'm about a week away from just creating a new server and migrating the data... but that's not giving me a reason why or a way to prevent it from happening again.
Hi,
I've been able to reproduce the following issue:
We've got several 2016 RDS servers. We use mstsc /shadow:<session> to shadow sessions if needed. Since installing KB4056890 shadowing it gives 'Unspecified error':
I've deployed a fresh RDS 2016 without that dreaded KB (it broke quite a few applications in our site as well...) and then it works fine, until installing KB4056890 again. Can other people confirm? Any statement from MS?
I have tried to delete the Userclass.dat file precisely as it is annoying to get deleted throwing pop up as : the userclass.dat is used by SYSTEM.
Here are the troubleshooting that I did so far:
1. Tried to delete the user from the User Profiles in System Properties but cannot fine that profile precisely as there are so many Unknown account.
2.deleted the profile from Profile List in registry and rebooted the system.
3. tried to disable inheritance to the .dat file and removed the SYSTEM from the Security.
Let me know what needs to be done next.
Hello,
I have a problem on several 2k8 servers: since a few days, when I get my hands on it in RDP the logon lasts 5 minutes. In the eventviewer I have:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service. And the same with the processes: Dnscache, CryptSvc, NlaSvc. the server reboot solves the problem but only for a few days. After
that starts again, I tried among other things:
- Testing from another workstation
- Disabling the print spooler
- Disabled smart card printers, etc. in connection settings
- Disable antivirus software
- GPO : System\Logon\Always wait for the network at computer startup and logon (Turns off Fast Logon Optimization)
- No Active directory replication problems
- No DNS problem
- The servers are in the OU computers and my user in the OU users (so no GPO)
without success, not against when I connect directly to it (without going through an RDP connection) I have no problem.
Do you have any idea?
Thansk in advance,
C.
Atradius
If I use my Domain1\Login1 to RDP into a trusted domain server (say Domain2\Server2), I receive a lock out message on the Domain1 Domain controllers that Domain1\Administrator was locked out from "Server2".
For one, we don't use the Administrator account in either domain. It has been renamed.
Secondly, I can't figure what is going on with Domain2\Server2 that it would be trying to do something back to Domain1 as Administrator.
On Domain2\Server2 I see a corresponding: Event ID 20499 "Remote Desktop Services has taken too long to load the user configuration from server \\SERVERNAME for user USERNAME" -- I am not sure if this is a cause or an effect.
This happens on servers in Domain2 where we are running RDS and it also happens if we just RDP into a server desktop.
Any ideas?
Hi , i am suffering a stranger problem.
I have 5000 computers network and only in 1 i have this problem.
When i log on the machine (name it PC_A, W7 machine) locally, and try to connect to any other machine through RDP, it takes about 1 or 2 minutes to connect. I try to connect to W7, W10, W2008, W2012 and in all cases is the same.
BUT, if i log on PC_B and i use RDP to connect to PC_A , then when i try to connect from PC_A to another machine, it works normal, 5 secods and i m in.
I dont know why, but only locally happens.
Hello,
I have problem with my RDS server - users session every moment is suspended with (4) in taskmgr.
When user session get this suspended, they can not connect to terminal again.
Only a hard restart helps server.
I haved servers on Windows Server 2012R2.
RDS licence server is on srv01(domain controller) and terminal servers is on srv03 and srv04.
Someone have problem with this suspended terminal session and knows how to solve it?
Hi
i like when user use rds service and will export any file from program remote only can save on local computer they remote to server.in save as show the local computer folder
Some admins in our IT group have been attempting to set-up RDS (incl RDG) on Windows Server 2016. It works in most scenarios:
I've also verified smartcard auth to a server directly (not with a remote desktop gateway). For some reason, I'm unable to passthrough my smartcard to a server when using a remote desktop gateway. It simply comes back with "login failed" on the client. The "login failed" message appears as an error during the hop to the gateway server (i.e. it doesn't seem to even try to connect to the destination server).
On the RDG server, there are two error events generated:
I'm not sure why a smartcard would work in one situation but result in Unknown user name or password in another. Any ideas on where to start?