Configuration overrides

When CDM starts, it typically applies your organization’s default configuration. Unless you’ve created custom configurations in Iris. When you create a custom configuration, Iris assigns it a unique ID. This is a registry string value that informs CDM about the custom settings it needs to apply for your organization at startup. While you can deploy this registry string value using an application deployment tool of your choice, this section provides information on how to do so through Group Policy (GPO) and Microsoft Intune. This process overrides your default configuration, and it applies to the following:

Custom mapping groups
Custom bandwidth policies
Custom drive collaboration policies
Folder redirection policies

Let’s look at an example of how this would work in a real-world situation:

Suppose you’re an IT administrator in a school, and you need to give both staff and students access to different SharePoint document libraries, while ensuring neither group can access the other’s document library.
This scenario won’t work if you only have a default mapping group with a Direct: SharePoint document library drive that is available to all users in the school.
Instead, you’ll need to create two custom mapping groups in Iris, called Staff and Students, each with its own Direct: SharePoint document library drive.
Depending on your requirements, you can deploy the IDs for these custom mapping groups to users’ devices or to specific users.