Server 2012 R2

Basically i have 2 problems related to each other.
When people connecting to terminal server, and then some become idle, and some are really working (i see "a dot" or numbers), after several minutes the idle list resetting for everyone!
This cause me another problem that lots of idle stay connected and not disconnected from server and then the RDP connection to the terminal server takes lots of time and even failed sometimes due to timeout.

Hi All

I have a virtualised (VMWare) RDS 2012R2 environment with 20 Session hosts spread across 6 Dell ESXI Hosts - 2 Sets of different PowerEdge Models. Over the past 4-6 weeks we have started to get multiple event 7011's followed by a 7046.

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

The following service has repeatedly stopped responding to service control requests: Remote Desktop Services UserMode Port Redirector

At this point some existing connected users cant sign out and applications start to crash including explorer.exe. Trying to shutdown via the GUI just hangs and the only way to get the server back is to reset the power using vSphere console. 

Applications on the Session Hosts are mainly MS Office 2016, Acrobat Reader, 7Zip and Webroot AV. Windows OS and applications are fully patched and up to date and Dell Firmware and drivers are fully up to date. 

Users connect in via RemoteApp and local drives and printers are redirected into their sessions. 

The weird thing is, like clockwork the crashes happen at the end of each day usually between 16:00 - 18:00 - To me its like a degradation symptom or perhaps its the actions of users disconnecting or logging off their session - Its affecting a couple of servers each day. 

On top of this, it appears 7011, 7046 results in a BSOD. I have grabbed the Memory.dmp file and opened it with WinDbg. 

Im now trying to figure out the dmp - uploaded to PasteBin here (happy to paste dmp here but didnt want to "dump" to much information in the post)

What stands out to me is rdbss.sys

Probably caused by : rdbss.sys ( rdbss!__RxAcquireFcb+1f3 )

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80179d3ba44, address which referenced memory

BUCKET_ID:  AV_rdbss!__RxAcquireFcb

PRIMARY_PROBLEM_CLASS:  AV_rdbss!__RxAcquireFcb

My rdbss.sys version - 6.3.9600.18895

Can anyone help to try and decipher the above and suggest next/best cause of action?

Many thanks :)

Hey

Unable to connect to RDSH (collection) from Windows 7 - All Windows 10 works.

If I disable NLA on the Windows 7 clients its able to connect to the RDSH (collection)

If I connect "directly" to a RDSH it works. (but not over our connection broker)

Any ideas?

Mike

When I try to access the remote apps from the RDS Web Server page, I receive the error;

This computer can't connect to the remote computer.  Try connecting again.  If the problem continues, contact the owner of the remote computer or your network administrator.

What am I missing here?

With the exception of certificates, I have all components configured.  As of now, this is all internal within our AD Domain, so I wasn't going to worry about certs until later on.

Can I import Server 2019 CALs into an existing Server 2016 Terminal Server License Server?

Or do I have to "upgrade" the 2016 server in order to issue 2019 CALs?

Or do I have to build out a new Server 2019 and install the Terminal Server License Server Role and import 2019 CALs?

Thanks!

We recently setup a Windows 2016 RDS collection. This consists of the following servers:

 - Server 1 (RDS Broker, RDS Licensing)
 - Server 2 (RDSH)
 - Server 3 (RDSH)
 - Server 4 (RDS Web Access & RDS Gateway) (server 4 is located in our dmz)

We have an external dns record "apps.somedomain.co.uk" which points to server 4. 
We have an internal dns record "rds.somedomain.local which points to server 1.

We can successfully log into https://apps.somedomain.co.uk\rdweb, however, when we attempt to connect to RDS using the RDP shortcut it attempts to log us onto the gateway/web access server rather than the broker!

Internally, if we RDP to rds.somedomain.local we are successfully redirected to the RDSH servers and we can see user session are load balanced correctly.

We have deleted and recreated the rds collection but we get the same issue. Where/how can we update the collection settings with the correct dns address (ie: rds.somedomain.local)?

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

Hi folks,

I am dealing with weird issue on my Windows Server 2012 R2 server. Server is used as DC and RDS server.

Everything was working fine until Friday where I saw this problem first time.

Users reported that they are unable to log on to RDP - they see black screen only. User with active RDP connection are able to work but unable to log off from RDP. In server console I see that RDS is not working properly. I am able to restart all RDS services except this one - UmRdpService.

And there are some errors in event viewer.

13:05:13 Source - System, Service control manager - event ID 7011 - service UmRdpService timeout. 

And then another:

The same source and event id but service is different - hidserv, Netman, ScDeviceEnum, transaction  SysMain 

and the last one - event id 7046 - UmRdpService

There is another error in app event viewer.

13:00:13 - App - Application Hang - event id 1002 - program StwPh.exe verze 5.1.12103.2 stopped cooperate with OS

I would say that problem is caused by app - STWPh.exe.

What do you mean?

Thanks.

Jendislav

Hello everybody,

I'm planning to install a new RDS farm with Server 2019. I'm customizing everything I need, but got stuck at the start menu.
How can I hide/remove the integrated Apps from start menu like Settings, Search and Windows-Security.
I'm ok with Settings and Search, but Windows-Security must be hidden before I can deploy this new farm.

Thanks for your help.

windows 2012 r2, hyper-v, clients connect via rds website and then launch a rds session (vdi windows 10 vm). It was working, but then a few users reported being unable to connect. Silly me, I figured "apply latest updates and reboot" and now no one can connect. I updated and reboot the RDS and Hyper-V server (RDS is actually a VM running on the same Hyper-V server).

From the RDS server's RemoteDesktopServices-RDPCoreTS log a connection looks like this:

Event ID 131, the server accepted a new TCP connection from client blah blah blah

Event ID 65, Connection RDP-Tcp#0 created

Event ID 141, PerCounter session started with instance ID 0

Event ID 133 the following network characteristics have been detected for tunnel 8;...

Event ID 132, a channel rdplic has been connected between the server and the client using transport tunnel 0

Event ID 132, a channel rdpcmd has been connected between the server and the client using transport tunnel 0

Event ID 98, a TCP connection has been successfully established

Event ID 100, the server has confirmed that the client's multi-transport capability. (really bad English there BTW)

Event ID 130, the server has initiated a multi-transport request to the client, for tunnel 1

Event ID 130, the server has initiated a multi-transport request to the client, for tunnel 3

Event ID 135, the multi-transport connection finished for tunnel 1, its transport type set to TCP, reason code 3 (no UDP packets received)

Event ID 135, the multi-transport connection finished for tunnel 3, its transport type set to TCP, reason code 3 (no UDP packets received)

Event ID 103, the disconnect reason is 1033

Event ID 102, the server has terminated main RDP connection with the client

I've found articles about RemoteFX and disabling it via GPO and registry values - which I tried to no avail.

HELP!!! please!

Hey Together,

we have a customer with a RDS Terminalserver Farm with 4 2016 RDS Session Hosts located in Azure.

The customer is facing the issue that the desktop icons are flashing, like they are pressing f5 all the time.
Already tried the specific registry key here: 
https://community.spiceworks.com/topic/1978620-rds-2016-desktop-icons-flickers-refreshes. that either did not work.

In addition the users are experiencing that the cursor sometimes start to randomly juming around.
For example, user is typing in the adress field of outlook, and the cursor jumps out of that field and the user has to click in it again to finish typing.

Probably the issue is related to the flickering and refreshing desktop, but not sure.

Best Regards,
Dominic

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 All

Quick Question:

Have a file server in Domain A and need users that have been migrated from Domain A to Domain B to RDP back to a file server in Domain A  (No Trust), what the simplest way of doing this ?

Effectively Domain A = Company 1  & Domain B = Company 2

Thanks

Running Windows Server 2016 Remote Desktop Services (session-based desktops).

Multiple session host servers, one DC, all running as VMs under Citrix XenServer 7.1. The servers are fully updated to present time as of 7 March 2019.

Every few days a user reports that after logging in to an RDS session he does not see his desktop but sees a black screen. When this happens, I can see that some users on that same RDS server still have their session working normally, but every user logging in after this also gets this black screen.

There are numerous references to this problem on the internet. It is apparently occuring since Server 2012 and has never been fixed.

Some people recommend to restart the Windows Audio service. Does not help in my case, never does when it happens to me. Other recommendations were to remove Firefox browser from the RDS session host servers. I did that two months ago and it seemed to help for one week but then it came back. I have not found any other recommendation - there seems to be simply no solution, except restarting that RDS session host server, which is a major inconvenience, it throws out the other users which still work, it takes 10 minutes or more to restart that server, and it can only be done manually. Most often it has to be force-restarted on top of it, as the server is totally unresponsive, and then some users may loose their user profile. Then I have to delete that user and recreate his user profile. Major trouble.

In the last few months I have rebuilt all RDS session host servers from scratch - total new installation, all updates, totally clean. It STILL happens. I have that system running since 2 years, and it has been a problem all the time.

When I try to log in to the console of the offending RDSH I can sometimes not even log in . Sometimes it does let me log in but I also get a black screen as local admin user (both Server\Administrator and Domain\Administrator). In this case, I can bring  up TaskManager via Ctrl+Alt+End and run a command prompt. I can restart services this way and execute other commands, but anything relating to the UI does not show up. Screen stays black.

Managed once to get the black screen off by restarting ShellExperienceHost service but then this logged out all users somehow and corrupted some profiles.

The only applications installed on the RDSH servers are Chrome browser, Thunderbird email client, Libre-Office.

From what I can find on the internet this problem occurs since the release of Windows Server 2012. This is seven years ago. I do not know if this happens to everyone, but there seems to be no common denominator from what I can find, it seems to happens on all sorts of environments, pointing to a bug within Windows Server itself.

From what it seems it is related to the new UI system implemented with Windows 8 (and Server 2012) because I can find no reference to this occurring with Server 2008. I have not run RDS on Server 2008 myself so I have no first-hand experience.

Is there ANYTHING I can do about this? It does NOT seem related to my setup which is really rock-bottom basic. Many users are reporting this as a dreaded issue they hope one day will be fixed by Microsoft.

Can it be related to the virtualization software? Anything having experienced that issue on bare-bone installs of RDSH servers? Any difference with Hyper-V VMs?

WHEN IS THIS GOING TO GET FIXED? THIS IS A PROBLEM SINCE 2012 - 7 YEARS!

I feel forced to start researching for non-Microsoft solutions for RDS type solutions because I simply cannot tolerate non-functional software. To the users it looks like it is me as admin who is not doing his job!

Atradius

When connecting to our RDS service, the user can use their credentials and get past the first screen, to the

Remote (Collection) Icon, but when they click on it it, the following appears:

If you offer solutions, please tell me which server any corrective action should be taken on. Still learning.

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