If I recall I've had problems in the past where a machine has moved from one domain to another. You can wind up with an orphaned computer account in active directory in the old domain (IIRC this affected older AD versions). Fix was to remove the Computer account from the old domain.
That said, I am not sure now if this caused winrm problems or whether it affected something else that stopped us from working - thought I'd mention it anyway. Jon On Thursday, April 6, 2017 at 10:05:59 AM UTC+1, Noel Verhoeven wrote: > > I have struggled with this a lot. I have run into the fact that a new > windows host, joined to a domain, sometimes needs to be rebooted again in > order to have its domain name reflected correctly in its group policies. I > have had GPresult /r say another domain name then what is displayed no the > computer properties screen. > -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/09cc4103-2ec9-480a-a143-dabaf4ef0d80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
