I think you got it figured out Jordan. I tried with a object that didn't previously exist and it worked.
I've been manually deleting the old computer objects beforehand, but I dont think I've been giving it enough time to replicate (our AD structure is messy/slow right now) I'll probably work a 'delete computer object' and 'wait 5 minutes' into my vm provisioning script (the one we've been working with here) Appreciate the help once again! On Sunday, March 1, 2020 at 9:02:41 PM UTC-8, Jordan Borean wrote: > > If you have multiple DCs then potentially it could be replication at fault > here but usually if a host is missing from the domain controller it queries > then a different error is shown (service not found in the database). > > Is the host you are connecting to sharing the same hostname as an older > host that it's potentially replacing? If so the SPN could be registered > under the newer host on 1 DC but still not been replicated to another DC > where it still thinks hostname is another host. Each host would technically > have it's own unique key and when the server goes to check the credentials > it is unable to decrypt the secret because it's using a different key than > the one the DC thought it had (older host) and thus think the credentials > were bad. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9244a1a2-714f-46f3-a055-caf18780b3ff%40googlegroups.com.
