Hi, after install the webclient and bind certificate to port 3392, I get this error message.
WebSocket connection to 'wss://dc.redecr.intranet:3392/rdp' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
There is no firewall between the client and the server, the port 3392 is open on RDS Server 2016.
Any ideas?
Thank You
Cesar Ramalheiro Jr
Hello,
I've been having an issue connecting to new RDS deployments, either Server 2012R2 or 2016, using the modern client (UWA?).
If I connect to the rdweb site via browser, any browser (Chrome, IE, Edge), I can connect fine w/ the downloaded RDP file, either via the old mstsc client, or the modern client. If I open the modern client and add my deployment as an RDS resource, it adds file, but when I try to connect, it doesn't do anything. Monitoring network traffic, it doesn't even try to connect to the rpcproxy.dll,or even send any packets on the wire to my gateway.
Doing some digging, I see the rdp file is saved in my user profile (C:\Users\#####\AppData\Local\Packages\Microsoft.RemoteDesktop_8wekyb3d8bbwe\LocalState\RADC\{9AFF1AD1-C68D-FC28-FA01-4BD806FA43E4}-Committed\Resource) without an extension. If I copy the file from there, give it a .rdp extension, I can also connect with that file via either client.
I also don't appear to be able to add the remote resources, at all, via the IOS RD Client. I haven't tried Mac or Android yet, waiting to stabilize this config, but perhaps that's a separate issue. I don't see it trying to logon or connect to webfeed.aspx on the RDSWeb page at all.
These would all be the lastest iterations of the clients, I just started this whole setup about a week ago. I've tried a standard deployment in 2016, then a quick deployment in 2016, and finally a quick deployment in 2012 R2. I'm familiar with all the cert requirements, etc, I don't think it is any sort of cert issue. I will say the 2012 R2 quick deployment seemed to work OK initially, until I added 2016 session hosts to the deployment, but now I can't say for sure. If needed, I could do another quick deployment to verify.
Any insights would be great. If we can only use rdweb and have users open RDP files I guess we're OK with that, but not ideal.
Thanks!
-jg
Hi,
to prevent users from knowing about other users on a terminal server what can I do?
By default users could:
-browse c:\users\*
-use taskmgr.exe
-tasklist
-qwinsta
-netstat
-? perhaps other commands, applications
to gain information about other users on a Terminal Server like Account Name, processes used, Network Connections.
I could prevent access to the obvoius like eventvwr + other administrative tools, c-drive or adjust permissions on qwinsta.exe but with cmd.exe and taskmgr.exe it already is difficult because it limits users e.g. from ending a hanging process.
Ideally it also would require to whitelist every single allowed application and prevent execution of portable software for users.
Are there any recommendations?
thank you
Markus
Several users across two different terminal servers are being forced into using a temporary profile. I have no way of knowing if they are logging off (despite continued re-education) or if they are just disconnecting, leaving the session to be interrupted later. The only way I've found to fix it is to reboot the Terminal server.
If I check regedit under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, I don't see a .bak. I can sometimes see the ProfileImagePath is to a temp folder.
The users have a roaming profile that's saved to the fileserver upon logoff. I can get into the folder, but if I try to go to a sub folder, I don't (as a domain admin) suddenly have access. So the profile server isn't able to do anything either. I could probably TAKEOWN on the folder, but that's not telling me what's causing this issue.
Is there anyway to fix this without rebooting? Also, what could be causing this? We've had more in the past 3 months than since I've started working here.
Ben Rollman
hi we have some old thin clients. they have RDP 5.2 clients.
can they be connected to server 2016 in any way ? any workaround available?
Hi all
This morning I have experienced a black screen of death on both my exchange server and domain controller. these are physical servers.
The Servers go on but after the Windows Logo, it just goes dark, no curser and I cant control-Alt-delete.
My suspicions is that it is a update that came through during the weekend.
What I tried.
I cant restore because It didn't set a restore point
I tried fixing the MBR but since it logs through and shows the windows logo that might mean the MBR is intact
tried all safe mode options but nothing.
I am running out of ideas,
So the Question is how do I remove an update from the server if t doesn't want to log in Windows?
your responses will be much appreciated
Ezekiel Sikaneta
Hello,
Why in Windows 2012 Standard dont show the Source Network Address?
Anyone knows how enable it ?
On Windows Server 2012 R2 i can see it but on Windows Server 2012 Standard not.
Thanks BR
Alejandro Zorrilla
I am facing a error, when the user click on sign out the session is closed normally, but, the follow image is displayed...
Just one server is showing this behavior and with all the users.
The errors found in Event Viewer are: 1296 and 1306.
“Vote As Helpful” and/or “Mark As Answered” - MCSA - MCSE - http://www.ucsteps.com/
We are running a 2016 Datacenter server under Azure. The server is primarily an RDS running Office Pro Plus and a couple of SQL backed applications.
Since Monday we've had problems with the user experience, with applications failing to clear down (Chrome was installed, would open once and close but then fail to open again - Chrome process remaining in background.)
The notifications for printing, new emails etc would appear but then fail to close afterwards. Left click on the start button would stop working and user experience was generally poor with noticeable lag on moving items on the screen. This sounds like a Shell type issue.
We have removed Chrome, disabled Skype for Business through GP, dialed down AV. We have run SFC /Scannow which found errors and fixed all except problems with Task Scheduler.lnk
Server is back up and we're waiting for it to happen again. Latest patch KB4489889 is applied, though this came out after the first problem.
What else might I have missed?
Issue: User Logs onto Client Machine remotely, then connects to Corp VPN and does RDP to any Corp machine. In case the VPN disconnects or client machine loses network connectivity momentarily, the RDP session re-establishes the connection. When it re-establishes a connection, it logs a bad password attempt on the users account. If this happens too many times, users are experiencing account lockout.
Upon checing the logs, I see that the Terminal Service is sending the bad password.
Can anyone suggest what could be the possible issue?
Hi guys,
I bought MS license WinSRV2019 with User CAL x8; RDS User Cal x4and I installed WinSRV2016.
after installed and Activated window, I checked on the RD Licensing manager -> the total license of RDS per User Cal still appear "0".
so that please help how to activate RDS service to appear as I bought- 4 x RDS User Cal.
Many Thanks
Then we clicking "update now" system asking to enter credentials. After the entering domain username and password everything is updating. After this procedure updating works fine 2-4 weeks and then start failing again. Our users required to change password every 3 months. That means password changing can't be the reason of this error.
Maybe it can be related with server rebooting? All RDS farm machines reboots once per month during the server patching
Thanks for help in advance.
hi
i have RDS CAL 2012 with a valid SA.
Can i use this to Remote Desktop Servise to Windows Server2016?
Do i need to upgrade my RDS License?
Hi.
We are rolling out RDS 2019 in our environment. We've got a lot of complaints about the DPI settings not being able to set in the session anymore like in 2008R2, but it has to be done on the local client, which is really cumbersome. However, when done so, we still have some applications with issues.
Now, for most of them I can fix it by setting the compatibility settings:
On a Server 2019 test machine, when set to Application, the application actually shows up fine. On RDS2019 though, it doesn't. I've been working on this for a while, until I installed a machine from scratch, do one step of our installation script at a time, and see where it started failing. It turn out as soon as we enable the RDS role, the DPI settings don't have any effect anymore, and the app is all blurry.
When I remove the RDS role, they start working again. Would anyone know how to fix this?
Hello,
We have 8 RDS, One Broker, Windows 2016 Std., on a Farm.
We have GPO's Policies on those servers.
From Time to Time, some users are experiencing task bar freezing.
The desktop icons are working, but the task bar is freezing and you can not do nothing on the Task Bar.
The only way is to log off and log in again.
It there a solution ?
With Best Regards,
Haim
Hi
I recently upgraded from Windows Server 2016 to 2019. On Windows Server 2016 I could define an initial program for the remote user in his usersettings, according to this guide:
https://social.technet.microsoft.com/Forums/de-DE/c73d0676-baab-4d54-801b-92e3b7e34365/start-program-for-rdp-user?forum=ws2016&prof=required
This apparently does not work anymore.
Is there a new solution for this problem or was the feature completely removed?
Hi all,
We're currently experiencing issues at a random interval with regards to freezing start menu's on Server 2016 RDS Hosts.
When the freeze happens we can see the following items in the eventlog: Event ID 5973
Seems to be related on a per user base, as multiple users can connect to the RDS server but only a few of them are experiencing issues.
We are using User Profile Disks and Start Menu redirection. Any thoughts?
"Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: Not enough storage is available to complete this operation. See the Microsoft-Windows-TWinUI/Operational log for additional information."
"Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The RPC server is unavailable. See the Microsoft-Windows-TWinUI/Operational log for additional information."
"Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information."
I have an issue with old Windows CE devices connecting to an new Windows 2016 terminal server. The old CE devices use the older login where you get connected to the server and then authenticate, as opposed to RDP 6, where is prompts you for credentials.
The CE devices are only 240x320 touchscreens (Old Motorola MC9090 RF guns), so what happens on the display is the username and password field are cut off, and users have a difficult time selecting these fields.
Previous Windows 2008, the login screen had a different orientation, so it was more user friendly for those devices. Any one have any ideas if its possible to rearrange the screen or change resolution on just this screen?
I have tried just about everything and would really be disappointed to have to revert back to 2008 R2, just because of a login screen. Updating or getting new devices are not possible at this time.
I have also tried:
This is a picture of what is displayed:
Thanks for any help on this.
Hi,
I have two forests(domainA, domainB) and RD Licensing server is in domainA.
May I know what are the ports to be opened from my RD Client to RD Licensing server to get the CAL licenses.
//Sampath Kovuri