Mounting Filespaces on Windows

  • Updated

 

New Default Mount Point for Windows 

We have introduced a new default mount point for Windows, C:\Volumes\<domain>\<filespace>. This allows us to ensure fixed file paths for teams connecting to multiple Filespaces simultaneously. Although drive letter-based mount points (e.g., L:, M:, N:) remain an option, this new strategy provides enhanced consistency, especially vital for applications that depend on fixed file paths.

 

Applications That Write to the Root of a Used Drive

Certain applications, like Avid Media Composer, require writing directly to the root of the used drive. For these scenarios, using a drive letter as a mount point is not only supported but also recommended. Filespace administrators should ensure they explicitly assign unique letters for each Filespace their team will be connecting to to guarantee seamless operations. This can be achieved via Control Panel > Global Defaults > Windows Mount Point.

 

Default Drive Letter Mount Point - Still an Option

Teams, whose workflows do not rely on fixed file paths, can still employ the old default drive letter mount strategy. However, they should be aware that the assigned drive letter for a given Filespace may vary upon reconnecting and across different machines connected to the same Filespace.

 

What to Expect During the Update 

After updating the LucidLink desktop application to a version supporting Multi-Filespace Connect, administrators attempting to connect to a Filespace will be prompted to choose a mounting strategy for any Filespace, lacking an explicitly set mount point on Windows. They will have the following options:

  • A guaranteed static mount point: This could either be done by adopting the new default mounting on the C disk or choosing another explicit mount point of their preference (which could still be a drive letter). 
  • A dynamic drive letter mount point: If administrators opt for this strategy, they should be aware that the drive letter assigned to a Filespace might be different across machines and upon reconnection on the same machine. This could result in a dynamic file path for any resource within the Filespace.

 

Filespaces Initialized with a Multi-Connect Desktop App

Please note that if you create a new Filespace and initialize it with a Desktop App version 2.5 or higher, you will want to ensure that all users connecting to the new Filespace also have Desktop App 2.5 or higher.

If there are users connecting to the Filespace using an older version of the Desktop App, they may encounter different mount points and, consequently, different file paths compared to users who are connecting with a newer version of the Desktop App. Since this can cause issues during collaboration, we recommend that everyone updates to the latest version of the LucidLink Desktop App. 

Was this article helpful?

1 out of 1 found this helpful