Information, Configuration and Advice for Microsoft Intelligence Communication.
Head of Customer Success Center @TRANS4MATION, specialized in Intelligence Communication (Teams & Modern Workplace). Microsoft Elite Team Member Redmond (PG). User Group Owner Teams & #
TrustinTech. Microsoft awarded me multiple times with MVP Office Apps & Service for my professional work and community support.
Subscribe to this blog
Follow by Email
Troubleshoot Outlook Plug-In for Teams
It can be happen, that the Outlook Plug-In for Teams isn't showing up or is removed during a Teams client updates.
This behavior is well-known issue and can be solved with some of the following procedures:
Install the Teams app as an administrator of the Windows computer.
Download, install and sign into Teams and then restart Teams and Outlook, in that order.
To ensure that the add-in is installed and loaded correctly, you may need to restart Teams and Outlook after installing. Follow these steps:
Download the Teams desktop app, run it, and sign in at least once.
After signing into Teams, restart the app.
Restart Outlook (after restarting Teams).
Ensure that the add-in is installed and enabled. If after all that, you still don't see the add-in, make sure that it isn't disabled for some reason.
In Outlook, clickFileand thenOptions.
Select theAdd-instab ofOutlook Optionsdialog box
Confirm thatMicrosoft Teams Meeting Add-in for Microsoft Officeis listed in theActive Application Add-inslist
If the Teams Meeting Add-in is listed in theDisabled Application Add-inslist, selectCOM Add-insinManageand clickGo…
Set the checkbox next toMicrosoft Teams Meeting Add-in for Microsoft Office
Hi all, (This is an updated version 2.2: 09.07.2015)
This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here.
there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains.
Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed
Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar. The feature depending on EWS ar…
Once more first. Really make always sure your environment is patched and up to date.
Mainly if you have a slow Join Conference user experience. Validate your DFS or File Server.
Just what we experienced during certain Skype for Business Updated, as well as support cases is: - Migration is slow - Join Conferencing experience is slow - Address Book generation is slow and more
This is, if the Fileshare is not fast enough. What does this mean: You should ensure the IOPS as well as the network throughput is sufficient and not the bottleneck in your environment. Do a measurement on the file servers, see what is happen if DFS replication is kicked in, check if this is share file server, whats happen if other app's access the shares and monitor the IOPS/ bandwidth. Just this is not all, also just perfmon for CPU load, and Memory especially paging.
If you experience slow conference joins, it will be the issues, mostly. (Sure the local SQL server also consumes performance on the Skype for Business Fron…