Exchange 2013 DAG creation issue on Windows 2012 R2
Pana acum am reusit sa creez DAG-ul pe Windows 2012 fara sa fac prestage la computer accountul pentru cluster (CNO), dar la o implementare noua pe Windows 2012 R2 nu am reusit. Chiar daca am setat permisiuni pe CNO-ul nou creat de setup pur si simplu nu a mers.
Imediat ce am urmat sfatul de aici, a mers fara probleme:
http://technet.microsoft.com/en-us/library/ff367878(v=exchg.150).aspx
In addition, when deploying a database availability group (DAG) using Mailbox servers that are running Windows Server 2012, you must pre-stage and provision the CNO. Pre-staging the CNO is required for Windows Server 2012 DAG members due to permissions changes in Windows Server 2012 for computer objects.
You create and disable a computer account for the CNO, and then either:
-
Assign full control of the computer account to the computer account of the first Mailbox server you’re adding to the DAG.
-
Assign full control of the computer account to the Exchange Trusted Subsystem universal security group (USG).
2 Responses to “Exchange 2013 DAG creation issue on Windows 2012 R2”
Comment from Andrei Ungureanu
Time May 19, 2014 at 9:41 pm
Pai era setup curat, totul nou. Eu sunt curios sa aflu care sunt acele schimbari “due to permissions changes in Windows Server 2012 for computer objects”.
Comment from Dragos
Time May 16, 2014 at 2:21 pm
Exact asta am patit si eu.
Era in urma unei migrari de la 2010 la 2013 si m-am gandit ca ala e motiviul.
Sunt curiso daca apar aceste scenarii si la un setup curat si nou pe 2012 r2 cu exchange 2013 sp1; ca daca da, atunci Microsoftul ar trebui sa isi rezolve problema.
Un DAG pe 2013 cu 2012 am mai facut acum un an si acolo a mers perfect.