Forum Discussion
Fslogix - delete profile -> Intune settings not applied
Hi,
Have got everything working fine with AVD (W11 multi session) and an FSlogix Profiles on an Azure File share. Settings are being applied with MS Intune.
The only issue is, when we delete a profile of a user (VHDX) and the user logs on to AVD, the Intune Configuration settings are not being applied anymore. Resulting in not all settings are correct (for example C drive should be hidden, Edge Home page not set, and so on....)
I cannot put a finger on where this issue is coming from and how to resolve it....
Hope someone can assist ?
5 Replies
Our profiles have been deleted weeks ago. The intune policy is being applied correctly - a long case with Intune support confirmed this. The Intune guesses something is kept on the device itself - but that was out of their knowledge/scope.
The initial profile works without any issues unless the profile is being deleted and recreated. No group policies are in place as only intune policies are being applied. Devices are AADJ and FSLogix logs don't show anything strange.
I think there may be a delay or sync issue after the FSLogix profile is deleted, preventing Intune settings from applying correctly. When the profile is recreated, make sure the device is properly synced with Intune, as it may not be fully enrolled or compliant after the profile deletion. Also, check for any conflicts between FSLogix settings and Intune policies, as FSLogix could be interfering with the application of certain configurations.
Also you can try reviewing Group Policies to ensure they aren't overriding Intune settings, and confirm that the AVD session is Azure AD joined and compliant. Have you checked both Intune and FSLogix logs in case of more insight?
Same issue here. Did you find a solution for this?
Some months ago I resolved a similar issue with Intune policies not being applied after deleting and recreating an FSLogix profile by clearing out any leftover cached data or artifacts. I made sure to remove any residual files and registry entries related to FSLogix and Intune, which I found could be causing interference. I also refreshed the device's identity in Azure AD by re-joining or forcing a sync, as there seemed to be caching issues with the device identity. I checked that the FSLogix profile was properly initialized and mounted when the user logged in, as I’ve experienced delays during profile recreation that caused issues. Finally, I manually triggered an Intune sync to ensure the policies were reapplied correctly. After that, was working properly, but I couldn’t identify exactly what caused the issue in the beginning. This approach worked for me, but I understand that it may not work for everyone, as each environment can have its own specific challenges. I hope it helps you too.
Would you have more information about the specific artifacts?
When logging off i don't see any leftovers of the profile so i suspect something in the registry.
