This message was deleted.
# _general
s
This message was deleted.
r
I thought someone figured out some hackey work around with a batch file?
k
I did 😄
😄 1
Or to be exact, my one of my colleagues did 🙂
This will fix the AAD Broker plugin, which apparently fails when using Office 365 published apps
if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin
👍 2
Implement it as a login script or even better as an external task in WEM
k
oh nice. why is this not mentioned in the CTX267071? 😉
k
Maybe it's not supported, who knows
r
@Devin McCubbins Didn't you try above method? I don't recall. I know for one client you had to revert to Office 2019, vs Office365...
d
I haven't needed to try it yet
Many kudos to kasper's colleague. I'm sure to need this eventually
👍 1
k
Office 2019 is also affected. the issue is Server 2019. It works fine on Server 2016
r
Not surprising. 2019 is a shitass OS
😂 1
d
Is this issue for published apps only or also in published desktops?
k
@Dennis Hirsch for published apps only
Apparently the AAD Broker Plugin works when using published desktop
d
Thanks for the clarification @Kasper Johansen
👍 1
k
The issue is not related to Citrix as I can reproduce the issue with RDS as well. It's a Windows issue.
...or published app issue
r
@Alain Assaf For your reference.
a
@Ryan Gallier. Fantastic! Thanks
👍 2