This blog series is designed to help kickstart your enterprise’s Microsoft Teams deployment, with a particular focus on voice and video (my specialty :smiling_face_with_smiling_eyes:). In part 1, we’ll focus on getting the Teams client deployed across the board, but first let’s talk about the Teams client architecture. Microsoft Teams is a web application – it’s designed to enable a consistent user experience across devices. Microsoft Teams clients exist for the following platforms:
If you’re starting with a pilot user group, or are facilitating a small POC, manual client installation would be my recommendation for getting started quickly. If you have bigger and better plans (for an enterprise-wide deployment), I’d suggest you explore our guidance for .msi deployment, as it outlines how to incorporate a Teams installation package with your software distribution platform. If you are looking to leverage Microsoft Teams within your VDI infrastructure, please take a look here, as there are some special considerations (and a separate installer) to take advantage of.
Once installed, the Microsoft Teams client is automatically updated via the cloud. Delta bits are pushed to the client, which notify the user to 'refresh' once available for consumption. Detail may be found here.
Well, that’s it for part 1! In part 2, we’ll talk through the coexistence and interoperability options to ease the transition from Skype for Business to Teams! See ya next week!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.