This message was deleted.

Presense status doesnt work in outlook if you exclude SFB i had the same issue and had to include SFB in my configuration.xml

Thanks @c4rm0

FYI, there may be a private hotfix for this. I've been following this thread since last May: https://discussions.citrix.com/topic/413111-teams-presence-addin-not-working-in-oulook/page/2/#comment-2097670

I saw this one, I hope they will share the fix (or case number) 🙂

we need to track this guy down 😁

I love those posts. "Hey everyone, MS gave me a fix and it works... seeya!"

Interesting https://techcommunity.microsoft.com/t5/microsoft-teams/display-online-status-next-to-name-in-outlook-greyed-out/m-p/730571/page/2

Came across this on Reddit today, for anyone feeling bold: https://www.reddit.com/r/Citrix/comments/11r2vnx/teams_presence_missing_in_outlook/jc6hpuj/

Awesome, I'm adding it to my 365 Apps install script

What I find weird are the tlb files these match those located in "C:\Program Files (x86)\Microsoft\Teams\current\resources\assets\tlb"

yep these files looks identical to me. I have registered uc.tlb and uc.win32.tlb with REGTLIB.EXE and it changed nothing. What am I doing wrong?

Thanks @Jonathan Pitre, is the reboot necessary?

nope, just restart Outlook. Teams must also be launched for the presence to be reported.

It doesn't work, maybe I'm doing something wrong...

Copy-Item "${env:ProgramFiles(x86)}\Microsoft\TeamsPresenceAddin\Uc.tlb" "${env:ProgramFiles(x86)}\Microsoft Office\root\Office16" -Verbose

Copy-Item "${env:ProgramFiles(x86)}\Microsoft\TeamsPresenceAddin\Uc.win32.tlb" "${env:ProgramFiles(x86)}\Microsoft Office\root\Office16" -Verbose

Start-Process -FilePath 'D:\officedeploymenttool_16026-20170\regtlib\REGTLIB.EXE' -ArgumentList "${env:ProgramFiles(x86)}\Microsoft Office\root\Office16\Uc.tlb" -Wait

Start-Process -FilePath 'D:\officedeploymenttool_16026-20170\regtlib\REGTLIB.EXE' -ArgumentList "${env:ProgramFiles(x86)}\Microsoft Office\root\Office16\Uc.win32.tlb" -Wait

I couldn't make it work using variables with the regtlib.exe command, try with the real path.

@Jonathan Pitre Good catch!

yeah that took me hours of testing to figure it out.