pablo007 Posted March 6, 2019 Posted March 6, 2019 Hi all i just installed exchange server 2016 on a new vm all seemed to go to go ok (followed the exchange server deployment assistant) got as far as going to create a new exchange 2016 mailbox using ECP and noticed that my exchange 2016 box is already fully populated with mailboxes from the current 2010 exchange server is this normal, i was expecting there to be nothing until i migrated them all over ? thanks as always for any guidance. Pablo
Jamman960 Posted March 6, 2019 Posted March 6, 2019 You'll see them in there as part of the exchange organisation, they'll still need to be moved into the new mailbox database 1
3s-gtech Posted March 6, 2019 Posted March 6, 2019 Moving them can be done via Powershell or the ECP - probably easier from the 2016 server. You can do it in batches, and it takes varying time depending on the size of the mailboxes. I did ours a year group at a time, and in batches of 10 teachers. Not a bad job at all. Just make sure you migrate all of your mail flow, certificates etc.
pablo007 Posted March 7, 2019 Author Posted March 7, 2019 The ECP looks friendly enough, just looking at certs now is there an opportunity to use the same cert that is currently on the 2010 box or will i have to buy a new one to stop any confusion during the transition period ?
3s-gtech Posted March 7, 2019 Posted March 7, 2019 (edited) You can install the same one. However, you’ll get cert errors until you swap DNS settings to point at the new box. Not a major issue. I have implemented Let’s Encrypt certs on my Exchange 2016 box - these are free and are set to auto-renew then scripted to apply to all services. Saves money and hassle. You’ll also want to go through the (fairly simple) steps to ensure that TLS 1.2 is enable for mail flow. Edited March 7, 2019 by 3s-gtech
pablo007 Posted March 7, 2019 Author Posted March 7, 2019 yeah let's encrypt is a good option but we do not manage our website, have no ssh access or otherwise to it (which is the way i like it..)
3s-gtech Posted March 7, 2019 Posted March 7, 2019 That's fair enough, but as long as LE can get through your proxy/firewall it should still work for Exchange. Here's my list of essential guides I used when installing Exchange 2016 late last year. There's some great stuff in these. https://malcolmplested.co.uk/2018/09/17/exchange-2013-2016-enabling-tls-1-2/ https://github.com/PKISharp/win-acme/wiki/Microsoft-Exchange https://www.msoutlook.info/question/set-reply-as-default-instead-of-reply-all-owa-2016 https://mediarealm.com.au/articles/lets-encrypt-microsoft-exchange-installation/ https://gist.github.com/anthonyeden/015c568b169901a9879a1b504a089596 https://docs.microsoft.com/en-us/exchange/clients/outlook-on-the-web/http-to-https-redirection?view=exchserver-2019 Technical Deep Dive: Exchange 2013 to 2016 Migration (Part 6) https://dirkjanm.io/abusing-exchange-one-api-call-away-from-domain-admin/ 1
pablo007 Posted March 7, 2019 Author Posted March 7, 2019 Brilliant list mate let me add this one for anyone else https://practical365.com/exchange-server/migrating-exchange-server-2016
ITGURU Posted March 7, 2019 Posted March 7, 2019 I've done exchange migrations from 2000 to 2016 but never jumped that far ahead. backups are critical and do your research online. the migration from 2013 to 2016 was the easiest one I ever did. Set up the new server, changed DNS records to point to the new server, all users use the new server for access but backwards compatible access to 2013 mailboxes, then did the mailbox migration and cleaned up the old server. if memory serves me right there will also be a fore more steps if you are decommissioning exchange 2010. good Luck!
pablo007 Posted March 7, 2019 Author Posted March 7, 2019 I had to contend with the residue of two previous iterations of exchange server (2003,2007) not being gracefully removed from the outset of this migration so had to dig into adsiedit but overall so far so good, i particularly like the way 2016 proxy's for the 2010 or vice versa dependant on where the mailbox is located although i wish it wish just a little more seamless.
pablo007 Posted March 11, 2019 Author Posted March 11, 2019 Moving them can be done via Powershell or the ECP - probably easier from the 2016 server. You can do it in batches, and it takes varying time depending on the size of the mailboxes. I did ours a year group at a time, and in batches of 10 teachers. Not a bad job at all. Just make sure you migrate all of your mail flow, certificates etc. Was there any particular permissions on the exchange 2010 box required? i have set the user doing the migration with Recipient Management & Organization Management roles in the exchange 2016 ecp but the moves are failing with what looks like a permissions error.
3s-gtech Posted March 11, 2019 Posted March 11, 2019 The user I used has Organisation Management, Discovery Management and Recipient Management roles, as well as being an Enterprise Admin.
pablo007 Posted March 11, 2019 Author Posted March 11, 2019 The user I used has Organisation Management, Discovery Management and Recipient Management roles, as well as being an Enterprise Admin. Yeah mine too so its not that, strange that i was able to move ny arbitration mailboxes without problems.
pablo007 Posted March 11, 2019 Author Posted March 11, 2019 working now, done nothing, i looked through logs it said Relinquishing job because of large delays due to unfavorable server but looks like its working now odd .
pablo007 Posted March 11, 2019 Author Posted March 11, 2019 working now, done nothing, i looked through logs it said Relinquishing job because of large delays due to unfavorable server but looks like its working now odd .
pablo007 Posted March 11, 2019 Author Posted March 11, 2019 i have obviously done something wrong a few users now can't connect to email via outlook they get a message the server is unavailable, the same user can access owa so it must be something to do with autodiscover ? any ideas anyone
3s-gtech Posted March 11, 2019 Posted March 11, 2019 You will need to enable IMAP (I think) service on the new Exchange server. It’s Disabled by default. I had to do the same for Thunderbird, but I don’t use Outlook so not 100% sure it uses that protocol. You just enable it from the normal Services list in Computer Management.
MS2011 Posted March 11, 2019 Posted March 11, 2019 That's fair enough, but as long as LE can get through your proxy/firewall it should still work for Exchange. Here's my list of essential guides I used when installing Exchange 2016 late last year. There's some great stuff in these. https://malcolmplested.co.uk/2018/09/17/exchange-2013-2016-enabling-tls-1-2/ https://github.com/PKISharp/win-acme/wiki/Microsoft-Exchange https://www.msoutlook.info/question/set-reply-as-default-instead-of-reply-all-owa-2016 https://mediarealm.com.au/articles/lets-encrypt-microsoft-exchange-installation/ https://gist.github.com/anthonyeden/015c568b169901a9879a1b504a089596 https://docs.microsoft.com/en-us/exchange/clients/outlook-on-the-web/http-to-https-redirection?view=exchserver-2019 Technical Deep Dive: Exchange 2013 to 2016 Migration (Part 6) https://dirkjanm.io/abusing-exchange-one-api-call-away-from-domain-admin/ Great [emoji106] Any suggestions regarding to migrate exchange 2010 to 2019? Our DC’s are 2012 R2
3s-gtech Posted March 11, 2019 Posted March 11, 2019 2019 should be almost identical to 2016 for doing this from what I’ve read. I chose not to go to 2019 even though it was out, because I don’t like being a paying beta tester, and there was a huge depth of info regarding 2016. 2019 is maturing well and it should be straightforward. 1
MS2011 Posted March 12, 2019 Posted March 12, 2019 2019 should be almost identical to 2016 for doing this from what I’ve read. I chose not to go to 2019 even though it was out, because I don’t like being a paying beta tester, and there was a huge depth of info regarding 2016. 2019 is maturing well and it should be straightforward. [emoji106]
pablo007 Posted March 12, 2019 Author Posted March 12, 2019 feel certain this is either proxy server related (we sit behind a netsweeper appliance) or GPO settings or user permissions that is stopping the profile being created. Will be investigating this today.
pablo007 Posted March 12, 2019 Author Posted March 12, 2019 this is my exact issue https://social.technet.microsoft.com/Forums/en-US/c3f162cb-bbd9-41d4-8245-01b4863e98e1/outlook-2010-cannot-connect-to-exchange-2016-during-migration-from-2010?forum=Exch2016SD But we have the two kbs already installed on our exchange 2010 any one any other ideas ?
pablo007 Posted March 12, 2019 Author Posted March 12, 2019 Managed to get a workaround at least for now, which involved moving the user to a GPO which allowed control panel/mail. When a new user logs on initially there is no outlook profile in control panel/mail so I create one called outlook it then goes through the connection wizard resolves username and server name etc and looks like it will work but it fails with the same error, however, if i go back to mail delete the profile that outlook has created called outlook2010 and just leave the one i created it works. This will do until we upgrade to office 2016 very soon.
MS2011 Posted May 2, 2019 Posted May 2, 2019 Hi all I’m doing migration from exchange 2010 to 2016. About 1500 users. Once everything moved, I want to setup office 365(hybrid). I need recommendation for new hardware and migration advice. Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now