John Yassa's Blog

Office 365 Periodic Table

As you know Office 365 is not just Word, Excel, Powerpoint and email service

Now Office 365 is a full SAS platform (Software As Service)

Like the Periodic Table of Elements’ way of organizing elements by similar chemical properties, my Periodic Table of Office 365 is organized by families of apps. It shows everything available in the O365 ecosystem, regardless of extra cost or license type, plus a little taste of what it does.

 

 

Source: Ican Sharepoint article by Matt Wade

New Service Health Dashboard for Office 365

Finally Microsoft has updated the Health Dashboard for Office 365 , lets first see how the old Health board look like

old

The old Health Board was actually annoying and doesn’t provide so much information, beside it wasn’t a user friendly dashboard

Now let’s have a look at the new Health Dashboard

new

The new Service health dashboard provides you with more relevant incident insights and features a new view that separates major business critical outages from others and splits them into two categories: incidents and advisories. This new view makes it easier for you to identify the issues relevant for you that you might want to act on immediately.

The biggest improvements come to light after you click on an incident or advisory to see more information. A summary is presented, with just enough detail to let you know what’s going on.

incident

The “Show details” link takes you to a full history of the incident, with a timeline of updates as Microsoft investigates and resolves the issue.

incident-details

You still can go back to the old Health Dashboard if you like “which i doubt” by clicking on “Go to the v2 Service Health page” on the New Health Dashboard

v2

This change has been rolled this out to First Release customers, and will begin rolling it out to the rest of Office 365. This roll out will be completed by the end of February.

Source: Office Blogs , Parctical365 article by Paul Cunningham

Default Mailbox size increasing for Office 365 E3 and E5 subscription

Microsoft has announced increasing of Mailbox size from 50 GB to 100 GB for Office 365 E3 and E5 subscription

Microsoft just started rolling this out immediately, and the roll out is expected to be completed by the end of December 2016.

 

office-365

Source: Microsoft Roadmap

Office 365 Achieved 99.99% Availability in Q3 2016

If anyone still care about Microsoft online services SLA, Microsoft just announced it SLA for Q3 2016

sla

But did you ever ask yourself how Microsoft calculate the SLA for its online services

Microsoft is calculating the SLA based on the below formula

sla-calc

Where Downtime is Any period of time when users are unable to send or receive email with Outlook Web Access. There is no Scheduled Downtime for this service.

You Can refer to this document for more clarification about SLA for Microsoft Online services onlinesvcsconsolidatedslawwenglishnovember212016cr

References: Microsoft Products

 

 

HOW TO RESTORE THE EXCHANGE DATABASE FROM A BACKUP FILE IN STATE OF INCONSISTENCY?

How to Restore the Exchange Database from A Backup File in state of inconsistency?

For restoring the database on Exchange Server, the user needs to have an up-to-date and usable backup in hand, because an incomplete or even no backup can create a troublesome situation during the database the process of restoration. Additionally, Microsoft Information Store needs to be in a healthy state to mount the database successfully.

With an unmounted Exchange Store, the users face several issues such as restricted access to the data and the mail flow. In order to smoothly restore your database on Exchange Server, it is important to perform certain tests to verify the database consistency.

Pre-assessment Phase: Verify the State of the Database on Exchange

Use the following steps to verify the state of the database:

  1. Launch a command prompt.
  2. Move to the Drive:\Program Files\Exchsrvr\Bin

(The default location of the of Exchange 2000 Server program files are located in this folder)

 

Move to Drive:\Program Files\Microsoft\Exchange Server\V15\Bin

(When using Exchange 2013/2016, then use the above-mentioned default path)

 

  1. Enter the below-mentioned command:

eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_name.edb”

Note: The default location of database files is on this Drive:\Program Files\Exchsrvr\MDBDATA folder. The public database file can be found with the name: “Public.edb”, whereas the mailbox store database file can be found with the name: “Priv1.edb”.

  1. Read the Output, in order to verify the state of the database. If the database appears in the state of inconsistency, then the output will appear, as:

State: Dirty Shutdown

Restoration Phase: How to Restore the database from a backup file

Upon using the pre-assessment phase, if the database appears in a consistent state, then simply restore the backup using the file.

Steps to Restore Database in A Consistent State:

Implement the following steps to restore the database from the backup file.

  1. Transfer the E00.log file to an another path or simply rename it.

The default location of E00.log file can be found on this Drive:\Program Files\Exchsrvr\MDBDATA folder.

  1. Restore the storage group and the log files from the backup file.

Note: Do not remove the existing log files, until you have performed the restore operation. Upon completing the restore operation, the log files are restored, and replay inside the restored database. This is how, the user can bring the database into a consistent state without involving the E00.log file.

  1. Once the storage group is restored, you can successfully mount the databases in the storage group.

Steps to Restore Database in an Inconsistent State:

  1. Launch the command prompt.
  2. Reach to the location – Drive:\Program Files\Exchsrvr\Bin folder.
  3. Enter the following command in the command prompt:

eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

  1. To use the database in a productive environment, try to defragment and then rebuild the database. Use the below mentioned command to proceed:

eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

Note: ‘x’ is a temporary drive location in the above-mentioned command.

  1. To determine the state of the database, enter the following command, and then read the output:

eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

When database is consistent, the output will appear, as:

State: Clean Shutdown

  1. Use the Microsoft’s Store Integrity utility (Isinteg.exe) to fix the logical corruption issues in the database. Use the following commands to repair it:

Isinteg –s exchange_server_name –fix –test alltests

After executing the command, the user is prompted to choose the database in the utility. Repeat the aforementioned command until no errors or fixes are appeared in the output.

However, if zero errors are not displayed for a database that  you want to repair, then the other option is to rebuild the database. To do that create a new mailbox store on either the existing Exchange server or new server and then transfer all the mailboxes to that one. However, if you are still unable to create a new mailbox store, then try to rebuild the database from the following method. To do it, try to export all mailbox information to PST files, and delete the database, and finally import the data.

  1. Repeat the steps from 3 to 6 for each database in the storage group.
  2. Mount the databases.

Once the database is restored and you can also perform an online backup of the storage group. However, if the database is not restored or rebuilt in the state of inconsistency, then try using a third-party Exchange recovery software like Kernel for Exchange Server to perform accurate recovery of lost information from corrupt EDB and STM files, and without requiring log files. The Exchange mailbox items can be successfully restored to live Exchange Server, Office 365 mailbox or to Outlook PST files.

https://www.kerneldatarecovery.com/exchange-server-recovery.html

Article Summary:

When Exchange database creates mounting troubles, then try to investigate the issues hampering the restore operation. Verifying the shutdown state (whether consistent or inconsistent) of the database becomes important, and Eseutil can be helpful in this scenario, but with certain restrictions.

Microsoft to drop Azure RemoteApp after partnership with Citrix

Microsoft has announced on 12th August,2016 next step in their broad partnership with Citrix in the remote desktop and applications space, they will start to “wind down” its Azure RemoteApp technology in favor of application virtualization software and services from its partner Citrix.

Microsoft plans to continue supporting existing Azure RemoteApp customers through August 31, 2017, after which time the service will be discontinued. New purchases of Azure RemoteApp will end October 1, 2016,

Microsoft has explained this step as below:

“Customers have provided us consistent feedback that they want a comprehensive, end-to-end, cloud-based solution for delivering Windows apps. The best way for us to deliver this is with Citrix through XenApp “express”, currently under development. XenApp “express” combines the simplicity of application remoting and the scalability of Azure with the security, management, and performance benefits of XenApp, to deliver Windows applications to any employee on any device. We will have much more to share on this offering through the coming months.”

Citrix officials described the situation a bit differently, saying Microsoft will be assisting Citrix in developing a next-generation Citrix XenApp and associated XenDesktop service.

Citrix officials added: “In many ways, you can look at this XenApp “express” service as Azure RemoteApp v2.0.”

 

Source: Microsoft Blogs , ZDnet

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

December 2017
S M T W T F S
« May    
 12
3456789
10111213141516
17181920212223
24252627282930
31  

BLOG STATS

  • 267,296 hits

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 1,127 other followers

%d bloggers like this: