Microsoft Teams MSI Installer

-
You can now install and distribute the Windows Teams Client via an MSI package.

 Simply download the installer and run it.

 Download 32bit
Download 64bit

 There are prerequisites:
1. 3.32GB of disk space for each user profile (recommended)
2. Windows 7 or later.
3. NET framework 4.5 or later


Deployment Procedure (Recommendations)
1. Retrieve the latest package
2. Use the defaults prepopulated by the MSI
3. Deploy to machines when possible

 For lager deployments, it is recommended using SCCM, Group Policies or Intunes.

 https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment



Comments

Post a Comment

Popular posts from this blog

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
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.
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more

Certificate Requirements Teams Direct Routing SBC

-
Running Microsoft Teams with Direct Routing for Cloud Voice, you have to deploy a certificate on your SBC. This certificate is used for encryption with TLS. Often there is the question how the certificate must be configured. SBC Public Certificate Requirements All deployed SBCs must have a public certificate from a trusted/supported Public CA, there are 3 options to create a certificate. Security Note: When generating the CSR, the private key size should be at least 2048. Support Note: onmicrosoft.com domain for certificates is not support. Option 1 - Single SBC A certificate with a single SBC FQDN. The SBC FQDN must be in the subject, common name and the Subject Alternate name. SN /CN SAN {Public FQDN of SBC }  {Public FQDN of SBC }   Option 2 - Multiple SBC A certificate with a multiple SBC FQDN’s. The SBC FQDN must be in the subject, common name and the Subject Alternate name, which includes the additional SBCs too.
Read more