https://worldofeuc.com logo
Join Slack
Powered by
How is everyone handling Teams as a published app ...
# microsoft-365
n
How is everyone handling Teams as a published app where by default it remains open on close? I wrote a PS script to edit the app_settings.json file to change _keep_app_running_on_close_ from True to False, and while it works, the second a user goes into Settings the change is reverted back to True.
r
I guess it's not an option but out of curiosity, why publish Teams to begin with? In my world, if a user needs Teams I give them the full Desktop.
n
I can't even answer that. I'm helping out the Ops team with this, and they apparently have a use case where this one team uses nothing but Teams as a published app. Makes no sense to me. I'd almost rather give them Teams via Edge, but the lack of optimization would cripple the VDAs.
👍 1
c
i use this but i have ivanti
n
Does Ivanti continually edit the file? My PS script delivered via WEM works, but something in the GUI changes the setting back almost immediately. I modified it to save it to a secondary file just to confirm, and it is definitely working.
I have a ticket open with MS and they are hell bent on me sending them a video of this even though I have explained to them multiple times that the changes happen in the background and you would not see it.
c
yeah open process > check file exists> update file
let me find a old post as other people had different methods
n
And it still monitors the file? I thought about updating the file and grabbing a timestamp of it, and keeping the process running while ms-teams is running. Every time the timestamp changes it modifies the file and updates the timestamp. But that seems incredibly exhaustive.
c
dont think it constantly monitors the file it only runs when ms-teams.exe process is started. Are you finding the setting is reverted when users go into teams settings ?
they manually changing
n
They don't even have to do that. The JSON is updated via script, and then x minutes later it's reverted.
Manually changing the value in Settings does stick. It's only when manipulating it via script that I see this behavior. Almost like Teams has its own check and backup/restore.
c
dont think mine gets reverted might be the way its editing the json. I can remember someone say they used WEM to modify the app_settings.json but cant find the post
n
Yeah, I'm using WEM to do this.
c
wem has built in json editing
n
It does, but I'm using an External task
WEM's JSON stuff looks like it's for net-new/staging stuff, not editing an existing file that you have to wait to be created first
c
n
Dennis is basically doing exactly what I'm doing in the script
I mean, I know my script works
I can copy the file quickly and see the changes it has made, but something is reverting it.
Gonna give this new script a shot where it continually monitors the file in that first session (run once) to see if I get different results.
At the end of the day, this is just another example of MS being enterprise hostile.
c
its so stupid as you cant copy in a custom app_settings.json and the file only gets created at first run
n
yep
At least with Classic Teams you could prestage the damn json file
I'm simply unable to get this 'keep app running on close' value to false. I wrote a script to monitor the JSON file, and with any change it reverts this settings. However, when you click on the X, Teams simply minimizes. Even if I modify the file and exit Teams it returns. I don't know others are able to successfully get this to work. And mind you, my script worked like 3 or 4 Teams builds ago. Seems like something changed.
To add to this, I submitted a ticket with MS where I was basically told there is no central policy control for anything Teams and that they don't feel that there is a need for it. Incredible response, but I did submit what they consider a feature request for this. They won't do anything about it, but I've at least done my part.
j
"The way we think you should run Teams is the right way. And yes, that means you should have it open at all times and be unable to save any type of resource because if you want to save resource then that just means really YOU NEED MORE COMPUTE"
c
maybe you got to modify the json directly rather than through a script as my Ivanti method seems to work. teams open processes running > close teams processes not running
this is my ivanti config
n
I've tried editing directly, as well, but that setting doesn't seem to want to stick now
There is a JS file that apparently monitors the file and is reverting our changes
😮 1
image.png
bundle.js
j
Delete it and create a folder called bundle.js so it can't come back
n
Bundle.js is actually in the install directory for Teams, not in the profile
j
Same applies
c
let me see if i can check that file in my enviroment
i see a bundle.js in Program Files\WindowsApps\MSTeams_26134.1702.4747.7366_x64__8wekyb3d8bbwe\client-bindings
n
That's the one. And it's massive. Looks like it does a ton of stuff, and it's not even clear what it's setting anything to.
c
they moving loads of config to the tenant level but dont ever recall seeing that setting
n
I'm legit considering trying Teams via Edge with BCR to see if that actually works.
j
I think I did Teams with BCR a long time ago, but obvs that was the old client
j
I am able to update the run in background via the json, maybe it's different for this setting but you need to roam it correctly to get it working otherwise if it's considered a first run, it will reset the values. Memory usage is through the sky. I made load of saving by excluding those API hooks ... I wonder if WEM would help here? I tried BCR on v2 and couldn't it working nicely
n
Yeah, BCR just isn't cooperating. I'm using WEM for my script, BTW.
j
WEM helping was to save memory. I use a basic Posh to update it.
n
That's what I mean, a PS external task delivered via WEM.
👍 1
5 Views
Open in Slack
PreviousNext
Powered by