-
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
Add RODC Creation Support #40
Comments
Commenting here as I am also curious if this will be supported. Otherwise, I guess using a custom script block in the DSC template will do? |
I'd like to see RODC in DSC as well. It's now 2017 and it's a simple parameter creation. Maybe write our own?? |
Hi @johlju - is this still relevant? |
@SSvilen If someone want to add this then I'm all for it, happy to review a PR that adds this. 🙂 |
I need to pre-provision the RODC account and then i need to promote it. Do I pick up a single domain controller to work with for both operations or is there another standard for such operations? |
The cmdlet |
Not sure we should have a resource that creates that pre-staged account, should we? It is one-time thing, and nothing that can be enforced, and needs to be done by a domain admin. I think to solve this issue I think we at least need to support the parameter |
You are right - you can provision RODC with Install-ADDSDomainController directly. But we could also build the functionality to pre-provision the account, couldn't we? I would still a part of xADDomainController - just a separate set of options. |
Creating a pre-staged (computer) account sounds more something xADComputer would do, not xADDomainController. Or another (new) resources. But what node should create the pre-staged account? It wouldn’t be the node that will end up as RODC, because then it wouldn’t make since to use a pre-stage account in the first place. The node that should be RODC should be using xADDomainControlle with It’s not really making since to me to create the pre-staged account using a DSC resource. 🤔 It’s because it is a one time operation, the account cannot be enforced, nor can it enforce any properties. Can someone provide a scenario where it would be good idea to have that functionality in a DSC resource? |
- Changes to xAdDomainController - Add support for creating Read-Only Domain Controller (RODC) (issue #40). - Refactored unit tests for Test-TargetResource.
|
@jojiklmts sorry, not following you. But if you mean the support for RODC it has been merged and will be included in the release of ActiveDirectoryDsc (which hopefully be soon). |
### Added - ADDomainController - New parameter UseExistingAccount for attaching a server to an existing RODC account (issue #711). - ADReadOnlyDomainControllerAccount - New resource for pre-creating Read Only Domain Controller accounts (issue #40 and issue #711). ### Fixed - ActiveDirectoryDsc.Common - Fixed Get-DomainControllerObject to allow checking non-local domain controller accounts. - Update build process to pin GitVersion to 5.* to resolve errors (issue #477).
Is there any plan to add support to install a server as an RODC?
The text was updated successfully, but these errors were encountered: