Skip to main content
Skip table of contents

Universal File Share System Requirements

The maximum number of characters allowed for a file path (file name + directory route) is 445.  For example "\\servername\root\childpath\filename.txt" is consider a file path. 

Universal File Share Connector Server

Before you install the Records Management Universal File Share Connector, verify that your system meets or exceeds the following requirements.

Cores

Memory (MB)

Minimum

4

4096

Recommended

8

8192

  • Windows Server 2016 or later

  • .NET Framework 4.5 or later (x64)

  • .NET Runtime 8.x (x64)

  • 100 MB Disk Space for Software

Note: The requirements above reflect the current version of the Universal File Share Connector, 5.3. Please contact Gimmal Support if you are installing a previous version.

Database Server

  • SQL Server 2016 or greater

  • 100 MB for File Share Connector Database

As a security best practice when using the .NET Framework, Gimmal recommends that you enable Transport Layer Security (TLS) 1.2, which provides communications security for client/server applications.

To enable TLS 1.2, you must add the following Windows registry settings to the Records Management Core server(s) and the servers of any Records Management connectors you are using (if applicable), and then reboot your system.

  • HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 "SchUseStrongCrypto"= dword:00000001

  • HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 "SystemDefaultTlsVersions"= dword:00000001

  • HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 "SchUseStrongCrypto"= dword:00000001

  • HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 "SystemDefaultTlsVersions"= dword:00000001

Note that some operating systems require additional steps to enable TLS 1.2. For more information, see Microsoft's TLS documentation To verify that your operating system supports TLS 1.2, read the Support for TLS 1.2 section of Microsoft's documentation.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.