I wondered if there was any sort of guide on how to migrate from Exchange 2010 to Exchange 2016? I already have SolidCP installed and working in my 2010 environment. I already found this question which has answered some of my queries and given me a decent start ->
However I did have some further questions.
a) All the other forum posts seem to refer to people that did this as a one big bang migration. Is it possible to do a slower side by side migration – i.e. have a week where some users are still on Exchange 2010 and others are on 2016 and have SolidCP work? Exchange 2016 would be installed alongside 2010, so same forest. I’m guessing I could point SolidCP to the Exchange 2016 box straight away and presumably if a tenant still on Exch 2010 tries to modify their settings through SolidCP, it will instruct the Exch 2016 server which in turn will be able to modify the mailbox on 2010 since they are the same AD and same Exchange organization? Or would this not work and Solid CP needs to talk to Exchange 2010 server component for users on exch 2010, and Exchange 2016 component for users on Exch 2016?
If the above won’t work, I’m also thinking I could create a new Domain Controller and Exchange 2016 box, install the SolidCP Server component on the new DC + Exch server, and create a new ‘virtual server’ in SolidCP to cover the 2 servers, giving me a Virtual Server that references the Exch 2016 environment. This would give me two virtual servers, one for Exch 2010 and one for Exch 2016. Then presumably I could migrate the mailboxes for one tenant (customer), and modify the SQL DB somehow to point that tenant to the new 2016 virtual server?
b) Do you need to install the Solid CP Server on ALL exchange servers in your environment or only 1 of them. For example lets say I have an Exchange 2016 environment of 2 CAS servers and 3 Mailbox servers in a DAG. Do I need to install the SolidCP Server on all 5 servers, or 2 servers (a CAS and a Mailbox), or only one of them?
Thanks in advance.
a) yes this is possible, however please note that it means solidcp needs to continue to point (and generate) oabs etc on Exchange 2010, rather then 2016.
Also note that it means you have to configure 2016 to use basic auth rather then negotiate due to public folders connectivity to exchange 2010.
OAB’s and PF’s can / should generally be done in one swoop once all mailboxes have been (slowly) moved.
Only after that you point SolidCP to 2016 server and provider. (by modifying the database provider ID in the services table) and connection info can be changed in the server –> settings –> top slide “connection info”.
b) exchange 2016 doesn’t have CAS and Mailbox roles seperated anymore (it’s all in one) you can ofcourse not assign some servers mailbox db’s which essentially makes them a CAS, but mailbox DB servers will still be used to provide OWA / ECP etc.
SolidCP generally only communicates with 1 (as external powershell perms are a bit bugged solidcp uses the locan fqdn of the server SolidCP Server is installed on).
I have a follow up question regarding your answer:
“a) yes this is possible, however please note that it means solidcp needs to continue to point (and generate) oabs etc on Exchange 2010, rather then 2016.”
We basically only have 2 company’s running public folders. If we move the 2 company’s to Exchange 2016 and migrate the 2010 public folder to 2016, could we have both 2010 and 2016 server running but change so that newly created users and ORG’s are created on 2016?
That way we can migrate company by company and not with “big bang”
The thing is the OAB’s still, it can only be on 2010 or 2016, not both.
and you normally do that only after all mailboxes have moved.
Atleast i personally would move things over to 2016 and only then flip over solidcp to 2016 not before.
to avoid downtime and other complications.
- Views2802 times
- Answers4 answers