Welcome to the Microsoft Q&A Platform!
Apologies for the delay in responding to your concern. Based on the details you shared, I would like to provide some information that may help resolve the issue.
1. Profile Container & ODFC Best Practices
- Ensure you are using a supported FSLogix version for your environment. FSLogix 25.09 (3.25.822.19044) is known to have issues. Please consider testing with the latest supported version if possible.
Reference: Known Issues - FSLogix | Microsoft Learn
FSLogix Release Notes - FSLogix | Microsoft Learn
- Profile and ODFC containers should be stored on reliable, high-performance network shares with proper permissions.
- Exclude problematic folders and registry keys in your redirections.xml as you have done, but review exclusions to ensure they do not interfere with Office/OneDrive authentication.
2. Persistent Credential Issues
- Problems with persistent credentials (especially for OneDrive, Teams, Office) are common when certain folders or registry keys are excluded from the profile container.
- Manual deletion of folders like IdentityCache, OneAuth, and TokenBroker may temporarily resolve issues, but is not a sustainable solution.
- Ensure that Office activation and OneDrive settings are included in the container if persistent sign-in is required.
3. OneDrive Troubleshooting
- OneDrive is more sensitive to profile container exclusions and may require specific folders to be included for seamless operation.
- Review the official FSLogix documentation for recommended exclusions/inclusions for OneDrive and Office 365 apps.
Reference: FSLogix FAQ - FSLogix | Microsoft Learn
Configuration Settings - FSLogix | Microsoft Learn
4. General RDS Profile Troubleshooting
- Check permissions on the profile share and ensure no network latency or connectivity issues.
- If users experience temporary profiles, verify that the VHD(x) is not locked by another session host.
I hope this information can help you a bit. Wish you a pleasant day!