Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

Failed to start user in mtr

%3CLINGO-SUB%20id%3D%22lingo-sub-1099207%22%20slang%3D%22es-ES%22%3EFailed%20to%20start%20user%20in%20mtr%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1099207%22%20slang%3D%22es-ES%22%3E%3CP%3E%3CSTRONG%3Ewe%20can't%20sign%20you%20in%20because%20the%20server%20couldn't%20be%20reached%20or%20the%20server%20version%20is%20incompatible%20with%20the%20device%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3CSPAN%3EI%20receive%20this%20error%20to%20log%20in%20to%20an%20MTR%2C%20I%20manage%20to%20log%20in%20with%20a%20100%25%20cloud%20user.%20But%20with%20a%20user%20who%20is%20in%20an%20organization%20that%20uses%20ADFS%20gives%20me%20that%20error.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20need%20to%20help%20with%20this%20error%2C%20if%20someone%20had%20it%2C%20if%20the%20ADFS%20has%20something%20to%20do.%20Thank%20you.%20Sorry%20my%20bad%20English.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F164526i2EB843A2D85A6FF0%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Mtr%20Error.png%22%20title%3D%22Mtr%20Error.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%E2%80%83%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1099207%22%20slang%3D%22es-ES%22%3E%3CLINGO-LABEL%3Emtr%20teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1100706%22%20slang%3D%22en-US%22%3ERe%3A%20Failed%20to%20start%20user%20in%20mtr%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1100706%22%20slang%3D%22en-US%22%3EWhat%20kind%20of%20device%20are%20you%20using%3F%3CBR%20%2F%3EDid%20you%20check%20your%20certificates%3F%20Maybe%20the%20root%2Fintermediate%20is%20missing%20on%20the%20device%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1101205%22%20slang%3D%22es-ES%22%3ERe%3A%20Failed%20to%20start%20user%20in%20mtr%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1101205%22%20slang%3D%22es-ES%22%3Ecrestron%20Flex%20UC-C160-T%20device.%20Do%20not%20install%20any%20certificate.%20I%20am%20testing%20from%20outside%20the%20organization.%20I%20understand%20that%20this%20is%20why%20ADFS%20serves%20me.%20I%20will%20try%20to%20join%20the%20domain%20on%20the%20device.%20%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20joining%20the%20domain%20the%20device%20will%20not%20need%20any%20type%20of%20certificate%3F%20%3CBR%20%2F%3Ethanks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1101409%22%20slang%3D%22en-US%22%3ERe%3A%20Failed%20to%20start%20user%20in%20mtr%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1101409%22%20slang%3D%22en-US%22%3EShould%20be%20done%20automatically..%20but%20you%20can%20also%20try%20to%20create%20a%20cloud%20only%20user%20account%20in%20Office%20365%2C%20this%20way%20you%20bypass%20the%20ADFS.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1155130%22%20slang%3D%22en-US%22%3ERe%3A%20Failed%20to%20start%20user%20in%20mtr%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1155130%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F34020%22%20target%3D%22_blank%22%3E%40Erwin%20Bierens%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F512110%22%20target%3D%22_blank%22%3E%40TeoDVz%3C%2FA%3E%26nbsp%3B%20Is%20there%20any%20update%20on%20this%2C%20did%20you%20get%20it%20working%3F%20We%20also%20are%20trying%20to%20setup%20Crestron%20Flex%20devices%20and%20are%20also%20seeing%20the%20same%20issues%20as%20above.%20Using%20a%20cloud%20only%20account%20is%20not%20viable%20for%20us%20as%20we%20have%20no%20external%20mail%20routing%20in%20O365%20cloud.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1155578%22%20slang%3D%22es-ES%22%3ERe%3A%20Failed%20to%20start%20user%20in%20mtr%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1155578%22%20slang%3D%22es-ES%22%3E%3CP%3EYes%2C%20I%20am%20in%20the%20last%20tests.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eone-.%3C%2FP%3E%3CP%3EI%20uploaded%20the%20MTR%20console%20to%20the%20domain.%20Using%20the%20same%20user%20created%20when%20going%20through%20ADFS%2C%20I%20was%20in%20the%20login%20loop%2C%20checking%20the%20log%20I%20see%20that%20if%20you%20login%20to%20Microsoft%20Teams%2C%20but%20it%20gives%20an%20Exchange%20Autodiscover%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Etwo-.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20user%20assigned%20to%20the%20MTR%20is%20created%20and%20assigned%20an%20authentication%20policy.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESolution%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eone-.%3C%2FP%3E%3CP%3EConnect%20to%20EXO%20by%20powershell.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Etwo-.%3C%2FP%3E%3CP%3ENew-AuthenticationPolicy%20-Name%20%22Allow%20Basic%20Auth%20EWS%20on%20MTRs%22%20-AllowBasicAuthAutodiscover%3A%20%24%20true%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESet-User-Identity%20user%40domain.com%20-AuthenticationPolicy%20%22Allow%20Basic%20Auth%20EWS%20on%20MTRs%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENOTE%3A%20The%20name%20of%20the%20Policy%20may%20be%20the%20one%20you%20prefer.%20Let%20me%20know%20if%20it%20turned%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eregards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENoel%20Naveda.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1155978%22%20slang%3D%22en-US%22%3ERe%3A%20Failed%20to%20start%20user%20in%20mtr%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1155978%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F512110%22%20target%3D%22_blank%22%3E%40TeoDVz%3C%2FA%3EThanks%20Noel.%20We%20have%20just%20set%20this%20but%20still%20not%20able%20to%20sign%20in%20but%20expect%20we%20may%20need%20to%20wait%20some%20time%20for%20the%20policy%20to%20take%20effect%20on%20the%20account.%20We%20will%20test%20again%20in%20the%20morning%20and%20report%20back.%20Thanks%20for%20your%20help%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

we can't sign you in because the server couldn't be reached or the server version is incompatible with the device

 

 I receive this error to try to log in to an MTR, I manage to log in with a 100% cloud user. But with a user who is in an organization that uses ADFS gives me that error.

 

I need help with this error, if someone has had it, if the ADFS has something to do. Thank you. Sorry my bad English.

Mtr Error.png

7 Replies
What kind of device are you using?
Did you check your certificates? Maybe the root/intermediate is missing on the device?
a Crestron Flex UC-C160-T device. Do not install any certificate. I am testing from outside the organization. I understand that this is why ADFS serves me. I will try to join the domain on the device.

When joining the domain the device will not need any type of certificate?
thanks
Should be done automatically.. but you can also try to create a cloud only user account in Office 365, this way you bypass the ADFS.

@Erwin Bierens @TeoDVz  Is there any update on this, did you get it working? We also are trying to setup Crestron Flex devices and are also seeing the same issues as above. Using a cloud only account is not viable for us as we have no external mail routing in O365 cloud.

 

 

Yes, I am in the last tests.

 

one-.

I uploaded the MTR console to the domain. Using the same user created when going through ADFS, I was in the login loop, checking the log I see that if you login to Microsoft Teams, but it gives an Exchange Autodiscover error.

 

two-.

 

The user assigned to the MTR is created and assigned an authentication policy.

 

 

Solution:

 

one-.

Connect to EXO by powershell.

 

two-.

New-AuthenticationPolicy -Name "Allow Basic Auth EWS on MTRs" -AllowBasicAuthAutodiscover: $ true

 

Set-User-Identity user@domain.com -AuthenticationPolicy "Allow Basic Auth EWS on MTRs"

 

NOTE: The name of the Policy may be the one you prefer. Let me know if it turned out.

 

regards

 

Noel Naveda.

@TeoDVzThanks Noel. We have just set this but still not able to sign in but expect we may need to wait some time for the policy to take effect on the account. We will test again in the morning and report back. Thanks for your help

@dingbat 

 

Did you manage to get this working with the above change?

 

I also have the same issue.

 

Thank you for your help.