Hi All, Looking for some advice. I recently disabled Shellbridge in a Citrix 2019 RDSH env. This was to combat Published apps launching all / unnecessary Run Key items (Teams, Intranet, etc) when launching the Published app. HOWEVER... Ive now got an issue where published apps that call M365 apps result in the 365 app coming back as "unlicensed"... I assume this is due to to the WAM process not running due to Shellbridge being disabled? Though I don't want to re-enable as it will mean I'm back to square one on the above published app issue.. Never had this problem with Server2016, assume this is due to ADAL being used and not WAM in 2019? As a workaround, I could try disabling WAM, though this could be a shoddy move. Rock and hard place 😞 Cheers

What profile solution are you using? You will either need to get AzurePRT working, or store legacy tokens in the profile with FSLogix or UPM.

Ivanti Env manager + FSLogix ODFC. The RDSH's are Hybrid joined. Can confirm it is working. When I re-enable Shellbridge, Office works and licenses as expected. I just get the RDSH's systray and all the other gunk loading up... I did look at capturing "%localappdata%\Microsoft\Office\16.0\Licensing" but didn't think it required given Sharecomputer should reach out and license when the user opens a 365 app. Figured roaming the tokens would cause isuses? Thanks

Yes, you will want to roam the tokens with the profile. If you want to disable teams launching with Shellbridge I outlined this in my deployment article. https://www.jeffriechers.com/wiki/teams-2-1-with-fslogix-setup-guide/

Thanks Jeff, Given that the affected users published apps aren't grabbing a token in the first place, roaming the tokens wouldn't fix this. Looks like my only option is to remove all entries from the Run key, re-enable shellbridge and then setup custom executes for the required run items in Env manager... What a PITA... Microsoft / Citrix et al are testing my patience HARD recently.

I am in same boat built a new 2022 image coming from 2016 where they used ADAL. The requirement was to use Same Fslogix profiles on the new image. With shellbridge enabled which is a requirement for WAM the gunk from the hkcu run/run once keys come in (using seamless apps). I am thinking of doing a GPP to delete the entries prior to moving them over