Information, Configuration and Advice for Microsoft Intelligence Communication.
Sycor Strategy Sales Enablement, 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.
These are the most common logs and are required for all Microsoft support cases. Debug logs are produced by the Windows and Mac desktop clients, as well as browser based clients. The logs are text based and are read from the bottom up. They can be read using any text based editor and new logs are created when logging into the client.
Debug logs show the following data flows:
Connection requests to middle tier services
The debug logs are produced using the following OS specific methods:
Right-click the Microsoft Teams icon in your application tray, select Get Logs
Choosing Get Logs from the Help pull-down menu
Keyboard shortcut: Ctrl + Alt + Shift + 1
Choosing Get Logs from the Help pull-down menu
Keyboard shortcut: Option + Command + Shift+1
The debug logs are automatically downloaded to the following folders.
Browser: You will be prompted to save the debug log to default save location
Media logs contain diagnostic data about audio, video and screen sharing. They are required for support cases only upon request and can only be inspected by Microsoft. The following table outlines the log location.
Desktop logs, also known as bootstrapper logs, contains log data that occurs between the desktop client and the browser. Like media logs, these logs are only needed if requested by Microsoft. The logs are text based and can be read using any text based editor in a top down format.
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) 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.
OPEN FEDERATION in Microsoft TEAMS With Microsoft Teams, there is an important difference configuring OPEN FEDERATION . While in Skype for Business, it was a simple Option: Off, Open with blocked Domains or Blocked with Allowed Domaind In Teams, it is different. Team Open Federation is activ by default ! Soon you are adding a "Allowed Domain", the Open Federation is revoked. Only Federation with users in the allowed Domain list is possible ! SOLUTION: Remove all Allowed Domains in Teams Admin Portal Different with Blocked Domains, here the Open Federation will be kept, but blocked Domains are expluded from Federation! In Teams Admin Portal, you will find the Statement About Federation. External access lets your Teams and Skype for Business users communicate with other users that are outside of your organization. By default, your organization can communicate with all external domains. If you add blocked domains, all other domains will be allowed but if y
Teams Guest User Access - Invite methods and process. Teams Guest User are member of a Office 365 modern group. There are two ways managing guest access. - Teams Client - Azure AAD You cannot managed, add guest users from within Office 365 groups, if the user isnt added as a guest user in Azure AD. Adding a Guest User from Teams Client The user self managed guest access is handled within Microsoft Teams client. The next illustrations will show you how. It is important, that Guest Access is enabled for your tenant (not show in this guide) Navigate to the Teams (…) and click manage team, from there you can add a guest user by typing his/her external Teams address in the format name@domain Upon the user is added, you will see this user as member in you Team. If you try managing a guest user / adding him/her via Office 365 Groups from you Admin Center, you will see that adding external user isn't possible. The user is shown as "Not Found"