I have a scenario where I have one RD server hosting all 5 roles and 3 servers that need to be accessed remotely from the internet (No RD roles installed on them). As a result of my setup I can only have 2x simultaneous RD sessions on each of the 3 servers. How to I go about increasing that with the licensing and what roles do I need to install on those servers?
Thank you,
LjAC
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.
I have an issue with client PC's getting multiple login requests to get an RDP session via RD gateway.
This configuration only uses RDGW and RDweb roles. there is no RDS deployment, we only use this gateway for remote desktop passthough.
I have a valid, trusted 3rd party certificate for the external DNS name.
Forms authentication is enabled on RDWEB site in IIS.
The RDgw server is a domain member and can authenticate logins to AD directly.
Client logs in to RDweb with domain credentials, tries to 'Connect to remote PC' then gets prompted for credentials for the RD GW server then again for the destination server to rdp (2008r2).
From here the behaviour is inconsistent depending what OS the client pc is.
On a windows 10 client, if I check 'remember password' from then on in it works seamlessly (although I shouldn't be getting requested to authenticate again in the 1st place)
On Win7 client, after authenticating multiple times and checking remember password, the destination internal server kicks back a message saying the 'admin does not allow saved credentials'. If I supply the password again I can get in.
Note that connecting RDP to the SAME server from the same client when directly attached to the internal network either locally or via VPN I do not get this message about not allowing saved creds and it just connects RDP session so this only occurs when coming in via the RDgw. (NB it also happens when just using mstsc.exe client)
How do I get SSO working with Rdweb, and why does this message about 'admin does not allow saved creds' only occur on Win7 clients, and then only when accessing via the RDGW
There are many posts about this same issue but I haven't seen any fixes applicable to my case
thanks
Hi,
We have 3 RDS servers and this is the 2nd time this issue has been happening. We have these servers setup since February 2015 and we never had this problem until this summer.
Last month, users were not longer able to connect to 1 of the 3 RDS servers and was caused by the fact that the RDP certificate had expired so my co-worker remove it, restarted the Remote Desktop Connection service and everything worked fine.
https://technet.microsoft.com/en-us/library/ee890902%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
Today, this happened again with another RDS server.
What is the best way to fix this ? I definitely don't want to fix this again in 6 months and I refuse to believe that the best solution would be to do a script that will delete the certificate each 5-6 months and restart the Remote Desktop Connection service at night.
Hi -
Have a public facing 2012r2 server running RDGW and RDweb roles. There is no RDS deployment, we only use this for RDP pass-through to internal servers.
After login in via RDweb and going to 'Connect to a remote PC' this connection may take anywhere from 30 seconds to 3 minutes to secure and establish the connection to the remote server.
Once it gets through, if I disconnect and try again, it will connect almost instantaneously. This occurs consistently. If the client hasn't connected in a while, it will take a long time initially, every time.
Each time the connection process is slow there is an eventid 11 is generated in the RDGW server:
event 11 Source: RDWebaccess
RD Web Access was unable to contact "computer.domain", which is the server that is specified as running the RemoteApp and Desktop Connection Management service. Ensure that the name of the server that is specified as running the RemoteApp and Desktop Connection Management service is entered correctly, and that the server is running and available on the network. Error code: 2147944122.
This message does not appear on subsequent connections.
As mentioned I do not have any remoteapp or SH servers setup in this deployment.
thanks
Env:
- Win 2012 R2, with RDS Role added, and Web Access enabled.
- Checked "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber". Port number is already new (not 3389).
Problem: When accessing RmoteApp via Web Access, the downloaded *.rdp file (eg., cpub-javaws-Session-CmsRdsh.rdp) contains the default port # as 3389: "server port:i:3389"
How to change the downloaded *.rdp file's port number?
What specific advantages or differences, if any, accrue to setting up a new RDS farm with Windows Server 2016 instead of Windows Server 2012??
For example, is performance better?? Network latency decreased?? What??
I am not really interested so much in 'what's new' as in ascertaining 'what's better' if anything.
I am trying to evaluate if it's better to jump right into Win2k16 RDS sooner than later, or put in Win2k12 RDS for a couple years, then do Win2k16 RDS.
Also if with Win2k16 it's better to serve a full desktop or applications.
Thank you, Tom
Hello,
I have come across several posts with a member "TP" was able to help resolve very similar issues.
Hoping he is still around and able to help me. I was not able to find a way to message directly on here.
So we have a 2012 RDS environment, the DC is also server 2012.
When users double click the RDP icon it takes almost almost a minute to connect.
It gets stuck at "configuring remote session"
I think its related to either the FQDN, DNS or certificate but we have had 3 people internally look at this and we just cannot figure it out. It was working fine when we intially set the servers up and worked for about 6 months, then last month, just out of the blue it started doing this.
Hoping someone will be able to assist
TP if you are here and able to assist we would be so very grateful to you!
Thanks!
Hi,
My problem is:
After a while, I cannot map my local resources (drivers and printers) anymore.
Only with a reboot I can map again my local resources.
It is important to say that I can always map my local driver by the
net use command.
So, its not network problem or permission.
It seems that run out of something... and I can only release with a reboot
Any help is welcome!
Marcelo
On Service RDS on windows Server 2008 Can configure and define policy for remote desktop client .
But on windows Server 2012 i install RDS already and configure RDS on web already but cannot found menu setting Configure Remote desktop client . Please Advise me
Hi all,
I have an issue with a 2008 r2 terminal server.
A line of business application is running on the server, remote users connect in and use the line of business application on the terminal server.
The line of business application has 5 user licenses, which mean 5 remote users can RDP into the terminal server and use the line of business application.
The issue is this...
some users seem to have TWO active RDP session from the same computer, I see this by logging into the terminal server, opening task manager then clicking the users tab. This of course causes issues with the licensing of the line of business application.
Is there a way I can prevent multiple RDP session for the same user on the terminal server?
Many thanks.
I have several servers that the last few weeks all randomnly have started causing connections via RDP to go to black screen for about 10-15 seconds then close the session.
I have checked roll up updates such as KB2887595 are installed, I can console into them from my VM Console, however RDP does not let me in unless a full Reboot occurs, sometimes multiple times. The fix may be temporary for a few hours, but may quickly revert back from not allowing new connections to log in.
These servers are part of a collection farm, I have disconnect sessions set to 1 minute, idle set to 15 min, active set to never for the connection properties for these farms.
I am at my wits end, cause I have roughly 6-8 servers all behaiving the same way with roughly 600 users hitting this set of servers on a daily basis, this is overflowing my help desk guys and I need a fix or solution...like last week.
Please help!
Joshua Craddock PinComputing LP. Systems Administrator
We have implemented remote aps from a server 2012
all clients are windows 10
we use navision as a remote app.
But sometimes when we work fore example in Outlook, the web app screen pops up in front of Outlook and then we miss write in navision in stead.
does anyone know a solution to this anoying problem?:-)
Hi guys,
On a random base (daily, weekly) we're experiencing major log-in problems on our Windows Server 2012 R2 Remote Desktop Services farm. The VM's are hosted on Hyper-V 2008 hosts and we're not using Citrix techniques etc.
Users are reporting that they cannot log-in, the log-in sessions hangs with a blank screen when loading their user profile (e.g. Please Wait For The User Profile Service).
In the System event log of the server on which the user is logging on the following errors are shown:
Source: Service Control Manager
Date: 23-12-2014 7:28:01
Event ID: 7011
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after 30 (or sometimes 60) seconds, the same error only another service (in random order):
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after exactly 30 seconds, the same error only another service:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxmSms service.
etcetera, with the following errors:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndPointBuilder service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WPDBusEnum service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
The Portable Device Enumerator Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TrkWks service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
These errors are logged continuously.
An administrator cannot solve this since he isn't able to login in as well (console or remotely), only a hard reset of the VM is possible to use the affected server again.
I took different steps to solve this problem without any success, like:
- Installing the latest Windows updates
- Removed unnecessary printer drivers, print monitors and print processors (no local printers/drivers are installed, only Remote Desktop Easy Printer driver is used)
- Searched different forum posts, but found only hotfixes for Windows Server 2008 R2.
Can someone please help me with this annoying problem?
Many thanks!!
EDIT:
Of course is increasing the time-out not really an option here... http://social.technet.microsoft.com/wiki/contents/articles/13765.event-id-7011-service-timeout.aspx
Hello All,
My configuration is as follows:
All servers are 2012 R2 and all roles are on separate virtual servers unless otherwise noted.
Server Name - Function
RDCB - Remote desktop connection broker in HA
RDCB2 - Remote desktop connection broker in HA
RDWA - Remote desktop web access server (Internal)
RDVH - remote desktop virtualization host
RDGW / RDWA - remote desktop gateway server and Web access (DMZ joined to RODC)
RDUPD - User profile disk server
All of the servers outside of the RDVH are part of a 17 node Microsoft cluster with over a TB of memory and 40GB/s network speed.
All of the storage is connected to a 3par SAN.
All connections (even internal ones) go through the gateway server. The connection issues I'm about to describe is intermittent but the error logs are always the same.
On the connection broker I get the following errors:
Event ID: 1306
Source: TerminalServices-SessionBroker-Client\Operational
Message:
Remote Desktop Connection Broker Client failed to redirect the user USERNAME.
Error: Unspecified error Sometimes there is NULL but always the same message.
The other error on the connection broker is:
Event ID: 1296
Source:
Message: TerminalServices-SessionBroker-Client\Operational
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : USERNAME
Error: Element not found.
The errors are usually in succession and I usually get error 1296 first then 1306.
The only other server I can find errors is on the RDVH. These errors have to deal with the UPD's (User profile disks)
On the RDVH I get the following errors:
Event ID: 8479
Source: TerminalServices-TSV-VmHostAgent/Operational
Message:
Remote Desktop Virtualization Host could not run the Hyper-V WMI job.
Error description: NULL
See also Hyper-V event logs
Hresult: 0x80078000
Event ID: 4890
Source: TerminalServices-TSV-VmHostAgent/Admin
Message:
Remote Desktop Virtualization Host could not apply a user desktop for a user account with a SID of <SID>. A temporary profile was enforced for the user. Verify that the user profile disk settings are correct.
Virtual desktop name: VMName
Error: 0x1.0
Event ID: 4893
Source: TerminalServices-TSV-VmHostAgent/Admin
Message:
Remote Desktop Virtualization Host could not attach a user profile disk to the virtual desktop for a user account with a SID of <SID>.
Virtual desktop name: VMName
Hresult: 0x80078000
To go with the above errors I have noticed that the UPD's don't always get unmounted when a user logs off. This has caused some of the connecting issues I noticed above. I know this because I will have a user not being able to connect, Ill find that their UPD is still mounted from the last time they successful connected. I'll unmount the UPD and they can connect again.
All of my clients go strait to a VM, so I do not have a session broker, so the connection issues be referenced in the event log do not make any sense. If anyone can shed any light on this I would be grateful
Thanks,
Scott
Using Windows Server 2012 Standard, in Remote Desktop Services I've configured the remote session to end, if the session is in a disconnected state for one minute.
However, after the user has closed the remote app. the session state status is 'Disconnected' and remains in that state without ending after one minute. At this point, without ending the session, the user is unable to connect to the remote app without having someone having to manually logoff the session on the server.
These same configurations have also been set in Group Policy in Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits . Also 'End session when time limits are reached' is enabled.
Still the session will not end when the status is disconnected.
Any suggestions are greatly appreciated.
Thanks
We have a Windows 2012 R2 RDS deployment with Session Hosts published applications and Virtual Desktop collections.
With Server 2016 coming in September has anyone found any documentation (I kind of hear the laughter already) on best practices to migrate from a 2012 R2 RDS deployment to 2016? I'm assuming we would build new 2016 servers and migrate the roles / upgrade the database.