This topic contains 3 replies, has 3 voices, and was last updated by
January 15, 2015 at 11:54 am #21892ParticipantTopics: 5Replies: 6Points: 0Rank: Member
I have a script the leverages the cmd-let Get-ADPrincipalGroupMembership. It was working fine for several months. Recently, the cmd-let started generating the error:
Get-ADPrincipalGroupMembership : The operation being requested was not performed because the user has not been authenticated.
Now I find that I can't run the cmd-let on several of my servers. However, I am able to run it on one server. All servers have the same Version (2.0), Build (-1), Revision (-1).
I can't see any real difference between the machines that don't work and the one that does.
I have Googled with no luck of finding a solution or even seeing this question asked.
Has anyone see the error "Get-ADPrincipalGroupMembership : The operation being requested was not performed because the user has not been authenticated" before when running a cmd-let and if so, any idea on cause / solution.
Thanks in advance for any help,
January 15, 2015 at 11:57 am #21894MemberTopics: 9Replies: 2322Points: 0Rank: Member
Are you logged on with a domain account when you get that error, or with a local account? What happens if you use the -Credential parameter?
January 15, 2015 at 12:04 pm #21895ParticipantTopics: 5Replies: 6Points: 0Rank: Member
Logged in with a domain account. Again, it works from one machine but not on others.
Every other AD cmd-let works. It is just the Get-ADPrincipalGroupMembership cmd-let that gets that error. So it does not seem to be a connectivity or permissions issue.
August 31, 2017 at 3:22 pm #78572ParticipantTopics: 0Replies: 1Points: 0Rank: Member
Old thread, but this got me... You must specify the server parameter when you get this error.
Get-ADPrincipalGroupMembership myuser -Server my-dc01
Hope that helps someone!
The topic ‘Get-ADPrincipalGroupMembership and error 1244’ is closed to new replies.