Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,173 questions
Make sure the CNO has the right permissions:
After adding the mailbox to the DAG, the server needs to be restarted
Cobion
111
Reputation points
Hello everybody!
There is a DAG on Exchange 2019 CU 12, I'm trying to add two mailbox servers to the DAG cluster. When you add the Add-DatabaseAvailabilityGroupServer -Identity DAG 03 -Mailbox Server MB 06 command, the server is added and the Failover Cluster role is being installed. I'm trying to add a second mailbox server to the cluster in the same way and I get an error. As it turned out, the source server requires a reboot - as far as I understood because of the cluster role. After that, he asks to add the mailbox to the cluster.
Can you tell me how to correctly add mailboxes to an existing DAG, that is, pre-install the Failover Cluster role?
Strange, but in the Exchange 2016 version I did not need to reboot the servers while adding mailboxes to the cluster, even when installing the Failover Cluster component, why is that?
Thanks!
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 31%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJX%3C/text%3E%3C/svg%3E)
Jame Xu-MSFT 4,171 Reputation points2023-02-06T07:38:29.7133333+00:00 Just checking in to see if above information was helpful. Please let us know if you would like further assistance.
If the question has been answered, please accept the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well.
Sign in to comment
Accepted answer
-
Andy David - MVP 144.4K Reputation points MVP2023-02-02T12:37:15.4966667+00:00 -
Cobion 111 Reputation points
2023-02-06T08:03:40.3033333+00:00 Hi! we tried everything possible, gave full rights from the CNO object to the server objects, the error is the same.
We decided to create a new DAG on Exchange 2019+Windows Server 2022 and everything worked out!
Thanks!
Sign in to comment -
9 additional answers
Sort by: Most helpful
-
Cobion 111 Reputation points
2023-02-01T13:44:35.07+00:00 These are the updates and components on the third server without the November SU:
-
Cobion 111 Reputation points
2023-02-01T15:28:33.41+00:00 I'm not trying the Third server, but it got even worse, I don't understand...
-
Cobion 111 Reputation points
2023-02-01T15:29:18.9+00:00 I'm not trying the Third server, but it got even worse, I don't understand...
-
Cobion 111 Reputation points
2023-02-01T22:46:37.75+00:00 Here is the log of the last server addition to the dag and it looks like there are not enough rights to the CNO object for the server and hence the error. Probably the cluster was installed before me through the preparation of CNO