@oksana said in Changes to Kerberos and Azure Active Directory Authentication:

Kerberos is an authentication protocol that has been around since Windows Server 2000.

That should read: Kerberos is an authentication protocol that was introduced to Windows in Server 2000.

It was around for a long time before then: https://en.wikipedia.org/wiki/Kerberos_(protocol)

So, because Veeam reapplied the old snapshot, everything between then and now was lost.

If I keep the old snaphot as current, all the systems have domain trust failure.
I have a backup and there is only a single shared folder on here that will need restored.

Because this site is only 20 Windows computers, and I wanted to stop wasting time after 2 hours, I went brute force.

I disjoined everything from the domain and rejoined them.
With that resolved, I restored the C:\shares folder on the DC from the last Veeam backup.
Site is now working again.
Veeam's replication is now also in the correct state to fall back the replica to the main hyper-v server.

Not fucking touching that tonight.. I R DUN.

Edit: Maybe not the perfectly correct answer, but the answer I went with.

Azure AD's Use of SAML Protocol

See the following for ideas as to how you can accomplish what you're seeking to do:

https://macmule.com/2011/09/08/how-to-map-drives-printers-based-on-ad-group-membership-on-osx/

@DustinB3403 said in FreeNAS Domain Failure on AD:

@scottalanmiller any news yet?

Nope

OpenLDAP is what the average Linux shop is going to turn to when looking to implement an "AD like" authentication mechanism when no Windows is involved.