2 docs added

Kim 2019-10-12 01:31:50 +11:00
parent f78b66621a
commit d68e93595f
35 changed files with 240 additions and 0 deletions

@ -0,0 +1,71 @@
# Setup RAWeb Web Interface
This will guide you through setting up RAWeb on the default web site in IIS on Win 8. Steps may vary slightly between operating systems.
The guide assumes that IIS is not already installed.
## 1. Go to Control Panel > Programs and Features
If you can't find it, just click the start menu and type **Programs and Features**.
![][1]
[1]: images/setup-raweb-web-interface/go-to-control-panel--gt--programs-and-features.png
## 2. Click Turn Windows features on or off
![][2]
[2]: images/setup-raweb-web-interface/click-turn-windows-features-on-or-off.png
## 3. Install IIS and ASP
Click the box next to **Internet Information Services**.
Expand **Internet Information Services > World Wide Web Services > Application Development Features**.
Click the box next to **ASP**.
![][3]
[3]: images/setup-raweb-web-interface/install-iis-and-asp.png
## 4. Wait for changes to apply
![][4]
[4]: images/setup-raweb-web-interface/wait-for-changes-to-apply.png
## 5. Right-click RAWeb and Extract All...
![][5]
[5]: images/setup-raweb-web-interface/right-click-raweb-and-extract-all.png
## 6. Extract files to C:\inetpub\wwwroot
Overwrite files if prompted.
![][6]
[6]: images/setup-raweb-web-interface/extract-files-to-c--inetpub-wwwroot.png
## 7. Browse to http://localhost/
You should see RAWeb with a Test Application.
![][7]
[7]: images/setup-raweb-web-interface/browse-to-http---localhost-.png
## 8. Publish your RemoteApps and Remote Desktop Connections
For each RemoteApp you want published on the page, save it's RDP file into **c:\inetpub\wwwroot\rdp**
If you want a custom image displayed for an app, put a PNG image file into **c:\inetpub\wwwroot\png** with the same name as the rdp file.
**For example:** Outlook2010.rdp would need an image called Outlook2010.png. Images will display at 64x64 pixels.
![][8]
[8]: images/setup-raweb-web-interface/publish-your-remoteapps-and-remote-desktop-connections.png

@ -0,0 +1,169 @@
# Setup RAWeb Webfeed with a Self-Signed Certificate
By connecting to a Webfeed, Windows and mobile clients automatically create shortcuts (in the Start Menu) for every RemoteApp and Remote Desktop Connection that is made available through RAWeb.
A requirement of webfeed is that the web server which hosts RAWeb must be running HTTPS and be secured with an SSL certificate.
This guide shows you how to setup RAWeb Webfeed (using a self-signed certificate) on a HOST computer, and then connect a CLIENT computer to it. Both computers are on the same local network. Steps may vary slightly between operating systems.
In this scenario, the HOST is Windows 8.1 and the CLIENT is Windows 10.
A limitation of using a self-signed certificate is that it must be installed on each client computer before it will be able to connect. If you wish to avoid this limitiation, you must purchase an SSL certificate from a vendor and install it on your server. Installing a purchased SSL certificate is outside the scope of this document.
## 1. Open IIS Manager (HOST)
**Windows 7**
**Control Panel > Administrative Tools > IIS Manager**
**Windows 8 and 10**
Click the Start button and type **IIS Manager**
![][1]
[1]: images/setup-raweb-webfeed-with-a-self-signed-certificate/open-iis-manager--host-.png
## 2. Open Server Certificates (HOST)
![][2]
[2]: images/setup-raweb-webfeed-with-a-self-signed-certificate/open-server-certificates--host-.png
## 3. Click Create Self-Signed Certificate... (HOST)
![][3]
[3]: images/setup-raweb-webfeed-with-a-self-signed-certificate/click-create-self-signed-certificate--host-.png
## 4. Give the certificate a name (HOST)
![][4]
[4]: images/setup-raweb-webfeed-with-a-self-signed-certificate/give-the-certificate-a-name--host-.png
## 5. Edit the Bindings for the Default Web Site (HOST)
![][5]
[5]: images/setup-raweb-webfeed-with-a-self-signed-certificate/edit-the-bindings-for-the-default-web-site--host-.png
## 6. Click Add... (HOST)
![][6]
[6]: images/setup-raweb-webfeed-with-a-self-signed-certificate/click-add--host-.png
## 7. Enter the Host name and choose your certificate (HOST)
![][7]
[7]: images/setup-raweb-webfeed-with-a-self-signed-certificate/enter-the-host-name-and-choose-your-certificate--host-.png
## 8. Export your certificate (HOST)
![][8]
[8]: images/setup-raweb-webfeed-with-a-self-signed-certificate/export-your-certificate--host-.png
## 9. Choose where to save the certificate and enter a password (HOST)
You need to make a password. It will be used later when importing the certificate on a client. Keep it simple.
![][9]
[9]: images/setup-raweb-webfeed-with-a-self-signed-certificate/choose-where-to-save-the-certificate-and-enter-a-password--host-.png
## 10. Copy the certificate file and open it on a CLIENT
![][10]
[10]: images/setup-raweb-webfeed-with-a-self-signed-certificate/copy-the-certificate-file-and-open-it-on-a-client.png
## 11. Import the certificate file (CLIENT)
Select **Current User**.
![][11]
[11]: images/setup-raweb-webfeed-with-a-self-signed-certificate/import-the-certificate-file--client-.png
## 12. Click Next (CLIENT)
![][12]
[12]: images/setup-raweb-webfeed-with-a-self-signed-certificate/click-next--client-.png
## 13. Enter the password (CLIENT)
![][13]
[13]: images/setup-raweb-webfeed-with-a-self-signed-certificate/enter-the-password--client-.png
## 14. Select the correct Certificate Store (CLIENT)
Ensure that **Trusted Root Certification Authorities** is selected.
![][14]
[14]: images/setup-raweb-webfeed-with-a-self-signed-certificate/select-the-correct-certificate-store--client-.png
## 15. Click Yes to confirm warning (CLIENT)
![][15]
[15]: images/setup-raweb-webfeed-with-a-self-signed-certificate/click-yes-to-confirm-warning--client-.png
## 16. Confirm certificate was successfully imported (CLIENT)
![][16]
[16]: images/setup-raweb-webfeed-with-a-self-signed-certificate/confirm-certificate-was-successfully-imported--client-.png
## 17. Open Control Panel > RemoteApp and Desktop Connections (CLIENT)
![][17]
[17]: images/setup-raweb-webfeed-with-a-self-signed-certificate/open-control-panel--gt--remoteapp-and-desktop-connections--client-.png
## 18. Click Access RemoteApp and desktops (CLIENT)
![][18]
[18]: images/setup-raweb-webfeed-with-a-self-signed-certificate/click-access-remoteapp-and-desktops--client-.png
## 19. Enter the webfeed URL (CLIENT)
This will typically be **https://HOSTNAME/webfeed.asp**
![][19]
[19]: images/setup-raweb-webfeed-with-a-self-signed-certificate/enter-the-webfeed-url--client-.png
## 20. Click Next (CLIENT)
![][20]
[20]: images/setup-raweb-webfeed-with-a-self-signed-certificate/click-next--client-1.png
## 21. Confirm successful connection (CLIENT)
![][21]
[21]: images/setup-raweb-webfeed-with-a-self-signed-certificate/confirm-successful-connection--client-.png
## 22. RemoteApps and Remote Desktop Connections should now appear in the Start Menu (CLIENT)
As RDP files are added and removed from RAWeb, clients will automatically update these shortcuts.
![][22]
[22]: images/setup-raweb-webfeed-with-a-self-signed-certificate/remoteapps-and-remote-desktop-connections-should-now-appear-in-the-start-menu---client-.png
## Notes
If you want a custom icon displayed for an app, put an ICO file into **c:\inetpub\wwwroot\icon** with the same name as the rdp file eg. **Outlook2010.rdp** would need an icon called **Outlook2010.ico**.
Mobile clients require each ico to be a 32x32 PNG. Icons for mobile clients should be placed in **c:\inetpub\wwwroot\icon32**

Binary file not shown.

After

Width:  |  Height:  |  Size: 65 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 72 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.6 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 89 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 65 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: 6.2 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 78 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB