-
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
xADDomainController: Get-DscConfiguration fails #155
Comments
This is for xActiveDirectory version 2.16.0.0. |
Yep getting this too. Have other xActiveDirectory resources in use and this is the only one (i've seen so far). Looking in a bit deeper the return statement is returning 'ensure' which is not in the schema.mof. In the resource this is reference on line 31 and 52. Is this actually needed for the Get? If i remove the entries for 'ensure' it works fine. |
Same here...other resources in the xActiveDirectory module 2.16.0.0 that I've used seem fine, just xADDomainController causing this error. |
The ensure property is returned in the hashtable. But the property does not exist in the schema. |
This bug exists in version 2.19.0.0 as well. Will this be fixed in the near future? |
This work is abandoned in PR #111. Anyone in the community may continue the work, by sending in a new PR that resolves this and have a unit test that tests that this property is returned correctly (and updated the Unreleased section in the change log). |
- Added Ensure Read property to xADDomainController to fix Get-TargetResource return bug (issue #155). - Updated readme and add release notes
…fails (dsccommunity#249) - Added Ensure Read property to xADDomainController to fix Get-TargetResource return bug (issue dsccommunity#155). - Updated readme and add release notes
The PowerShell DSC resource returned results that are not valid from Get-TargetResource. The Ensure key is not a valid property in the corresponding DSC resource schema file. The results from Get-TargetResource
must be in a Hashtable format. The keys in the Hashtable must be the same as the properties in the corresponding DSC resource schema file.
The text was updated successfully, but these errors were encountered: