Skip to content

Commit b13559b

Browse files
authored
Merge pull request #134210 from VikasPullagura-MSFT/patch-142
(Azure CXP) resolves MicrosoftDocs/azure-docs#64509
2 parents e45a3d4 + 88d05e8 commit b13559b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-desktop/teams-on-wvd.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ You can deploy the Teams desktop app using a per-machine or per-user installatio
8686
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1
8787
```
8888
89-
This installs Teams to the Program Files (x86) folder on a 64-bit operating system and to the Program Files folder on a 32-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.
89+
This installs Teams to the Program Files (x86) folder on a 32-bit operating system and to the Program Files folder on a 64-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.
9090
9191
There are two flags that may be set when installing teams, **ALLUSER=1** and **ALLUSERS=1**. It is important to understand the difference between these parameters. The **ALLUSER=1** parameter is used only in VDI environments to specify a per-machine installation. The **ALLUSERS=1** parameter can be used in non-VDI and VDI environments. When you set this parameter, Teams Machine-Wide Installer appears in Program and Features in Control Panel as well as Apps & features in Windows Settings. All users with admin credentials on the machine can uninstall Teams.
9292

0 commit comments

Comments
 (0)