diff --git a/Teams/devices/teams-ip-phones.md b/Teams/devices/teams-ip-phones.md index ed6a5fce8d..050d559316 100644 --- a/Teams/devices/teams-ip-phones.md +++ b/Teams/devices/teams-ip-phones.md @@ -101,7 +101,7 @@ The following devices are Certified under the Microsoft Teams panels Certificati | Device model| Firmware version | Current certification end date | Android OS version | |:------------------------|:-----------------|:--------------|-----------------------| -|Cisco Navigator | `CiscoOS 11.20 `|August 15, 2027 | 12 | +|Cisco Navigator | `CiscoOS 11.20 `|August 15, 2027 | 13 | |Audiocodes RX-Panel | `2.1.457`|August 15, 2027 | 12 | |Crestron TSS-770 | `2.001.0058` |September 3, 2025 | 10 | |Crestron TSS-1070 | `2.001.0058`|September 3, 2025 | 10 | diff --git a/Teams/teams-powershell-release-notes.md b/Teams/teams-powershell-release-notes.md index 60fd4186bf..69b64ac836 100644 --- a/Teams/teams-powershell-release-notes.md +++ b/Teams/teams-powershell-release-notes.md @@ -26,6 +26,7 @@ This page provides the latest Teams PowerShell change log for both General Avail | Date | Version | Updates | |------- | -------------------- | ------------------------------ | +| August 2024 | [6.5.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/6.5.1-preview) |
  • Releases Export-CsAcquiredPhoneNumber cmdlet.
  • Releases Get-CsExportAcquiredPhoneNumberStatus cmdlet.
    • | August 2024 | [6.5.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.5.0) |
  • [BREAKING CHANGE] Deprecates Set-CsOnlineDialInConferencingUserDefaultNumber cmdlet. More details in [Set-CsOnlineDialInConferencingUserDefaultNumber](/powershell/module/teams/set-csonlinedialinconferencinguserdefaultnumber).
  • Fixes mapping for postal code in Set-CsOnlineLisCivicAddress.
  • Releases [Get\|Set]-CsTeamsExternalAccessConfiguration cmdlets.
  • Adds CaptchaVerificationForMeetingJoin parameter to the [New\|Set]-CsTeamsMeetingPolicy cmdlets.
    • | July 2024 | [6.4.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/6.4.1-preview) |
  • [BREAKING CHANGE] Deprecates Set-CsOnlineDialInConferencingUserDefaultNumber cmdlet. More details in [Set-CsOnlineDialInConferencingUserDefaultNumber](/powershell/module/teams/set-csonlinedialinconferencinguserdefaultnumber).
  • Fixes mapping for postal code in Set-CsOnlineLisCivicAddress.
    • | June 2024 | [6.4.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.4.0) |
  • Adds ExternalAccessWithTrialTenants parameter to the Set-CsTenantFederationConfiguration cmdlet.
    • diff --git a/Teams/trusted-organizations-external-meetings-chat.md b/Teams/trusted-organizations-external-meetings-chat.md index af6cd7abac..949ea15726 100644 --- a/Teams/trusted-organizations-external-meetings-chat.md +++ b/Teams/trusted-organizations-external-meetings-chat.md @@ -137,33 +137,6 @@ When set to **Blocked**, users from these trial-only tenants aren't able to sear Users from trial-only tenants are blocked by default (with no option to override) from external communication with users in other Microsoft 365 cloud environments and with Microsoft Skype for Business server users. Two tenants with only trial subscriptions can federate with each other if the -ExternalAccessWithTrialTenants is Allowed by both tenants. -##### How block federation will affect your organization - -Teams PowerShell will support a new Tenant Federation setting, `-ExternalAccessWithTrialTenants`, with the values **Allowed** or **Blocked**. - -When set to **Blocked**, all external access with users from Teams subscriptions that contain only trial licenses will be blocked. This means users from these trial-only tenants won't be able to search and contact your users via chats, Teams calls, and meetings (using the users' authenticated identities) and your users won't be able to reach users in these trial-only tenants. - -If this setting is set to **Blocked**, users from the trial-only tenant will also be removed from existing chats. - -##### More information - -- A **trial tenant** is defined as a tenant with a Teams service plan that has only Trial subscriptions (0 purchased seats). -- Shared Channels and Anonymous Meeting joins won't be affected by this setting. -- The feature supports the tenant admin control only for same-cloud external communication. For cross-clouds and Skype for Business Server on-premises deployments, external communication with trial tenants will be disabled by default, with no option to override by the admin setting. -- If your tenant has disabled external access by default and is using a specific domain Allowlist instead, trial tenants will still be blocked even if they are in the organization's Allowlist. - -##### What you need to do to prepare - -- Tenant admins need to install the latest PowerShell package (6.2.2) and use the `Set-CsTenantFederationConfiguration` command to set the desired value for the federation with trial tenants: - - Download or upgrade to the latest PowerShell package: PowerShell Gallery | MicrosoftTeams 6.2.0 - - To allow external communication with trial-only tenants, use this command: -    `Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants "Allowed"` - - To block external communication with trial-only tenants, use this command: -    `Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants "Blocked"` - -> [!IMPORTANT] -> If you want to restrict external access for most trial tenants, but still allow a few legitimate trial-tenants with which you need to federate, you'll need to purchase a license for those specific accounts. - #### Diagnostic Tool If you're an administrator, you can use the following diagnostic tool to validate if a Teams user can communicate with a Teams user in a trusted organization: diff --git a/Teams/vdi-2.md b/Teams/vdi-2.md index 11cf3e2c38..704c3848a1 100644 --- a/Teams/vdi-2.md +++ b/Teams/vdi-2.md @@ -427,27 +427,31 @@ For further investigating VDI connection-related issues, using keyword **vdiBR ### Connection error -If there's a connection error, the error code can be found from the log line containing "loadErrc" and "deployErrc". The code logged here needs to be mapped using this table: - -|Error code |deployErrc |Definition |Notes | -|-----------|-----------|---------------------------------|------| -|0 |0 |OK |Special code for 'ConnectedNoPlugin' Telemetry Messages. | -|5 |43 |ERROR_ACCESS_DENIED |MsTeamsVdi.exe process failed at startup. Could be caused by BlockNonAdminUserInstall being enabled. Or the endpoint could be busy registering multiple MSIX packages after a user logon and it didn't finish registering SlimCoreVdi. | -|404 |3235 |HTTP_STATUS_NOT_FOUND |Publishing issue: SlimCore MSIX package isn't found on CDN. | -|1260 |10083 |ERROR_ACCESS_DISABLED_BY_POLICY |This error usually means that Windows Package Manager can't install the SlimCore MSIX package. Event Viewer can show the hex error code 0x800704EC. AppLocker Policies can cause this error code. You can either disable AppLocker, or add an exception for SlimCoreVdi packages in Local Security Policy -> Application Control Policies -> AppLocker. Check 'Step 3' under "Optimizing with new VDI solution for Teams". | -|1460 |11683 |ERROR_TIMEOUT |MsTeamsVdi.exe process failed at startup (60-second timeout). | -|1722 | |RPC_S_SERVER_UNAVAILABLE |'The RPC server is unavailable' MsTeamsVdi.exe related error. | -|2000 |16002 |No Plugin |Endpoint doesn't have the MsTeamsPlugin, or if it has it, it didn't load (check with Process Explorer). | -|2001 | |Virtual Channel Not Available |Error on Citrix VDA WFAPI. | -|3000 |24002 |SlimCore Deployment not needed |This code isn't really an error. It's a good indicator that the user is on the new optimization architecture with SlimCore. | -|3001 |24010 |SlimCore already loaded |This code isn't really an error. It's a good indicator that the user is on the new optimization architecture with SlimCore. | -|3004 |24035 |Plugin irresponsive |Try restarting RDP or ICA session. | -|3005 |24043 |Plugin timeout while downloading |Failure to download the MSIX within 2 minutes. | -|3007 |24058 |Load timeout |SlimCore download or installation timed out (slow internet or App Readiness Service is busy). | -|4000 | |ERROR_WINS_INTERNAL |WINS encountered an error while processing the command. | -|15615 |1951 |ERROR_INSTALL_POLICY_FAILURE |SlimCore MSIX related error. To install this app, you need either a Windows developer license, or a sideloading-enabled system. AllowAllTrustedApps regkey might be set to 0? | -|15616 | |ERROR_PACKAGE_UPDATING |SlimCore MSIX related error 'The application cannot be started because it is currently updating'. | -|15700 | |APPMODEL_ERROR_NO_PACKAGE |The process has no package identity. There's no alias for MsTeamsVdi in %LOCALAPPDATA%\Microsoft\WindowsApps. [Feedback Hub](https://support.microsoft.com/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) logs are needed while reproducing the error (make sure you select **Developer Platform** as the category and **App deployment** as the subcategory)| +If there's a connection error, the error code can be found from the log line containing "loadErrc" and "deployErrc". A deploy error (also known as install_error) is an error that happens when the plugin was trying to download the SlimCore MSIX package from Microsoft's CDN and stage or provision it to the endpoint using the App Readiness Service for AppX. A load error is an error that happens when the plugin tried to start MsTeamsVdi.exe and establish a Remote Procedure Call (RPC) to it. + +The code logged here needs to be mapped using this table: + +|loadErrc |deployErrc |Definition |Notes | +|-----------|-----------|-----------------------------------|------| +|0 |0 |OK |Special code for 'ConnectedNoPlugin' Telemetry Messages. | +|5 |43 |ERROR_ACCESS_DENIED |MsTeamsVdi.exe process failed at startup. Could be caused by BlockNonAdminUserInstall being enabled. Or the endpoint could be busy registering multiple MSIX packages after a user logon and it didn't finish registering SlimCoreVdi. | +|404 |3235 |HTTP_STATUS_NOT_FOUND |Publishing issue: SlimCore MSIX package isn't found on CDN. | +|1260 |10083 |ERROR_ACCESS_DISABLED_BY_POLICY |This error usually means that Windows Package Manager can't install the SlimCore MSIX package. Event Viewer can show the hex error code 0x800704EC. AppLocker Policies can cause this error code. You can either disable AppLocker, or add an exception for SlimCoreVdi packages in Local Security Policy -> Application Control Policies -> AppLocker. Check 'Step 3' under "Optimizing with new VDI solution for Teams". | +|1460 |11683 |ERROR_TIMEOUT |MsTeamsVdi.exe process failed at startup (60-second timeout). | +|1722 | |RPC_S_SERVER_UNAVAILABLE |'The RPC server is unavailable' MsTeamsVdi.exe related error. | +|2000 |16002 |No Plugin |Endpoint doesn't have the MsTeamsPlugin, or if it has it, it didn't load (check with Process Explorer). | +|2001 | |Virtual Channel Not Available |Error on Citrix VDA WFAPI. | +|3000 |24002 |SlimCore Deployment not needed |This code isn't really an error. It's a good indicator that the user is on the new optimization architecture with SlimCore. | +|3001 |24010 |SlimCore already loaded |This code isn't really an error. It's a good indicator that the user is on the new optimization architecture with SlimCore. | +|3004 |24035 |Plugin irresponsive |Try restarting RDP or ICA session. | +|3005 |24043 |Plugin timeout while downloading |Failure to download the MSIX within 2 minutes. | +|3007 |24058 |Load timeout |SlimCore download or installation timed out (slow internet or App Readiness Service is busy). | +|4000 | |ERROR_WINS_INTERNAL |WINS encountered an error while processing the command. | +|15615 |1951 |ERROR_INSTALL_POLICY_FAILURE |SlimCore MSIX related error. To install this app, you need either a Windows developer license, or a sideloading-enabled system. AllowAllTrustedApps regkey might be set to 0? | +|15616 | |ERROR_PACKAGE_UPDATING |SlimCore MSIX related error 'The application cannot be started because it is currently updating'. | +|15700 | |APPMODEL_ERROR_NO_PACKAGE |The process has no package identity. There's no alias for MsTeamsVdi in %LOCALAPPDATA%\Microsoft\WindowsApps. [Feedback Hub](https://support.microsoft.com/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) logs are needed while reproducing the error (make sure you select **Developer Platform** as the category and **App deployment** as the subcategory) | +|16389 | |E_FAIL reported by Package Manager |Usually the same as Load error code 5 (ERROR_ACCESS_DENIED). +Most likely caused by the BlockNonAdminUserInstall policy when the user is not an Admin. Check [this link](/windows/client-management/mdm/policy-csp-applicationmanagement#blocknonadminuserinstall) for more details. | ## Using Event Viewer on the VM for troubleshooting