-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xADDomain and xADDomainController: Ability to enable/disable Global Catalog #75
Comments
Couple comments. Be careful about GC placement without planning your FSMO holders. The scenario you paint would be bad in a multi-domain forest since the infra master would be a GC and your other DC's would not.
" |
I am submitting a pull request with the IsGlobalCatalog option for the xAdDomainController. |
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Added new parameter to disable or enable the Global Catalog (GC) (issue dsccommunity#75).
- Changes to xADDomainController - Added new parameter to disable or enable the Global Catalog (GC) (issue #75). - Fixed a bug with the parameter `InstallationMediaPath` that it would not be added if it was specified in a configuration. Now the parameter `InstallationMediaPath` is correctly passed to `Install-ADDSDomainController`. - Refactored the resource with major code cleanup and localization. - Updated unit tests to latest unit test template, and refactored the tests for the function 'Set-TargetResource'. - Improved test code coverage.
Currently all DC's promoted using xADDomain and xADDomainController are set as GC's.
This is fine for the first DC on in a domain (or site), but usually undesirable for additional DC's added to a domain (usually only one GC per site is recommended).
Could we add a parameter to disable GC when promoting a DC? If the DC is already promoted then this switch would need to disable GC on the DC by calling something like this:
http://blogs.msmvps.com/richardsiddaway/2012/03/18/enable-global-catalog/
This probably only needs to be added to the xADDomainController resource because there must always be at least one GC in a domain so the xADDomain should always create a GC, although, if the first DC on the domain (that was promoted using xADDomain) needed to have the GC removed then xADDomain should also support enabling/disabling the GC. Thoughts?
I don't think that this needs to be a tri-state switch (like the DNS one).
The text was updated successfully, but these errors were encountered: