I was instructed to change the UPN for users because of O365 migration and Bit Titan. I tested with my user account chris@newupnA.com and everything seemed to work fine. I did every user's and now I'm getting a bunch of Kerberos errors like this:
A Kerberos authentication ticket (TGT) was requested.
Account Name: Username@newupnB.com
Supplied Realm Name: DOMAINNAME.LOCAL
User ID: NULL SID
Service Name: krbtgt/DOMAINNAME.LOCAL
Service ID: NULL SID
Client Address: ::ffff:10.1.0.182
Client Port: 57618
Ticket Options: 0x40810010
Result Code: 0x6
Ticket Encryption Type: 0xFFFFFFFF
Pre-Authentication Type: -
Certificate Issuer Name:
Certificate Serial Number:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options, encryption types and result codes are defined in RFC 4120.
There are 3 new UPNs that are different based off of which department the users are in, but they're all still members of the same domain realm in AD. It looks like the Kerberos ticket includes the FQDN(with the new UPN) as the authenticating accountname, but is trying to access using the old domain realm. Obviously this is going to fail..
Anyone seen this issue before?
Anyone know if adding the suffix's to Domains and Trusts will fix this and is a smart thing to do?
Any help is welcome.
Thanks in advance!
In exchange environments, the point is to make the UPN match the email of the person so the person just uses the UPN to login into their email.
Make sure that the request is well formatted (using Prewindows 2000:: DOMAIN\User) or (UPN)
look at this: krbtgt/DOMAINNAME.LOCAL (this is backward, the format is USER\DOMAIN instead of DOMAIN\USER)