We wanted an overview of which domains our users were using in a certain country (Netherlands in this case). So, a simple Powershell snippet that counts all unique domains it encounters in the ProxyAddresses field of all users under a certain OU.
Note that if you have set contacts / forwarders, some domains that appear may not actually be accepted domains in your exchange organization.
#Author: Jos Lieben (OGD)
#Date: 13-06-2016
#Script help: www.liebensraum.nl
#Purpose: retrieve all unique domains in use under a specific OU and count them
#Requirements:
#active directory PS module
########
ipmo activedirectory
$users = get-aduser -Filter * -Properties * -SearchBase "OU=Netherlands,OU=Countries,DC=lieben,DC=nu" -SearchScope SubTree
$domains = @{}
foreach($user in $users){
$emails = $user.ProxyAddresses
foreach($email in $emails){
$domain = $email.Split("@")[1]
if($domain){
$domains[$domain] += 1
}
}
}
Write-Output $domains
A demonstration of one way to get shared mailbox permissions exported to a CSV file. We needed both users, groups and users in groups (so, a recursive search). Only Shared mailboxes had to be included, we could identity these by a simple rule:
the first portion of the primary email address does not contain a dot
See line 126 and 127 for this rule if you need a different method.
Edit: make sure you replace CED\ with your own domain! Sorry bout that…
This export excludes Deny permissions and looks for users in groups up to 2 levels deep. Credits to Piotrek for his Get-ADNestedGroupMember function.
This powershell snippet will tell you which mailbox is actively forwarding email, in what method (dual delivery or pure forwarding), to which email address and if the corresponding contact still exists and is active.
#Module name: findForwarderDetails
#Author: Jos Lieben (OGD)
#Date: 01-04-2016
#Description: this snippet will discover all active forwarders in your organization, and will print the original mailbox, target contact and target address and forwarding method
$output = @()
$mailboxes = Get-Mailbox -ResultSize Unlimited | Where {$_.ForwardingAddress -ne $Null}
foreach ($mailbox in $mailboxes){
$obj = New-Object PSObject
$obj | Add-Member NoteProperty mailboxName($mailbox.DisplayName)
if($mailbox.DeliverToMailboxAndForward){
$obj | Add-Member NoteProperty forwardingMode("Dual delivery")
}else{
$obj | Add-Member NoteProperty forwardingMode("Forward Only")
}
try{
$contact = Get-MailContact -Identity $mailbox.ForwardingAddress.DistinguishedName -ErrorAction Stop
$obj | Add-Member NoteProperty forwardingToName($contact.DisplayName)
$obj | Add-Member NoteProperty forwardingToEmail($contact.ExternalEmailAddress)
}catch{
$obj | Add-Member NoteProperty forwardingToName("CONTACT DOES NOT EXIST OR IS DISABLED")
$obj | Add-Member NoteProperty forwardingToEmail("CONTACT DOES NOT EXIST OR IS DISABLED")
}
$output += $obj
}
Write-Output $output
If, for some reason, you want to see which domains in your exchange organisation are not being used (not registered in the ProxyAddresses fields of your users), use below snippet in the Exchange Powershell Module.
Note: this does NOT (yet) check for domains used in Public Folders or Mail Contacts.
In organisations that have moved to Office 365, or are moving to Office 365 while using a hybrid setup with an on-premises Exchange 2010, 2013 or 2016 server and/or Lync/Skype, your helpdesk tools and scripts need to be adjusted.
While previously, you would provision your account in Active Directory, the mailbox on the onpremises Exchange Server and voip functionality on the Lync/Skype server, after your migration, you no longer need to provision mailboxes or lync accounts on premises. After a user has been migrated to Office 365, his ‘user type’ in the Exchange on premises server is ‘Remote Mailbox’. But for new users, this is not set automatically.
If you’re using scripting or tools like ADManager, you can use some simple Powershell commands to set the correct properties on a newly created user.