John Yassa's Blog

Home » 2016 » March

Monthly Archives: March 2016

Do you know where is your Office 365 mailboxes located ?

I started to get a lot of questions regarding the location of the mailboxes hosted on Office 365 , and where is my tenant is hosted ?

Now we are going to look on how we can know the location of the Tenant and the mailboxes

So to check your tenant location (and mailbox location), open up PowerShell and connect to the Exchange Online Shell

$UserCredential = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

Now if you need to know the Location of one mailbox, run the below command

Get-Mailbox -Identity “Mailbox ID” | fl PrimarySmtpAddress,OriginatingServer,OrganizationId

You will get the below result

Org

The Organization ID represents Tenant within EM EA (Starts with EURP)

The Originating server shows that the mailbox is hosted in AM (Amsterdam)

No if you need to get the location of all your mailboxes hosted in Office 365

Get-Mailbox |fl PrimarySmtpAddress,OriginatingServer

The result as below is showing that all mailboxes are hosted in Amsterdam

org2

 

Notice about certificate expiration for Exchange 2013 Hybrid customers (MUST be completed before 4/15/2016)

If you’re running Exchange 2013 and you’ve configured a hybrid deployment with Office 365, this post contains important information that might impact you. Please evaluate this information and take any necessary action before April 15, 2016. If your latest run of the Hybrid Configuration Wizard was initiated from Exchange 2010 than you are NOT affected.

On April 15 2016, the Office 365 TLS certificate will be renewed. This certificate is used by Office 365 to provide TLS encryption between Office 365 and external SMTP servers. The new certificate, which will help improve the security of mail sent to and from Office 365, will be issued by a new Certificate Authority and it will have a new Issuer and Subject.

This change has the potential to stop hybrid mail flow between Office 365 and your on-premises Exchange servers if one of the following conditions applies to you:

  • Your on-premises Exchange servers are running Exchange 2013 Cumulative Update 8 (CU8) or lower.
  • You’ve upgraded the Exchange 2013 servers that handle hybrid mailflow to Exchange 2013 CU9 or higher. However, since upgrading to CU9, you HAVE NOTre-run the Hybrid Configuration wizard (either from the Exchange Admin Center or via the direct download link).

How to keep hybrid mail flowing (MUST be completed before 4/15/2016)

Let the new Hybrid Configuration wizard do it for you

You can use the latest Hybrid Configuration wizard (HCW) to configure your Exchange 2013 servers to work with the new TLS certificate. Just follow these steps:

  1. If the Exchange 2013 servers handling hybrid mail flow are running Exchange 2013 CU8 or lower, follow the instructions in Updates for Exchange 2013 to install the latest cumulative update on at least one server.
  2. After you install the latest cumulative update, download the new HCW application and run the wizard following the instructions here .
Manual update

If you can’t upgrade Exchange 2013 to latest cumulative update right now (although we would like to remind you of our support policy), you can manually configure your servers to work with the new TLS certificate. On each Exchange 2013 server that’s used for hybrid mailflow, open the Exchange Management Shell, and run the following commands:

$rc=Get-ReceiveConnector |where {$_.TlsDomainCapabilities -like “*<I>*”}

Set-ReceiveConnector -Identity $rc.Identity -TlsDomainCapabilities “mail.protection.outlook.com:AcceptCloudServicesMail”

Source: The Exchange Team Blog

The connection to the server ‘Server URL’ could not be completed during mailbox migration

When you try to Migrate a mailbox from Exchange On Premise to Exchange we faced the below error

1

to be able to get more information about this issue , open the power shell and run the below command

Test-MigrationServerAvailability  -ExchangeRemoteMove -Remoteserver “Server URL”

And  got the below error

2

We found that something is not working perfectly with the certificate published to the internet , we fix the certificate and re run the same command again but with credentials for accessing the servers URL

3

As you see it works fine now , after fixing the Certificate publishing issue

 

 

 

Storage improvements for SharePoint Online and OneDrive for Business

Upload larger files, up to 10 GB each

Microsoft has increased the per file size limit to 10 GB. This applies to files uploaded to Team Sites, Office 365 Groups and OneDrive for Business, as well as for videos uploaded into the Office 365 Video portal. Office 365 customers no longer need to leave big files stranded on file shares and local hard drives.

Before it was only 2 GB

1

 

1 TB additional space for overall pooled SharePoint Online storage allocation

The amount of content in Office 365 is growing 300 percent year over year. To meet your needs for more storage, we’re increasing default storage to 1 TB plus 0.5 GB per user to use across SharePoint Online, Office 365 Groups and Office 365 Video up from the previous allocation of 10 GB. This is in addition to the unique default per-user OneDrive for Business storage space and individual storage provided for user email inboxes. Office 365 customers on our premium Enterprise, Government and Education plans will receive OneDrive for Business unlimited storage, and we’re pleased to announce that the first stage of providing 5 TB for each user is now complete.

2

Source : Office Blogs

%d bloggers like this: