To configure remote file transfer for a client policy, do the following:
In the RAS Console, select the Policies category.
Right-click a desired policy in the right pane and choose Properties.
In the left pane, navigate to Session > Local devices and resources.
Select the File transfer node.
In the right pane, select one of the following in the Allow file transfer drop-down list:
Client to server only: Transfer files from client to server only.
Server to client only: Transfer files from server to client only.
Bidirectional: Transfer files in both directions.
For additional information about client policies, see Client Policies.
To configure remote file transfer in User Portal, do the following:
In the Parallels RAS Console, navigate to Farm > <Site> > Secure Gateways.
Right-click a desired RAS Secure Gateway in the right pane and choose Properties.
Select the User Portal tab.
Select the Allow file transfer command option and click the Configure button. In the dialog that opens, select one of the following:
Client to server only: Transfer files from client to server only.
Server to client only: Transfer files from server to client only.
Bidirectional: Transfer files in both directions.
For more information about configuring User Portal, see Configure User Portal.
To configure remote file transfer for an RD Session Host, Provider, or Remote PC, do the following:
In the Parallels RAS Console, select the Farm category and then select a desired server type (RD Session Host, Provider, Remote PCs) in the middle pane.
Right-click a desired server in the right pane and choose Properties.
Select the Agent Settings tab.
Select the Allow file transfer command option and click the Configure button. A dialog opens where you can specify remote file transfer options as described below.
In the Direction drop-down list, select one of the following:
Client to server only: Transfer files from client to server only.
Server to client only: Transfer files from server to client only.
Bidirectional: Transfer files in both directions.
In the Location field, specify a UNC path to a folder to be used as the default upload location. This path will also be used as the default source location when a user tries to download a file from a remote server. You can select from one of the locations predefined in the drop-down list or you can specify your own. Standard Windows environment variables, such %USERNAME%, %USERDOMAIN%, %USERPROFILE%, can be used. If the location is not found during an upload or download operation, the standard (default) download location will be used.
The Do not allow to change location option prohibits the user to change the UNC path specified in the Location field. If the option is enabled, the user cannot select a different location while trying to upload or download a file. If the option is cleared, the user can specify a different location.
Important: Please note that the Do not allow to change location option cannot prevent the user from accessing the specified remote location directly. For example, a user can try to upload a file, note the default location's UNC path (to which he/she has access), then open it in File Explorer and copy it to any folder in his/her profile. To prevent such a scenario from happening, you need to implement additional measures to control locations other than the location that you specify here.
Parallels RAS provides end users with the ability to transfer files remotely to and from a remote server.
Note: At the time of this writing, file transfer is supported in Parallels Web Client and Parallels Client for Chrome only. Bidirectional file transfer is supported in Parallels Web Client only. In Parallels Client for Chrome, you can only enable or disable file transfer.
To make the remote file transfer functionality flexible, Parallels RAS allows you to configure it on the following three levels:
File transfer settings that you configure on each level take precedence in the order listed above. For example, if you enable file transfer on a User Portal, but disable it on an RD Session Host, file transfer will be disabled for all users who connect to the given RD Session Host through the given User Portal. As another example, you can enable file transfer on an RD Session Host and then disable it for a particular Client policy (or an User Portal). This way you can control which clients can use file transfer and which cannot.
Read the subsequent sections to learn how to configure file transfer on each level.