User1 modifies their desktop but the changes do not appear after reconnecting. FSLogix profile include/exclude and local group memberships are defined as shown. To ensure User1 sees the modified desktop while minimizing impact on other user profiles, what should you do?

The FSLogix Profile Container configuration uses Group1 for inclusion and Group2 for exclusion. User1 is a member of Group1, which would normally include their profile. However, User1 is also a member of Group3, and Group3 is a member of Group2 (the exclusion group). This means User1 is indirectly excluded from FSLogix profile management. To ensure User1's profile is managed by FSLogix, they must be removed from the exclusion path. Removing User1 from Group3 directly removes them from the exclusion group's membership, allowing their profile to be included. Adding User1 to both FSLogix Profile Include list groups is redundant as they are already in Group1. Removing Group2 from both FSLogix Profile Exclude list groups would affect all users in Group2, not just User1. Removing Group3 from Group2 would also affect all users in Group3, which might be an unnecessary broader change.