AZ-140 · Question #281
You have an Azure subscription that contains two users named User1 and User2 and the Microsoft Entra groups shown in the following table. You have an Azure Virtual Desktop host pool named Pool1 that…
The correct answer is C. Remove User1 from Group3. User1's profile changes are not persisting because User1 is part of Group3, which is on Host2's FSLogix Profile Exclude list, preventing proper profile redirection.
Question
You have an Azure subscription that contains two users named User1 and User2 and the Microsoft Entra groups shown in the following table. You have an Azure Virtual Desktop host pool named Pool1 that contains two session hosts named Host1 and Host2. The session hosts use FSLogix user profiles. Host1 contains the local groups shown in the following table. Host2 contains the local groups shown in the following table. User1 connects to Pool and modifies his desktop. User1 reports that when he reconnects to Pool1, the desktop modifications fail to appear. You need to ensure that User1 sees the modified desktop when he connects to Pool1. The solution must minimize the impact on other user profiles. What should you do?
Options
- AAdd User1 to both FSLogix Profile Include list groups.
- BRemove Group2 from both FSLogix Profile Exclude list groups.
- CRemove User1 from Group3.
- DRemove Group3 from Group2.
How the community answered
(32 responses)- A13% (4)
- B6% (2)
- C63% (20)
- D19% (6)
Why each option
User1's profile changes are not persisting because User1 is part of Group3, which is on Host2's FSLogix Profile Exclude list, preventing proper profile redirection.
Adding User1 to the FSLogix Profile Include list (Group1) will not resolve the issue, as the Exclude list takes precedence, meaning User1 would still be excluded if they are in Group3 on Host2.
Removing Group2 from the FSLogix Profile Exclude list on Host1 is irrelevant because User1 is not a member of Group2, and the problem occurs specifically when connecting to Host2 where Group3 is the issue.
User1 is a member of Group3, and Group3 is configured in the FSLogix Profile Exclude list on Host2. This configuration prevents FSLogix from redirecting User1's profile on Host2, causing any desktop modifications to be lost upon reconnection. Removing User1 from Group3 ensures their profile is no longer excluded, allowing FSLogix to properly manage and persist their profile.
Removing Group3 from Group2 does not address User1's direct membership in Group3, which is the root cause of the exclusion on Host2's FSLogix Profile Exclude list.
Concept tested: FSLogix Profile Container Exclude/Include Lists
Source: https://learn.microsoft.com/en-us/fslogix/configure-profile-container-directory-include-exclude-list-how-to
Topics
Community Discussion
No community discussion yet for this question.