When Microsoft Teams Users tend to chat privately naturally, using the conversation feature, some guidance shall be provided.
Summary of some important features :
Channels are public to the team, conversation are privated to their members.
A Channel message do not notifies users by default, conversations do.
Conversation history is shown automatically in a channel and optionnally in a conversation.
Channels support more apps interactions. Both supports tabs where applications go, but channel have more application such as planner and many other connectors, bots and teams meeting recorded as video in Stream.
Channels for team collaboration, app and main information
What goes in a channel ?
Communication you would send to people as CC in an email surely go to a channel as it does not notify users.
Communication in an open space.
Important announcements, information.
On the spot meeting with your team.
To use apps using tabs channel (onenotes, planner, website, a sharepoint library etc)
Conversation for day to day operational conversation
Users can create 1:1 or for example 50 people named conversations.
What goes into conversation
Each conversation notifies users so use it when you need immediate answers from ALL those colleague.
Think about it as a phone call or a skype chat
That is why day to day discussion, information that could be deleted or forgotten, go to a conversation. The entire team DONT need to know about those operational chats.
Share images etc to explain what you need to your colleagues
Once an information or a decision shall be shared, share to the channel.
Channel for FYI message such as people as CC in an email
Channel for Actionable conversation to certain team members (using @name in a channel).
Conversation to replace phone call or direct Skype message when you need quick answer from a limited group of colleagues. Use it wisely as it would create notification to every conversation members.
Id like to know your take on those recommendations ! Comment below.
Fri Nov 09 2018 15:00:11 GMT+0100 (Paris, Madrid) <10264> — info — L’authentification moderne a échoué, mais vous pourrez toujours vous connecter. Le code de votre statut est 4c7. diag:0
Fri Nov 09 2018 15:00:11 GMT+0100 (Paris, Madrid) <10264> — info — adalsso:statusChanged to: L’authentification moderne a échoué, mais vous pourrez toujours vous connecter. Le code de votre statut est 4c7.
Fri Nov 09 2018 15:00:11 GMT+0100 (Paris, Madrid) <10264> — info — Sso failed, updating cookie settings. Status:4c7 diag:1
Fri Nov 09 2018 15:00:11 GMT+0100 (Paris, Madrid) <10264> — info — Focusing main window
More information about Microsoft Teams modern authentication
Microsoft Teams has implemented a better way of signing in—we call it modern authentication. (If you’ve ever heard the term “single sign-on ” or “SSO”, that’s what we’re talking about here.) The benefit of modern authentication is that it makes it possible for you to sign in to Microsoft Teams without re-entering your email and password every time you want to start a new session. It’s a more secure and reliable way to sign in to Microsoft Teams.
Modern authentication is a process that allows you to sign in to an app securely. Since modern authentication includes SSO, it’s also part of the process that lets Microsoft Teams know that you’ve already entered your credentials (like your work email and password) elsewhere, and you shouldn’t be required to enter them again to launch the app.
Signing in with modern authentication will vary depending on a couple things, like if you’re working in Windows or on a Mac. It will also vary depending on whether your company has enabled single-factor authorization or multi-factor authorization (multi-factor authentication usually involves verifying your credentials via your phone, by providing a unique code or entering a PIN number or presenting your thumbprint). Either way, once you complete the sign in process using modern authentication, you won’t be required to provide your credentials again—from that point on, Microsoft Teams will automatically sign in to your account once you launch the app from the same machine.
As a SharePoint administrator you need to sometimes restarted services that are crashed due to a lot of potential reasons, such as : distributed cache, excel calculation services (if you display excel in sharepoint pages), user profile synchronization, user profile etc.
This script allow to restart a service on two servers
How to restart a SharePoint 2007 / 2010 / 2013 / 2016 / 2019 service programmatically ?
List of services that could be restarted
Access Database Service 2010
App Management Service
Business Data Connectivity Service
Claims to Windows Token Service
Document Conversions Launcher Service
Document Conversions Load Balancer Service
Excel Calculation Services
Lotus Notes Connector
Machine Translation Service
Managed Metadata Web Service
Microsoft SharePoint Foundation Incoming E-Mail
Microsoft SharePoint Foundation Sandboxed Code Service
Microsoft SharePoint Foundation Subscription Settings Service
Microsoft SharePoint Foundation Web Application
Microsoft SharePoint Foundation Workflow Timer Service