From the course: Windows 10: Manage Remote Access

Optimize Remote Desktop settings for an end user - Windows Tutorial

From the course: Windows 10: Manage Remote Access

Start my 1-month free trial

Optimize Remote Desktop settings for an end user

- [Instructor] We've looked at the settings for the remote desktop connection app in this course already. But in this video, we'll configure the settings from a different point of view. Here, we want to pre-configure the client for a specific end user. The intent is to set up the connection for maximum ease and best performance. So all the user has to do is connect. To make the client easier to find, we can put it on the task bar. I'll type for remote desktop. Right click it then choose pin to task bar. Now, when the client is ready to connect, they simply need to click this icon and the client will open. I'll click show options. To create the best experience possible, we'll need to look at each of the tabs. On the first tab, one thing to consider is to input the user's credentials for them and click save. What you input and save will appear when the user opens the app. You can create multiple connections and related profiles. This makes it easier for the user to connect, especially if they use and connect to multiple computers. Here's my computer and here's my username. And I can click save. I could also choose to always ask for credentials. Every time you click save, a new profile is created. I have three computer profiles here, one to connect to my office PC, one to connect to my laptop, and one to connect to another computer that's named Gateway. It's not necessarily a gateway. Make sure if you do this, that you let the user know they don't have to click open. They simply click the down arrow next computer to choose the one they want. The display tab is configured with default settings, including connecting in full screen mode. The display tab is already configured with default settings, including connecting in full screen mode. While that's a good setting for experienced users, it might be best to move the slider down a notch so that the novice can distinguish easily between their local screen and the remote one and have the ability to resize it easily. I'll connect to show you what it looks like when an end user can see both their own desktop and their remote one. Here, I'm connected to the remote PC. I can easily see my computer screen back behind it. I'll disconnect from this and restart the app. Let's look at the display tab again. If you know the user is connecting with an older monitor, you might also consider lowering the color depth. Perhaps you'll change from the highest quality, 32 bit, to something more like 16. From local resources, you can configure how you want to include or not include the client computers connected devices. Want to consider are key combinations. By default, the key combinations are set to only when using the full screen. That's because windows assumes if you're not in full screen mode, the key combinations you use should be applied to the local machine. You can, however, set it such that all key combinations are applied either to the local or the remote computer no matter the mode. You'll have to ask your end user what they prefer. Another setting to consider changing is the local devices and resources defaults. If you want the user to print to a device on the company network, remove the tick here. If you don't, the print command will send the task to their local personal printer. You might also disable clipboard. You might also disable some other things they have connected to their computers. From the experience tab, choose a connection type that the end user will be using. If you know the user connects from home with a satellite connection, you should change it here. If I choose satellite, watch what happens here. In this case, certain aspects of the remote desktop won't be applied. Sending the desktop background or using menu and window animations will cause more data to be sent and thus make for a slower experience. Also here's the option to reconnect if the connection has dropped. You can decide if you want users to auto reconnect or have to go through the signup process again. The last tab lets you configure what happens if server authentication fails and offers a place to configure gateway settings. You'll need to ask your end user about their own local network and how they plan to connect to configure these settings. To save the changes, click the general tab and click save. Feel free to explore some more and when you're ready, close the remote desktop connection app.

Contents