Aug 18 2021 11:03 AM
Hello!
Not sure if TAC = Teams Admin Center behaves strange or I my expectations are fundamentally wrong:
Case1:
Say I have a brand new Teams device (say a MTR) setup with room1@mydomain.com account it does show up in the TAC of mydomain.com.
However if I simply logout and repurpose it by using room2@OTHERDOMAIN.COM it is still reporting back to the mydomain TAC for some time INCLUDING that the unit is now using an otherdomain.com account.
=> My expectation would be, that it would immediately stop reporting back to the old TAC as in not even disclosing what the new account is.
Case 2:
Let's move on and simply setup another MTR with our old MYDOMAIN account.
Now guess what? TAC totally freaks out, by still showing the account linked to the old MTR incl. showing its last known config incl. the otherdomain.com
BUT
assigning the CDRs of the new MTR to this very account.
So yes, TAC show the acount being offline for many weeks but CDRs from todays meeting (with the new hardware). There seems to be no way of forcing TAC to read in the current config of this very account.
CASE 3:
It keeps getting better. IF I delete this device from the TAC I would assume, that it comes back with the new info within a short time frame. But NO; even after waiting a few hours, there is still no MTR listed in TAC although the unit works perfectly.
Q:
a) what is the correct way of decomissioning an MTRoW and hand it over to another domain?
b) How to bring back an (accidently) erased device into TAC?
Thanks for reading through this.
HST
Aug 19 2021 02:21 AM
Aug 19 2021 02:33 AM
Aug 19 2021 08:43 AM
Sep 19 2021 12:16 PM
Sep 29 2021 02:57 AM
Oct 28 2021 02:37 AM
Solution@Harald_Steindl Noncertified devices (home hacks) do not show in up TAC
Oct 28 2021 02:37 AM
Solution@Harald_Steindl Noncertified devices (home hacks) do not show in up TAC