Windows: Upgrading from 23.251 to the Latest Version

If you are running FileCloud in a high availability environment, to upgrade to the latest version, please Contact FileCloud Support.

FileCloud Support can help you upgrade or can provide a PDF with instructions if you would like to perform the upgrade without assistance.

Pre-upgrade

• As always, make a full backup of your existing installation before upgrading.
  Backup on Windows

• Beginning with version 23.252, a new group, Externals, automatically includes all External users, and the Everyone group does not include External users. External users who were include in the Everyone group in earlier versions of FileCloud are no longer included in it.
  
  The Externals group functions to prevent External users from having the same share, folder, and policy access as users in the Everyone group. 
  
  Previously created DLP rules that denied access to the Everyone group will now deny access to both the Everyone and Externals groups. Previously created DLP rules that allowed access to the Everyone group will continue to allow access to the Everyone group and not to the Externals group.
  
  If your use cases require that external users have the same access to files and folders as other users, you can give the Externals group the same permissions as the Everyone group by running the tool assignexternalsgroup.php.  See Assign the Externals Group the Same File Access as the Everyone Group for help.

• Beginning in FileCloud 23.253, by default, a more granular dynamic content security policy replaces the existing content security policy in the .htaccess file. If you are upgrading, to make this change effective, you must make a small change to the Content-Security-Policy header in the .htaccess file:

  • Open the .htaccess file.

    in Windows:
    C:\xampp\htdocs\.htaccess

    in Linux:
    /var/www/html/.htaccess

  • Find the line that begins:
    Header set Content-Security-Policy:

  • Change set to setifempty:
    Header setifempty Content-Security-Policy:

    

• If your system uses ServerLink, perform the following steps:

  1. Before upgrade, ensure all ServerLink nodes are fully synced and are at the same state.

  2. Make backups of all nodes as needed.

  3. Stop the FileCloud ServerLink client service in secondary nodes.

  4. Upgrade the primary node first.

  5. Upgrade each secondary node after upgrading the primary node.

  6. Start the FileCloud ServerLink client service in secondary nodes. (In HA setups, client service must run only in one of the servers from each secondary node.)

Note: All connected ServerLink nodes, both primary and secondary, must be upgraded to the same ServerLink version before enabling access to the site again.

• If your system uses MongoDB authentication or a custom IP binding, follow the steps at Disable MongoDB Authentication and IP Binding.

Upgrade instructions

1. Before running the upgrade tool, confirm that each of your FileCloud services is running and that your storage is in a READY state.

2. Use the Windows Upgrade tool to do a full upgrade. (You cannot upgrade using the admin portal.)
   Upgrade using Update Tool (Windows Only)

3. For all upgrades, once upgrade is complete, refresh the browser using CTRL-F5 to clear any prior setup information from the cache.

Post Upgrade

Upgrade Windows environments using Solr and Solr+OCR

1. Upgrade FileCloud

2. Upgrade OpenJDK to version 17.

3. Set JAVA_HOME to the new version's path.

4. Log in to the FileCloud admin portal.

5. In the FileCloud Control Panel, and stop and restart Content Search.