Core components

Drive engine

We have built the CDM drive engine on our custom file system driver called IAMFSP and an array of sophisticated control systems, including but not limited to the following:

• Cloud Provider framework

• Drive mounter

• Conflict resolver

• Data synchronizer

• Delta translator

• Content repo

• Metadata observer

• Handle manager

• Operations router

Together, these control systems allow CDM to create local drives, integrate with cloud storage services, and efficiently handle the interactions between the two.

Client user interface

In the first-generation client, up to version 2.x (aka CDM Legacy), you could only perform basic functions such as refreshing mapped drives, obtaining license information, and so on when interacting with it. CDM was almost invisible, and our customers used its mapped drives just like any other drive. We have upgraded the latest version of the client to provide you with additional functions like viewing file activity, identifying problem files, and self-solving issues to more advanced user-driven options.

File Explorer integration

Up to version 2.x (aka CDM Legacy), File Explorer did not integrate with the CDM client. CDM was more like a traditional network drive, without the ability for you to have advanced interactions with your files, folders, and drives. By contrast, the latest version of the CDM client integrates directly with File Explorer, bringing all types of useful features into your hands, such as seeing the status of files and folders or performing additional actions simply by right-clicking on them.

Cloud authentication

For its integration with Microsoft 365, CDM uses the Microsoft Authentication Library (MSAL). MSAL enables CDM to benefit from its compatibility with Microsoft Entra ID and other features, including single sign-on, multi-factor authentication, and conditional access.

Real-time browse

Sync systems like the OneDrive sync client operate by maintaining a complete local profile of your drive structure, which works well when you have a limited number of files and your own persistent machine. However, when it comes to large volumes of data or a nonpersistent environment (such as a VDI or when you’re hotdesking), you’re bound to run into issues with synchronization – even when you don’t sync the content.

A sync system only presents a synced drive once it has enumerated the entire file structure. This process can take hours initially or indeed every time you log on, especially if the previously enumerated data has not persisted.

Additionally, even though you are likely to only need access to a handful of files or folders during a typical day at work, a sync system checks for changes to the entire drive's contents. This results in considerable redundant web traffic and local computation. It creates inefficiencies that impact productivity.

Real-time browse overcomes these fundamental sync issues. It tracks, and syncs changes solely upon your interaction with a file or folder. This hybrid, real-time approach enables CDM to efficiently map drives with large volumes of data while delivering the resilience and performance more favorably associated with traditional sync systems. Better yet, this balance between real-time and sync behaviour can be controlled by policy, putting the power to decide what is best for an organization into the hands of IT teams.

Iris

Iris is a centralized admin portal that allows our customers and partners to manage their IAM Cloud products. Iris makes managing, configuring, and deploying CDM easier and significantly more powerful. Its dynamic policy engine allows you to translate an array of configurations and settings to a policy ID, which you can then pass on to the CDM client via MSI parameter or Group Policy.