I am looking at setting up some RDS servers. I will need 2 different ones, but will probably end up building 2 of each. The user groups are totally different so the needs for each box such as programs will need to be different.

Is it a bad idea to run the Session Host servers as VM's as opposed to running that on the physical box?

I am looking at getting a gpu to use remotefx on server 2016 for the VM's. The users are not doing any cad cam work, just basic web browsing with the occasional video to watch. I would prefer to put a GPU in to help keep the cpu usage down. Is a P4000 from Nvidia a good card to use?

If running the session host in a VM is a bad idea am I better off just using the GPU on the physical host and using the Group Policy to force the RDS users to use the gpu for video acceleration?

Thank you

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 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

Hi Guys,

From last 3 months i am having issue with my Windows Server 2012, that after login it (RDP or VMWare Console), screen goes black with a cursor. I tried use Alt+Ctrl+End trick to get the task manager but that is also not appearing. I am using vSphere Client version 6.

Also i want to add, that if i login to Safe mode, i can see the display. (No issues)

Many Thanks.

Areeb Hassan

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:

• to auto login the account - i know not secure, but could not get it to work
• remove user profile picture - was not able to get the image removed.

This is a picture of what is displayed:

Thanks for any help on this.

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,

So nothing like being on the cutting edge......

I have been testing Server 2019 RDS and so-far-so-good apart from an issue with the Windows Search Service.

It appears that in Server 2019 each user gets their own search database EDB file in their profile path (appdata\roaming). e.g.

C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-3901271148-1553943383-1671037523-1629\S-1-5-21-3901271148-1553943383-1671037523-1629.edb

When they log on and log off; this is connected to the search service and the following event log is generated

Source:ESENT
EventID: 326
SearchIndexer (10896,D,50) S-1-5-21-3901271148-1553943383-1671037523-1629: The database engine attached a database (3, C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-3901271148-1553943383-1671037523-1629\S-1-5-21-3901271148-1553943383-1671037523-1629.edb). (Time=0 seconds)

Unfortunately it appears that this process is not very stable and on some logons the database in the users profile does not attach and the following error is generated

Source:Search
EventID: 3057
The plug-in manager <Search.TripoliIndexer> cannot be initialized.
Context: S-1-5-21-3901271148-1553943383-1671037523-1629 Application

Source:Search
EventID: 3028
The gatherer object cannot be initialized.
Context: S-1-5-21-3901271148-1553943383-1671037523-1629 Application, SystemIndex Catalog
Details: The specified object cannot be found. Specify the name of an existing object.  (HRESULT : 0x80040d06) (0x80040d06)

And a few more similar but related errors....

No subsequent logon/off will succeed in attaching the database until the Windows Search service is restarted

I am not testing with User Profile Disks or Roaming Profiles
There is no AV on the server

Any ideas?

Andy

Andrew

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 All,

I have a number of VDI collections in my RDS 2016 deployment, personal desktops each with some base applications and obviously at a specific patch level (eg 1803).

Has anyone established a process to update the personal VD template image (updated apps/new Windows10 patch level) for existing collections?

WSUS will eventually take care of the patch level, but ideally I'd like to keep the template current.

Thanks!

I have a Windows Server 2019 as a Remote Desktop server, with an app that relies on Word Viewer 2003 for printing.

All printer redirect connect nicely, Clients are Windows 7 and Windows 10 and all work as it should, until I try to print. - Word Viewer shows only printer installed directly on server the user has rights to, and blank printer spot if there are no printers. (I uninstalled them). 

I even tried set up that only default printer redirects via GPO, but that didn't work either.

Does anyone knows if there was some permission change on Server 2019? Didn't have that problem before.

Hi Windows 10,

I am having an issue with Windows 10 - every day.

But last 3-6 months, remote desktop connections fail with a black screen on my network!

Now I have started to feel true hate towards this OS, as this error, now seems to settle as a forever error that will stay?!

Issue is using RDP to other Windows10 device on my network, now serves a black screen after connection has been idle for some time - or it just turns black, just as i log in?!

I am able to remove black screen - only if disconnect, and reconnect. But again. After some time. I get a black screen again?!

As Windows continues with their disapointments towards the proffesionals on Windows10 since release.

This error in question, I really want fixed - to be working as it has always been - since the dark ages . RDP should just work! Every time - all the time. 

So anyone - before I look up a lawyer to fight this - Please assist with the right trick to get this fixed......

Awaitng that true fix------ anyone?

Regards, Kato.

We have a server farm of 12 Session Hosts and a Broker.  We have a major issue now that I can't find any info on.  Our users will start complaining they cannot get on the farm.  When you try and RDP you get Cannot connect, the two computers cannot connect in the time.  If I go into Hyper-V and go to this machine, I need to restart it.  That is the only way we have found to fix this issue.  However, when I clock on start and then the Power button, the menu that pops up is blank.  Let me be perfectly clear, this is NOT any admin setting or GPO.  I am the administrator and I do not have this set.  Also, if you restart, then the shutdown menu again works and it is ok for a while.  Soon after, this returns.  This is becoming a major problem for us as this started happening about shortly after the 3/19 patch KB4489889.

Anyone have any words of wisdom for this?  I have tried to find anything that relates to this.  And just to help I have included screenshots of the remote error and what the start menu shutdown options look like.

Brad

I'm trying to set up 2019 RDS to replace our 2008R2 Terminal Server.  I used this paper as a guide, but did not publish any apps, just using session based desktops: https://gallery.technet.microsoft.com/Windows-Server-2016-Remote-ffc383fe

I have a broker server, gateway server, web server and two session hosts.  Licensing server is running on the broker server but not activated yet.  I also haven't enabled the gateway server yet as I'm just testing internally. So far I have just one collection pointing to one of the session host servers. We are not testing any remote apps, just session based desktops.

Here's the problem:

• I'm able to initially get two users connected (either directly on the broker server, or through the Remote Desktop Web Access page) If a third tries to connect, it hangs at a black screen and eventually gives the message "failed to reconnect to your remote session.  Please try to connect again".  I would expect to see a message about not enough licenses or do you want to bump someone else off.
• During the black screen time, and before the error message, the active two users get bumped off, but then automatically reconnect.
• If I then log off one or both of the active users, I'm unable to log anyone into the server again.  They all get the black screen and the error message.  At this point I'm only able to log into the server on the console.  The only way to fix this is to reboot the broker server, and the cycle begins again.

Here's what shows up in the Event Viewer on the Broker server:

• When active users get bumped out theTerminalServices-LocalSessionManager log shows an error like this: “Session 3 has been disconnected, reason code 3489660929”. Also shows reason codes 12 and 0.  Also get this error in the same log: “An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070102)”

• In the RemoteDesktopServices-RdpCoreTS Operational log, we get lots of weird errors:

-TCP socket READ operation failed, error 10054”; “RDP_TCP: An error was encountered when transitioning from StateUnknown in response to Event_Disconnect (error code 0x80072746).”;

-RDP_SEC: An error was encountered when transitioning from FStateProcessingData in response to FEventPostReceiveFailed (error code 0x80072746).”

-RDP_SEC: An error was encountered when transitioning from FStatePassthrough in response to FEventCheckAndCompleteReadsFailed (error code 0x8007139F)”.

-Failed InputMgr->GetHandles' in CUMRDPConnection::GetInputHandles at 4043 err=[0x80070102]”; “'GetInputHandles Failed' in CUMRDPConnection::GetInputHandles at 1401 err=[0x80070102]”

Here’s what I’ve tried:

• All servers are updated
• Removed and recreated my collection
• Rebooted many times
• Restarted the Windows Audio service
• Tried both from the RD Web Access page and directly connecting to the Broker server
• Tried disabling firewalls on all RDS servers

I’m kind of at a loss and it’s driving me bananas. Any suggestions would be much appreciated!

George Moore

Hi,

our workstations with Windows 10 pro are in this weekend updated to version 1803. For main system we use RemoteAPP aplications on Windows server 2012R2 (Windows server 2012R2 is full updated). After update on client station are RemoteAPP slower, and  right mouse button is unresponsive, or react verly long time... 

It is a big problem for us.

PS: after replace mstsc.exe and mstscax.dll from older version Windows 10 is all OK. but this is not a solution.

Thanks.

I have a RDS 2016 Farm, with 2 CB's and 8 RSH servers. There are 4 collections with 2 RSH in each collection.

The issue is when I connect and launch the .RDP i created for one session collection, all of the other RSH servers are provide as the server holding the .RDP session which of course they are not.  the session collection has a set of apps setup on only two servers which are added to the collection (no other RSH are available in the collection)

How do we isolate the RSH/collection from the other RSH/collections so only the servers supporting the .rdp are queued?

RD Licensing Diagnoser has this error message: 

The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server --- does not have any installed licenses with the following attributes:
Product version: Windows Server 2016
Licensing mode: Per User

RD Licensing Manager shows: 

Windows Server 2016 - Installed RDS Per User CAL  | Open (license program) |  10 (Total Licenses) | 0 (Available) | 0 (Issued) | Never (expiry date) | 3 (Keypack ID)

Why are 0 licenses available? The licensing agreement shows WINRMTDSKTPSRVCSCAL 2019 SINGLE NL USRCAL 6VC-03748  10

Is it because these are designated 2019? In my experience, I could always install later version licenses on a previous version of Windows.

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