I have an external user who connects to a remote app via RdWeb. They had no issue until last week and no changes were made on the terminal servers.

THE ISSUE:

When they launch the remote app, the user gets a black screen if you click details. They can RDP to the server fine (using the Connect to another PC tab in IE).

The mstsc.exe process has to be killed via Task Manager. 

Another user in their office is having no issues.

Things I have tried:

1. Had the user with issues try from the PC of the user without issues. Same problem.

2. Had the user connect to 3 instances of this remote app in 3 different collections. 1 uses User Profile disks. 1 does not and sits on the same network as the previous. 1 does not use profile disks and sits in our DMZ. The user can get a successful connection from the server in the DMZ but the speed is an issue. 

3. Looked for a profile disk for the user on the network share and there was none (the user is in our Guest child domain which is not a 2 way trust), there was no profile disk, but there WAS a profile with the username and .backup on the actual terminal server.

4. Deleted the local user profile on the both internal servers and had the user try again. Same result.

5. Had the user RDP to the server and launch the app and it worked without issue. 

I am thinking it is related to the user's terminal server profile because the issue is repeatable from another user's workstation. However, the user is able to RDP to any of the terminal servers and work fine. 

The difference in the server in the DMZ and the internal servers is that the server in the DMZ uses a different encryption/compression policy. The internal policy forces the encryption level to "low", does not use an encryption algorithm and is set to not require NLA. The server in the DMZ was specifically created with a different encryption policy to resolve a previous issue with external users getting a black screen to the internal servers. The internal servers go through a Cisco WAAS in some cases and the internal policy was set to the recommendations for this setup. 

Keep in mind though, that everything worked fine last week and everything still works fine for everyone except this single user.

Any insight or steps for further troubleshooting would be appreciated.

Hi

I am currently setting up a 2016 RDS server deployment using version 1607. The problem we are having is the trying to hide individual settings pages in the immersive control panel when using gpedit.msc Computer Configuration > Administrative Templates> Control Panel > Settings Page Visibility. However it doesn't work with version 1607. Is there anyway to get this to work as we need to open up display and screen saver settings as would like our users to access this. Currently we are having to lock down both the control panel and the immersive control panel using User Configuration > Administrative Templates > Control Panel > Prohibit access to control panel and PC settings as we dont want them to access other stuff in PC settings such as windows update  

Can anyone provide any suggestions\workarounds  

Hi,

Our production environment is RDSH windows server 2016. I just want to know how RDSH server worked with RDS broken server. does they communicate with any service? How I can troubleshooting it if one of them broken.

By the way, if one of the server broken. does the RDS console still can be used? from my testing if one of them broken is impossible to lauch the RDS console.

Best Regards,

Apollo Ye

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

I have asked this question many times before as we seem to be experiencing some problems with icons flickering on the desktop on our RDSH Servers.  It started way back in server 2012 and since upgrading to server 2016 we still have the same problem.  The flickering occurs on the local LAN and from remote locations.

What have I done so far and it doesn't resolve the situation:

1.  Ensured that bitmap caching is turned off.

2.  dword NoRemoteChangeNotify.

3. Always show icons, never thumbnails

4. Enabled Always show menus

5. Enabled Display file icon on thumbnails Enabled Display file size information in folder tips

6. Enabled Display simple folder view in Navigation pane

7. Enabled Display the full path in the titlebar (classic folders only)

8. Disabled Hidden files and folders Do not show hidden files and folders Hide extensions for known file types

9. Disabled Hide protected operating system files (Recommended) Enabled Launch folder windows in separate process

10. Disabled Remember each folder's view settings

11. Enabled Restore previous folder windows at logon

12. Disabled Show drive letters Enabled Show encrypted or compressed NTFS files in colour.

13. Enabled Show pop-up description for folder and desktop items.

14. Enabled Show preview handlers in preview pane Disabled Use check boxes to select items Disabled Use sharing wizard (Recommended) .

15. EnabledHKEY_CURRENT\USER\SOFTWARE\Classes\CLSID\{031E4825-7B94-4dc3-B131-E946B44C8DD5} on user logon.

16.   RDP client version is current and up to date on all client devices.

As I have stated none of these have worked.

Here is a video of the flickering:

https://photos.app.goo.gl/EvNp8jHLG2Z6Hsjh6

Quite frankly I am completely lost about this situation.  On normal services servers which maybe one or two people connect to the problem is not there.  With servers that have many connections it is there.  This also occurs regardless of the OS you are connecting from.

Many thanks in advance.

Chris

For some time I have been investigating flickering both in our 2012 Terminal severs and now the same thing in our 2016 Terminal servers.  I know that flickering problems are well documented around various forums and help portals but every suggested fix has done nothing for our situation.  Here are the fixes so far that have not worked:

Group Policy:

Always show icons, never thumbnailsEnabled Always show menusEnabled Display file icon on thumbnails Enabled Display file size information in folder tips Enabled Display simple folder view in Navigation pane Enabled Display the full path in the titlebar (classic folders only) Disabled Hidden files and folders Do not show hidden files and folders Hide extensions for known file types Disabled Hide protected operating system files (Recommended) Enabled Launch folder windows in separate process Disabled Remember each folder's view settings Enabled Restore previous folder windows at logon Disabled Show drive letters Enabled Show encrypted or compressed NTFS files in color Enabled Show pop-up description for folder and desktop items Enabled Show preview handlers in preview pane Disabled Use check boxes to select items Disabled Use sharing wizard (Recommended) Enabled

HKEY_CURRENT\USER\SOFTWARE\Classes\CLSID\{031E4825-7B94-4dc3-B131-E946B44C8DD5} on user logon.

As I have stated none of these have worked.

Here is a video of the flickering:

https://photos.app.goo.gl/EvNp8jHLG2Z6Hsjh6

Hi all,

             putting together a HA RDS farm design - and im having trouble finding guidance on sizing for RD Connection brokers, RD Web and RD Gateway servers.

I get the for the session hosts, it is very dependant on what is running within the sessions and hence, the lack of hardware sizing guidance.

For the other roles it would be nice to have some sort of general advice - i.e. 1 connection broker per 1000 users, 1 RDGateway per 200 users etc....

Does anyone know if sizing guidance such as this exists? (and I just haven't been able to find it)

Last week, we retired our Remote Desktop 2012R2 system and launched Remote Desktop 2016 hosting Office 2016 on RDSH 2016 servers.  We have several hundred clients running a variety of systems including IOS, Windows 7, Windows 8.1 and Windows 10 Professional.

A few days after launch, some of our Windows 10 users issued complaints that maximizing, resizing and moving around Remote Web App windows causes all types of distortion including a disappearing window that cannot be maximized again and issues where only a small portion of the full window is displayed.    

A sample is shown below where portions of Excel 2016 are cut off in a remote web app session on Windows 10 Pro, version 1803.

We have combed the internet for a fix.  We've tried updating display drivers, Docking Port drivers, updating Windows 10 Pro from version 1709 to 1803.  We've tried unchecking 'use Bitmap cache' in the RD Client.  We've adjusted display resolution, all without any luck.  None of these users have a dual monitor setup.

The issue has cropped up on docked/undocked Dell Latitude laptops.

Hello,

We are currently using office 2010 on server 2012 r2 demote desktop

Any time someone tries to open an attachment from inside outlook they get a file corrupted error, but if they are in the office, using outlook and try to open the same attachment it works. This includes administrators on remote desktop

On top of this users are unable to open some files in remote desktop, either excel or word, but when in the office and using their own computer all files open correctly.

We recently moved our remote desktop to a different, more powerful/better server and everything was set up the same in terms of the remote services, but this server does have a couple of additional services running that weren't on the old one.

Any ideas, everything I have found here before has had no affect on this problem.

Thanks

Hello everyone,

I'm looking for some guidance on how to disable SSL 3 and TLS 1.0 on a 2012 R2 box acting as a RD Gateway, Connection Broker & Licensing Server.  I have disabled SSL V2 successfully via IIS Crypto. When I disable SSL V3 though my Remote Apps stop working - specifically the connection to the remote desktop host server fails. I didn't try disabling TLS 1.0 yet, as I haven't conquered SSL3. We are using a 3rd party signed SSL cert.

Any have specific experience doing this? 

All

I have a server with Windows Server 2012 R2 Standard. When I try to reach it from another computer over remote desktop connection, I frequently get error "Remote desktop can't connect to the remote computer for one of these reasons..."

The weird thing is that the message does not always pop up.  And if it pops up and I keep retrying instantly, I eventually get through...  Even more weird is that it mostly does not work in the morning...  In the afternoon the connection mostly succeeds at first attempt.

I have no idea about the root case.  It does not matter if I use the computer name or the IP-address.  Same issue turns up on other computers from which I try to connect to that specific server.  The server does respond on PING-command.

Does someone knows the root cause of this issue and a permanent fix?

Regards
Ino

Hi, I am getting this message when one of our users connect to the RDS Host server:

Error during driver installation. Result = 0x80070422 for devnode"TERMINPUT_BUS\UMB\2&2C22BCC9&0&SESSION137MOUSE0"

Event ID 121:

Hello,

I set up an RDP farm with Broker.  We are running server 2008 R2.

I tried to make a SAN cert in our Enterprise CA but every time I adopt the cert for the RDP connection it still says Certificate Mismatch.  It shows the server name on the RDP Cert and not the farm name.

https://blogs.technet.microsoft.com/isablog/2011/10/09/how-to-generate-a-certificate-with-subject-alternative-names-san/

This is the article I used.   Has anyone else had this problem before?

Thanks,

Jason

Jason Munsterteiger

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.

Hi all,

 I have set "per session" IP virtualization on the windows 2012-R2 server.

My question is aboutthe behavior of IP virtualization if the range of IP addresses in the pool is exhausted.

Experiment description:

1. Virtualization parameters used (3 addresses in the pool):
   
2. 4 users are logged-in (last logged user1 has NIC address, because pool is exhausted):
3. Logoff user with 104.0.2.51
   
4. Login other (Administrator) user
   

As you can see - Administrator has obtained Nic IP address (192.168.56.1), although 104.0.2.51 was released in step c). I supposed that released address should be reused. But it is not. From this point only Nic address is assigned to the new users.

Q: Can server reuse the released virtual IP address for the next logged user instead of using Nic address?

Thanks for your answers

-Marian

Atradius

I have 2 different customers that both have 1 PC each that will not run RemoteApps from their terminal server.  This started on about 4/15/2018 for the first customer, and the second customer had the issue since at least 4/23/2018.  These are established Remote Desktop Services installations with other PCs able to run the apps fine, and these PCs were able to successfully run the RemoteApps previously.

When they attempt to run the RemoteApps, it immediately pops up an error message stating "Your computer was unable to connect to the remote computer.  Try to reconnect. If the problem continues, contact the owner of the remote computer or your network administrator."  However, both workstations can still successfully open a Remote Desktop Session to their respective terminal servers.

I have gone through Event Viewer on the Remote Desktop Services servers and could not find any correlating events. I searched through Application, System, Security, and all of the Remote-Desktop*, RemoteApp*, RemoteDesktop*, and TerminalServices* logs in Applications and Services Logs/Microsoft/Windows/.

On the client PCs, I do find a correlating event in Microsoft-Windows-RemoteApp and Desktop Connections/Operational. Example:

At the first client, the Remote Desktop Services server is Windows Server 2016 and the workstation is Win 10 Pro.

At the second client, the Remote Desktop Services server is Windows Server 2012r2 and the workstation is Win 7 Pro.

Any and all help would be appreciated.

Thanks,

jeff

We came across this RDS access right / authorization anomaly two days ago.

A user in the AD wanted to open an RDS session in a server (let's call it serverA) which is Windows Server 2012 R2.  He got the following message:
"The connection was denied because the user account is not authorized for remote login."

This is normal because his AD account was not a member of "Remote Desktop Users" group in serverA.

I then added his AD account into the group. *Four hours later*, when he tried to open an RDS session again, he still got the same error message!

I have gone through everything, every group, etc but I could not find the reason.  Then I took another computer, told him to log in and then told him to open an RDS session from there to the same serverA.  This time it worked!  And almost immediately when he tried to open the RDS session again from his own computer, that worked too!

What the hack is this anomaly?  Was there a workaround without having to have another computer to open RDS session first?

I think if he had closed and re-opened Windows session in his own computer, that would have worked too.  But of course, he had too many programs running at that time that it was impossible for him to logout & login again.

And I also think this issue is similar to "network shared folder still rejects access" issue:

simply put, it's like this: a user was rejected when he tried to access some network folder without authorization.  Then the access was later on granted by domain admin but all his attempts to access the same folder are rejected.  He has to reopen his Windows session to get around this.

Are these two issues all related to problem in Kerberos?

Pallab Chakraborty

Hi,

When I'm trying to deploy RemoteApp and Desktop Connections through GPO, it works but then it fails to update.

Start-Process -FilePath rundll32.exe -ArgumentList 'tsworkspace,WorkspaceSilentSetup', "\\shares\feed.wcx" -NoNewWindow -Wait

the Feed.wcx file:

<?xml version="1.0" encoding="utf-8" standalone="yes"?><workspace name="Enterprise Remote Access" xmlns="http://schemas.microsoft.com/ts/2008/09/tswcx" xmlns:xs="http://www.w3.org/2001/XMLSchema"><defaultFeed url="https://remote.domain.com/RDWeb/Feed/webfeed.aspx" /></workspace>

Applying the previous works perfectly for the first time, but when I update the connection from Task Scheduler it fails with the following error in event viewer:

Now, when I manually add the connection in control panel, the update task works normally without any issues.

Do you have any idea why silently deploying the connection causes an issue with the update task?

Thanks in advance,

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!