Determines whether the remote session window appears full screen when you launch the connection. 1: The remote session will appear in a window - 2: The remote session will appear full screen: 2: Yes: smart sizing:i:value: Determines whether or not the local computer scales the content of the remote session to fit the window size. Screens Connect is a free utility that lets you connect back to your Mac or Windows PC from anywhere in the world. Download Screens Connect 4 (macOS 10.11 or later) Screens.
-->The following table includes the list of supported RDP file settings that you can use with the Remote Desktop clients. When configuring settings, check Client comparisons to see which redirections each client supports.
The table also highlights which settings are supported as custom properties with Windows Virtual Desktop. You can refer to this documentation detailing how to use PowerShell to customize RDP properties for Windows Virtual Desktop host pools.
Connection information
| RDP setting | Description | Values | Default value | Windows Virtual Desktop support |
|---|---|---|---|---|
| full address:s:value | PC Name: This setting specifies the name or IP address of the remote computer that you want to connect to. This is the only required setting in an RDP file. | A valid name, IPv4 address, or IPv6 address. | No | |
| alternate full address:s:value | Specifies an alternate name or IP address of the remote computer. | A valid name, IPv4 address, or IPv6 address. | No | |
| username:s:value | Specifies the name of the user account that will be used to sign in to the remote computer. | Any valid username. | No | |
| domain:s:value | Specifies the name of the domain in which the user account that will be used to sign in to the remote computer is located. | A valid domain name, such as 'CONTOSO'. | No | |
| gatewayhostname:s:value | Specifies the RD Gateway host name. | A valid name, IPv4 address, or IPv6 address. | No | |
| gatewaycredentialssource:i:value | Specifies the RD Gateway authentication method. | - 0: Ask for password (NTLM) - 1: Use smart card - 2: Use the credentials for the currently logged on user. - 3: Prompt the user for their credentials and use basic authentication - 4: Allow user to select later - 5: Use cookie-based authentication | 0 | No |
| gatewayprofileusagemethod:i:value | Specifies whether to use default RD Gateway settings. | - 0: Use the default profile mode, as specified by the administrator - 1: Use explicit settings, as specified by the user | 0 | No |
| gatewayusagemethod:i:value | Specifies when to use an RD Gateway for the connection. | - 0: Don't use an RD Gateway - 1: Always use an RD Gateway - 2: Use an RD Gateway if a direct connection cannot be made to the RD Session Host - 3: Use the default RD Gateway settings - 4: Don't use an RD Gateway, bypass gateway for local addresses Setting this property value to 0 or 4 are effectively equivalent, but setting this property to 4 enables the option to bypass local addresses. | 0 | No |
| promptcredentialonce:i:value | Determines whether a user's credentials are saved and used for both the RD Gateway and the remote computer. | - 0: Remote session will not use the same credentials - 1: Remote session will use the same credentials | 1 | No |
| authentication level:i:value | Defines the server authentication level settings. | - 0: If server authentication fails, connect to the computer without warning (Connect and don't warn me) - 1: If server authentication fails, don't establish a connection (Don't connect) - 2: If server authentication fails, show a warning and allow me to connect or refuse the connection (Warn me) - 3: No authentication requirement specified. | 3 | No |
| enablecredsspsupport:i:value | Determines whether the client will use the Credential Security Support Provider (CredSSP) for authentication if it is available. | - 0: RDP will not use CredSSP, even if the operating system supports CredSSP - 1: RDP will use CredSSP if the operating system supports CredSSP | 1 | Yes |
| disableconnectionsharing:i:value | Determines whether the client reconnects to any existing disconnected session or initiate a new connection when a new connection is launched. | - 0: Reconnect to any existing session - 1: Initiate new connection | 0 | Yes |
| alternate shell:s:value | Specifies a program to be started automatically in the remote session as the shell instead of explorer. | Valid path to an executable file, such as 'C:ProgramFilesOfficeword.exe' | Yes |
Session behavior
| RDP setting | Description | Values | Default value | Windows Virtual Desktop support |
|---|---|---|---|---|
| autoreconnection enabled:i:value | Determines whether the client will automatically try to reconnect to the remote computer if the connection is dropped, such as when there's a network connectivity interruption. | - 0: Client does not automatically try to reconnect - 1: Client automatically tries to reconnect | 1 | Yes |
| bandwidthautodetect:i:value | Determines whether automatic network type detection is enabled | - 0: Disable automatic network type detection - 1: Enable automatic network type detection | 1 | Yes |
| networkautodetect:i:value | Determines whether or not to use automatic network bandwidth detection. Requires bandwidthautodetect to be set to 1. | - 0: Don't use automatic network bandwidth detection - 1: Use automatic network bandwidth detection | 1 | Yes |
| compression:i:value | Determines whether bulk compression is enabled when it is transmitted by RDP to the local computer. | - 0: Disable RDP bulk compression - 1: Enable RDP bulk compression | 1 | Yes |
| videoplaybackmode:i:value | Determines if the connection will use RDP-efficient multimedia streaming for video playback. | - 0: Don't use RDP efficient multimedia streaming for video playback - 1: Use RDP-efficient multimedia streaming for video playback when possible | 1 | Yes |
Device redirection
| RDP setting | Description | Values | Default value | Windows Virtual Desktop support |
|---|---|---|---|---|
| audiocapturemode:i:value | Microphone redirection: Indicates whether audio input redirection is enabled. | - 0: Disable audio capture from the local device - 1: Enable audio capture from the local device and redirection to an audio application in the remote session | 0 | Yes |
| encode redirected video capture:i:value | Enables or disables encoding of redirected video. | - 0: Disable encoding of redirected video - 1: Enable encoding of redirected video | 1 | Yes |
| redirected video capture encoding quality:i:value | Controls the quality of encoded video. | - 0: High compression video. Quality may suffer when there is a lot of motion. - 1: Medium compression. - 2: Low compression video with high picture quality. | 0 | Yes |
| audiomode:i:value | Audio output location: Determines whether the local or remote machine plays audio. | - 0: Play sounds on the local computer (Play on this computer) - 1: Play sounds on the remote computer (Play on remote computer) - 2: Do not play sounds (Do not play) | 0 | Yes |
| camerastoredirect:s:value | Camera redirection: Configures which cameras to redirect. This setting uses a semicolon-delimited list of KSCATEGORY_VIDEO_CAMERA interfaces of cameras enabled for redirection. | - * : Redirect all cameras - List of cameras, such as camerastoredirect:s:?usb#vid_0bda&pid_58b0&mi - One can exclude a specific camera by prepending the symbolic link string with '-' | Don't redirect any cameras | Yes |
| devicestoredirect:s:value | Plug and play device redirection: Determines which devices on the local computer will be redirected and available in the remote session. | - *: Redirect all supported devices, including ones that are connected later - Valid hardware ID for one or more devices - DynamicDevices: Redirect all supported devices that are connected later | Don't redirect any devices | Yes |
| drivestoredirect:s:value | Drive/storage redirection: Determines which disk drives on the local computer will be redirected and available in the remote session. | - No value specified: don't redirect any drives - * : Redirect all disk drives, including drives that are connected later - DynamicDrives: redirect any drives that are connected later - The drive and labels for one or more drives, such as 'drivestoredirect:s:C:;E:;': redirect the specified drive(s) | Don't redirect any drives | Yes |
| keyboardhook:i:value | Determines when Windows key combinations (WIN key, ALT+TAB) are applied to the remote session for desktop connections. | - 0: Windows key combinations are applied on the local computer - 1: Windows key combinations are applied on the remote computer when in focus - 2: Windows key combinations are applied on the remote computer in full screen mode only | 2 | Yes |
| redirectclipboard:i:value | Clipboard redirection: Determines whether clipboard redirection is enabled. | - 0: Clipboard on local computer isn't available in remote session - 1: Clipboard on local computer is available in remote session | 1 | Yes |
| redirectcomports:i:value | COM ports redirection: Determines whether COM (serial) ports on the local computer will be redirected and available in the remote session. | - 0: COM ports on the local computer are not available in the remote session - 1: COM ports on the local computer are available in the remote session | 0 | Yes |
| redirectprinters:i:value | Printer redirection: Determines whether printers configured on the local computer will be redirected and available in the remote session | - 0: The printers on the local computer are not available in the remote session - 1: The printers on the local computer are available in the remote session | 1 | Yes |
| redirectsmartcards:i:value | Smart card redirection: Determines whether smart card devices on the local computer will be redirected and available in the remote session. | - 0: The smart card device on the local computer is not available in the remote session - 1: The smart card device on the local computer is available in the remote session | 1 | Yes |
| usbdevicestoredirect:s:value | USB redirection | - *: Redirect all USB devices that are not already redirected by another high-level redirection - {Device Setup Class GUID}: Redirect all devices that are members of the specified device setup class - USBInstanceID: Redirect a specific USB device identified by the instance ID | Don't redirect any USB devices | Yes |
Display settings
| RDP setting | Description | Values | Default value | Windows Virtual Desktop support |
|---|---|---|---|---|
| use multimon:i:value | Determines whether the remote session will use one or multiple displays from the local computer. | - 0: Don't enable multiple display support - 1: Enable multiple display support | 1 | Yes |
| selectedmonitors:s:value | Specifies which local displays to use from the remote session. The selected displays must be contiguous. Requires use multimon to be set to 1. Only available on the Windows Inbox (MSTSC) and Windows Desktop (MSRDC) clients. | Coma separated list of machine-specific display IDs. IDs can be retrieved by calling mstsc.exe /l. The first ID listed will be set as the primary display in the session. | All displays | Yes |
| maximizetocurrentdisplays:i:value | Determines which display the remote session goes full screen on when maximizing. Requires use multimon to be set to 1. Only available on the Windows Desktop (MSRDC) client. | - 0: Session goes full screen on the displays initially selected when maximizing - 1: Session dynamically goes full screen on the displays touched by the session window when maximizing | 0 | Yes |
| singlemoninwindowedmode:i:value | Determines whether a multi display remote session automatically switches to single display when exiting full screen. Requires use multimon to be set to 1. Only available on the Windows Desktop (MSRDC) client. | - 0: Session retains all displays when exiting full screen - 1: Session switches to single display when exiting full screen | 0 | Yes |
| screen mode id:i:value | Determines whether the remote session window appears full screen when you launch the connection. | - 1: The remote session will appear in a window - 2: The remote session will appear full screen | 2 | Yes |
| smart sizing:i:value | Determines whether or not the local computer scales the content of the remote session to fit the window size. | - 0: The local window content won't scale when resized - 1: The local window content will scale when resized | 0 | Yes |
| dynamic resolution:i:value | Determines whether the resolution of the remote session is automatically updated when the local window is resized. | - 0: Session resolution remains static for the duration of the session - 1: Session resolution updates as the local window resizes | 1 | Yes |
| desktop size id:i:value | Specifies the dimensions of the remote session desktop from a set of pre-defined options. This setting is overridden if desktopheight and desktopwidth are specified. | -0: 640×480 - 1: 800×600 - 2: 1024×768 - 3: 1280×1024 - 4: 1600×1200 | 1 | Yes |
| desktopheight:i:value | Specifies the resolution height (in pixels) of the remote session. | Numerical value between 200 and 8192 | Match the local computer | Yes |
| desktopwidth:i:value | Specifies the resolution width (in pixels) of the remote session. | Numerical value between 200 and 8192 | Match the local computer | Yes |
| desktopscalefactor:i:value | Specifies the scale factor of the remote session to make the content appear larger. | Numerical value from the following list: 100, 125, 150, 175, 200, 250, 300, 400, 500 | 100 | Yes |
RemoteApp
| RDP setting | Description | Values | Default value | Windows Virtual Desktop support |
|---|---|---|---|---|
| remoteapplicationcmdline:s:value | Optional command-line parameters for the RemoteApp. | Valid command-line parameters. | No | |
| remoteapplicationexpandcmdline:i:value | Determines whether environment variables contained in the RemoteApp command-line parameter should be expanded locally or remotely. | - 0: Environment variables should be expanded to the values of the local computer - 1: Environment variables should be expanded to the values of the remote computer | 1 | No |
| remoteapplicationexpandworkingdir:i:value | Determines whether environment variables contained in the RemoteApp working directory parameter should be expanded locally or remotely. | - 0: Environment variables should be expanded to the values of the local computer - 1: Environment variables should be expanded to the values of the remote computer. The RemoteApp working directory is specified through the shell working directory parameter. | 1 | No |
| remoteapplicationfile:s:value | Specifies a file to be opened on the remote computer by the RemoteApp. For local files to be opened, you must also enable drive redirection for the source drive. | Valid file path. | No | |
| remoteapplicationicon:s:value | Specifies the icon file to be displayed in the client UI while launching a RemoteApp. If no file name is specified, the client will use the standard Remote Desktop icon. Only '.ico' files are supported. | Valid file path. | No | |
| remoteapplicationmode:i:value | Determines whether a connection is launched as a RemoteApp session. | - 0: Don't launch a RemoteApp session - 1: Launch a RemoteApp session | 1 | No |
| remoteapplicationname:s:value | Specifies the name of the RemoteApp in the client interface while starting the RemoteApp. | App display name. For example, 'Excel 2016.' | No | |
| remoteapplicationprogram:s:value | Specifies the alias or executable name of the RemoteApp. | Valid alias or name. For example, 'EXCEL.' | No |
Sharing files between two or more computers on the same network is easy. All you have to do is set up a workgroup using your system's network file sharing options or using the popular LAN cable method. But these methods have their own limitations. i.e, both the machines should be at the same place or at least on the same network.
But, what if you want to remotely access files on your computer? Like browsing files on your home computer from your office laptop or even from your smartphone?
We've made a list of all the possible ways to remotely access your computer files. Although all the following methods are free, works on almost every platform, and has no bandwidth restrictions, some methods do require the host computer be turned on and connected to the Internet all the time. If not, you cannot access your files over the internet.
Related: How to Share Files Between Two Computers Using WiFi
Remotely Access Your Computer's Files
1. Cloud Storage Services
Online backup services like Google Drive, Dropbox, OneDriveetc provide an easy way to access files from anywhere. Simply create a free account (almost every cloud service offers 10 -15 GB free storage) and upload your files. After uploading, you can access those files and folders remotely. All you have to do is log into your account from any web browser or use their mobile app.
For Google Drive Users
If you are using Goole Drive, then you don't have to manually add files or folders to Google Drive folder. Simply right-click the folder you want to sync with Google Drive and select the option 'Google Drive > Sync this folder.' This action will sync the folder with Google Drive.
After syncing, you can access it by opening the Google Drive page in your favorite browser and then navigating to the 'Computers' tab on the left panel.
For OneDrive Users
OneDrive lets you access all your computer files and folders without actually syncing them with the cloud. To access your computer's drive using OneDrive, open the OneDrive settings window by right-clicking on the OneDrive icon in the taskbar and selecting the option 'Settings.'
In the Settings window, navigate to 'Settings' tab and select the checkbox 'Let me use OneDrive to fetch any of my files on this PC.'
That's it. From this point forward, you can access any of the files on your computer from OneDrive's web app using any browser on any computer. All you have to do is select the 'PCs' option appearing on the left sidebar. Do mind that you need to have your computer turned on and connected to the internet for this method to work.
Pros: Easy to use, secure, access any file remotely without the need of host machine kept on (not applicable to the OneDrive method discussed above).
Cons: You only get limited space on any cloud storage service. It is not possible to clone the entire hard drive to the cloud.
2. Dedicated NAS Devices
NAS (network-attached storage) devices are like setting up your personal cloud storage. Consider it as a big external hard drive connected to your home network. You store all your files on NAS and access them over the internet or from any device in your home. This method is great for file sharing and backing up multiple computers. If you want to, you can even configure your NAS to access files via FTP and/or web browsers.
Some NAS devices don't have this remote access turned on by default, but one can easily forward port to make its web interface accessible on the internet. Unless you know how to properly configure a NAS for internet access, it is not a secure technique. Especially for beginners.
Pros: Access any file remotely without the need of host machine being kept on. The NAS should be turned ON and be able to access the internet for you to fetch files, though.
Cons: NAS are expensive and designed for being accessed from the local network. Remote FTP should not be the only reason why you should buy a NAS. But if you already have one, then it makes sense to use it to fetch files remotely over the internet.
3. Router With USB Port
Most routers these days come with a USB port where you can plug in the external drive or a pen drive and then access all its contents from anywhere in the world. To get this setup working, you need to enable remote sharing and setup dynamic DNS on your router. If you are not familiar with home networking, the following video will help or check out this step by step tutorial.
Pros: Access any file remotely without the need of host machine turned on. Cheaper than NAS.
Cons: Most consumer routers internet file sharing features are insecure.
4. VPNs
Another good option to access your PC's files remotely is setting up a VPN server on your computer. Using that VPN, you can access your computer files just as you would do on your local network. When configured properly, VPN makes your remote computer appear as a part of the local network and allows access to all the local file shares.
This is the way, big businesses grant access to their shared files remotely. Vectoraster 7 0 2 download free. To overcome the problem of an insecure web interface, VPN servers are widely used with NAS.
Pros: https://downhfil265.weebly.com/gambling-help-forum.html. Offers the most control out of other options available.
Cons: Requires the remote desktop to stay on. Moreover, the setup is complicated and time-consuming.
5. FTP Server
FTP (File Transfer Protocol) is partially similar to VPNs where you install them on your home computer and grant access to it from the Internet. Normally FTP is unencrypted, which means people can easily monitor your files in transit and spoof your passwords. It may not be an ideal method from the security perspective, as you'd have to expose your FTP server to the Internet.
To deal with that, you can use SFTP which encrypts the connection over the internet. But you should create self-signed certificates to create the SFTP connection. The process can be a bit confusing and complicated for beginners.
Pros: Offers complete control to the user.
Cons: Unless you are using SFTP, FTP servers are unencrypted and considered unsafe. Requires the remote desktop to be turned on.
6. Remote Desktop Softwares
If you are looking for a way, that takes care of all the geeky stuff and lets you access your computer files remotely then try remote desktop software. Some of that software include but not limited to Unity, GoToMyPC, LogMeIn, PushBullet, etc. Let's take a look at few of them. https://terpsceninas1988.mystrikingly.com/blog/speedtest-by-ookla-1-3.
LogMeIn Pro: It is popular software which offers some extra functionalities like remote printing, 1TB storage, unlimited users. But all this comes at a price. LogMeIn Pro varies from $349.99/year to $1539.99/year for large businesses.
GoToMyPC: GoToMyPC is similar to LogMeIn. In fact, it offers similar advanced features like drag and drop file transfer in any other remote desktop app. GoToMyPC offers subscription service for $20 per month for one computer (Mac or Windows).
Pros: Simple and secure way for remote file access. Cross-platform support.
Cons: Requires the remote desktop to stay on. You need to pay to use the service, there is no free version.
7. TeamViewer
Screens 4 3 7 – Access Your Computer Remotely Drive Windows 10
Finally, it is by far the best, simple and secure way of remotely accessing your files over the internet. Most people knew TeamViewer as a screen sharing software but it has a hidden feature which also lets you access your computer's files remotely.
Screens 4 3 7 – Access Your Computer Remotely Drives
TeamViewer is completely free for personal use. Moreover, it supports Windows, Mac, and Linux. It has no bandwidth restrictions. But the best part is that you can access your files remotely from any device – even from your smartphones.
Pros: Cross-platform support, simple and secure way of remote file access.
Cons: Requires the remote desktop to stay on.
Related: How to Access your Computer Files from Anywhere With TeamViewer
Wrapping Up
There are many ways to remotely access files on your computer over the Internet. But we recommend TeamViewer. Cloud storage services can be useful if you are happy syncing your files online and don't mind the limited storage available to each free user accounts. If you are dedicated Windows user who is also using OneDrive the I recommend using the OneDrive method discussed above. This eliminates the need to install any third party software.
Screens 4 3 7 – Access Your Computer Remotely Drive Software
If you can afford to buy a NAS device or router then that can also help you in accessing files remotely. If you have a larger network like a business with multiple file shares then you can set up a VPN server. However, we would recommend to not use VPN, SSH, or FTP servers unless you know what you are doing. If not configured properly, it can be a big risk.
