Migrating to Office365 (Hosted Exchange)
- Thread starter R.O.S.S.I
- Start date
Soldato
- Joined
- 19 Oct 2006
- Posts
- 3,708
Really there are loads of guides 
I assume you are going to migrate the lot rather than have on premise/cloud hybrid, try here http://technet.microsoft.com/en-us/library/jj874016(v=exchg.150).aspx
I assume you are going to migrate the lot rather than have on premise/cloud hybrid, try here http://technet.microsoft.com/en-us/library/jj874016(v=exchg.150).aspx
lol you sure?Here are some links I hope they help:
http://www.msexchange.org/articles-...gration-office-365-exchange-online-part1.html
http://community.office365.com/en-us/forums/685/t/168109.aspx
That MS Exchange article looks a bit dated, it's not got screenshots of Wave 15.
Are you fully migrating and canning your existing environment or going hybrid?
http://technet.microsoft.com/en-gb/exchange/hh127068
http://technet.microsoft.com/en-us/library/hh852466.aspx
Will have most things you need to get cracking.
Are you fully migrating and canning your existing environment or going hybrid?
http://technet.microsoft.com/en-gb/exchange/hh127068
http://technet.microsoft.com/en-us/library/hh852466.aspx
Will have most things you need to get cracking.
It's easy. Point your MX at your O365 instance and set up the delivery in that to pass messages onto your Exchange server as well. As you're on Exchange you have AD already so just federate to O365 and update the clients. There are migration tools to bring old messages across.
I want to fully migrate all mailboxes across to O365 and then bin the on site Exchange server. All of our other servers are on site (for now) and everyone uses the full Outlook 2010 client - if I just migrate all users to 365 what config will be needed clientside, will there be any change to their experience?
Also, was at a supplier event on 365 not long back and they were talking about using I AM CLOUD's Federate365 product or something? Does anyone know what that is needed for specifically? Is it something to do with single sign on?
Also, was at a supplier event on 365 not long back and they were talking about using I AM CLOUD's Federate365 product or something? Does anyone know what that is needed for specifically? Is it something to do with single sign on?
Last edited:
Everything you need to federate with an AD domain is included with O365 for no extra costs as long as you have the right product.
When you change your DNS over to O365 then part of this will involve the change in autoconfig information so new clients pick up the new servers automatically. Existing clients I think will require some intervention, I'm not 100% sure but I think you can initiate this from your Exchange server to say "go and look here now" - or to be a bit bodge-tastic if you are using the same credentials then you can add a DNS entry to point requests to your existing Exchange server to O365 while you get around to updating clients.
When you change your DNS over to O365 then part of this will involve the change in autoconfig information so new clients pick up the new servers automatically. Existing clients I think will require some intervention, I'm not 100% sure but I think you can initiate this from your Exchange server to say "go and look here now" - or to be a bit bodge-tastic if you are using the same credentials then you can add a DNS entry to point requests to your existing Exchange server to O365 while you get around to updating clients.
Associate
- Joined
- 22 May 2012
- Posts
- 58
Control and links to what?
Yeh could you divulge a bit more information as to why?
We aren't a big organisation - only about 45-50 users!
Associate
- Joined
- 14 Sep 2007
- Posts
- 302
Same - have had several clients that came BACK to exchange 2010 from O365. It's not all its cracked up to be.
Any info as to why they did this?
Associate
- Joined
- 23 Apr 2012
- Posts
- 2,175
- Location
- Edinburgh
Might be nice to get some idea of why companies are backing out of 365 - my colleague is evaluating O365 for management and it's be handy to give him some real-world experience
We've certainly not got any clients reversing their decision after moving to 365... and we're dealing with a huge number of seats
I'd harbour that a) whoever did the implementation did a shocker and made it more complex than it should be or b) the technical team are leading these decisions for your client and are protecting their own interests
Things like exchange are a commodity item, unless you have specific reasons to do so (e.g. security/governance) then there is no reason to on-prem exchange any more.
I'd harbour that a) whoever did the implementation did a shocker and made it more complex than it should be or b) the technical team are leading these decisions for your client and are protecting their own interests
Things like exchange are a commodity item, unless you have specific reasons to do so (e.g. security/governance) then there is no reason to on-prem exchange any more.