I have a small RDS setup that consists of a gateway, connection broker, and 2 session hosts.  All are running Server 2016.  Session hosts have the same apps installed and are presenting a remoteapp collection to my users.

I'm having an issue where my RemoteApp users are occasionally being disconnected due to connectivity problems (bad internet, poor wifi signal, etc.) and when they reconnect they are being directed to the alternate session host.  At that point all their apps have to be reopened.    Is it possible to configure the connection broker to 'sticky' a user to a particular session host for a period of time?

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.

RDS apps hangs with error 0xe0464645 in unexpected moments.
I can see above behaviour on basic Windows apps like explorer or taskmgr, third party apps like totalcmd and java apps on jdk 1.8.  Amazingly Chrome browser seems to not fail with this error maybe because lack of user interactions like in apps above.

Error occurs for clients on Win7 and Win 10.
Error details from windows server 2016 log is always the same:

Faulting application name: dwm.exe, version: 10.0.10240.16384, time stamp: 0x559f3907
Faulting module name: KERNELBASE.dll, version: 10.0.10240.17394, time stamp: 0x590285b4
Exception code: 0xe0464645
Fault offset: 0x000000000002a1c8
Faulting process id: 0x1180
Faulting application start time: 0x01d41f5858025678
Faulting application path: C:\Windows\system32\dwm.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 176068bc-37fb-47f6-8bbb-8a8ee6b801d0
Faulting package full name:
Faulting package-relative application ID:
Event ID:1000

Other apps hangs with detials "Top level window is idle"

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-07-19T13:34:46.000000000Z" /> <EventRecordID>4580</EventRecordID> <Channel>Application</Channel> <Computer>RDS.int</Computer> <Security /> </System>
- <EventData><Data>dwm.exe</Data> <Data>10.0.10240.16384</Data> <Data>559f3907</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.10240.17394</Data> <Data>590285b4</Data> <Data>e0464645</Data> <Data>000000000002a1c8</Data> <Data>1180</Data> <Data>01d41f5858025678</Data> <Data>C:\Windows\system32\dwm.exe</Data> <Data>C:\Windows\system32\KERNELBASE.dll</Data> <Data>176068bc-37fb-47f6-8bbb-8a8ee6b801d0</Data> <Data /> <Data /> </EventData></Event>

Hi, 

I have several clients using handheld devices that RDP to WS2012, but on logon they see the WS2012 Start screen (Metro). I need them to logon straight to desktop. I have a .bat script that starts an erp program which does happen, but is obscured by the Metro screen and from their devices it is difficult to minimise to desktop.

In WS2012(R2) on task bar properties there is a navigation tab where this can be configured but this is not available on WS2012.

I've read that RDP should go straight to desktop on login but it's not the case for these users.

Hi All,

Currently running a RDS setup, via the remote app multiple connections can be established however while using RDP only 2 connections can be established at a time. 

Is this feature by design or is this due to configuration/licensing?

Hi there, 

All in the subject really, dont want to get ranty but why is windows 10 such a UI mess of things that just dont work 

Anyway, I'm on a domain, trying to RPD to the DC and this crappy MicrosoftAccount. It dosent work, is it a live account?

It has my domain credentials, but entering the correct password, just fails?

Dear All,

I am new to RDS.

my queries as follows

1. how to give access to our on-premise servers from the internet? (connect to remote PC).

2. I would like to add 2-factor authentication when the user tries to access through the internet

3. only group of users should have access to the group of servers

4. does it require RDSH for above requirements?

5. does it require RDCB for above requirements? 

Thanks,

Shashidhar

I will try explaining the scenario we have there:

We created two RDS collections to seperate desktop sessions from remote app sessions, so in this case we can control who can access which applications:

Collection1: Remote Desktop

Collection2: RemoteApp

Issue 1:

Each collection has it's own UDP (That's by design), so in order to allow users to have the same desktop folder, documents... etc we implemented Folder Redirection to another shared location, and that's worked perfectly.

My question is:

Does that have any impact on performance, because the environment is still fresh now and we don't have much users using it, but I don't know what will happen when the environment grows and users save gigabytes on there desktops?

Issue 2:

The other issue I have here is related to the remote apps:

RemoteApps are installed on collection2 and published inside the desktops in Collection1 by GPO: 

https://blogs.msdn.microsoft.com/dsadsi/2011/11/30/automating-the-silent-deployment-of-remoteapp-and-desktop-connection/

Running a remote app at the first time a user logs in fails at the first attempt, and it works the second time a user tries. I can't figure out what would cause such a behaviour.. do you have any idea?

Thanks in advanced

Housam Smadi

If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!

I am using a remote Server 2016 VPS from a provider and wish to configure a  user account Test to terminate after 1 hour of being disconnected. From the server Admin account I have accessed Computer Management -> Local Users and Groups-> Users -> Test and in the Sessions tab of account properties set Ends a Disconnected Session to 1 hr. However, the disconnected Test session does not close after 1 hr of disconnection. (As shown by Task Manager-> Users which shows the Test account in a disconnected state after more than 1 hr of disconnection.)  I have restarted the server and disconnection still does not occur after 1 hr. Is there something else I need to do?

Dear All,

We have published remote apps through RDS 2016. when user click on the apps RDP file it showing logged in credential didn't work try with new credential

remote computer: connection broker

Need you help!

Thanks,

Shashidhar

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license

I was reading up on RDS licensing but I could not find any documentation specific disaster recovery practices. We have a secondary warehouse location we we would like to setup a second RDS server. This server would only be for disaster recovery purposes when the primary site is unavailable. We'd probably just keep it offline except for updates and DR testing.

Our primary RDS server only has about 2-5 people using it at a time, but we might have as many as 25 or more remoting in during a situation where the primary site is physically inaccessible. Are there DR CALs that can be purchased, or do we need to purchase the CALs we anticipate using in a DR scenario ahead of time, even if that DR scenario might be 4 years in the future?

Also, our two sites are very close and only have a ~5ms ping, so we do have the option of just doing a Hyper-V replica instead of setting up a second virtual machine. My main reason for not wanting to do this, however, is that it seems unnecessary to be replicating all that data offsite, and we have limited bandwidth and want to use it wisely. They are also on different subnets so I wanted to minimize the work required to failover. A secondary machine would already have all of the networking configure, so fewer steps need to be taken to get the secondary site operational.

Im hoping to gain some insight on how RDS handles Printer Redirection, specifically in how printer preferences and printer defaults are applied.  I really would like to understand (as much as is possible, anyway) under what conditions I should expect settings to be saved or not, when they might be reset, etc.  Here's our scenario:

We've set up a RDS server and have multiple client workstations (Windows 7 and up) connecting to the RDS server, with printer redirection checked within the RDP client (using the standard Microsoft supplied mstsc.exe).  On the RDS server, we are not using the Remote Desktop Easy Print driver, due to a couple of the printers manufacturers that we work with that do not support the Easy Print driver.  The printers are connected locally to the client machines, typically via USB (in other words, no network printing).  We install the same version of the driver on both the client workstations and the RDS server.  When the users connect from the client to the RDS server, redirected print queues appear with no issue.  If a printer requires changing the printer preferences and/or defaults, we have had to go through a process of allowing the logged in user to take ownership, take over management of the printer, and then finally setting preferences and/or defaults.  We will then generally take care of other setting changes within the session, such as defining shortcuts and whatnot, which "should" give the system ample opportunity to write out settings and replicate wherever they need to go within the registry.  If a user logs off and logs back in later, the session queues appear, having retained the printer preferences and/or defaults.

However, on occasions that I have yet to identify, sometimes when a user logs in after all of the above has been done and tested and verified to be working, the redirected print queue will all of the sudden "reset" itself, in that all of the printer preferences and defaults are reset back to whatever the default driver configuration is.  Sometimes if we go in and perform all of the steps I mentioned above, then its no longer a problem.  Other times, the settings are only good until I log off.  The amount of time in which the printer preferences hold varies and I have yet to understand why.

This is a setup that we have used multiple times for different clients of ours and have seen this type of behavior in some form over the years since Server 2008 was released. 

I have several specific questions.

• What am I missing/doing wrong/not understanding?  Im fairly certain there's a piece to the puzzle that I dont get, yet.
• Are there any kind of additional logging options available to me to give me any kind of additional clues.  The Windows Event log doesnt really give me anything, unless a printer isnt defined because it couldnt find a driver.  Outside of that, I havent seen anything that was useful.
• When a session printer is defined and printing preferences and/or defaults are defined, where are those setting stored in the registry.
• Is it possible to set up the system in such a way that whenever a session printer is defined, the defaults that are pulled in are somehow custom set.  In other words, if the print queues are going to reset back to some default, is it possible to define what those defaults are.  I realize this may be more of a question geared toward the printer manufacturers, as this likely driver specific.  I guess I'd just like to know what is possible, to potentially avoid issues later.

Any input is appreciated.

Guys,

I want to migrate user profile from 2008 r2 Terminal server to 2012 r2 Terminal server.... How I can I do this without any problem? 

Thanks  

Hi there,

has anybody heard/does anybody know whether the graving COM/.NET bug in KB4345418 does affect Remote Desktop Services deployments or not?

I've installed several Windows Server 2016 VMs last week, made a new RDS deployment and built half of it. The early deployed servers had like May Cumulative Update installed.

Now I want to add the second RDWA server as well as additional RDSHs - and the only thing I get is "Microsoft.RemoteDesktopServices.Common.RDManagementException" during the configuration phase. That means role installation and reboot via Server Manager passes but then it throws at the beginning of the configuration phase.

I've also tried adding the RDMS logging registry values but the expected "RDMSDeploymentUI.txt" doesn't exist in C:\Windows\Logs. The "RDMSUI-trace.log" gets written but doesn't contain helpful info.

As the 2nd RDWA as well as the other RDSH candidates have been patched to KB4345418 meanwhile and since .NET and COM are essential parts of Windows management and operations I suspect there might be a connection here.

I can only pinpoint two essential events that happened after the first RDWA and RDSH were added successfully:

• The RDCB server was HA'ed
• All RD servers including RDCBs as well as the undeployed candidate servers were patched to KB4345418

So either something is wrong/went wrong with the RDCB HA (but I don't get any other errors) or, for me a bit more likely, the hotfix issues are somehow impacting the manageability/deployment.

I've tried to uninstall KB4345418 from the 2nd RDWA candidate plus reboot but to no avail; regrettably, because of the way my deployments are structured, the RDCB servers had already gotten their "dism /Online /Cleanup-Image /StartComponentCleanup" thus making removal of the hotfix impossible.

Maybe it's also something totally different from the hotfix but I'm puzzled and in the dark here, not knowing how to proceed/better diagnose this.

For the time being cutting the whole RDS deployment down and starting fresh is out of the question especially since it is likely I might hit the same problem again.

Maybe someone of you has experience with this exceptions on 2016 or maybe even connections to the dev team regarding the current hotfix situation. Or someone that has patched their servers but is still able to add new RDWAs or RDSHs.

Regards and thanks a lot in advance,

Markus

Hello All,

Weird situation here:

I have one TS server running 2008 R2.

One of our satellite offices uses it to connect to HQ to run an application. That office has about 10 workstations. On 8 of the 10 workstations, the remoteapp is very low quality resolution. Blocky text, mouse pointer is a black box, etc. On the other two workstations, everything is fine.

All 10 workstations are almost exactly the same make and model, if not exactly the same. Same OS, etc.

I initially pointed fingers at the settings on my terminal services server, but since not all workstations have the issue, I am now at a loss. 

Everything was fine just a few weeks ago. I cannot confirm, at this point, if all workstations have the same exact MS updates, or, if it was an update that caused the issue.

Besides that, is there anything else I can check to see where my issue is? 

Hi. We have a new WS2016 RDS deployment (VMs on Hyper-V):

 - 2x WS2016 RDGW in NLB

 - 2x RDCB in HA configuration

 - couple RDSH servers

The problem is that in 30-50% of the connection attempts via these gateways, the connection is stuck at the "Configuring remote session" message. The connection is never successfully estabilished when this happens and it is closed without any error couple minutes later. When you try again (or just immediatelly cancel the connection and reconnect), the connection may or may not go through.

When this problem happens, I can see there's single HTTP connection on the RDGW that accepted the connection with 0 bytes transferred in either direction. There are no related errors at this time.

Can anyone help? Btw. this problem also happens when connecting to a different single-host RDS deployment through these gateways.

I suspected the problem might be in the NLB, but removing either of the gateways from the NLB configuration (and from RDS farm) doesn't help, the issue is still there.

Rebooting the gateways helps for a short while (hours), but then the issue is back.

There are some other errors on the gateways, but these don't correlate to the connection attempts (event 210, source terminalservices-gateway: "Http transport: IN channel could not find a corresponding OUT channel" with no other details).

RDP clients are various ... W8.1, W10, Mac...

Hello Every one,

I'm implementing a RDS 2016 solution and I have been trying find a MS article around Recommended RDS Capacity planning and Sizing. But Im surprised that there is none of that sort. can anyone please share any link on this or please provide suggestions how it can be planned, below are my questions.

1. How to plan RDS server sizing?

2. How many connections can each RDSH server can take(i understand that it can be 999999 and depends on compute of the server),  there must be some calculation we should go with to optimize the traffic.

3. During login storms how many parallel connections can each RDgateway can handle?

Thanks,

Shaikh