**This is an old revision of the document!**
Enabling the CIFS Provider
Appliance Requirements
This CIFS feature is only available for version 3.0+ of SME Appliance. Please use the prior mechanism to work with CIFS if you have an older version of the appliance.
Introduction
From version 3.0 of the SME Cloud Appliance there is an easier way to expose Windows based CIFS shares from the SME Enterprise File Share and Sync service . This guide steps an Admin through how to enable the CIFS connector (provider) in the SME Appliance.
Turn SELinux to permissive mode
In most cases the File Fabric's CIFS provider can be used without changing the File Fabric's SELinux settings. Depending on the CIFS implementation, however, it may be necessary to switch SELinux to permissive mode to make the CIFS provider work. If you have set up the CIFS provider without changing the SELinux configuration and the provider is not working as expected, follow these instructions to set SELinux to permissive mode.
ssh as root
For these commands you will need to su as root
$ ssh smeconfiguser@appliance IP address
after establishing ssh session su as root
-bash-3.2$ su - root Password:
SELinux to permissive mode
as root execute the following command this will temporarily make SELinux permissive
setenforce 0
To permanently make SELinux permissive edit /etc/selinux/config
and change the line
SELINUX=enforcing
to
SELINUX=permissive
Enable CIFS provider for the user package
- Login as appladmin in to the appliance
- go to User Packages and select the package assigned to the user
- Enable CIFS provider for the package and save
Add CIFS to the account
Login in to the SME user account and you should see CIFS as provider in the dropdown list when you login as SME user
At this point you can use the provider wizard to add a CIFS share.
FAQ
If you have added a CIFS share that is later directly removed then the metadata will remain visible in SME but you will be given warnings that SME cannot connect on upload, download or sync.
If you wish to remove this metadata you need to remove the provider entirely via the Cloud DashBoard.