Exchange 2010 to Office 365 Migration
We are wanting to migrate a customer to Office 365. We have on-premises Exchange 2010 SP2.
We want to set it up hybrid so that we can slowly move users over.
We are in the planning stages with this. Does anyone have any good clean walkthroughs that we might use?
I have seen a few walk throughs on google that just arent very clean. I already have two ADFS servers set up and load balanced.
If anyone can provide insight of what we should look out for or anyone have any good walk throughs, that would be great.
This is our first migration and I am experienced with Exchange on-premises, just never used Office 365.
We want to set it up hybrid so that we can slowly move users over.
We are in the planning stages with this. Does anyone have any good clean walkthroughs that we might use?
I have seen a few walk throughs on google that just arent very clean. I already have two ADFS servers set up and load balanced.
If anyone can provide insight of what we should look out for or anyone have any good walk throughs, that would be great.
This is our first migration and I am experienced with Exchange on-premises, just never used Office 365.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
one problem i am having is even though I have set up the dns records as microsoft requests, i cannot change my default domain.
Its not even an option in the dropdown menu.
Its not even an option in the dropdown menu.
ASKER
I see that a federated domain cannot be set up as a default domain in office 365.
So with a hybrid deployment, your mail domain has to be a federated domain.
Anyone see a way around this?
So with a hybrid deployment, your mail domain has to be a federated domain.
Anyone see a way around this?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok thanks for that. I did see a little earlier that I need to go from SP2 to SP3. I am currently doing that now.
I think that may be where I was going wrong the whole time. I will use the Hybrid Configuration Wizard afterwards to get it all pieced together.
I have dirsync working. ADFS is being a tad tricky. I think its a load balancing issue though.
For ADFS, do yall use Unicast or Multicast on the NLB configuration?
I think that may be where I was going wrong the whole time. I will use the Hybrid Configuration Wizard afterwards to get it all pieced together.
I have dirsync working. ADFS is being a tad tricky. I think its a load balancing issue though.
For ADFS, do yall use Unicast or Multicast on the NLB configuration?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am seeing that first hand. Its very irritating to say the least.
I am having an issue with the Exchange Migration wizard.
It will not authenticate my ownership of my domain.
I have domain.com that has the corresponding txt record in the public DNS. If I check the record it is resolved, even on the exchange server itself.
I cannot get it to go past this step.
Any ideas?
I am having an issue with the Exchange Migration wizard.
It will not authenticate my ownership of my domain.
I have domain.com that has the corresponding txt record in the public DNS. If I check the record it is resolved, even on the exchange server itself.
I cannot get it to go past this step.
Any ideas?
ASKER
Ok I have Office 365 working with a test domain and a test user.
Federated servers work flawlessly inside for Single Sign-On with the web portal.
Only problem now is that when I open a test users account that was migrated from the on-premises exchange to the cloud, outlook asks for a password upon opening it. When i enter the password it works fine, I just want to get outlook to not prompt for credentials as the DirSync and ADFS work fine.
Does anyone know how to get outlook to not prompt for credentials since the credentials match what the user is logging into their desktop with?
Federated servers work flawlessly inside for Single Sign-On with the web portal.
Only problem now is that when I open a test users account that was migrated from the on-premises exchange to the cloud, outlook asks for a password upon opening it. When i enter the password it works fine, I just want to get outlook to not prompt for credentials as the DirSync and ADFS work fine.
Does anyone know how to get outlook to not prompt for credentials since the credentials match what the user is logging into their desktop with?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now outlook will not accept the username or password.
I think its a problem with my ADFS from the outside.
I have one internet connection. The ADFS server sit with the domain/exchange on-premise server.
Since this is hybrid and I am moving over slowly, 443 is used for my mobile devices to connect back to exchange.
Autodiscover will not work externally or internally when a test user is migrated.
How could I get ADFS to work externally for Office 365 to be able to use ADFS without having to take 443 away from my exchange server?
I think its a problem with my ADFS from the outside.
I have one internet connection. The ADFS server sit with the domain/exchange on-premise server.
Since this is hybrid and I am moving over slowly, 443 is used for my mobile devices to connect back to exchange.
Autodiscover will not work externally or internally when a test user is migrated.
How could I get ADFS to work externally for Office 365 to be able to use ADFS without having to take 443 away from my exchange server?
ASKER
I am just having problems with understanding exactly what is needed for my instance.
Do I need to use ADFS to keep SSO up to date, or just let the Windows Azure Directory Synchronization do the password updating?
I need to use the hybrid deployment as we have large mailboxes and I will not be doing a cut over with that much data.