Open jkrgr0 opened 2 years ago
Hey
Sadly that is not possible in the way the ADMX is designed. So you should create 3 policies with the following mappings: N:\ O:\, Z:\ N, O, Z, W N, O, Z, W, X
As an advantage you have additional flexibility in case you later need to change mappings for a specific group but of course it is a little redundant.
But you can merge with the other policy settings (so for example the Enabled setting or the Interval).
Best regards Hauke
Hi
Okay, thanks.
If the ADMX is designed like this (for each drive a specific policy) we would be able to split the drive mappings in multiple configuration policies without the risk of conflict.
Any chances of an implementation like this?
Hey
Yea I may consider it :). I would need to implement side-by-side with the old mechanism to ensure that versions configured the other way still need to work :).
Best Hauke
That would be nice!
This would also increase the visibility of the configured drive mappings in the profile itself.
Hey
Sadly that is not possible since you can only provide one set of drives with a policy (This is by design of how the ADMX templates work). So you should create 3 policies with the following mappings: N:\ O:\, Z:\ N, O, Z, W N, O, Z, W, X
As an advantage you have additional flexibility in case you later need to change mappings for a specific group but of course it is a little redundant.
Best Hauke
Hello,
I'm currently trying to implement your solution for one of our customer but I'm not sure how to manage different drive mappings for specific users.
Example:
- All users needs the drives N:, O:\ and Z:\
- User1 needs additionally drive W:\
- User2 needs additionally drive W:\ and X:\
So my idea was to create three configuration profiles (N:\ O:\, Z:\ | W:\ | X:) and assign the profiles to the specific user groups. But with this approach it seems that I've created a conflict and not all drives are being mapped.
What would be the optimal approach for this?
Thanks!
We also need this. We have multiple shares assigned to multiple groups. So for exact mappings we literally need a lot of profiles. I'm curious if we edit the ADMX and add a second policy name with a new name <policy name="NetworkDriveMappings2" and a new regkey will this work or does the app/agent doesn't support this? What is necessary to make this work :-) Virtual beer ?
We where able to do this, where we can deploy it to different user groups. It works OK. So maybe the developer can consider it. What we did. Deploy the Store App. Ingest the ADMX, but in the OMA Uri policy we have not set the NetworkDriveMappings value, only the other ones. Now, on a reference PC in local registry of HKCU\Software\Policies\Weatherlights folder (where the drive letters are set for the app) we have created all possible Drive mappings with Dummy information in it. So FDrive with value \networkpath\
Hello,
I'm currently trying to implement your solution for one of our customer but I'm not sure how to manage different drive mappings for specific users.
Example:
So my idea was to create three configuration profiles (N:\ O:\, Z:\ | W:\ | X:\) and assign the profiles to the specific user groups.
But with this approach it seems that I've created a conflict and not all drives are being mapped.
What would be the optimal approach for this?
Thanks!