RDP and left-handed mouse users

September 7, 2012, 1:34 am

≫ Next: mapping specific drives to specific users on their RDS RemoteApp Session

≪ Previous: RDP Requirements für Server 2016

$

0

0

Hi there,

I'm a left-handed person. So I use the mouse with my left hand and naturally I use "Switch primary and secondary buttons" mouse control panel option.

When it comes to RDP connections, I almost always connect to the desktops where "Switch primary and secondary buttons" is set for right handed people. When I'm inside an RDP session the mouse stops respecting my mouse settings and apply guest desktop settings which creates a lot of confusion to me.

Is there a way to setup my RDP client so that it automatically handles right vs. left buttons translation ?

---

mapping specific drives to specific users on their RDS RemoteApp Session

November 13, 2018, 12:22 am

≫ Next: 2012R2 RD Connection Broker -> session-host connection established by IP or fqdn?

≪ Previous: RDP and left-handed mouse users

$

0

0

We are trying to map specific shared folders to specific users logging onto the RDS Server

we have 

RDS Server - "Server02"

5 Users who login to this RDS using RemoteAPP

User01
User02
User03
User04
User05

All users are memeber of Security Group "RemoteUsers"

We have File Server - "Server01"

And all 5 users have a shared folder assigned as below

User01 - \\server01\User01$
User02 - \\server01\User02$
User03 - \\server01\User03$
User04 - \\server01\User04$
User05 - \\server01\User05$

What we are trying to acheive is

When "User01" logs on to the RDS Server "Server02" we need to map drive letter S to "\\server01\User01$"

This is only specific to "server02" hence we have enabled"loopback policy" on this specific server. 

How do we achieve this mapping specific to this user, specific to this server?

2012R2 RD Connection Broker -> session-host connection established by IP or fqdn?

November 18, 2018, 8:33 am

≫ Next: Shell Extension for all users on a terminal server

≪ Previous: mapping specific drives to specific users on their RDS RemoteApp Session

$

0

0

Hi,

i'm trying to extend a Remote Desktop environment, consisting of an RD Gateway server and 2 Session Hosts. I came across a behavior when establishing the connection to the session hosts that I can't quite explain.
In my understanding, the connection-sequence is as follows: The client establishes a connection to the connection broker. This decides which session host is suitable, and returns the corresponding host, stating the IPv4 address and fqdn. (I use the RDP file generated via RD-Web).
Although I could not find a clear statement, the behavior seems that the client is now trying to establish the session based on the IPv4 address.
With this behavior, I now have 2 use cases that cause problems:
Access to RD-Farm via DirectAccess: After DirectAcces can not directly address IPv4 addresses, the connection will fail. A direct RDP connection to the session hosts specifying the fqdn works fine.
The second case concerns a NAT-linked external network segment. Although the DNS of the foreign network responds with the correct addresses from the transfer network, here too it seems that the client uses the internal addresses reported by the Connection Broker.

I am now at the end of my knowledge, and on the one hand would ask for your opinion on my stated behavior. Of course, I also gladly accept a solution proposal. Maybe there is a way to force the connection to the session host via fqdn. That should actually solve the problems described.

Thank you very much for any help

Shell Extension for all users on a terminal server

November 15, 2018, 7:08 pm

≫ Next: RemoteApp Connection Freezing

≪ Previous: 2012R2 RD Connection Broker -> session-host connection established by IP or fqdn?

$

0

0

I am trying to set up an application on a Windows 2008 R2 Remote Desktop server. It is a fairly old application, and we are moving it from desktops to a terminal server (.....long story......domains merging.......legacy apps). There is a component of the application which just refuses to play nice. The application is a document management system (TechnologyOne ECM), and when you install it it adds a 'Send To' entry to Explorer. The idea is you right-click a file, select Send To ECM, and ECM opens up with the file ready to be registered.

The 'Send To' entry isn't a normal part of the application install - you need to do a custom install and select it - but on the image we apply to our PCs it wasn't installed, so whenever we re-image a PC we just uninstall this application, reinstall it and the missing Send To target works just fine. But I can't get it to work on a terminal server. I have tried the uninstall/reinstall trick, but this does not help. I have created a brand new VM and installed the application fresh, but this hasn't worked either  I have grabbed a copy of ShellExView and I can see that this component is listed as an installed shell extension. What normally happens on a PC is when a user first logs on, setup for this shell extension is triggered and the appropriate entry is added to the Send To menu. On a terminal server, this first-logon process does not seem to be being triggered for anyone other than the first user to log on.

I logged onto the terminal server as admin, and did a regsvr32 on the dll in question. The next time a user logged on to the terminal server, the first-logon process was triggered and the Send To entry was properly added and configured for that user, and that user was able to right-click a file, select Send To ECM and ECM opened as it should.

However, the first-logon process has not run for ANY subsequent users logging onto the terminal server. I am at my wit's end.....I have spent hours combing through Process Monitor logs......countless uninstall/reinstalls.......countless rebuilding-of-the-terminal-server-and-start-again episodes. Nothing I seem to do will make this shell extension register properly for anyone other than the first user of the terminal server.

If anyone has any ideas I would be most grateful.

RemoteApp Connection Freezing

November 2, 2018, 7:23 am

≫ Next: RDS 2016 RemoteApp – Orphaned session

≪ Previous: Shell Extension for all users on a terminal server

$

0

0

Hello,

Sometimes when connecting to the RemoteApps from RDWeb site connection is freezing and had to manually kill the connecting screen. If I relaunch the application it would work.  The below screen keeps spinning.

RDS is on windows server 2012 R2. When users trying to launch they noticed this issues.



Please suggest me how can I fix this issue

---

Shekar

RDS 2016 RemoteApp – Orphaned session

November 13, 2018, 3:38 pm

≫ Next: Surface users being asked for Creds when opening apps via RemoteApps

≪ Previous: RemoteApp Connection Freezing

$

0

0

We seem to have new issue developing with multiple users now reporting the problem.

It seems very similar to the many RemoteFX issue that have been experienced over the last year and wondering whether a recent windows 10 update has caused this.

 

Connecting directly to the users computer the remoteapp seems to be running but nothing happens visually when trying to use the app/no reaction to mouse or keyboard input.

 

At the same time, shadowing the app from the backend, it look to be running normally.

If we Control the session is can be used normally but nothing we do is being relayed to the client. To them the app is sitting on the same screen as it was when it stopped accepting input.

It is like RemoteApp clients has lost its connection but still thinks its connected; very weird.

 

We are within Azure so there are factors such as Accelerated Networking and Azure Load Balancers but just wondering if other may have seen this behavior of late.

Surface users being asked for Creds when opening apps via RemoteApps

November 14, 2018, 7:52 am

≫ Next: RemoteAPP after windows 10 update 1803 are slow and right mouse button is not responding (it reacts only sometimes)

≪ Previous: RDS 2016 RemoteApp – Orphaned session

$

0

0

Hello,

We have a couple of users in IT using Surface pro's.

When connecting to apps via RemoteApps they get a security pop up....

"The Credentials that were used to connect to "Server name" did not work. Please enter new credentials.

It has the correct user name already. and if i enter the password then it connects fine.

If connecting to apps on a windows 10 or windows 7 laptop we get no security pop up the app just opens up as expected.

It's only on the surface.

Not sure why this is just happening on the Surface?

RemoteAPP after windows 10 update 1803 are slow and right mouse button is not responding (it reacts only sometimes)

May 2, 2018, 7:30 am

≫ Next: Slow typing in MS Access through Remote Desktop

≪ Previous: Surface users being asked for Creds when opening apps via RemoteApps

$

0

0

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.

---

Slow typing in MS Access through Remote Desktop

November 14, 2018, 3:10 am

≫ Next: Roaming profiles not being fully removed after logoff

≪ Previous: RemoteAPP after windows 10 update 1803 are slow and right mouse button is not responding (it reacts only sometimes)

$

0

0

We have a remote office that has about 5 users that use a remote desktop connection back to our main office to access an Access database. There are normally two or three in here at all times and normally there are no issues. We have a 100Mbps connection between offices and the server is 2008R2 running the Terminal Services.

I have one computer that types extremely slow but only when using Access on the Terminal Server. Word/Excel work fine as does notepad and any other program. For some reason it is only Access through Terminal Server. I can have this user go to another computer and it works fine. I can have this same user log on as someone else at her computer and it still runs slow. It is just the remote desktop connection from this one computer and only when using Access.

Has anyone seen anything like this?

Roaming profiles not being fully removed after logoff

November 14, 2018, 2:10 am

≫ Next: Redirecting a COM port grater than 32?

≪ Previous: Slow typing in MS Access through Remote Desktop

$

0

0

Our users log into a 2016 terminal server with roaming profiles - set in Group Policy to remove profiles upon logging off.

We have been having a few profile issues, and having looked into it, when the user logs off, part of the profile is being left behind (c\users\username\appdata\roaming\appname). Then when the user logs back on again, it creates a new profile entry (username.domain.001, username.domain.002, username.domain.003, etc).

Is there a way to stop this from happening? It seems that an application isn't closing down correctly when the user logs off, and then leaves some files behind (unfortunately this is an app that our users need).

Any ideas??

Redirecting a COM port grater than 32?

November 9, 2018, 12:18 am

≫ Next: RDS 2016 - TLS 1.2 Supported on Connection Broker Connections?

≪ Previous: Roaming profiles not being fully removed after logoff

$

0

0

I'm using COM port redirection via RDP. If I assign a COM port number smaller than 32, redirection works fine. I log on to the server and access the device that is connected locally. However, if I assign a COM port greater than 32, I can't access the device from RDP. I get an error "The port COM100 does not exist".

So, is there some limit to RDP com port redirectoions?

RDS 2016 - TLS 1.2 Supported on Connection Broker Connections?

November 19, 2018, 2:00 am

≫ Next: How can I make the client by the connection quality of lan10mkps forcely under Windows Server 2012 R2?

≪ Previous: Redirecting a COM port grater than 32?

$

0

0

Okay, we currently have an RDS 2016 Configuration, with the following:

- 1 x RDS 2016 License Manager server

- 2 x RDS 2016 Gateway/Web Access servers

- 2 x RDS 2016 Connection Broker servers

- 4 x RDS 2016 Session Host servers (2 x Session Hosts on load-balanced servers)

The RDS 2016 Connection Broker server is configured in High Availability Mode, and stores it's database on a SQL 2016 Cluster. The initial setup doesn't allow you to specify SQL 2016 *until* you later configure CB to be in High Availability Mode, so it's my understanding that it initially uses a WID (Windows Internal Database) and continues to do so even after configuring High Availability Mode?

Is there any way of "removing" the dependency between the CB and WID, as this TechNet Article seems to suggest that TLS 1.2 can't be configured if WID is involved in the installation?

https://support.microsoft.com/en-ca/help/4036954/disabling-tls1-0-can-cause-rds-connection-broker-or-rdms-to-fail

The reason for asking this, is that we configured the SCHANNEL registry settings to disable everything apart from TLS 1.2, and this broke the connection between RDS and the Connection Broker. The only way to "recover" this was to re-enable TLS 1.0 (TLS 1.1 didn't work).

Any ideas appreciated.

Many thanks.

How can I make the client by the connection quality of lan10mkps forcely under Windows Server 2012 R2?

November 13, 2018, 1:27 am

≫ Next: Default value for session disconnect because of network disconnection

≪ Previous: RDS 2016 - TLS 1.2 Supported on Connection Broker Connections?

$

0

0

Hello,

I made a virtualized host here and enabled remotefx. The client is Win7, rdp8.1 protocol. When I use the remote desktop, I need to manually select LAN 10 Kmps connection quality to connect to the remote desktop. When using automatic detection of connection quality, I stop to estimate the connection quality and exit. . Similarly, when I use rdweb pages, I stop to estimate connection quality and then exit.

May I ask what I can do to solve this problem (similar to remote connection using LAN connection quality)

I would like to express my thanks for any advice and help you can give.

Default value for session disconnect because of network disconnection

November 19, 2018, 5:50 am

≫ Next: When using RDP to play an FPS or similar game, how do I allow myself to turn around fully within the game itself?

≪ Previous: How can I make the client by the connection quality of lan10mkps forcely under Windows Server 2012 R2?

$

0

0

Hello everybody,

I am searching for the default value after which amount of time, or possibly count of packets a rdp session is getting disconnected.

We have keep-alive enabled and set to 1 (minute).

We also have set the limits for idle state and so on, but my question is really basic.

If I pull out the cable of a Client (say Windows 7 or 10) which has an established rdp session to a Windows Server 2012 R2:
How long does it takes for the session to change to state disconnected?

And additionally: is there a way to modify this time?

Best regards, Stefan

When using RDP to play an FPS or similar game, how do I allow myself to turn around fully within the game itself?

November 19, 2018, 6:00 am

≫ Next: update KB4467697 breaks remote desktop

≪ Previous: Default value for session disconnect because of network disconnection

$

0

0

Whilst doing said activity the mouse seems to be locked within a theoretical window, the application seems to never get full range of the mouse as it does when playing an FPS natively.

You would be surprised how well this works with adequate bandwidth. 

Any ideas?

---

update KB4467697 breaks remote desktop

November 19, 2018, 9:50 am

≫ Next: Upgrade 2012 RDS CALs to 2016 RDS CALs?

≪ Previous: When using RDP to play an FPS or similar game, how do I allow myself to turn around fully within the game itself?

$

0

0

On a 2012 R2 remote desktop server, update KB4467697 breaks some remote desktop services.  I had the exact same problem with the preview KB4462921.   Removing either update makes the problem disappear.

Passthrough RDP connections through the gateway work just fine so there is no problems there.  The problem seems to be related to RDP on the remote server itself.  These two updates break direct RDP logins, we have to use TeamViewer or visit the physical console in order to gain access to the desktop.  Clients can login to the RDP website and see published apps, they just won't open.

With either of these updates installed, thousands of these errors appear in the event log:
A fatal error occurred while creating an SSL client credential. The internal error state is 10013.

Does anyone have information as to why the latest November 13 cumulative update for Windows Server 2012 R2 breaks RDP and Remote Desktop published apps with 10013 errors in the event log?

Upgrade 2012 RDS CALs to 2016 RDS CALs?

November 19, 2018, 11:39 am

≫ Next: Performance issues when using RDS 2016 in Azure with Azure AD DS and Azure App Proxy

≪ Previous: update KB4467697 breaks remote desktop

$

0

0

So we were running a virtual machine on the cloud, that was our RDSH, Win 2012, with 15 2012 CALs. The worst of the worst happened, and let's just say, we lost it completely (accept for our backups of the data, which is all we needed). However, we did need a new server, and desired (due to cost savings), to purchase an in-house server, instead of resuming our cloud use. Unfortunately, the only pre-built servers (as we needed it ASAP), was a 2016 machine, so we bought it, and got everything working again in half a day, not too bad....

Well, after seeing the annoying "120 days, 90 days, now 75 days, of unlimited licenses" warning, I decided it was time to dig up my old CALs (from only 2 year ago, bought summer of 2016). I installed all the old 2012 CALs just fine... but now I learn that 2012 CALs won't allow users to connect to a 2016 RDSH... okay?? So how do I upgrade these, or is this just some... you're s.o.l., too bad, Microsoft likes licensing fees, and throw those 2012 CALs in the garbage....? And pray we don't have server troubles again, and never upgrade your server version again?

Performance issues when using RDS 2016 in Azure with Azure AD DS and Azure App Proxy

February 10, 2017, 2:48 am

≫ Next: admin account disabled

≪ Previous: Upgrade 2012 RDS CALs to 2016 RDS CALs?

$

0

0

Hello,

Ihave the following in Azure:

1 Server 2016 RDS Session host server - contains the RDS Broker & Licensing roles 

1 Server 2016  RDS Web & Gateway server that conatins the web and gateway roles in addition to the application proxy connector.

1 Server 2016 Broker and licensing server.

The three servers are in the new (Resource Manager) portal.

I've set up a non-overlapping VNET and Azure AD DS in the classic portal. I've also set up application proxies for the RD web and Gateway roles.

Everything works fine. The only issue I have is the connection quality. When I RDP straight into the RDS server, connection quality is fine and there is no lag when inputting text in to a document, moving windows, etc.

When I access the RDS server via the application proxy, connection quality is 'good' and I experience lag inputting text, moving windows, etc.

My question is, is this normal? I suspect it's due to the fact that the application proxy can only work on https(443) and RDS2016 requires both HTTPS (443) and UDP 3391 to perform optimally?

If not, then how can I improve performance? Thanks

I've been through the documentation but cannot find anything that would indicate why the connection wuality drops when using the proxy. I have tried both passthrugh and Azure Preauthentication for the RDweb application as well.

Thanks,

HA20

admin account disabled

November 19, 2018, 5:25 pm

≫ Next: Remote Desktop App with Azure AD

≪ Previous: Performance issues when using RDS 2016 in Azure with Azure AD DS and Azure App Proxy

$

0

0

i am trying to access a windows server 2016 remotely.. it says my account is disabled, because i am accessing it remotely by windows remote desktop tool, i cant do a cmd boot version of resetting it... what other options of getting it enabled ?

Remote Desktop App with Azure AD

July 30, 2018, 12:28 am

≫ Next: mapping a folder or making it a home folder

≪ Previous: admin account disabled

$

0

0

It seems that I am unable to connect to a computer on my network with the Remote Desktop App (trusted Windows Store App on my Windows Laptop or from the iOS App store on my iPhone), while I am able to connect successfully to it from Remote Desktop Connection (old Windows app).

The remote computer is joined to Azure AD (Windows 10 Pro, up to date; again, this works from the old Remote Desktop Connection application on Windows).

Can anyone tell me if connection to a machine joined to Azure AD is supported on the Remote Desktop App or if there is something I need to do to configure it properly?

Thanks.