-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
win_domain / win_domain_controller - log path missing #59348
Comments
Files identified in the description: If these files are inaccurate, please update the |
I don't see a log related parameter for win_domain. |
Thats the issue, there is no method to set the active directory log directory. This is a parameter for Install-ADDSForest and all other common parameters are included in the module. Why allow the module to specify sysvol and the database but not the db log path. :) |
Issue is a feature request not a bug, edited post to reflect this. |
|
I've opened #67108 which deprecates the existing (previously undocumented) |
This has been implemented in |
SUMMARY
The equivelent powershell command to win_domain includes the option to specify log path:
This has been missed in the win_domain module but SYSVOL and Database path are included, this is not consistent.
In addition to this, the win_domain_controller does not include it as a parameter in docs but it is in the examples! but also has no effect.
Should be an easy fix to make, otherwise please fix the example in docs. Would be greatly appreciated. The only way to change this is by rebooting into restore mode while AD if offline.
ISSUE TYPE
COMPONENT NAME
win_domain
win_domain_controller
ANSIBLE VERSION
CONFIGURATION
For example, the config below is ignored and the logs are in the C:\ drive
OS / ENVIRONMENT
Non OS Specific, Tested on Server 2019 and 2016
STEPS TO REPRODUCE
n/a
EXPECTED RESULTS
Logs go to E:\Windows\NTDS\ etc...
ACTUAL RESULTS
Logs go to %systemroot%\NTDS\
The text was updated successfully, but these errors were encountered: