You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Love what you're doing, wondering if you would be open to allowing us to use / combine your code with the windows_ad cookbook or offer suggestions on how to better handle joining domains.
Do you think checking for existence of the domain is necessary or is it acceptable to just allow the join to fail if the domain isn't found (DNS, typo etc.)
The text was updated successfully, but these errors were encountered:
That cookbook does look pretty comprehensive. I'd love to hear if there is a way to improve joining domains. We see very rare domain join problems when we quickly destroy and recreate a windows 2012R2 VM in some of our datacenters. (About 1 out of 100 fail to join)
Feel free to use what ever you want from this cookbook. Eventually these cookbooks could probably be merged, but we are using this one pretty heavily at the moment. The biggest feature that we use is rebooting the VM twice.
I don't think we do any checking to see if the domain exists.
@derekgroh I'd love to talk more about this.
We have 2 environments (prod, lab) , the cookbook works 100% of the time in one environment, and 95% of the time in the other.
What ways have you found to make the domain join more reliable?
Love what you're doing, wondering if you would be open to allowing us to use / combine your code with the windows_ad cookbook or offer suggestions on how to better handle joining domains.
Do you think checking for existence of the domain is necessary or is it acceptable to just allow the join to fail if the domain isn't found (DNS, typo etc.)
The text was updated successfully, but these errors were encountered: