list of users that we on Exchange online in a excel format

1.      Save below script to note pad document as a .ps1 file.
2.      Save to desktop.
3.      Run PowerShell migration tool.
4.             Then go to start
5.             All Programs
6.             Microsoft Online Services  
7.             Migration
8.             Migration command shell
 
$owaserver = "red002.mail.microsoftonline.com"
$AdminCredential = get-Credential
$colUsers = get-msonlineuser -Credential $AdminCredential -Enabled `
| Select-Object @{name='DisplayName';Expression={$_.displayname}}, `
@{name='Identity';Expression={$_.identity}}, `
@{name='IsActive';Expression={$_.isactive}}, `
@{name='PasswordExpirationDate';Expression={$_.passwordexpirationdate}},`
@{name='LastSignedInDate';Expression={$_.lastsignedindate}},`
@{name='CreatedDate';Expression={$_.createddate}},`
@{name='FirstName';Expression={$_.FirstName}}, `
@{name='Lastname';Expression={$_.LastName}}
$colusers | Export-Csv "-$((Get-Date -uformat %Y%m%d%H%M%S).ToString()).csv" -NoTypeInformation

The script is only exporting 252 users out of 320 users, Attched screen shot of the warning. This is been run in the migration console for Microsoft's BPOS.
What needs to be change on the script above to allow all 320 users to be pulled.

 Powershell warning
RickdangerousireAsked:
Who is Participating?
 
Dale HarrisConnect With a Mentor Professional Services EngineerCommented:
according to a microsoft page, it's supposed to be <Int32>.

This would tell me ResultSize cannot be a string.  Int32 maximum value in case you're wondering: 2,147,483,647

I think your ` at the end might be causing you some issues.

If you're troubleshooting this one command and waiting for us to help, it might be beneficial to try to troubleshoot your command one step at a time.

So I would do something like this:

Get-MSOnlineUser

What does that return?

Then

Get-MSOnlineuser -Credential $AdminCredential

Then

Get-MSOnlineuser -Credential $AdminCredential -Enabled

Then

Get-MSOnlineuser -Credential $AdminCredential -Enabled -resultsize 999999

HTH,

Dale Harris
0
 
Benjamin MOREAUConnect With a Mentor Project ManagerCommented:
Try to add :

Get-MSOnlineUser -ResultSize 9999 ...
0
 
Dale HarrisProfessional Services EngineerCommented:
Can't you use "0" as a universal "unlimited feature"?  I don't know because I haven't tried it, but that's how you can specify it in other commands.

DH
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
RickdangerousireAuthor Commented:
script was ran after this was added, came back with errors

$colUsers = Get-MSOnlineuser -Credential $AdminCredential -resultsize 999999 -Enabled `
0
 
AkhaterConnect With a Mentor Commented:
please run the below alone does it return the same warning ?

 $colUsers = get-msonlineuser -Credential $AdminCredential -Enabled -ResultSize unlimited

0
 
chrismerrittConnect With a Mentor Commented:
Not used MSOnline, but in regular Exchange powershell this error shows up if you don't include a switch for -ResultSize.

What happens if you enter this?

$Mailboxes = get-msonlineuser -Credential $AdminCredential -Enabled
$Mailboxes.count

How many objects does that return? if you then run this what is returned?

$Mailboxes = get-msonlineuser -Credential $AdminCredential -Enabled -ResultSize "Unlimited"
$Mailboxes.count
0
 
RickdangerousireAuthor Commented:
Thanks for the help everyone. The issue was internal with user names, however all of the above worked once that other issue was fixed.
0
 
RickdangerousireAuthor Commented:
Very long day, My writing was not the best. Thanks again.
0
All Courses

From novice to tech pro — start learning today.