RecoveryFix for Exchange Server Recovery

One of the most important component of the Exchange server is the database and it stores the user’s mailbox with emails, contacts, calendar, tasks, notes etc.

MS Exchange is considered as mission critical application as most of the business transaction happens over email. Hence, it is very important that the database are protected. Exchange server provides multiple native option to protect the database. Exchange backups, multiple database copy, LAG database copy are the common ways to protect database with minimum or no data loss.

In spite of multiple options and complex configuration, there is always a possibility of exchange database getting corrupt and cause a major downtime for the users with data loss. Exchange native tool ‘ESEUTIL’ could be used to fix the database corruption, but in most of the occasions, it take enormous amount of time to fix the corruption. Alternatively, you could restore data from the backups but it is subjected to data loss between the backup time and the restore time.

Lepide software Pvt. Ltd. offers RecoveryFix for Exchange Server Recovery tool, it helps to recover Exchange database from corruption. It works on all version of Exchange database file starting from Exchange 5.5 to latest version of Exchange. It is a very simple, easy and efficient tool.

RecoveryFix for Exchange Server Recovery tool accepts the database file .edb and .stm (for legacy database only) as source files.

 

image

Image: Selecting Corrupted database to recover

 

Operating the software, once the source database file is selected then it provides three different recovery mode options:

1. Automatic Analyze and recover: It is the recommended and fastest mode to restore the corrupted database. It scans through the database, fixes the corruption and lists all the recovered mailboxes in the database. Recovered mailboxes from the database can be exported to the .pst files.

2. Advance Scan: It is selected when database is severely corrupted and ‘Automatic Analyze and Recover’ option fails. This mode performs deep scanning of the database and it takes some time to recover the database. Once the database is fixed, it lists all the recovered mailboxes in the database. Recovered mailboxes from the database can be exported to the .pst files.

3. Rebuild corrupted database: This option reduces unnecessary efforts of exporting the user’s mailbox to .pst file and sharing with the users. It creates/rebuilds a new clean database by fixing the corruption in the database. The new recovered database is ready to mount on the Exchange servers.

 

image

Image: Recovery Modes to Recover Corrupted Database

 

Automatic analyze and recover and Advanced scan are the most common options, when you have bigger database and large number of mailboxes to recover. Once scanning process is done, it proves effective in fixing all the corruption and allows administrator to view/validate the mailboxes and its content.

image

Image: RecoveryFix for Exchange Server Console

Administrator can save all the recovered mailboxes into .pst file format. These .pst files can be imported into the target user’s mailbox or any other temp mailbox. Administrators can also share the .pst with users and can be accessed through their MS Outlook.

Saving the recovered mailboxes can be done easily by selecting ‘Save’ button from the top ribbon bar. Saving option provides some great flexibility to filter only the necessary emails based on date.

Administrator can easily filter emails based on predefined date or custom date. Finally at the end, one just got to define the path of the destination folder to save the recovered .pst files.

 

image

Image: Saving Option to export the .pst

 

Conclusions:

I think it’s a great tool to fix the corrupted Exchange database and at the same time can save your efforts and time. I recommend this tool for all the Exchange Server administrators. You can download the copy of the software from the Recoveryfix Website – http://www.recoveryfix.com/exchange-server-recovery.html

LepideMigrator for Exchange (LME)

Exchange migration involves a lot of effort and time; it is one of the most complex migrations to perform. After doing tons of exchange migration, I realized that not every environment is the same and not every migration is the same. During an exchange migration, everyone’s mailbox will be moved from one version of Exchange to the latest version or to the other organization. With the upgrade of Exchange servers, it is important that client outlook version is also upgraded to the latest level or to the level of Exchange servers. Thus, in a way everyone has to undergo some kind of changes with learning, while adopting a new Exchange environment into the organization.

LepideMigrator for Exchange (LME) is the new latest Exchange migration tool from Lepide which helps in performing a migration from one Exchange Environment to another which is either located locally or another network or even in the Office 365 or Exchange hosted solution in the cloud environment. It supports different migration scenarios, like

· Exchange 2003 / 2007 and Exchange 2010

· Exchange 2003 / 2007 and Exchange 2013

· Exchange 2010 and Exchange 2013

· Migration from any Exchange Server to Office 365

· Public Folder Migration

· Intra-forest Exchange Migration

· Cross-forest Exchange Migration

Given below are a few interesting features of the products.

1. Innovative technique to migrate the large number of mailboxes from source Exchange server to the target which enhances the performance. It can be installed on multiple computers and increase migration volume depending on the requirement. We can also schedule the mailbox move by creating schedule jobs. It provides rich filtering options to filter unwanted email and migrate only necessary email to the target and can also provide the option to undo or rollback the mailbox migration, if necessary.

2. Exchange migration is a time-consuming process which needs a lot of effort and time. To reduce the migration efforts, we can sync the complete source mailbox to the target much ahead of time and just do an incremental sync only before the final cutover. This helps in avoiding any kind of data loss and outage to the users.

3. Report is very important for the migration and helps in tracking migration history and plan for the future migration. Notification helps administrator to notify the status of the migration status with email alerts for the job status, job completion, or job cancelation.

Migrations of the mailbox using LepideMigrator for Exchange is a very easy process and let’s understand on how easy it is to configure and to migrate a mailbox from one forest to another.

Given below is the Setup of my lab

1. Source forest Green.com

2. Target Forest blue.com

3. Creating DNS forwarding and trust between green.com and blue.com

Given below is a step-by-step instruction to perform cross forest migration.

1. Install LepideMigrator for Exchange at the source or target forest. In this scenario, the tool is installed on the source forest green.com. It is installed on the Windows 7 machine with outlook client installed

2. To perform the configuration, start the LepideMigrator for Exchange, Right click on All projects -> click on ‘Add Project’ -> provide the name to the Mailbox migration project

image

3. Then, create the new Job for the mailbox migration and provide the name for the same and click on ‘Next’

image

4. Connect to the source forest domain control by providing the IP address and administrator credentials. Then click on ‘Next’

image

5. Select all the necessary required users to migrate into the target domain and click on ‘Next’

image

6. Input the target domain controller IP address and the admin credentials. Make sure to specify ‘Different Domain’ for cross forest migration scenario and then click ‘Next’. You can also pull down ‘Migrate To’ to select the different options like same domain or office 365.

image

7. It also provides the filters to include or exclude the message based on date and folder. Click on ‘Next’ to continue

image

8. Here, we need to map the source mailbox with the target forest mailbox. It provides the option to map the source mailbox to target pre-created mailbox automatically. If not, we could provide the CSV file specifying the source and target mailbox mapping.

image

9. Another option could also be to create the target mailbox using the tool itself. Select all the source mailbox and click on message icon, then click on ‘Start’.

image

10. Once the target mailbox is created, then you could see the mapping done automatically for each of the source mailbox with the target. Click on ‘Next’ to continue.

image

11. Specify option to Skip the Bad item count or if you just want to do only the mailbox content synchronization, and then click on ‘Next’.

image

12. Specify the email address to receive various notifications for Job start, Job stop, Job completion, mailbox migration start / finish etc.

image

13. Notification configuration needs the SMTP address and other necessary configurations. Please provide the same and continue with the ‘Next’.

image

14. Specify the time duration to deny or permit the migration for the specific time period. It is important to make sure that migration is not done at the production hours, which could have the user performance impact. Click on ‘Next’ to continue.

image

15. Then schedule the migration depending on the requirement and click on ‘Next.

image

16. Finally, verify the summary details and click on ‘Finish’ to complete the Job creation.

image

17. It’s now the time to generate the license file and upload it to http://www.lepide.com/lepide-migration-for-exchange. It generates the generate activation file, download the import it to activate the same.

image

18. Once the license is activated, we are ready to start the mailbox migration by right clicking on the Job and select the option ‘Start Job’.

Report Console

1. Report console helps to generate the migration statistics report. It helps to analyze the migration details and also to track the status. This report has the complete statistics of the migration performed using the server. It has details of number of jobs, with the domain details and the Exchange version specifications.

To start the report console

2. Start the LepideMigrator for Exchange

3. Click on tool -> click on Report Console

image

4. Login with the account and password as ‘lepadmin’

image

5. To understand the details of each of the migration job, click on the Job name. It gets the detailed information with number of mailboxes, total folders, migrated messages and status. Below is the reference screen shot.

image

6. You could also generate some quick reports in html or pdf file using the options available in the bottom left corner of the LepideMigrator for Exchange tool.

image

Conclusion:

This migration could take some time depending upon factors like the size of the source mailbox, bandwidth, source and target server performance, etc. Migration using a ‘LepideMigrator for Exchange’ is much simpler to configure and manage than a native migration tool. It provides option to migrate the account with SID History and also copy the password from the source to target account, which is very important for the cross forest migration scenario. It also provides option to migrate public folders and also apply the settings like mailbox rights, send as permission, public folder administration rights send on behalf, message delivery restriction, and public folder client permission.

I believe, LepideMigrator for Exchange is a compressive tool to perform migration under various scenario. This tool has all the features to perform end to end migration.

You can find the detailed information about the tool at http://www.lepide.com/exchangemigrator/ and  also download the trial version from http://www.lepide.com/exchangemigrator/download.html

ADFS Claim based Authentication for SharePoint with Cross forest authentication

 

Wonderful in-depth setup by step instruction to configure ADFS Claim based authentication for SharePoint with cross forest authentication by Jay Simcox from summit7systems.com

 

Part 1: The Beginning

Part 2: Installing and Configuring AD FS 3.0

Part 3: Configuring SharePoint 2013 for ADFS

Part 4: Troubleshooting

Part 5:Authentication Across Multiple Forest

Kernel for Exchange Server Recovery

Exchange Server is one of the most business critical applications in an organization; accessed by everyone in the organization, everyday and round the clock. It can be from their outlook client, tabs, mobile devices etc. Exchange Server emails are also considered to be legal and many organizations retain the user’s mailbox data for compliance and regulatory requirement with legal hold option in Exchange Servers. This adds a lot of pressure on the IT Department to make sure that emails servers are protected from various unforeseen situations like DB failure, Server failure and AD site failure. The latest version of Exchange Server offers some high availability and site resiliency with DAG. These options can only protect the database from different physical failures or physical corruption, but they cannot protect it from logical corruption. Logical corruption could be due to physical hard drive errors, file size errors, JET errors, human errors, virus attacks, hardware problems, etc. During the logical corruption we may have to rely on the backups to restore the database and this is subject to data loss for the users.

Kernel Exchange Server Recovery and EDB Repair Tool can easily perform database recovery without any data loss from the corrupted database. It can not only connect to the corrupted database repairs corrupt, damages but also allow exporting of the user mailbox data into the PST. Again, it can even copy the content to the user’s mailbox in the live exchange servers.

It is an easy to use to tool with simple GUI which can connect to any database file from Exchange 2000 to Exchange 2013.

image

It provides the option to perform a standard or advanced scan. Generally, scan is used but advance scan mode is used only when a DB is severely corrupted and unable to recover it using the standard scan.

image

Once it is connected, it scans through the entire EDB file, fixes the corruption and displays the entire mailbox in the EDB file. Right click on the EDB file and save the contents of all the mailbox into individual users .PST or it can even connected to the live exchange server mailbox. If required, you can also export the content of the individual mailbox only to the .PST or to the live exchange server, depending on the requirement.

 

image

It also provides the option to perform advance search for the individual mailbox and export the contents.

image

It is a great life-saving tool for Exchange administrators who can even recover the items which are permanently deleted from the deleted items folder. It also support public folder and provides the option to export the public folder content into PST. It provides options to export the individual emails to MSG, EML, RTF, HTML, TEXT and PST files. It can even export the mailbox bigger than 2 GB and in case there is no 2GB mailbox size limitation, it can split the mailbox, which is more than 2 GB into multiple PST files.

I think this is a great and handy tool for all Exchange administrators and would recommend this tool for the all Exchange administrators to explore this product and when there is a critical server’s database corruption. Also, the free trail can saves/export 25 items per folder. Please check download page for more information.

http://www.nucleustechnologies.com/Exchange-Server-Data-Recovery.html

http://www.nucleustechnologies.com/download-exchange-server-recovery.php

Why Exchange Server backups are important

Most of the business communications are these days carried out through emails. Even in the organizations that have full-fledged enterprise level CRM system in place, many sales related communications takes place through emails, particularly in the initial phase. Many of the emails contain critical client related information as email attachments that can be required anytime in the contract phase. Hence, Exchange Server data protection should be of primary importance for all the Exchange Server administrators.

When it comes to Exchange Server data protection, there are different measures that you can take. All these measures can be broadly classified into two parts based on the approach: pre-emptive measures where you try to prevent the occurrence of a disaster situation that can put the data to risk; and reactive measures where you make provisions after a disaster has struck.

Here we will discuss how backups can be a used a very effective methods to deal with any unforeseen circumstances. Exchange Server backups can be used in any of the following situations:

To recover from disaster situation: If your Exchange environment experiences a hardware or software failure, Exchange Server backups can help you to restore to a point-in-time with zero loss of data.

Recover any accidently deleted item: If any User deletes an email item accidentally, it can be restored from the correct backup. With Exchange 2013, the recovery of accidentally deleted items is even faster with Recoverable Item folder and the Hold policy that can be applied to it.

Uphold Compliance: Compliance requirements require you to archive email data for extended period of time. Backup is an excellent way to archive email communication to satisfy compliance requirements.

With Exchange 2013, many such features have been decentralized and even end Users can archive, perform granular recovery and search across mailboxes.

Let’s see what all options are available to backup Exchange Server data:

Normal backup: Normal backup process backups the entire Exchange Server and directory in its entirety. The log files are also backed up. You can restore mailboxes from just a normal backup.

Creating a Copy: A Copy backup is similar to the normal backup without the incremental and differential context. It can be used to backup the entire Exchange Store without disturbing the state of any incremental or differential backups that might be going on.

Incremental: This type of back up only backups the components that have changed since last normal or incremental backup. To restore from an incremental backup, normal backup and all incremental backups created in between are required.

Differential: This kind of backup captures the changes that have occurred since last normal backup and the current state. To restore from this kind of backups, one normal backup the specific differential backup is required.

While recovering data from backups, you may require to setup a recovery server apart from the production Exchange Server; this causes additional cost for setting up an expensive recovery server. There are some third-party software that can restore data directly from backups, thus doing away the need of recovery server and save significant cost. Lepide Exchange Recovery Manager is a third-party application that can be tried in such situations.

CodeTwo Exchange Migration

CodeTwo Exchange Migration tool is one of the great products from CodeTwo, which allows us to migrate Exchange mailboxes from one version of Exchange to the other version of Exchange. It can be a direct migration from Exchange to Exchange or from the SBS to Exchange and can be used in exchange cross-forest scenario as well. It also supports to migrate from non-Microsoft products like Google apps or Gmail to Exchange servers. It is easier and faster to use; and safer to migrate exchange in the below supported scenario.

· Exchange 2003, 2007 to Exchange 2010 migration

· Exchange 2003, 2007 to Exchange 2013 migration

· Exchange 2010 to Exchange 2013 migration

· Google Apps to Exchange migration

I think the most interesting feature is the support for cross-forest migration. Cross-forest migration using traditional tool it more complex, tedious and can be extremely slow and time consuming.

In this article we will perform cross-forest migration using the CodeTwo Exchange Migration tool. Normally, organizations perform cross-forest migration when there is a merger or acquisition, a security reason or when leaving the old environment and when starting a fresh one, etc.

Our lab environment consists of two forest Green.com – Source forest and blue.com – Target forest, which allow users to migrate from source forest to target forest.

image

As part of the migration, we need to prepare our environment to perform the cross-forest migration. Given below are the configurations necessary between the two forests which help to perform the smooth migration.

1. Configure DNS resolution between green.com and blue.com

2. Configure Trust between the two forests, green.com and blue.com

3. Configure the mail flow between source to target using the send and receive connectors

4. At the green.com domain, change the accepted domain as an internal relay to make sure that emails continue to be received even after the migration of mailbox to blue domain.

5. Configure Free busy sharing between blue.com and green.com

6. Configure GAL Sync between blue.com and green.com

7. Install and Configure ADMT and password export server which will export the password to the target account after user account migration.

8. Migrate users AD account from source to Target forest using ADMT

9. Finally, enable the mailbox for all the migrated users at the target forest. This can be done using PowerShell or using Exchange management console.

 

We are almost done with the environment configuration. Next, install CodeTwo Exchange Migration tool on any machine on the source forest with the necessary prerequisites:

Given below are the step by step instruction to configure CodeTwo Exchange migration tool and migrate the users to the target forest.

1. Login the machine where Exchange migration tool is installed with the Domain admin account

2. Run “ Exchange Migration Administrator Panel” from the start menu

3. Source server connection wizard helps to connect to the source forest. Select the option “on-Premises” Exchange server and click on Next

image

4. Select the Exchange 2010 server from the green.com (source) forest and make sure to select the Administrator account which has necessary permission to enumerate mailboxes in the source forest and then click on “Next”

image

5. Select the necessary folder for migration and by default, most of the folder is selected except the junk folder. Keep the default settings and click on “Next”

image

6. “Email address rewriting” has to be checked when mailbox has to be migrated to the different forest, it rewrites the email address based on the target forest. Since the new forest has a different domain and its email address is different, these settings are mandatory.

image

7. Finally, verification checks the source server connection and validates administrator account for the necessary permission and group membership.

image

8. Target server connection helps to connect to the target forest servers.

9. I would prefer to connect manually using FQDN of the Target exchange 2010 server. Exchange Web service URL (EWS URL) gets auto filled based on the target exchange server name and click on “Next”. EWS URL is necessary to connect and access the mailbox during the migration.

image

10. Enter the User Principal Name (UPN) and password of the target forest administrator account at the Admin’s credentials, and click on “Next”

image

11. Final verification allows us to validate the target server connection, impersonation rights to access the migration mailboxes through PowerShell.

image

With this we are almost ready to start the migration. Identify the source mailbox which you want to migrate and associate it with the new target mailbox in the CodeTwo Exchange Migration Administration panel. Association can be done both manually and automatically. Manually, you can select the source mailbox from the list and then highlight target mailbox in the window. This process is painful, when you have larger number of users to migrate. Automatically, association can be done by selecting all the users and click on Automatch button on the Administration Panel’s ribbon. This automatically matches the all the users account from the source forest to the target forest and generate the report for the reference. Once the association is done, you can start the migration. By default, it can only migrate two mailboxes at a time and this count can be increased by modifying the settings at the administration panel.

I personally feel I like the tool and it helps me to perform migration tasks in a simpler, easier and more effective way than using the traditional migration tool. It has a simple GUI which helps the administrator to perform the operation much easier. Again, it supports various migration scenario and even perform the direct upgrade from Exchange 2003 to Exchange 2013. It voids any kind of caveats which occur during the migration and also avoids the complexity of two step migration. CodeTwo also has a great support team which can help us to address any queries, issue or problem whenever there is a situation

Download CodeTwo Exchange Migration

 

 

Office 365 Hybrid Configuring Using Windows Azure – Part 6

I tried to keep this article series as brief as possible and cover end-to-end configuration of Exchange and Office 365. This should give you a complete understanding to take the base on-premises exchange environment and integrate with the Office 365 in the hybrid mode.

This is the final and last part of this article series. We will continue with the discussion on the topics mentioned below.

I. Provisioning Office 365 mailbox from on-premises Exchange Admin center

II. Accessing provisioned mailbox using Single Sign On(SSO)

III. Migrating mailbox from on-premises to Office 365

Other part of the Articles can be found at below link

Office 365 Hybrid Configuring Using Windows Azure – Part 1

Office 365 Hybrid Configuring Using Windows Azure – Part 2

Office 365 Hybrid Configuring Using Windows Azure – Part 3

Office 365 Hybrid Configuring Using Windows Azure – Part 4

Office 365 Hybrid Configuring Using Windows Azure – Part 5

 

Provisioning Office 365 mailbox from Exchange Admin Center

It is recommended to provision all the mailbox for both on-premises and Office 365 through On-premises Exchange Admin Center.

1. Login to on-Premises Exchange admin Center

2. Click on recipients -> mailboxes and click on ‘ + ‘ to select ‘Office 365 mailbox’

1

3. Provide all the necessary new user details and save to create the mailbox in Office 365

2

4. This will create an AD object at on-premises active directory and create the mailbox at Office 365. Given below is a reference snapshot of Exchange EAC with the new Office 365 mailbox.

3new

5. The newly created object at on-premises has to be synced with Office 365. Scheduled synchronization happens every 3 hours. Follow the steps given below to force the directory synchronization immediately and allow users to login with the new accounts.

a. Login to the Dirsync server – Krisdirsync.cloudapp.net with the admin credentials

b. Access windows explore and navigate to the path “%programfiles%\Windows Azure Active Directory Sync”

c. Double-click on DirSyncConfigShell.psc1 to open a Windows PowerShell window with the cmdlets loaded.

d. In the Windows PowerShell window, type Start-OnlineCoexistenceSync, and then press ENTER

4new

6. With force synchronization, we should be able to see the new account at Office 365 portal and given below is the reference screen shot.

These accounts need to be activated and assigned the license to allow users to login to their mailbox. Select the required ‘synced with Active Directory’ user and click on ‘Active Synced user’

5new

7. Active the user by specifying the user location , assigning the required licenses and click on ‘Next’

6

8. The ‘Send result in email’ page is to send the mailbox creation with password detail to the authorized person. Since we have synced the objects from active directory, passwords are not reset for the users. Click on ‘Active’ to active the mailbox.

7

9. The ‘Results’ page has the mailbox activation confirmation with the message ‘The password wasn’t reset because its user’s password is synced with your on-premises’

8

Accessing provisioned mailbox using Single Sign on (SSO)

1. Login to the client machine and connect to the Office 365 portal via explore. Sign in with the new account rajesh.kumar@checkwhatsin.com and use the TAB key

9

2. Office 365 portal will check for ‘checkwhatsin.com’ SSO configuration and it will immediately redirect to the organization sign-in page

10

3. Input the domain\username and password and click on ‘Sign In’ to authenticate

11

4. The welcome page is ‘Get started with Office 365 page’, with all the necessary information to connect to Outlook, Outlook Web App, installing Office client software’s setting up the mobile device etc.

Click on ‘Outlook’ on the top ribbon to access the Outlook Web App

12

5. Shown below is the new and first look for users Outlook Web App

13

Migrating mailbox from on-premises to Office 365

The idea of having a hybrid environment is to have some or the majority of mailboxes in Office 365 and others in on-premises. Let understand how to migrate users from on-premises to Office 365 and understand as to how they continue to access their emails

1. Connect to the Exchange on-premises EAC with Organization admin credentials

2. The Mailbox Replication Proxy (MRSProxy) service is installed on every Microsoft Exchange Server Client Access server. MRSProxy helps to facilitate cross-forest move requests and it runs on the local Exchange Client Access server. However, MRSProxy is disabled by default.

3. To Enable MRS Proxy select Servers -> Virtual directories -> Double click on “EWS (Default Web Site)”

14

4. Select ‘Enable MRS Proxy endpoint’. This is the important configuration to allow cross forest migration of users from on-premises to Office 365.

15

5. Identify the user for the migration to Office 365 and click on “To Exchange Online” under ‘Move Mailbox’ to start the move mailbox wizard.

16

6. Confirm the migration endpoint with the Remote MRS Proxy server. Internet facing CAS server with MRS proxy enabled is Krisexch.cloudapp.net and the Internet alias name for the same is mail.checkwhatsin.com. Specific the ‘Remote MRS proxy server’ and click on ‘Next’

17

7. Specify the ‘New migration batch name’, ‘Target delivery domain’ name and other necessary details. In our case, Target delivery domain is ‘checkwhatsin.mail.onmicrosoft.com’. Specify the same and click on ‘Next’

18

10. Specify the account to deliver the batch competition status report. Also select the preferred option to start and complete the batch. Click on ‘New’ to start the migration batch

19

11. Click on ‘Yes’ to go to the migration dashboard to see the status of the migration batch.

20

12. This will automatically redirect the page to Office 365 Migration page with details of the migration batch status as syncing.

Syncing: The migration batch has been started, and mailboxes in the migration batch are being actively migrated.

21

13. Once synchronization of the selected mailbox is completed, click on ‘Complete this migration batch’ to perform the final migration process.

22

14. Confirm with ‘Yes’ to start the process.

23

15. Wait for the completed status to make sure the mailbox is migrated from on-premises to office 365.

24

16. Once mailbox is migrated to Office 365, users should start to use the Office 365 portal to connect to Outlook Web App application. Users can still connects to on-premises OWA portal to connect to the Office 365 OWA

25

17. Once you login to on-premises OWA, it determines the location of the mailbox in Office 365 and specifies the Office 365 portal URL to access their mailbox.

26

18. Click on the link to open then the new Office 365 authenticate page. This URL can be saved in the favorites for the further usage. Enter the user email address and press the Tab key

27

19. Since, Federated SSO is configured for the domain checkwhatsin.com, it will redirect to the on-premises reverse proxy server for authentication

28

20. Once authenticated using on-premises credentials, it will redirect back to Office 365 OWA page

29

21. Accessing Office 365 OWA seems to be a bit completed with the redirection happening forth and back in the hybrid mode. It is not the same experience for outlook users and user can continue to access the same profile and OST without changing the profile configuration

22. Once the migration is completed, the user will lose connection and it prompts the user to restart outlook.

23. When outlook is started again, it will prompt for the basic authentication popup. Input the user UPN(username@checkwhatsin.com) and password then click on ‘OK’

30

24. This will allow outlook to communicate, authentic and connect office 365 for email access. Below snap has the details of outlook with ‘Connected to Exchange server’ status.

31

25. We can connect to ‘Outlook Connection Status’ to verify the Office 365 connection. We should be able to see the connection proxy server as outlook.office365.com, which are office 365 servers.

32

With this we have come the end of the article series. I suppose if you want to learn Office 365 and configure Hybrid, then this is one of the best and easiest ways to learn it. Hope you have got some sound understanding as to how to build and configure Office 365 hybrid environment using Windows Azure.

It was a great experience for me to work on this article series and hope it will help you greatly to deploy and configure Office 365 hybrid mode in the production environment.

 

Other part of the Articles can be found at below link

Office 365 Hybrid Configuring Using Windows Azure – Part 1

Office 365 Hybrid Configuring Using Windows Azure – Part 2

Office 365 Hybrid Configuring Using Windows Azure – Part 3

Office 365 Hybrid Configuring Using Windows Azure – Part 4

Office 365 Hybrid Configuring Using Windows Azure – Part 5