Windows RDS server 2022 + problemen met nieuwe profielen

Question

Windows RDS server 2022 + problemen met nieuwe profielen

Azure 0

We hebben enkele Windows Server 2022 RDS servers waarbij er een probleem is ontstaan voor nieuwe profielen.

Bij nieuwe profielen werkt de startknop, search balk en outlook config oa niet...

Dit geldt voor zowel domain users als voor lokale users.

We merken dat in het profiel van nieuwe user onder de map appdata\packages niets verschijnt...

Normaal gezien moet daar oa staan:

Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy

Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy

Microsoft.Windows.Search_cw5n1h2txyewy

We hbben zelfs de server als eens gerestored via back-up, dan gaat het enkele weken goed.

Maar nadien duikt hetzelfde probleem opnieuw op.

0 opmerkingen

1 antwoord

Uw antwoord

Answer 1

Hello,

Thank you for posting question on Microsoft Windows forum!

Based on your query of malfunction of start button, search bar and outlook config for new profiles. The missing folders in AppData\Local\Packages for new profiles are an indicator of the problem. Since these folders contain the essential files for Universal Windows Platform (UWP) apps, which include the Start Menu, Search, and other modern Windows features. When these are missing or corrupted, those functionalities break. The followings are suggested potential troubleshooting steps for the issue.

1.Check Event Logs:

System Logs: Look for errors related to User Profile Service, disk I/O, or any other system-level issues around the time new users experience the problem.
Application Logs: Look for errors related to StartMenuExperienceHost.exe, ShellExperienceHost.exe, SearchApp.exe, or any other UWP applications.
Microsoft-Windows-AppXDeploymentServer/Operational logs: These logs are important for UWP app deployment and can show errors related to package registration.
Antivirus/Security Software Logs: Check your antivirus/EDR logs for any blocked processes or files related to AppData\Local\Packages or user profile creation. This might be a very common source of this problem.

2.Review UPD/FSLogix Configuration:

If using UPDs:
Check the UPD settings in Server Manager. Ensure AppData\Local is not excluded from the UPD. Excluding this can lead to issues, as UWP app data is often stored here.
If using FSLogix:
Verify your FSLogix GPOs and configuration.
Ensure AppData\Local\Packages is included in the profile container.
Pay close attention to any "Folder Redirection" or "Exclude/Include" lists within FSLogix.
Look into the FSLogix "Enable search roaming" setting. Misconfigurations can cause issues with search.
Check for issues with the User_MirroredFolderExclusion policy if you are using it.

3.Check the Default User Profile:

Comparing C:\Users\Default of the affected new profile user on a problematic RDS server with a working one
Look for missing or zero-byte files.
Ensure that AppData\Local\Microsoft\Windows\WinX, AppData\Local\Packages exist.

Hope the above information is helpful!