Home Dashboard Directory Help
Search

Windows 8.1 - Powershell 4.0 Get-ADComputer -Properties * bug by jbarkl3y


Status: 

Active


68
0
Sign in
to vote
Type: Bug
ID: 806452
Opened: 10/24/2013 9:09:48 AM
Access Restriction: Public
3
Workaround(s)
view
40
User(s) can reproduce this bug

Description

When running the Get-ADComputer command I run into the following. There has been a couple of posts on this error but they are related to Powershell 3.0 and can be fixed by changing your AD Schema to version 47. This bug still exists except now my Schema version is 47 and the bug still persists.

Get-ADComputer : One or more properties are invalid.
Parameter name: msDS-AssignedAuthNPolicy
At line:1 char:1
+ Get-ADComputer SPAREPC -Properties *
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo         : InvalidArgument: (SPAREPC:ADComputer) [Get-ADComputer], ArgumentException
    + FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.ArgumentException,Microsoft.ActiveDirectory.Management.Comm
ands.GetADComputer
Details
Sign in to post a comment.
Posted by James Dobbs on 7/7/2014 at 6:19 PM
This is JDobbsy1987 (i updated my display name)
@Jamie Bilinski, you are correct, mine started working again since the latest preview update
Posted by Jamie Bilinski on 7/3/2014 at 12:04 PM
I seems to be resolved in current WMF 5 Preview. @JDobbsy1987 perhaps it was resolved in May update 1?
Posted by James Dobbs on 4/18/2014 at 2:33 AM
I still get the same issue with Powershell 5.0 using 'Windows Management Framework 5.0 Preview' from - http://www.microsoft.com/en-us/download/details.aspx?id=42316
Posted by -Nick on 2/20/2014 at 7:08 AM
Still an issue here with 8.1 enterprise x64. is this going to be fixed or do I need to go back to windows 7/2008r2?
Posted by Allen J. George on 1/15/2014 at 12:35 PM
Matthew,
You can probably do this: get-adcomputer -filter * -properties PasswordExpired,pwdLastSet,etc -- You will need to use the object name: http://www.kouti.com/tables/userattributes.htm
Posted by Matthew McDonald at ION on 1/15/2014 at 9:21 AM
The workarounds do not work for all cases. For example, I need to use the command "get-ADuser -properties *" as I am looking for a number of various properties of the account. When alternatively piping Get-ADUser to Get-ADObject -Properties *, many of these properties are not returned. For example: PasswordExpired, PasswordLastSet, PasswordNeverExpires, and PasswordNotRequired.

What can be done to fix this issue?
Posted by Allen J. George on 1/14/2014 at 8:11 AM
The workarounds that others have posted work, but required rewriting multiple scripts. Microsoft please fix this as it is a pain for those that want to do get-adcomputer -filter * -properties *
Posted by Chris.Duck on 11/6/2013 at 1:38 PM
I can repro on Windows 8.1 Enterprise. Our domain is 2003 forest and domain functional level, with 2008 R2 Domain Controllers. Schema version is 47. I do not have the problem from PowerShell 3.0 on 2008 R2 or 2012.
Posted by JoMalin on 10/25/2013 at 10:21 AM
This bug is also in get-aduser and get-adprincipalgroupmembership but seems to be fine in get-adgroup.
Sign in to post a workaround.
Posted by StaceyIsLearning on 4/7/2014 at 10:48 AM
If you only need to "Know" the properties. one of the examples in the help for Get-ADComputer has a sample output of the properties.
Posted by Alon.or on 12/9/2013 at 11:49 PM
Get-ADComputer -Identity $computer |Get-ADObject -Properties *

It needs a "-" before "properties"
Posted by JoMalin on 11/7/2013 at 1:00 PM
Seems like you can use this to get what is needed.

Get-ADComputer -Identity $computer| Get-ADObject Properties *

Should work for any other broken commands as well