Author Archive

How to perform a PST migration to Office 365 | Uploading PST files

March 13, 2017 2 comments

You will find overview of importing PST files and SharePoint data to Office 365 from below URL,

According to the above article, it has mentioned various methods to transfer data to the cloud.

In my article I will show you how to perform the PST migration using the Admin portal,

As the first step, you need to add the admin user/s to the import and export group on Exchange Admin Center to elevate he/them to perform import process.



If you haven’t created the RBAC role for Mailbox Import Export yet follow this article to get it created before you proceed to the next step.

Initial work to be completed for PST migration

Go to Office 365 Portal –> Active Users –> Data Migration



Select upload PST files which will take you to the Wizard,



Once you create the new job, Upload file over the network interface will appear,



Click show SAS URL, once it is appeared save it in to a Notepad



Install Azure AZ Copy tool to the default location (Recommended)




Upload the PST files to the temporary storage

Open the command prompt with elevated privileges and go to the directory where you have installed the AzCopy.exe tool in Step 1. If you installed the tool in the default location, go to %ProgramFiles(x86)%\Microsoft SDKs\Azure\AzCopy.

Run below commands to upload PST’s to the cloud,

AzCopy.exe /Source:<Location of PST files> /Dest:<SAS URL> /V:<Log file location>


Source: Location of the PST files save locally.

Dest: SAS URL which you have saved during Upload File Over the Network.

V: Specify the log file location on the server.






How to view the list of the PST files uploaded to Office 365

This is and optional step and you may install Microsoft Azure Storage Explorer to view the uploaded PST files to the temp storage on Azure.






Select Use a SAS URL and paste the SAS URL





Once the above steps are completed you will grant access to the Ingestiondata tab where you can see all the uploaded PST’s



Create the PST Import mapping file

Now it is time to merge those PST’s to the Exchange mailboxes. You may access Security and Compliance tab and click on Data Governance section. After that click on import to create a PST import job.



You have already uploaded the PST files to the temp Azure storage and you can safely tick both I’m done updating my files and I have access to the mapping file boxes. Then hit Next.




Provide a suitable name for the import.



It is time to create the CSV file to include information related to the PST file and email addresses which we want to merge those file.

You may download the CSV file from here.



Once the CSV is uploaded you need to validate for any errors.



Once it is validated you can safely close the wizard



Finally once you go to Import data to Office 365 page, it is showing the pending tasks.




Ok everything is done we can check the mailbox and see all the emails are there which were on my old PST file. Here we go  I have got everything!!!



Categories: Exchange

Create RBAC Role for MBX Import and Export in Office 365 Portal

Sometimes it is important to have permissions to export emails to a PST file incase, one of the employees leave or email box is exceeding the capacity than the assigned size. Additionally, sometimes admin may needs to work on importing PST files to the on premises Exchange or office 365.

In order to perform these activities, admin need to have Exchange mailbox import and Export privilege. In the below article I have outlined how the admin can create a RBAC role by assigning mailbox Import Export privilege.

Let’s create the Role!!

Access your office 365 Portal –> Exchange Admin Center –> Permission –> Admin Role and click the + mark


Fill the below form accordingly and assign the Mailbox Import Export permission under Roles section. Finally, assign the user which you want to assign as the Mailbox Import Export admin and click save.




I hope this article would helpful for you guys…

Categories: Exchange

Create ActiveSync Exchange Profile with one step (iOS | Android | Windows)


Once you setup your Exchange environment some users may complain that they have to follow more than one step to configure their mobile email profile using ActiveSync. I will demonstrate hoe to get rid of these additional steps by creating a Exchange email profile in my iOS device.




Usually once you enter your Email Address and Password it will bring you to another page to enter the Server Address, Domain Name and ect details to complete the process. 




What if you could complete the profile creation without this hustle and if you could create the profile by only entering your email address and password. You may say “Oh Yeah” Smile


Ok lets me guide you, which changes need to be done in Microsoft Active Directory side to get rid of this hustle,

1. Login to Active Directory Domain Controller

2. Go to Active Directory Domain and Trust

3. Add your public domain name as an Alternative UPN Suffix




4. Go to Active Directory Users and Computers

5. Go to properties of a single user and change the User Logon Domain to Public Domain instead of your local Domain.



Note: You can use ADModify tool to facilitate bulk user attribute modifications 


Now let’s try to configure the Exchange Profile (ActiveSync) again,




Once you enter “Next” you will be redirected to below page without asking any Server name or Domain Name,




I hope this article would helpful for you guys, Happy learning.

Categories: Exchange

Get certificate errors when configuring ActiveSync profiles for Android and iOS devices


I came across with above issue when I was migrating one of my clients Exchange Server 2010 to 2016. All the CAS servers are load balanced with KEMP Load Balancer and virtual directories are load balanced with Layer 7. As the initial step I did install the root certificate which I downloaded from Comodo SSL website.



Get certificate errors when configuring ActiveSync profiles for Android and iOS devices.



The only solution for this issue is to install all the intermediate certificates to KEMP load balancer.




I hope this article would help for you guys Smile!!!!

Categories: Exchange

Outlook client stays disconnected once the mailbox migrated to Exchange 2016 from 2010 and error to configure outlook clients with migrated mailboxes

February 1, 2016 Leave a comment



Hello folks,

Last week I was doing an Exchange migration from 2010 to 2016 and had to came  across with this issue, and this forced me to go through many KB articles to sort out it because of that I thought to share this valuable information with you guys to make your life little bit easier. Smile

According to Microsoft this is a known issue. It occurs because when a mailbox is moved to Exchange 2016 from Exchange 2010, the mailbox itself still has a cache entry that points the client back to the 2010 server. According to Microsoft, this cache expires after an "undetermined" time interval for Exchange 2013 and 2016.


Restart IIS service (This will affect all the Exchange services attached to IIS virtual directory so make sure before you carry out the task)


Recycle below application pools,




Information Sources :

Categories: Exchange

Configure Directory Integration between Azure Active Directory and Windows Server Active Directory with Azure AD Connect

December 12, 2015 Leave a comment

image_thumb Image result for office 365


In this section we will configure Directory Integration between Azure Active Directory and Windows Server Active Directory using the Azure AD Connect Tool.

First let’s download the Azure AD Connect Tool. Once you downloaded the tool follow below instructions to install the tool and configure the Synchronization.




Accept terms and conditions and click Continue



In the below step you can either select “Customize” or “Use express settings”



I will select Customize settings then it allows you to manually enter below options,



So I am going to enter the Service Account name to the AD Connect tool to continue with the Sync.



In this step let’s select Password Synchronization as we need to Sync all the passwords attached to local Active Directory Users.



Before we go to the next option we have to create a service account for DirSync in Office 365 Directory.

Note: The created user should have Global Admin privileges assigned.




Once it is done we can enter the created DirSync service account information



Then insert Domain Admin account information and add Directory



Let’s click next and continue the installation



Since we have single Active Directory forest I will go with “Users are represented only once across all directories” option. Incase if you have more than one forest you may select the “Users are represented only once across all directories” option.

Once again let’s keep the default values for “Select how users should be identified with Azure AD option”.



Select “Synchronize all users and devices” radio button



In addition to the default selection I have selected “Password write back” option as well.

What is Password Writeback : By enabling this option, password changes that originate with Azure AD will be written back to the onpremises Directory.



Let’s start the installation,





As you can see below installation is completed with a warning. This is what I wanted you to see at the end so intentionally select password write back option in “Optional Feature” step. Since I am using the Azure Active Directory Basic edition I am not eligible to this facility. In order to have this feature you need to have AAD Premium edition. This article provides detail information about Azure Active Directory editions.



Click Exit.

As you can see in the below screenshot our onpremises users are synced with Azure Active Directory.



I hope this article would helpful for you guys.. Happy reading Smile

Categories: Office365, Windows Azure

Windows Azure Site Recovery Scenarios

December 6, 2015 Leave a comment


Windows Azure Site Recovery provides a complete DR solution (replication of workloads and automated DR for failover/failback). ASR helps you to automate the replication of your on-premises servers and virtual machines to a secondary data center.


Deployment Scenarios 

ASR provides you five different options to protect your on premises VM workloads from to an extended data center.


1. Hyper-v to Hyper-v (On Premises)


In this scenario you can orchestrate and automate workloads running on virtual machines hosted on Hyper-V servers that are managed by Virtual Machine Manager (VMM) private clouds to replicate to the secondary site. All the virtual machines are replicated from primary site VMM to a secondary VMM site by using Hyper-v replica.



Hyper-V to Hyper-V (On Premises) step by step –


2. Hyper-V to Hyper-V SAN Replication


In this scenario you can orchestrate and automate workloads running on virtual machines hosted on Hyper-V servers that are managed by Virtual Machine Manager (VMM) private clouds. All the virtual machines are replicated from primary site VMM to an extended VMM site by using Storage Array-Based (SAN) replication. SAN replication capabilities provided by storage partners across both Fiber Channel (FC) and Internet Small Computer System Interface (iSCSI) storage. This supports for asynchronous replication for flexibility or synchronous replication for the lowest RPO/RTO.




Hyper-V to Hyper-V SAN Replication step by step –


3. Hyper-V to Windows Azure


In this scenario you can orchestrate and automate workloads running on virtual machines hosted on Hyper-V servers that are managed by Virtual Machine Manager (VMM) private clouds to replicate to the secondary site. All the virtual machines are replicated from primary site VMM to a secondary VMM site by using Hyper-v replica.




Hyper-V to Windows Azure step by step –


4. VMWare or Physical to VMWare


Microsoft has acquired InImage in 2014 and merged with Azure Site Recovery service in order to give customers a simple, cost-effective way to ensure business continuity with the power and scale of the Azure global cloud. This supports heterogeneous replication and protection of physical and virtual environments regardless of underlying hardware.




Prod Servers

•Discovery of production server OS & configuration (physical & virtual)

•Continuous capture of changing data blocks (CDP)

•Continuous transfer of captured blocks to Process Server cache

•Application detection and consistency


Process Server

•In-line compression of incoming CDP data on behalf of prod. servers

•Caching of compressed CDP data and resiliency to WAN outages or QoS problems

•Bandwidth throttling of replication traffic to a Master Target

•Encryption of replication traffic

•Capture of each prod. server & volume level change rate stats


Configuration Server

•Replication and recovery policies stored in its DB

•Web-based UI with extensive graphs, reports, and UI/email/SNMP alerts

•User management

•Management dashboard, monitoring pie-charts, real-time granular RPO display


Master Target Server

•Downloading data from Process Server and writing to DR VM disks for multiple prod servers (on behalf of all the powered off DR VMs)

•Copying older data from DR VM disks into a journal to allow point-in-time recovery

•Cataloguing the application consistency and recovery points

•Virtual snapshots to allow file and folder recovery at any point in time

•Recovery and cloning of DR VMs for failover as well as non-disruptive drills

•N-tier application recovery

•Inter application recovery sequencing

•Network adaptation of DR VMs to the recovery IP subnet/VLAN


Note: Incase you plan to failover VM’s from DR site to Primary Data Center, it is mandatory to have a Master Target server setup in Primary Data Center.


VMware or Physical to VMWare step by step –


5. VMware or Physical to Windows Azure


In this scenario you can plan to replicate, failover and recovery of on premises VMware Virtual machines, Physical Windows and Linux Servers by using Azure Site Recovery Service.

If you have one or more VMware Data Centers now you can failover over all the Onpremises VM work load to the Windows Azure with a technology call SCOUT. This technology falls under the azure site recovery umbrella which lets you manage and orchestrate your disaster recovery. This is using the guest based replication technology to failover VM’s between Onpremises and Windows Azure.




Vmware or Physical to Windows Azure Step by Step –



Azure does not support VHDX. Is VHDX supported for replication?

Yes. Microsoft converts VHDX to VHD for failover. On failback, and get back to VHDX.

Is Gen2 supported?

Yes. ASR converts Gen-2 VMs to Gen-1 on Azure.

What are the OSes supported?

ASR supports all the OSes supported in Azure, which includes most flavors of Windows and Linux.

Can I send my replication traffic over ExpressRoute?

Yes. You can use ExpressRoute to send your replication traffic in a secure and fast manner.

Can I control the network traffic used for replication?

Yes you can use the network throttling on the host agent to control how much network bandwidth is used for replication.

What is the RTO for failover?

Depends on the applications of the customer. The SLA for Azure is 4 hours

How do I connect to the VMs post failover?

If you are connected to the on-premises network via Azure Network Gateway, you connect in the same way as before failover. You can open the RDP port on the VMs if you are planning to connect to the VMs via the public internet.

Do I pay for the IaaS VM?

When you are protected, you are paying for the ASR license. Only post failover, you will pay for the license of the Iaas VM.

Is failback supported?

Yes – you can failback to on-premises. There are flexible options which optimize for resources or for downtime.


Source: ASR Partner Presentation

I hope this article would help for you guys.. Happy reading… Smile

Categories: Windows Azure