Best Practices for FSLogix Profile After Major Windows or Office Updates on VDI Parent Image

Hello,

I am seeking guidance regarding best practices for managing FSLogix profiles following significant upgrades to the Windows or Office builds on our VDI parent image. Post-upgrade, we've been experiencing slower startup times and issues with Office applications, and we're trying to pinpoint potential causes.

Specifically, what steps, if any, are recommended to take with the FSLogix profiles after these substantial updates? Should we consider creating fresh FSLogix profiles for our users, or are there tools available that can efficiently prune unnecessary items in the profile which no longer relate to the new builds of Windows or Office?

Our goal is to optimize our system performance and user experience, and any insights or suggestions about how to handle FSLogix profiles in this context would be greatly appreciated.