When members of a group have differing OU values in the AD configuration, the value for the group is displayed as a blank. However if group change is made, this blank value causes all machines to have their OU values reverted to the default.
I’m requesting a feature where if the value is blank, instead of reverting to defaults, it leaves the value unchanged, with an option to use the default value specified separately, possibly with a checkbox next to the OU box labeled “Use Default Value”
When members of a group have differing OU values in the AD configuration, the value for the group is displayed as a blank. However if group change is made, this blank value causes all machines to have their OU values reverted to the default.
I’m requesting a feature where if the value is blank, instead of reverting to defaults, it leaves the value unchanged, with an option to use the default value specified separately, possibly with a checkbox next to the OU box labeled “Use Default Value”
@Tom-Elliott
Understood, it’s not what I’d prefer but I see the reasoning.
I’ll submit a feature request.
" It will display the OU if ALL hosts in the group have the same OU."
That’s not the behavior I am seeing. The OU is never displayed, even if all the members have the same value. If I create a group, add two machines to it, then assign an OU to the group, I can then check the individual machines, and they do have the OU populated, but the group still shows a blank value.
Since the value is blank, if I then update the group and forget to re-type the OU data, the group members then get reverted back to the default.
The combination of reverting to blank and having the blank value destroy existing data is why I considered it a bug, since it’s surprising and unexpected behavior that causes loss of data.
When I use a group to apply AD settings to machines, some of the AD settings are remembered, but the OU is not.
If I’m wrong and this is not expected behavior feel free to tell me what I’m doing wrong, but from what I’ve read in the forums this seems to be by design.
Since the other fields are all filled in, but the OU is not, and since a blank value for the OU causes it to use the default, this makes it very easy to accidentally revert the existing OU assigned to machines back to the default value.
Having a blank value be the default, and also having that blank value cause a destructive change is a bad combination.
If the OU cannot be stored for the group for some reason, then there should be an option when applying group settings to keep the previously assigned value rather than replacing it with the default.
The OU is a particularly bad field to have this behavior, as it’s the most likely to be long and complex and hard to remember.