Run an Action Set based on user group membership. For example, create a single package for printers. For each printer, you can create an action set and add the 'is a member of group' filter. With this approach, you only need to maintain one package for all printers in your organization. The same applies to drive mappings.
| Product | Application Workspace |
If we can use Group Membership directly within actions within a package we do not need to create Contexts . Now we create a Context to add an Entra ID group in it to use it in a package. This gives allot of administration overhead and allot of unnecessary Contexts. This really would be an upgrade and basically an important improvement.
Graag implementeren! Dit zou echt handig zijn!
"Run an Action Set based on user group membership. For example, create a single package for printers. For each printer, you can create an action set and add the 'is a member of group' filter.
With this approach, you only need to maintain one package for all printers in your organization. The same applies to drive mappings.
Add functionality to filter actions at the action level based on the group membership of both the computer and the user. This would allow certain actions (e.g., printer configurations) to be executed for specific user groups. With this feature, it would be possible to create a single package for User Environment configuration, including printers, drive mappings, and other settings, streamlining the management process.
Waarschijnlijk al eerder ingeschoten.
We missen de mogeliijkheid om AAD groepen te kunnen gebruiken in filters. Dit kan nu alleen door eerst een context te maken obv een AAD groep.