Windows Power Shell Command wording

Question

Windows Power Shell Command wording

Gary Huber Admin 136

Power Shell Command
After I sign in to power shell as admin and run my sign on info I then use this command: It works but does not give me Job Title information. The column is there in the CSV download but the data is not. Should I be using a different command?

Get-User -ResultSize Unlimited | select FirstName,LastName,JobTitle,Manager,Department,Company,HomePhone,MobilePhone,WindowsEmailAddress,StreetAddress,Office,City,PostalCode | export-csv c:\exportedcontacts.csv

Gary Huber Admin 136 Reputation points

2022-09-02T13:29:06.303+00:00

Solved, the correct one to use is Title not Jobtitle. I am also having an issue with the correct selection for State.

Answer accepted by question author

Dillon Silzer 60,931

Hi @Gary Huber Admin

Instead of JobTitle, try Title

--------------------------------------

If this is helpful please accept answer.

0 comments

2 additional answers

Your answer

Gary Huber Admin 136 Reputation points

2022-09-02T13:29:06.303+00:00

Solved, the correct one to use is Title not Jobtitle. I am also having an issue with the correct selection for State.

Answer 1

Gary Huber Admin 136

This is my entire Powershell command:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Set-ExecutionPolicy RemoteSigned

Install-Module -Name ExchangeOnlineManagement

Import-Module ExchangeOnlineManagement

Connect-exchangeonline

Then after the above finishes:

Get-User -ResultSize Unlimited | select FirstName, LastName, Title, Manager, Department, Company, Phone, MobilePhone, Office, StreetAddress, City, St, PostalCode, WindowsEmailAddress | export-csv c:\exportedcontacts.csv

Using the above the St column header does show but there is no data in the rows below it.

Rich Matheisen 48,116 Reputation points

2022-09-02T18:48:19.557+00:00

The Get-User is an Exchange cmdlet. Are you sure it returns the properties you want? Have you tried running your script from a PowerShell session started with "Run as administrator"?

Using the Get-MSOLUser may be a better cmdlet to use, but I don't know if it will return all the properties you want.
Gary Huber Admin 136 Reputation points

2022-09-03T16:53:35.82+00:00

This works fine except for not returning data on State. The column header is there but as I said there is no data in the below rows. There is date in the exchange area of each mailbox that does contain State data. And I am using the Run as Administrator function.

Answer 2

Gary Huber Admin 136

Dillon, got that, worked. One more question what about State. I tried State, State/province and a few more variations of that.

Regards,

Gary

Dillon Silzer 60,931 Reputation points

2022-09-02T04:51:45.257+00:00

I believe it's st.
Rich Matheisen 48,116 Reputation points

2022-09-02T15:15:40.897+00:00
Either "St" or "State" will work, but that's not a property that's available unless you specify it in the Get-ADUser cmdlet. The same is true of other properties (e.g., "Department") that you use in your Select-Object cmdlet.

A nice, clean, way of coding long lists of properties might use something like this:

$props = "FirstName,LastName,JobTitle,Manager,Department,Company,HomePhone,MobilePhone,WindowsEmailAddress,StreetAddress,Office,City,PostalCode" -split "," Get-ADUser -Filter * -ResultSize Unlimited -Properties $props | Select-Object $props

Share via

Windows Power Shell Command wording

2 additional answers

Your answer