Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
cloudappliance/cifs30 [2018_09_06 20:36] dougcloudappliance/cifs30 [2019_05_08 21:19] – [FAQ] steven
Line 10: Line 10:
  
 For CIFS to be available it must be enabled both for the appliance and in the User Package for an organization. For CIFS to be available it must be enabled both for the appliance and in the User Package for an organization.
 +
 +===== Enable CIFS provider for the appliance =====
 +
 +  * Login as appladmin in to the appliance
 +  * Go to Settings -> Site Functionality
 +  * Toward the bottom of the page under Providers ensure that CIFS is enabled
 +  * To ensure proper SELinux functionality do not change the default mount point ( /mnt/CIFS ) 
 +  * Click Update Options at the bottom of the page
 +
 +{{::cifsenabled.png |}}
  
 ===== Enable CIFS provider for the user package ===== ===== Enable CIFS provider for the user package =====
  
   * Login as appladmin in to the appliance   * Login as appladmin in to the appliance
-  * go to User Packages and select the package assigned to the user+  * Go to Menu button in the top right of the screen -> User Packages  
 +  * Select the package assigned to the user/organization
  
 {{:/cloudappliance:cifs30:.:sme_user_packages.png|User Package}} {{:/cloudappliance:cifs30:.:sme_user_packages.png|User Package}}
Line 61: Line 72:
 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 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.+If you wish to remove this metadata you need to remove the provider entirely via the Cloud Dashboard.