Jump to content

Recommended Posts

Posted

I've come across this article that seems to cover a number of issues around installing various elements of Office / Microsoft Apps / Whatever they are calling it today, so it may prove helpful: https://www.christiaanbrinkhoff.com/2019/04/27/the-little-unknown-secrets-of-using-office-365-proplus-and-office-2019-on-a-virtual-desktop-environment-survival-guide/

 

Buried in there I found this about installing Teams per-machine, please note that I have not tested this myself yet:

 

"Install Microsoft Teams per-machine

 

First we must create the following registry key in the image

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\IsWVDEnvironment]

Type: REG_DWORD Value: 1

 

Download Teams and run the command below to install Teams per-machine

 

Note: To use the WebRTC AV redirection client, you must use Teams version 1.3.00.4461 or later – the 64-bit version is highly recommended.

•64-bit version (recommended)

•32-bit version

msiexec /i c:\install\Teams_windows_x64.msi /l*v c:\install\Teams.log ALLUSERS=1 ALLUSER=1

 

If everything ran perfectly you will see Teams showing up in the Program Files directory."

 

 

If you have already done this, how did it go? I haven't seen anyone mention this in the past, on here.

  • Thanks 1
Posted

I've tried this however one thing to note is that it seems to install to each user's AppData directory. Even though it is still machine wide, it'll copy itself into AppData.

 

Not sure why that is but I know for us it caused a ton of sync issues due to log files Teams creates in AppData.

Posted
You can just deploy the MSI that Microsoft offer, but it does indeed install directly into AppData for each user on login, which means for anyone with UE-V and no local profile stored, it takes a few minutes each time before it's available. It's a pain in the wossit, frankly; I gather it's done this way so that the client always has the rights to update itself, because it's updated so often, but it reeeally doesn't work with the way a school works (see also: syncing to OneDrive for Business)
  • Thanks 1
Posted

Thanks for this guys, days like this that I really appreciate edugeek.

 

Our plan is set in motion for September which means staff will be moving around and the kids staying put. We've upgraded all our staff machines to 250GB SSDs for space and all the profiles going along with it.

 

Teams is something we are heavily looking at - the good part is at the moment we just want to use Virtual Meetings.

Posted
msiexec /i teams_windows_x64.msi OPTIONS="noAutoStart=true" ALLUSER=1 ALLUSERS=1

 

The reg key you need is HKLM\Software\Citrix\PortICA

 

Works for us...Definitely installs and runs from c:\program files (x86)\microsoft\teams\current\teams.exe

 

It does dump a load of stuff into appdata, but not the exe

 

https://www.vcloudinfo.com/2020/01/microsoft-teams-cannot-install-vdi-environment-is-not-detected.html

 

Are you sure? That registry key is for Citrix VDA and not Teams? Don't see how that could change anything.

Posted
Are you sure? That registry key is for Citrix VDA and not Teams? Don't see how that could change anything.

 

It's the VDI only flag (ALLUSER) you're using though he's referring to :p Worth reading the link he linked.

 

Steve

Posted
Ah. I see. That's interesting. Odd that Microsoft wouldn't have VDI checks for RDS and only VMWare / Citrix?

 

Would the reg key in my OP not resolve this?

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\IsWVDE nvironment]

Type: REG_DWORD Value: 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...