I feel all of your pain. I am working on a solution for our group, which is nearly identical to what you're experiencing. FSLoigx is going to be of little help. In order for it to work properly, ...
See more...
I feel all of your pain. I am working on a solution for our group, which is nearly identical to what you're experiencing. FSLoigx is going to be of little help. In order for it to work properly, as of Feb '23, you need to have your ICs "AADJ" or "HAADJ" (hybrid azure ad joined). https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues "Virtual machines, which are AADJ or HAADJ create the user's primary refresh token (PRT) at sign-in. Primary refresh token(s) created at sign-in are used to authenticate to Azure AD based applications. Standard Domain Joined (DJ) virtual machines don't create a PRT at sign-in, instead rely on the Microsoft Azure AD broker plugin." I've tried it again with this GPO setting: Install FSLogix 2210 hotfix 1 (2.9.8440.42104). Configure the new RoamIdentity setting by setting the registry value to 1 or enabling via Group Policy. But no luck. DEM is mostly useless with regard to roaming o365 profile, but I have got it to work using this profile: https://communities.vmware.com/t5/Dynamic-Environment-Manager/DEM-template-for-Office-365-is-insufficient/td-p/2899781 However, it is not "user friendly" and requires signing into Outlook/Teams, signing out, signing in again, then hoping the license file is there when signing back in again. It's VERY CLUNKY, but it does kind of work. Look at the post by Lansti. The other thing that I've been trying to do, but have not been successful with, is trying to PREVENT office from recognizing the "signed in user" (and it's user token) when first opening the application. This plays a part in how well DEM/FSLogix stores the profile/license information and more importantly, what account is seen when o365 opens. However; it is not possible to remove that setting - at least that I've been able to find. It's a "feature" to make it easier to use the o365 applications. Also, a site I reference often with this setup is here: https://www.stephenwagner.com/2021/08/06/microsoft-office-365-vdi It's a pretty good guide. I've had the most luck with this over anything else, but like I said, it's still clunky, and every time MS updates o365, less and less stuff works right.