Exchange 2013 Error creating new Database

[dapaulio]

Server 2008r2 with Exchange 2013 (onsite)

 

Earlier in the year I introduced a 2016 dc server and since I have not been able to create a new database in EMC

 

The error itself references my 2016 dc in the error that has been redacted in the screen shot.

 

Other info which may help

Domain Functional Level 2008R2

 

Any help would be greatly appreciated

[colly72]

Are your domain controllers replicating correctly? Try Repadmin /showrepl to see if there are any issues

[Oaktech]

I just googled the error and yeah, loads of hits about replication... So do the repadmin /showrepl first, it might be a permission.

 

I assume the schema has been upgraded, firstly for exchange 2013... https://technet.microsoft.com/EN-US/library/bb125224(v=exchg.150).aspx

 

and secondly for 2016 DC? https://samilamppu.wordpress.com/2016/11/06/upgrading-ad-ds-schema-to-windows-server-2016/

[dapaulio]

Are your domain controllers replicating correctly? Try Repadmin /showrepl to see if there are any issues

 

yeah repadmin ok

 

 

Realised i made a mistake in exchange version which I only realized whilst looking at the Objectversion attribute in ADSI Edit is at 14322 which is 2010 SP3

[dapaulio]

looking at documentation it is my understanding that Exchange 2010 SP3 is not supported within 2016 AD environments.

 

We have currently 4 dc servers (2 x 2008r2, 1 x 2012r2, and 1x 2016) the idea was to roll the 2008r2's out of production for 2 x 2016 dcs.

 

Any further advice would be appreciated

[colly72]

We went from Exchange 2010 SP3 to 2016 a while ago - this would seem like your best option if you're set on 2016 DCs. As is often the case with Exchange you have to install 2016 alongside your existing 2010 servers, then migrate across. What's the pressing need for a 2016 dc?

[dapaulio]

worked it out

Rather than use EMC which selected my 2016 server to pull info from I PS the database creation

new-mailboxdatabase - name "name" -server "mailserver" -domaincontroller "anotherDC fqdn" 

 

Thanks all for your help

 

- - - Updated - - -

 

We went from Exchange 2010 SP3 to 2016 a while ago - this would seem like your best option if you're set on 2016 DCs. As is often the case with Exchange you have to install 2016 alongside your existing 2010 servers, then migrate across. What's the pressing need for a 2016 dc?

 

we are planning moving to O365 hopefully this summer

 

Partly because I'm looking to decommission the 2008r2 dc's over the next year and replace them with 2016. it just made sense rather than doing 2012r2 then upgrading again. Plus wanted to play with AD activation

Edited June 23, 2017 by dapaulio