Teams Admin Portal or 3rd party Management for Devices

%3CLINGO-SUB%20id%3D%22lingo-sub-2494494%22%20slang%3D%22en-US%22%3ETeams%20Admin%20Portal%20or%203rd%20party%20Management%20for%20Devices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2494494%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20following%20questions%20have%20arisen%20regarding%20device%20management%20in%20Teams.%26nbsp%3B%20Specifically%20for%20IP%20Phones%2C%20but%20could%20apply%20to%20other%20devices.%3C%2FP%3E%3CP%3E1)%26nbsp%3B%20Is%20there%20any%20way%20to%20look%20at%20detailed%20reports%20for%20device%20updates%3F%20success%20(what%20was%20actually%20updated)%5CFailure%20(exactly%20why%20did%20it%20fail)%3C%2FP%3E%3CP%3E2)%26nbsp%3B%20What%20about%20summary%20reports%3F%26nbsp%3B%20Updating%20bulk%20batches%20should%20show%20success%5Cfailure%20with%20a%20drill%20down%20as%20to%20why%20the%20updates%20failed.%3C%2FP%3E%3CP%3E3)%26nbsp%3B%20Detailed%20reports%20for%20the%20devices.%26nbsp%3B%20Having%20to%20pull%20up%20individual%20devices%20and%20then%20History%20is%20cumbersome%20and%20time%20consuming.%3C%2FP%3E%3CP%3E4)%26nbsp%3B%20Can%20the%20time%20period%20devices%20are%20allowed%5Cnot%20allowed%20to%20update%20be%20set%20anywhere%3F%3C%2FP%3E%3CP%3E5)%26nbsp%3B%20Method%20to%20set%20up%20separate%20groups%20for%20doing%20updates.%26nbsp%3B%20POC%20group%20and%20then%20other%20groups.%3C%2FP%3E%3CP%3E6)%26nbsp%3B%20More%20control%20for%20the%20updates%20other%20than%20Immediately%5C30%20day%20defer%5C90%20day%20defer.%26nbsp%3B%20If%20using%20OVOV%20or%20YMCS%2C%20need%20to%20be%20able%20to%20turn%20off%20the%20Microsoft%20device%20updates%20so%20any%20newer%20updates%26nbsp%3B%20installed%20using%20OVOC%5CYMCS%20are%20not%20overwritten.%3C%2FP%3E%3CP%3E7)%26nbsp%3B%20Reporting%20that%20doesn't%20give%20errors%5Cwarnings%20for%20devices%20if%20the%20installed%20version%20is%20newer%20than%20the%20Microsoft%20released%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20there%20are%20more%20than%2040%20devices%20in%20a%20deployment%2C%20the%20Microsoft%20Admin%20portal%20becomes%20very%20difficult%20to%20manage%20all%20of%20the%20devices.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2494494%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

The following questions have arisen regarding device management in Teams.  Specifically for IP Phones, but could apply to other devices.

1)  Is there any way to look at detailed reports for device updates? success (what was actually updated)\Failure (exactly why did it fail)

2)  What about summary reports?  Updating bulk batches should show success\failure with a drill down as to why the updates failed.

3)  Detailed reports for the devices.  Having to pull up individual devices and then History is cumbersome and time consuming.

4)  Can the time period devices are allowed\not allowed to update be set anywhere?

5)  Method to set up separate groups for doing updates.  POC group and then other groups.

6)  More control for the updates other than Immediately\30 day defer\90 day defer.  If using OVOC or YMCS, need to be able to turn off the Microsoft device updates so any newer updates  installed using OVOC\YMCS are not overwritten.

7)  Reporting that doesn't give errors\warnings for devices if the installed version is newer than the Microsoft released version.

 

If there are more than 40 devices in a deployment, the Microsoft Admin portal becomes very difficult to manage all of the devices.

0 Replies