Forum Discussion
bad history with teams
Ed Woodrick thx. if it was jitter it appears from what i just read that my phone would have the same problem and it doesnt. i use teams now and then on my phone using the same wifi and location in my house without issue. as for whats installed on my pc, its basically the same as the old. and on the old i never had a problem with products like zoom. essentially i have sql server (which should mostly be inactive), outlook and chrome installed. there are a couple of development tools but they arent normally open anyway.
does anybody know how/where a support ticket can be entered for this issue?
I entered a ticket (#2309040040006667) on the 365 admin portal. It isnt clear if i'll be charged for this help. I'll probably decline if thats the only choice.
- we'll see later how this worked as MS apparently closes tickets before they are proven to be solved. And makes you reopen or re enter if the solution was "premature". And they get you to fill out a survey before you know if the solution worked.
nonetheless, my assigned tech set a property in the installed teams instance called "compatibility". He used some terms when speaking to me that only an msft employee would understand but it wasnt terrible and he was patient when i sometimes questioned him on stuff like that. He explained that this property was left "unset" when an "exploratory" version (e3 maybe ef3) of teams was installed by ms with creds belonging to a virtual user (these are necessary when setting up a free azure subscription) in my tenant. He set that compatibility to windows 2007. I run w11 pro but that choice didnt appear in the dropdown.
one thing that bugged me after we were done is what would happen if i stayed on the web when clicking a teams invite. i think that is always an option but i'll wait for another day to understand that more clearly. the concern is that a web based instance may not care about properties set locally on the installed app.- that didn't work in today's meeting. Assuming there are no other new mitigating factors, it made it worse. I'm usually fine with one other attendee in a teams meeting but this time it was bad even that way. I never have problems with zoom etc.
Lots more to say about not being able to personally reopen the prematurely closed service ticket but that story is too convoluted to post here. I sent my tech an email asking him to do that.I sent an email to the tech's ms manager and leads complaining about this...this is pretty frustrating..