8000 xADGroup Get-TargetResource doesn't use the Credential parameter for all AD calls · Issue #78 · dsccommunity/ActiveDirectoryDsc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
xADGroup Get-TargetResource doesn't use the Credential parameter for all AD calls #78
Closed
@kylebevans

Description

@kylebevans

In xActiveDirectory/DSCResources/MSFT_xADGroup/MSFT_xADGroup.psm1, some of the AD calls such as the Get-ADGroupMember on line 96 do not use the Credential parameter. This causes, for example, Test-TargetResource to fail when the script running it is being run as Local System.

The error is something like this:

[Invoke-DscResource], CimException + FullyQualifiedErrorId : ActiveDirectoryServer:0,Microsoft.ActiveDirector y.Management.Commands.GetADGroupMember,Microsoft.PowerShell.DesiredStateCo nfiguration.Commands.InvokeDscResourceMethodCommand Invoke-DscResource : The PowerShell DSC resource '[xADGroup]DirectResourceAccess' with SourceInfo '' threw one or more non-terminating errors while running the Test-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.

Powershell Cmdlet failed: Invoke-DscResource : The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0