Remote File Storage (RFS) for Windows Install Overview

Remote File Storage (Windows) Install Overview

The following article is intended to assist AirWatch Customers and Agents install, validate and troubleshoot Windows Remote File Storage (RFS).

CLICK HERE
for more information on an
assisted install. Reach out to
your Account Executive to
purchase.

RFS (Windows) Install Guide

The install guide is intended to walk users through the preparation, installation and configuration of the Windows Remote File Storage.

Pre-Install Requirements Worksheet

Provides a detailed explanation of all general, hardware, software and network requirements for a successful installation of RFS for Windows. Please only reference the tab for the component you wish to install.

Install Validation

Provides tests and checks to perform in order to validate that the component has been successfully installed and configured. These should always be performed after a new install or upgrade to confirm functionality.

RFS (Windows) Logs

How to guide for gathering RFS logs. These logs will be needed if you run into any issues with the RFS during or after an install or upgrade. It will also help our support team assist you more quickly if these are provided up front.

Install Troubleshooting

This forum provides resolutions to common issues and error messages that are encountered during an RFS install. Please be sure to gather logs prior to beginning troubleshooting.



Install Validation


The following steps should be performed after an RFS install or On Premise upgrade to confirm that RFS was insatlled/updated successfully. If you encounter issues at any point during validation, please proceed to the RFS (Windows) Logs and Install Troubleshooting sections.

Validation Step Actions Expected Results
Step 1 - Ensure Services are Running on Server Go to your RFS server and open Services. AirWatch RFS services appear and are running.
Rfs-cre_-_Windows_Step_4.jpg
Step 2 - Ensure Remote Storage and Content Viewer is enabled and active. Navigate to Groups & Settings > All Settings > Content > Remote Storage. Also under Content go to Content Viewer to ensure that is enabled. Both pages are configured and the "Active" icon is green.
RFS_Linux_1.jpg

Feature Validation


The following steps should be performed after an RFS install or On Premise upgrade to confirm RFS functionality.

Validation Step Actions Expected Results
Step 1 - Add Files to Self Service Portal Navigate to Groups & Settings > All Settings > Content > Personal Content and ensure that Personal Content is enabled with a storage quota. Log into the Self Service portal and add any file into the portal. The file saves to SSP successfully.
RFS_Linux_3.jpg
RFS_Linux_4.jpg
Step 2 - Check RFS Desination Folder for Files/Folders Navigate to your server where you directed the files to be stored. Check for files and folders. The folder should have files with long strings of characers. This indicates AirWatch has started placing files here.

RFS (Windows) Logs


The following article provides information on how and when to collect and verbose logs related to Windows RFS.

Collecting Logs


Collecting Logs from the RFS server is extremely important for the installation process. If any issues arise during the installation, the logs will reveal what failed so you can begin to troubleshoot. There are a few troubleshooting steps you can try before collecting logs but if you are submitting a support ticket the time to resolve the ticket will be much quicker if you include the logs for the component you are having issues with.

RFS has important default directories that store their install logs, server logs and configuration files. There are two separate logs for RFS Tokens and RFS Files. The paths are by default:

C:\AirWatch\Logs\RemoteFileStorage\rfs-tokens.log
C:\AirWatch\Logs\RemoteFileStorage\rfs-files.log

Setting Log Levels


Follow the steps below to change logging levels:

1. Access the “\AirWatch\RemoteFileStorage\rfs-files\config\logback.xml” and “\AirWatch\RemoteFileStorage\rfs-tokens\config\logback.xml” files contained in the File or Token configuration folder.
2. Edit the file
3. Change the logging level XML attribute value in both logger and root XML elements to the corresponding logging level you would like, for example: verbose.

logger name=”com.airwatch” level=”info”
root level=”info”

4. Restart each service after saving changes.

Have more questions? Submit a request

0 Comments

Article is closed for comments.