As I mentioned in my previous post, I recently had to define certain Exchange mailbox properties in order to cleanup the Global Address List for our users, specifically the Company value in each user's Exchange properties. To do this, connect to Office365 using the Azure Active Directory Module and run:

Set-User UserPrincipalName -Company "Microsoft"

Of course, utilizing PS doesn't save as much time if you have to bash out each user individually, so export your user mailbox names to .csv from O365, groom the list (if needed) and input the following:

Get-Content -Path c:\LocationOf.CSV | Set-User -Company "Microsoft"

Though I only needed to define the Company for each mailbox, I've already utilized the Set-User cmdlet to define other properties. Explore the other parameters available by running Get-Help Set-User, while connected to O365. Also note that you must be assigned the appropriate permissions from within the EAC.

@scottalanmiller said:

Not really that surprising. So called scientists were so adamant that the Big Bang was unquestionable that it really was a case of Shakespeare's "they doth protest too much." It was obvious that they knew it was flimsy but didn't want people to question them.

Ironic, considering the nature of science and the scientific method is to question everything; to constantly improve the models.

Now on to the "Law" of Gravity . . . I resent its hold on me.

[Thanks to Greg Hall for assisting me with this!]

We recently underwent a corporate name change, which required us to migrate our users over to email addresses on the new domain.

Because most users still require access to their old account, I was unable to remove those mailboxes, which created confusion for the majority of users who pull from the Global Address List, which displays all mailboxes on our corporate Office365 account. Despite a change in the naming convention from <first initial><lastname> to <firstname>.<lastname>, folks were still sending plenty of email to old user mailboxes, thwarting our efforts to wean them away.

Initially I sought to segregate the old domain from the new using Address Book Policy, but found we had not defined certain parameters upon which New-AddressBookPolicy is dependent. So, moving away from that approach, and with the help of Greg Hall, I decided to simply hide the old mailboxes from the Global Address List - which worked perfectly. Here's how I did that . . .

Connect to Office365 using the Azure Active Directory Module, then input:

Get-User -Filter {Company -eq 'Microsoft'} | Get-Mailbox -resultsize unlimited | Set-Mailbox -HiddenFromAddressListsEnabled $true

And don't forget your Distribution Groups!

Export the list of group names to .CSV and input the following:

Get-Content -Path C:\LocationOf.CSV | Set-DistributionGroup -HiddenFromAddressListsEnabled $true

Bam. Done.

Of course, we had not defined the "Company" value in our users' Exchange properties, but I'll discuss using PS to edit Exchange properties in another post.

That's a good question!

I don't think the name.nk2 file draws from the GAL, rather it's populated through use over time. To that end, we simply asked users to delete their AutoComplete cache early on and start over (I know, some were rather distraught, including our technician who sat and cleaned up the HR Manager's list personally!).

I would definitely be curious to know if there's a way to simply edit the list, rather than manage it in broad strokes like delete, import and export. Though that doesn't seem to be the case.

As I mentioned in my previous post, I recently had to define certain Exchange mailbox properties in order to cleanup the Global Address List for our users, specifically the Company value in each user's Exchange properties. To do this, connect to Office365 using the Azure Active Directory Module and run:

Set-User UserPrincipalName -Company "Microsoft"

Of course, utilizing PS doesn't save as much time if you have to bash out each user individually, so export your user mailbox names to .csv from O365, groom the list (if needed) and input the following:

Get-Content -Path c:\LocationOf.CSV | Set-User -Company "Microsoft"

Though I only needed to define the Company for each mailbox, I've already utilized the Set-User cmdlet to define other properties. Explore the other parameters available by running Get-Help Set-User, while connected to O365. Also note that you must be assigned the appropriate permissions from within the EAC.

[Thanks to Greg Hall for assisting me with this!]

We recently underwent a corporate name change, which required us to migrate our users over to email addresses on the new domain.

Because most users still require access to their old account, I was unable to remove those mailboxes, which created confusion for the majority of users who pull from the Global Address List, which displays all mailboxes on our corporate Office365 account. Despite a change in the naming convention from <first initial><lastname> to <firstname>.<lastname>, folks were still sending plenty of email to old user mailboxes, thwarting our efforts to wean them away.

Initially I sought to segregate the old domain from the new using Address Book Policy, but found we had not defined certain parameters upon which New-AddressBookPolicy is dependent. So, moving away from that approach, and with the help of Greg Hall, I decided to simply hide the old mailboxes from the Global Address List - which worked perfectly. Here's how I did that . . .

Connect to Office365 using the Azure Active Directory Module, then input:

Get-User -Filter {Company -eq 'Microsoft'} | Get-Mailbox -resultsize unlimited | Set-Mailbox -HiddenFromAddressListsEnabled $true

And don't forget your Distribution Groups!

Export the list of group names to .CSV and input the following:

Get-Content -Path C:\LocationOf.CSV | Set-DistributionGroup -HiddenFromAddressListsEnabled $true

Bam. Done.

Of course, we had not defined the "Company" value in our users' Exchange properties, but I'll discuss using PS to edit Exchange properties in another post.

@scottalanmiller said:

Not really that surprising. So called scientists were so adamant that the Big Bang was unquestionable that it really was a case of Shakespeare's "they doth protest too much." It was obvious that they knew it was flimsy but didn't want people to question them.

Ironic, considering the nature of science and the scientific method is to question everything; to constantly improve the models.

Now on to the "Law" of Gravity . . . I resent its hold on me.