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
Add optional server argument to allow join to specific domain controller.
ISSUE TYPE
Feature Idea
COMPONENT NAME
microsoft.ad.membership
ADDITIONAL INFORMATION
In large environments with globally distributed domain controllers, a random domain controller is chosen during the join process. After joining and rebooting, the host may fail to log in to the domain because the join might have been completed on a remote domain controller. In such cases, the domain replication changes may not have propagated to the domain controller handling the login request. Assigning a specific domain controller will avoid this issue. See -server parameter from add-computer cmdlet: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/add-computer?view=powershell-5.1
- name: join host to ansible.vagrant with automatic rebootmicrosoft.ad.membership:
dns_domain_name: ansible.vagranthostname: mydomainclientdomain_admin_user: [email protected]domain_admin_password: password123!domain_ou_path: "OU=Windows,OU=Servers,DC=ansible,DC=vagrant"server: mynearestloginserverstate: domainreboot: true
The text was updated successfully, but these errors were encountered:
I presume that Add-Computer uses DsGetDcName to lookup the DC to use, so it should use the closest one (requires you to have your sites configured correctly). Nonetheless, this feature might be useful in some cases, I do not see a harm in adding it.
SUMMARY
Add optional server argument to allow join to specific domain controller.
ISSUE TYPE
COMPONENT NAME
microsoft.ad.membership
ADDITIONAL INFORMATION
In large environments with globally distributed domain controllers, a random domain controller is chosen during the join process. After joining and rebooting, the host may fail to log in to the domain because the join might have been completed on a remote domain controller. In such cases, the domain replication changes may not have propagated to the domain controller handling the login request. Assigning a specific domain controller will avoid this issue. See -server parameter from add-computer cmdlet:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/add-computer?view=powershell-5.1
The text was updated successfully, but these errors were encountered: