2 more docs added

Kim 2019-10-12 02:12:17 +11:00
parent d68e93595f
commit ced84724be
14 changed files with 152 additions and 0 deletions

@ -0,0 +1,106 @@
# Configuring RAWeb for a multi-user environment
RAWeb allows different users to see different apps by configuring IIS and setting some permissions.
You control access to your remote apps by setting file permissions on the RDP files. You can grant access to Active Directory or local users or groups.
This works with both the web-based RAWeb and also the webfeed.
This guide will show you how to setup a basic configuration to give a single local user access to some apps as an example.
## Install
Install RAWeb as per the instructions on the main RAWeb page.
You will also need to add **Windows Authentication** to IIS by adding the Windows Feature:
![][1]
[1]: images/configuring-raweb-for-a-multi-user-environment/install.jpg
## Configure authentication
In IIS Manager, open the Authentication feature for your site.
![][2]
[2]: images/configuring-raweb-for-a-multi-user-environment/configure-authentication.jpg
## Select authentication method
Disable Anonymous Authentication and enable Windows Authentication. Other methods may work but are untested.
![][3]
[3]: images/configuring-raweb-for-a-multi-user-environment/select-authentication-method.jpg
## Permissions
**Summary:**
* RAWeb users (or groups) should *only *have **List folder contents** permissions on the **rdp** directory (disable inheritance).
* Any user or group requiring access to a remoteapp must have **Read** permissions to the RDP file for the app.
**Example:**
In the example that follows, we will give a single local user access to some (but not all) apps available.
Go to the **Security **tab in **Properties **of the **rdp** directory, and click **Advanced**, then **Change Permissions**.
![][4]
[4]: images/configuring-raweb-for-a-multi-user-environment/permissions.jpg
## Disable inheritance
Depending on your OS, click either **Disable inheritance** or untick **Include inhertiable permissions from this object's parent**.
![][5]
[5]: images/configuring-raweb-for-a-multi-user-environment/disable-inheritance.jpg
## Keep permissions
Again depending on your OS, click either **Convert inherited permissions into explicit permissions on this object** or **Add**.
![][6]
[6]: images/configuring-raweb-for-a-multi-user-environment/keep-permissions.jpg
## Set rdp folder permission
Click OK, and go back to the main **Properties **window. **Edit** the permissions: Click on the **Users **group and ensure that only **List folder contents** permission is allowed (untick the others).
![][7]
[7]: images/configuring-raweb-for-a-multi-user-environment/set-rdp-folder-permission.jpg
## Add RDP files
Now fill up your **rdp** folder with some RDP files.
![][8]
[8]: images/configuring-raweb-for-a-multi-user-environment/add-rdp-files.jpg
## Assign RemoteApps to users by setting permissions
Now to assign an app to a user, give the user **Read** permissions to the appropriate RDP files.
In this example, there is a local user named TestUser who will be granted access to Calculator and Chrome but *not *TestApp.
Simply add **Read **permissions for **TestUser **on Calculator.rdp and Chrome.rdp.
![][9]
[9]: images/configuring-raweb-for-a-multi-user-environment/assign-remoteapps-to-users-by-setting-permissions.jpg
## ScreenHunter_17 Oct. 01 13.46.jpg
In this case, TestApp is not displayed (as desired).
This applies to web-based RAWeb as well as the webfeed feature.
![][10]
[10]: images/configuring-raweb-for-a-multi-user-environment/screenhunter_17-oct-01-1346jpg.jpg

@ -0,0 +1,46 @@
# File type associations for RAWeb webfeed clients
RAWeb can associate file types on clients to RemoteApps. For example, you can configure RAWeb so that when a client opens a DOC file, it opens with a Microsoft Word RemoteApp.
**Requirements**
* Client must be connected to RAWeb's webfeed.
* The client webfeed URL must be configured via Group Policy (or Local Policy).
* RDP files need to have file types listed within.
* RemoteApps on host must be configured to allow command line parameters.
File type associations **will not work** if you configure the webfeed URL via the RemoteApp and Desktop Connections control panel! You **must** configure it via policy.
## Add file types to RDP files
With a text editor, open the RDP file for the application that you would like to add file type associations for.
Add a new line:
remoteapplicationfileextensions:s:[file extensions separated by commas]
![][1]
[1]: images/file-type-associations-for-raweb-webfeed-clients/add-file-types-to-rdp-files.png
## Configure the RemoteApp to allow command-line parameters
Using RemoteApp Tool, edit your RemoteApp and
set **Command line option** to **Optional**.
## Configure webfeed URL via local group policy on the client
Navigate to **User Configuration > Administrative Templates > Windows Components > Remote Desktop Services > RemoteApp and Desktop Connections**.
**Edit **the policy setting **Specify default connection URL**. Click **Enabled** and** enter the URL** to the webfeed below. Click OK.
![][2]
[2]: images/file-type-associations-for-raweb-webfeed-clients/configure-webfeed-url-via-local-group-policy-on-the-client.png
## Add document icons
If you want a custom icon displayed for a particular file type, put an **ICO **file into the **icon **folder** **with the same name as the rdp file followed by a dot (.) and then the file extension.
Example: To set an icon for all XLS files which will open in Excel 2010 (Excel2010.rdp) your would need an icon file named: Excel2010.xls.ico

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 111 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB