This message was deleted.
# _general
s
This message was deleted.
d
You can use a MST from materpackager to set some properties like autolaunch and desktop shortcut https://www.masterpackager.com/blog/mst-to-install-microsoft-teams-msi-vdi-to-regular-windows-10
n
I have just been deleting the desktop shortcut and registry key for the autolaunch as part of my install (since I had been doing that in early testing).
s
Thanks, Rene and Nick. Nick, if your testing watch out for the fact that almost any user setting thats rights to the JSON, does not work. While I only tested open application in background, and autostart, I am almost positive that every setting in that left hand colum rights to the JSON file and if it does it wont work.
n
How were you applying those settings before? Copying them to the install directory in AppData? I believe that’s what I was trying to do last year before the machine installer was released. This is one of those things that Microsoft really needs to expand upon in group policy.
s
There is a setup.json in program files that sits with the installer that you can edit so that when a user logs for the first time after you install the teams vdi msi it should use as defaults when they login. (It doesnt) Then there is the json that is in each users app-data that gets written to when a user selects their own preference in the above screen shot. While I cant remember if the settings above are wrote to the appdata json like they should be, but it doesnt matter. All json files are ignored when using ALLUSER=1
So not only can you not setup first time defaults through the setup.json in program files, you cant push settings to the users after the install through the desktop-config.json in appdata, and then users can not keep their own choices saved in the above picture. (Because all these settings write to the json) The GPO would be great, but the GPO that is out there only works with the PROplus version of office or the version of teams that comes with 365. So basically we are screwed using the VDI multiple ways. And to answer you, before using the VDI MSI I could edit the json files and thats how i got my defaults and etc for teams. The only way teams looks at json is to use the non VDI version and live with all the bloat in the profile (Or technically the vdi version without the ALLUSER=1)
j
There must be setting that look for that json file strickly in %localappdata%. Maybe you can find it running procmon.
Once you've find that setting, you could redirect it using FSLogix app masking. You can redirect hklm reg key to hkcu and files to user profiles as well.
s
Jonathan, thats the issue. Running the MSI in VDI mode by using the switch Alluser=1 makes teams completively ignores json files. It ignores the setup.json and it ignores the desktop-config.json file. It must be a bug. Redirecting it to any other json file anwhere else wont help as it doesnt respect json files.
n
So I'm testing v1.3.00.4461 of Teams using that switch, and if I modify C:\Users\*\AppData\Roaming\Microsoft\Teams\desktop-config.json Teams does seem to obey the changes.
👍 1
k
@Nick Panaccio are you using some fancy JSON editor, or jus plain old Notepad?
n
Plain old Notepad. If I were looking to set some defaults, I'd create a WEM PowerShell task to load the file, then search/replace text strings.
I tested by changing "runningOnClose":true to false.
d
Nick, that’s exactly what we need. We have customers that use Teams as a pub. app. Closing Teams doesn’t really quit the app, so I have to try this out. It’s a big mess with all the O 365, FSL, RDS and VDI issues. It all doesn’t work together yet and I assume it never will 😤
k
I cannot believe MS is making us modify/edit JSON files to enable us to do some pre-configuration of Teams
n
I can, unfortunately.
@Dennis: Returning the favor. Here's my QA Teams Config task for WEM, script included.
👍 1
Should be pretty easy to modify for any other setting you want to adjust.
k
Thanks!
I agree it should be fairly easy to extend that script to do some additional configuration
Like dark mode 🙂
n
I think I may roll with this, but one stumbling block I'm seeing is that I only want it to run once, letting the user choose whether or not they want it to run in the system tray (that's how I use Teams). If the WEM task launches before they launch Teams for the first time, this won't do much unless I run it constantly.
k
Who can live without dark mode?
n
Could always just replace the contents of that script with Get-Process Teams| Stop-Process -Force...
k
Hmm...yes it would be nice if WEM had a feature like Invanti where you can configure something to run at process startup
You could do that, it's not a pretty solution though
n
You could get a little dirty and modify the PS script to check for that file first. No file, exit. Once it finds the file, modify it, then create a new blank file that the script also looks for. If that blank file exists, no more modifying the json.
k
Hmm...WEM has the "execution order" feature, I haven't worked very much with that, but if I remember correctly it should enable you to execute something before something else
I can see that you can configure execution order on an external task
n
I thought that was just to choose which of your WEM execution tasks went before the other?
k
It is and you can't configure execution order on actions
sorry not actions application shortcuts
At a few customers I use WEM to execute Teams, because they don't want all users running Teams
I remove the registry entry in Run and then configure WEM to start Teams
n
Ahhh. Yeah, I remote the reg entries for Teams. I had planned on users manually launching it, since we'll have both Teams and Skype at the same time for a while.
If we lose Skype, then I'll definitely be using WEM to launch it.
s
@Nick Panaccio Nick, are you using the full command? msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1
n
All but the logging, yes.
r
I am curious why you guys are using both?ALLUSER=1 ALLUSERS=1
s
You only really need the ALLUSER=1 to run it in VDI mode. The ALLUSERS=1 adds it to the control panel uninstall so that if needed it could be uninstalled on a per user basis on the machine
r
Oh ok, I just read this If you have dedicated persistent VDI environments and you want the Teams application to auto-update and would prefer Teams to install per-user under Appdata/Local, use the .exe installer or the MSI without ALLUSER =1.
So looks like I woudnt want that
Shit read it wrong, so I do want ALLUSER =1. ( because I dont want it updated) and ALLUSERS=1 adds it to the control panel
s
you want alluser=1 to run it in VDI mode. The no auto update is more of a limitation then a reason to run it in vdi mode.
and yes allusers=1 adds it to control panel
r
Thanks man.
We are getting ready to deploy this. Not looking foward to it
s
So far I had to throw it into production with 0 testing. No real problems besides a few gothas here and there. Is this in VDI or a session host liek 2016
r
Going to be Both. I tested in 2016 with the API hooks and it works ok. But havent tested with VDI yet
This was what I used for 2016 https://support.citrix.com/article/CTX265011
s
for me it worked with out the above link.
r
Oh. well damn
Oh I also had to add Teams.exe to excludimagenames for the API part for the hooks
s
But now that i read, i publish full desktops and not lauching it seamlessly like the article states
r
If it works for you, It might be because I had 2 versions ago.
s
As a follow up. This is a recognized issue now. There is a workaround at the bottom of James website comments but I am leary of using it as it throws up errors. https://james-rankin.com/articles/microsoft-teams-on-citrix-xenapp/ when ran manually