Hello,
RDMS user interface on WINDOWS 2016 :
How to install it, without any Active Directory ?
Regards,
↧
RDMS user interface on WINDOWS 2016 : How to install it, without any Active Directory ?
↧
My RDWEB is Empty after deploying App !!!!!!!
i have 3 servers everyone contain all roles related to RDweb and after deploying apps and working fine during 7 months the rdweb showing empty there no apps on it and when i try to open old RDP file give me this massege:
"there are no available computers in the pool try connecting again rds"
also whene i try to create new server to provide same service and after install all roles also rdweb was empty !!!!!!
↧
↧
Remote Desktop licensing/cal usage issue
Built a new Citrix farm with Server 2016, with XenApp 7.15. We only use Citrix for published applications. 15 years worth of previous Citrix installs using per device cal's, never had an issue. Since building the new farm, every 2 months or so all the cal's are in use/unavailable, users get a "Remote Desktop License issue" error when launching an application. Have to rebuild the license database to free up the cals. Does anyone know what changed in server 2016 or Citrix after 6.5 that might be causing this issue? The license GPO's are correct, no errors on the server, can't figure out why the cals are not made available after a machine disconnects. We only have RDS installed for Citrix. We are small, only 20 cals, at most we will have 5 concurrent connections. Need to figure out what is going on with the licensing.
Since we are only publishing applications would it be better to use per user cal's?
Any help would be appreciated.
↧
Remote Desktop Web App users cannot connect.
Hello All,
I have an issue on one of my Windows server 2008 r2 servers. For some reason our users accessing the server using the remote desktop web app cannot connect randomly. They are able to authenticate and get past in the login screen and connect to remote desktop but when they try to open an app it starts to load the app and you select show details it goes from setting up desktop to logging off instantly.
This is only affecting the users accessing the server using remote web apps and does not affect the users accessing the server using remote desktop. Also the only way I can get the web app users back online is by restarting the remote desktop service on the server. I have checked the logs and nothing looks off and I have tried looking at the IIS roles and restarting this service and it did not help. I also ran an elevated command prompt and used sfc /scannow.
↧
Azure RDS Random Disconnects
We have about 60 users that connect to a Server 2012 R2 Remote Desktop Server Collection in Azure. A couple times per week, many users (not all) who are actively using the Servers will get disconnected from their RDS session. They are able to reconnect and get right back into their profile and open applications.
We can't find a pattern or figure out why the disconnects are happening. The disconnected users are in different cities and on different Session Hosts. Not all users get disconnected.
Environment:
Multiple Sites, site-to-site VPNs to Azure
Several Servers in Azure, Domain Controller, Application Servers etc.
4 RDS Session Hosts, 1 Collection - Server 2012 R2
2 RDS Connection Brokers in HA Mode - Server 2012 R2
RDS Gateway & Web Access Server (not used for internal connections) - Server 2016
RDS User Profile Disks & RDS Licensing on File Server - Server 2012 R2
We have Group Policy set for:
End session when time limits are reached - enabled
Idle session limit = 2 hours
Active session limit = 12 hours
End a disconnected session = 3 hours
Any ideas?
↧
↧
update KB4467697 breaks remote desktop
On a 2012 R2 remote desktop server, update KB4467697 breaks some remote desktop services. I had the exact same problem with the preview KB4462921. Removing either update makes the problem disappear.
Passthrough RDP connections through the gateway work just fine so there is no problems there. The problem seems to be related to RDP on the remote server itself. These two updates break direct RDP logins, we have to use TeamViewer or visit the physical console in order to gain access to the desktop. Clients can login to the RDP website and see published apps, they just won't open.
With either of these updates installed, thousands of these errors appear in the event log:
A fatal error occurred while creating an SSL client credential. The internal error state is 10013.
Does anyone have information as to why the latest November 13 cumulative update for Windows Server 2012 R2 breaks RDP and Remote Desktop published apps with 10013 errors in the event log?
Passthrough RDP connections through the gateway work just fine so there is no problems there. The problem seems to be related to RDP on the remote server itself. These two updates break direct RDP logins, we have to use TeamViewer or visit the physical console in order to gain access to the desktop. Clients can login to the RDP website and see published apps, they just won't open.
With either of these updates installed, thousands of these errors appear in the event log:
A fatal error occurred while creating an SSL client credential. The internal error state is 10013.
Does anyone have information as to why the latest November 13 cumulative update for Windows Server 2012 R2 breaks RDP and Remote Desktop published apps with 10013 errors in the event log?
↧
Win10 RDP Black or unresponsive screen after RealPlayer Slimware "driver update"
I have a two computers with Win10 pro update 1089 installed - a desktop (ethernet) and a laptop (wireless). I RDP from the laptop to the desktop when I need the faster internet connection. Recently, when I logged in to my laptop; realplayer update opened, i OK'ed, slimware driverupdate updated drivers for: Intel graphics driver; intel USB eXtensible host controller; realtek high definition audio driver; synaptics clickpad driver. now when i RDP to my other computer I mostly get just a black screen; sometimes I get a clear screen that does not respond to my mouse; sometimes I get a session with very blurry screen.
I uninstalled realPlayer and Slimware, then did a system restore (then Windows updates back to 1809), but I still have the problem -- my drivers did not change. There are no restore points prior to the slimware update/install/malware. Also, windows defrag now takes more than 12 hours to run (15 passes).
↧
Open License login
This program was simple in the past, easy to login, easy to add a license. Now even logging in is almost impossible, they have made it crazy difficult then their system doesn't even work. The "company" or "personal" is nuts, I can't even move forward have to keep changing computers or browsers to get access. I can't believe how much time I waste with something that should be painless..............
It seems the larger a company gets the more stupid they get, same with AppleID and password and secret questions etc.
↧
Local User (no AD, no Domain) : How to specify a other folder to store the local profile used by Remote Desktop ?
Hello,
On Windows 2016, for a local user (no AD, no Domain),How to specify a other folder to store the local profile used by Remote Desktop ?
The goal is to use D:\USERS\<logon_name>\ .
I also try to user the Local GPO without success... (the user name is "toto")
A folder D:\USERS\toto\ appear, but the entire profile is stored in C:\users\toto\
Regards,
↧
↧
rds gw mfa rdp file timeouts
Hi,
I have 2 question.
Question 1:
We are trying to implement a 3rd party MFA in our RDS environment for our external customers..
We are using the RDGW to protect our internal environment from the external world..
At this moment we are using webform based MFA in front of our RDWA page.. So the MFA happens on sort of proxy page, which is then passing the necessary username & pw to the RDWA page once the MFA process is handled...
While doing some tests with the RDP file that we receive once we click on the App/Desktop icon and saving the file locally, we noticed that this file (even without the MFA) contains all the necessary credentials to login to the RDSH...
How long are these credentials valid? We tried 1 day after saving the file, and while executing the file, we are logged on automatically..
So in this case our MFA will not really help, because when the End Users would save the file, they will always be able to connect...
Do you guys know what are the timeouts for such file/credentials/.. Is this valid forever? What can we do to block this ?
Question 2:
We are checking to perhaps implement Free Radius (because we are in POC of this setup) which will be used for the MFA process.. How easy is it to plug in into our NPS (or RDGW CAP&RAP policies) so that we can use this instead for MFA.
Thx!
Robby
↧
RD is terminated before even starting, Access is Denied.
I've been having this error for while now, I connect to one of the servers and it starts doing its thing apparently going through every step just fine but then I get this Access is denied message:
Normally I wouldn't bother trying to fix it because I don't have the time nor the resources to throw at it, I just snapshot the machine back to a working state, files will are centralized in non-Microsoft redundant servers, they are safe. However, when I tried snapshotting back this VM way back to the beginning of the month the error was still there. I figured, it's a domain issue then, so I took it out of the domain and it still wouldn't let me in.
I connected to the machine's console (via Fusion, it's hosted on ESXi) and checked the log.
There was nothing descriptive except for a "reason code 12" which I knew meant basically nothing because I had looked for it before when this started happening, so I went deeper since my snapshot safety is over I need to know how's it fixed.
Most of the RDS related branches in the tree were empty but in Microsoft/Windows/RemoteDesktopServices-RdpCoreTS/Operational I found some data, actually a ton, 50+ events per connection attemp. They all occur in the same second. I started following the messages, the one where everything fails is:
Disconnect trace:CUMRDPConnection Disconnect trace:'calling spGfxPlugin->PreDisconnect()' in CUMRDPConnection::PreDisconnect at 4477 err=[0xc], Error code:0xC
Here's a table of the logs I made copying them one by one, I tried adding it here but exceeded the message length: http://fetch.vitanetworks.link/stationary/technet/eventlogerror.pdf it's a PDF, so it should show right in the browser.
Using the system with another account reveals the user that failed to log in, tho whom access was denied, is somehowstill logged in. I was informed this when I tried to restart the computer and the warning I would kick other users out showed up. No configuration has been changed on the server, on DCs/GPOs, on the client, nor on the hypervisor. And of course I have no idea what does that graphics thing mean.
The other directory with events was on Microsoft/Windows/RemoteDesktopServices-SessionServices/Operational with a way more decent 2 events per connection attempts:
1 Error The RDP display control module failed to change the session monitor layout. The operation failed with error code 0xFFFFFFFF.
2 Information The RDP display control module successfully changed the session monitor layout. New layout has 1 monitors.
And that's all the info I have. Could you point me where to go next to get more information or how to proceed from here? I don't want to reinstall Windows, I put way too much time on these machines. :/
Thanks for your help!
I bet you think this post is about you. Don't you…don't you. ♪
↧
Problem with Windows Server 2019 RDS License
We want to deploy few new rds servers on server 2019 but it seems that the per user licensing is not working correctly if in a workgroup.
Evertime when a user logs in it gets the following message:
'There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes, Contact your system administrator to to fix this problem'
In the gpo the license server is specified and the "per user" mode is selected.
Same issue as :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/e69d9a47-1e2a-4d37-8073-97327ac91154/problem-with-windows-server-2019-rds-license?forum=winserverTS
↧
Your credentials did not work .Remote Desktop Connection
l need help here with Remote Desktop Connection .l configured window 10 PC to remotely accessed but the problem the login are rejected .When try to connect l am getting window security Message saying "Your credentials did not work . The credential
that were used to connect to xxxxx.gotdns.com did not work . please enter new credentials " .
l used the following the details to connect to remote computer
Username : <ComputerName>\<Username>
Password : Password for above UserName
The Name of the remote computer ,Username , password are valid but they can't allow me to login .The machine had no password so l added a new one for remoter Access .Please help guys ,
l used the following the details to connect to remote computer
Username : <ComputerName>\<Username>
Password : Password for above UserName
The Name of the remote computer ,Username , password are valid but they can't allow me to login .The machine had no password so l added a new one for remoter Access .Please help guys ,
↧
↧
Windows server 2016 RDS issue
Hello,
I have recently installed RDS licensing n workgroup environment and after 180 days it is causing an issue like i have to delete the registry entry "Grace period" and restart the systems.
Is there any other way to fix this issue so that i don't need to do remove the registry entry every 180 days and restart systems.
Thank you
Dayanand Gavas
↧
RD Gateway on Windows 2016 Two Factor Authentication
I need to setup AD with 2 Factoru authentication. The RD Gateway server is in DMZ in standalone environment. Is there a way/solution to setup 2F authentication?
↧
Event 4005 - WinLogin [Windows logon process has unexpectedly terminated]
Folks,
Just noticed this becoming an issue on a Windows 2012 R2 Terminal Server after the last round of Patch Tuesday updates stemming from August 9th, 2016.
Typically, I'm rebooting the server every 24 hours to over-correct the issue - rebooting not being the best option here.
In previous discussions, it's advised to remove KB3002657 or KB3035132 from the server. Is this still the best option to restore full functionality even with the last round of patches and updates? Just to confirm, we are not using webroot as an AV solution.
↧
Unable to display RD Web Access when using FQDN
I am setting up a test server for RD Web access, after the setup I tried accessing the page using FQDN but after the login page I get the: Unable to display RD Web Access error message, this only happens with Edge HTML 17.17134 if I use Chrome or Firefox it all works fine. Also with Edge if I just use the netbios name or IP address the error doesn't occur.
I need to use FQDN because of the certificate.
Any ideas?
↧
↧
Printer Redirection Stops Working After Several Hours
Summary: Remote desktop users are unable to print to redirected USB printer after 2 hours. Issue began around 5/14/18.
Detailed Overview: I'm running Server 2012 R2 and we have 30 users. A majority of the users have local printers connected via USB. Printer redirection has been working successfully for these users for over 2 years, up until Monday 5/14/18.
I started receiving calls from multiple users, stating they cannot print in remote desktop.
I updated the local printer drivers on the user side, as well as on the server to match. The printer works perfectly for a few hours. Then I receive calls from these users that their printer is no longer working. No print errors in the remote desktop session, in fact it acts like it sent the print job. If I have them perform a test print locally, the printer works fine, have them test print through RDS, the print job isn't sent to the printer. I see it flash in the print queue briefly on the RDS side.
Temporary Workaround -
(1) I can have the sign out (not disconnect) from their remote desktop session and reconnect. The printer works again for a few hours. Disconnecting doesn't resolve the issue.
(2) Rebooting the server will force all users off, as a result once they log back in, everyone is able to print for 2 hours or so before it stops working. Network share printers are not impacted by this issue.
Recent Updates
We rolled back several KB's leading up to 5/14/18 and rebooted. Still didn't resolve the issue.
KB4103724 - Installed 5/17
KB4098972 - Installed 5/17
KB4096417 - Installed 5/12
KB4095875 - Installed 5/12
Event Log: Event ID 36
I did notice the event log showing the following event ID 36. However, these event ID's have appeared long before there was an issue printing. I also haven't found anything to address this issue.
| 6MGPRS02 | 36 | Warning | Microsoft-Windows-TerminalServices-ServerUSBDevices | Microsoft-Windows-TerminalServices-ServerUSBDevices/Admin | 5/30/2018 12:16:08 PM |
Redirection of additional supported devices is disabled by policy.
Local Group Policy Editor Changes
I made the following adjustments to the local policy editor to see if I could eliminate the Event ID 36 warnings, the changes have not made any difference. Even after trying GPUPDATE /Force.
Device and Resource Redirection -
Do Not Allow Supported Plug and Play Device Redirection - (disabled) changed from not configured.
Printer Redirection -
Do not allow client printer redirection - (disabled) changed from not configured.
Redirect only the default client printer - (Enabled) changed from not configured.
Any thoughts or suggestions would be much appreciated.
↧
Server 2016 msg problem.
Hello.
I have very strange problem with Server 2016 RDS Remote App.
Previously i used server 2012R2. And when i send message for user (msg command), they can easy click on OK button and close this message.
But a completely different situation with the server 2016. Users receive a message, but cannot press OK buttom. This message on background and block all windows. They need to press alt+tab combination and select remote app. And only after that they can press Ok buttom and unblock all other windows.
All clients have windows 10 1803
Any ideas how to fix this problem?
↧
Remote Desktop Fails as soon as a RDS Collection is Created
Abbreviated Problem:
As soon as I create a RDS application collection I am unable to use any remote desktop services. Reboot has no effect. Security Layer is set to "Negotiate" and Encryption Level is "client compatible". Prior to creating the collection standard RDP works; after it is created, however, RDP (including remote apps) fail to connect with the error :
Likewise, Immediately upon deleting the collection, Remote Desktop begins working again.
-This is a quick setup RDS deployment that exists only on one virtual Server 2016 instance.
___________________
Additional info:
The collection was working as intended for several months but I discovered that the above error would occur for all users and devices after a reboot of the RDS server or after a restart of the remote desktop services on the RDS server. Heeding the advice of a RDS forum I deleted the application collection and thought my troubles were behind me once remote desktop began to work again.. wrong.. As soon as a new RDS collection is created the error returns for all connections. I initially created the collection over an RDP connection and thought that might be the cause but the issue remains even when using a vmware console while creating the collection.
Obviously my RDP ports are open from the client computers to the RDS since RDP works after the collection is deleted -windows firewall is also off.
Hoping someone with more expertise and experience with RDS can help here.
↧