Restore get-aduser functionality
I have a script that has the following command:
$Users = Get-ADuser -Filter * -Properties * | `
where { $_.whenCreated -ge $week } | sort | select Name,WhenCreated,Descripti
I have been successfully running this as a scheduled task on a Windows 7 box for quite awhile. Then something changed and the script errors out without returning the list of users. I have a similar, almost identical, script using get-adgroup which continues to work fine.
Has something changed or broken with the get-aduser command?
Thanks
$Users = Get-ADuser -Filter * -Properties * | `
where { $_.whenCreated -ge $week } | sort | select Name,WhenCreated,Descripti
I have been successfully running this as a scheduled task on a Windows 7 box for quite awhile. Then something changed and the script errors out without returning the list of users. I have a similar, almost identical, script using get-adgroup which continues to work fine.
Has something changed or broken with the get-aduser command?
Thanks
With v5 I get the same error shown below:
-----
Get-ADuser : The server has returned the following error: invalid enumeration context.
At D:\Program Files\SystemAdmin\PowerShe
+ $Users = Get-ADuser -Filter * -Properties * | `
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-ADUser], ADException
+ FullyQualifiedErrorId : The server has returned the following error: invalid enumeration context.,Microsoft.ActiveD
0 new users in last 7 days
-----
The script is using the same loop used for the get-adgroup script. Both scripts worked originally. Now the get-adgroup script works but the get-aduser scripts errors out as shown above.
-----
Get-ADuser : The server has returned the following error: invalid enumeration context.
At D:\Program Files\SystemAdmin\PowerShe
+ $Users = Get-ADuser -Filter * -Properties * | `
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-ADUser], ADException
+ FullyQualifiedErrorId : The server has returned the following error: invalid enumeration context.,Microsoft.ActiveD
0 new users in last 7 days
-----
The script is using the same loop used for the get-adgroup script. Both scripts worked originally. Now the get-adgroup script works but the get-aduser scripts errors out as shown above.
That did it ... not sure why it worked for so long the way it was and then quit but am very glad to have the report back. And I got updated to v5 in the process. Win-Win.
I guess your number of items is just at the point that this error is occurring with all these properties included