Office 2016 and Kerberos

[clareq]

I'm looking at rolling out Office 2016, however, when I try and run any Office 2016 program on a Mac (running Yosemite, authenticating to AD) I get a pop up "Kerberos authentication required". Putting in the user password returns "unable to reach any KDC in realm , tried 0 KDCs"

 

Logging on as a local user also gives the pop-up.

 

I have run the VL Serializer as part of the DeployStudio Task Sequence when loading the machine.

[Achandler]

It's not Office 2016 trying to go online and your school is using Kerberos Authenication is it.

 

First run with Office does that how to update check and maybe even an activation check, that might be erroring/ not support Kerberos hence the issue.

[Achandler]

It's not Office 2016 trying to go online and your school is using Kerberos Authenication is it.

 

First run with Office does that how to update check and maybe even an activation check, that might be erroring/ not support Kerberos hence the issue.

[clareq]

Maybe it is, but there is no reason they can't go on-line. We go through a Smoothwall proxy, but Microsoft is whitelisted. Do I need to configure Smoothwall to allow this?

[clareq]

Maybe it is, but there is no reason they can't go on-line. We go through a Smoothwall proxy, but Microsoft is whitelisted. Do I need to configure Smoothwall to allow this?

[Achandler]

Some programs/ websites need to be exceptions as oppose to being whitelisted because they can't see the Kerberos or NTLM details.

 

If you swap your proxy on the mac to be one where you have to type in your username and password instead (usually uses port 8080 on smoothwall), then see if it instead asks you to type that in. If it does, try typing it in and see if it works.

[Achandler]

Some programs/ websites need to be exceptions as oppose to being whitelisted because they can't see the Kerberos or NTLM details.

 

If you swap your proxy on the mac to be one where you have to type in your username and password instead (usually uses port 8080 on smoothwall), then see if it instead asks you to type that in. If it does, try typing it in and see if it works.