Get-ADUser Script Runs but issues error command before returning all results

Question

Greetings;
I am running Windows Server 2008-R2 and try to execute a PowerShell command as follows:
I am trying to locate user objects that have been inactive since September 1 and do not have any Exchange mailboxes. The query does run and I do get a number of records, however, the error is issued, as shown above.
can you please shed some light as to why I am getting this error message? I do appreciate your time.
Behrooz

Answer 1

I see this thread isn't answered yet, so I'm taking another shot at it.  I am positive my script is going to give you the results you are looking for. I have reproduced this in my lab.
What I did:
- I created a set of users in an OU in my domain.
- I populated the 'employeeType' property on a handful of them
- I created mailboxes fora subset of those users on my Exchange server
- I did NOT log in with any of these accounts, but that is the easy part.
Run this query and you will get a returned set of accounts that:
- Have not logged on since 9/1/2013
- Do NOT have a mailbox (this is query-able through Get-ADUser because the HomeMDB property is only populated when you have a mailbox.  Using the Exchange tools is not necessary)
- Accounts that do NOT have any anything in their 'employeeType' property.
Get-AdUser -filter * -properties * |
Where-Object {$_.HomeMDB -eq $NULL -AND
$_.employeeType -eq $NULL -AND
$_.lastlogondate -ge "9/01/2013"} |
Select displayname,distinguishedname,samaccountname,employeetype |
Export-Csv "employeetype.csv" -notypeinformation
** This result is going to find people with NO employeeType.  If that is the opposite of what you're looking for, change that like from -eq (equal) to -ne (not equal) or you can use -like and -notlike.  Both give the same results.
Your results will export to a CSV and will not print to the screen.  Again, with the way this is written, the employeetype column will be empty.
If you want to copy and paste this script, please paste it into the ISE and push play.  If you save it as a .ps1, you'll have to ensure you have the appropriate executionpolicy set (Open PS as an admin, run 'set-executionpolicy unrestricted')
If you chose to run it in a PS window as is, please ensure this whole syntax is all on one line.
Okay! Come back and tell me you were successful and mark me as the answer!! :)
Chris Ream