Merge pull request #15318 from MicrosoftDocs/main

Publish main to live, Thursday 3:30PM PDT, 08/01
MicrosoftDocs · Aug 1, 2024 · 704c794 · 704c794
2 parents cc81fab + 305e25e
commit 704c794
Show file tree

Hide file tree

Showing 2 changed files with 50 additions and 0 deletions.
diff --git a/Teams/devices/teams-ip-phones.md b/Teams/devices/teams-ip-phones.md
@@ -171,6 +171,7 @@ The following are the latest firmware versions released via Microsoft Teams Admi
 #### <b> Yealink </b>
 | Device model  | Latest firmware version  | Minimum firmware version | Included Microsoft applications  | Release date|
 |:----------------|:-------------------|:----------------------------|:----------------------------------------------------------------------------------------------|:--------------------------------------------|
+|MP52 E2/MP54 E2/MP56 E2/MP58 E2| `176.15.0.19`| `N/A` | Teams client: `1449/1.0.94.2024071104` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: ` 1.0.0.202402202353.product`| July 31, 2023|
 |MP52| `145.15.0.94`| N/A | Teams client: `1449/1.0.94.2024060310` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: `1.0.0.202402202353.product`| July 2, 2024|
 |VP59| `91.15.0.147`| N/A | Teams client: `1449/1.0.94.2024060310` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: `1.0.0.202402202353.product`| July 2, 2024|
 |MP52| `145.15.0.83`| N/A | Teams client: `1449/1.0.94.2023072509` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202306202019.product`| January 18, 2024|

diff --git a/Teams/new-teams-vdi-requirements-deploy.md b/Teams/new-teams-vdi-requirements-deploy.md
@@ -284,6 +284,55 @@ Type: DWORD
 Value: 1
 ```
 
+## New Teams auto-start
+
+The auto-start behavior of Teams is controlled by three components:
+
+1. By default, MSIX-based applications will not auto-start until there is a first launch, because the Windows OS doesn't auto-start packages in a provisioned state. An AppX registration is needed with user consent. After the first launch, users can go to **Settings** > **General** and fill the **Auto-start Teams** checkbox, or enable auto-start from the Windows Setting menu.
+
+2. If the "Auto-start Teams" checkbox is greyed out, it means a system-wide GPO is disabling this option for UWP apps:
+
+```Registry editor
+[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] 
+"EnableFullTrustStartupTasks"=dword:00000000
+"EnableUwpStartupTasks"=dword:00000000
+"SupportFullTrustStartupTasks"=dword:00000000
+"SupportUwpStartupTasks"=dword:00000000
+```
+
+This registry setting causes the option to be unavailable in the operation systems under **Settings** > **Apps** > **Installed Apps**. In order to change this, create the regkeys with the values as shown below:
+
+```Registry editor
+[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
+"EnableFullTrustStartupTasks"=dword:00000002
+"EnableUwpStartupTasks"=dword:00000002
+"SupportFullTrustStartupTasks"=dword:00000001
+"SupportUwpStartupTasks"=dword:00000001
+```
+
+Restart the virtual machine to see the startup options active in the operative system’s settings menu.
+
+3. This registry key controls the Teams auto-start behavior, so you can enable or disable it programmatically.
+
+```Registry editor
+[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\TeamsTfwStartupTask]
+"State"=dword:00000002
+"UserEnabledStartupOnce"=dword:00000001
+```
+
+|State            |Number |Information                                                              |
+|-----------------|-------|-------------------------------------------------------------------------|
+|Disabled         |0      |The task is disabled.                                                    |
+|DisabledByUser   |1      |The task was disabled by the user. It can only be re-enabled by the user.|
+|EnabledByUser    |2      |The task is enabled.                                                     |
+|DisabledByPolicy |3      |The task is disabled by the administrator or group policy. Platforms that don't support startup taks also report DisabledByPolicy. |
+|EnabledByPolicy  |4      |The task is enabled by the administrator or group policy.                |
+
+You can learn more at [this link](/uwp/api/windows.applicationmodel.startuptaskstate#fields).
+
+> [!IMPORTANT]
+> If you're using non-persistent VDI, you must make sure the TeamsTfwStartupTask registry key is roamed. FSLogix ODFC containers won't roam this, so you must rely on your other profile management tools (VMWare DEM, AppSense, Citrix UPM) to persist this key.
+
 ## Profile and cache location for new Teams Client
 
 All the user settings and configurations are now stored in: