Skip to main content

Check if you have users with both mailboxes on-prem and online

An Exchange Online license was applied to the user before the Exchange GUID got synchronized from on-premises Active Directory. For synchronized accounts, having the Exchange GUID synchronized from on-premises is used to tell Exchange Online that the mailbox hasn’t been migrated yet, and is what allows customers to pre-license accounts prior to migration.
 From: My user has a mailbox both on-premises and in Exchange Online.

So, in my case many times we get into situation where license is applied before Exchange GUID is synchronized to O365. I am using this script to check whether user has two mailboxes. Script closes Exchange session BEFORE it opens connection to Exchange Online as both use same commands. You can use Get-Mailbox both on-prem and Online, therefore it is crucial to close connection before you open other.

# DISCLAIMER:
# This code is provided "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
# Use at your own risk
#
#
# Use "install-module ExchangeOnlineManagement" if module is not yet installed 
# Use "import-module ExchangeOnline" to import it to session

# Connect to the on-premises Exchange server using remote PowerShell
$onPremisesExchangeServer = "on-premexchange.example.com"
$onPremisesSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$onPremisesExchangeServer/PowerShell/ -Credential exchadmin@example.com
Import-PSSession $onPremisesSession
$OnPremisesMailboxes = Get-Mailbox -server $onPremisesExchangeServer -ResultSize unlimited -RecipientType UserMailbox -Filter {ExchangeGUID -ne $null}
# Disconnect the remote PowerShell session to the on-premises Exchange server
Remove-PSSession $onPremisesSession
# Connect to Exchange Online PowerShell
Connect-ExchangeOnline -UserPrincipalName admin@example.onmicrosoft.com
# Initialize an array to store the users with both an on-premises and an Office 365 mailbox
$usersWithBothMailboxes = @()
# Loop through all mailboxes to check if any user has both an on-premises and an Office 365 mailbox
foreach ($OnPremisesMailbox in $OnPremisesMailboxes) {
    $userIdentity = $OnPremisesMailbox.UserPrincipalName
    $Office365Mailbox = Get-EXOMailbox -Identity $userIdentity -ErrorAction SilentlyContinue
    # Check if the user has both a mailbox in Office 365 and a mailbox on-premises that is not remote
    if ($Office365Mailbox -ne $null) {
        Write-Host -BackgroundColor DarkRed -ForegroundColor White "User $userIdentity has both an on-premises and Office 365 mailbox"
        $usersWithBothMailboxes += $userIdentity
    } 
}
# Check if any users were found with both an on-premises and an Office 365 mailbox
if ($usersWithBothMailboxes.Count -eq 0) {
    Write-Host -BackgroundColor Green -ForegroundColor White "There are no users with both on-premises and Office 365 mailboxes"
}
# Disconnect from Exchange Online PowerShell
Disconnect-ExchangeOnline -Confirm:$false

 


Labels:

Comments

Post a Comment

Popular posts from this blog

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
1 comment
Read more

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use. You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters. But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US) Third option you have is opening Internet Explorer settings (I am using Windows 2016) Click languages Click Set Language Preferences Add language you want to use by clicking Add language Use Move up or Move Down options to put desired language on top Close Internet Explorer Open it again and login again to Exchange Admin Center
Post a Comment
Read more

Free/Busy missing - Cloud to On-Premises

We had a problem where M365 users could not retreive Free/Busy information from on-premise Exchange server. Hybrid setup was run and everything was working fine except this. After research I found out that TargetSharingEpr is the way to look at. There are many sites out there that are pointing to the same setting but only Set-OrganizationRelationship is used to change the value. The problem is, this value is available for two commands: Set-IntraOrganizationConnector Set-OrganizationRelationship While we changed the value in  Set-OrganizationRelationship it didn't work until we changed the value in  Set-IntraOrganizationConnector too. By default it should work with just  TargetAutodiscoverEpr but for us it didn't. Finally we ran this command on Intra Organization Connector which is used from Cloud to On-prem:  Set-IntraOrganizationConnector -TargetSharingEpr   https://mail.domain.com/ews/exchange.asmx And it worked.
Post a Comment
Read more