Error AD Replication: (8456) The source server is currently rejecting replication requests
Dear All
Currently i have 3 dc running in my company, and one of the dc has exchange 2010 running, and today i found out that the exchange DC has the below error and also checked Go to the HKLM -> System -> CurrentControlSet -> Services -> NTDS -> Paramaters. The DSA Not Writable is set to 4, the USN Rollback occurred
Error AD Replication: (8456) The source server is currently rejecting replication requests
i have no choice have to decommission the affected domain controller by using DCPROMO /ForceRemoval. but this is the exchange server, i dont think it is a good idea to decommission the DC which has exchange 2010 running, any better way to do that ? or i should resize the fsmo to the exchange dc server ?
Currently i have 3 dc running in my company, and one of the dc has exchange 2010 running, and today i found out that the exchange DC has the below error and also checked Go to the HKLM -> System -> CurrentControlSet -> Services -> NTDS -> Paramaters. The DSA Not Writable is set to 4, the USN Rollback occurred
Error AD Replication: (8456) The source server is currently rejecting replication requests
i have no choice have to decommission the affected domain controller by using DCPROMO /ForceRemoval. but this is the exchange server, i dont think it is a good idea to decommission the DC which has exchange 2010 running, any better way to do that ? or i should resize the fsmo to the exchange dc server ?
This kind of issue is exactly why Installing Exchange on a Domain Controller is Not Recommended.
Unfortunately the best way to recover from a USN rollback is to decommission the DC and then rebuild and promote it. Otherwise you will need to recover from a system state backup if once is available, but obviously some Exchange data will be lost.
Hopefully you have another Exchange Server to migrate to so you can demote the DC.
Unfortunately the best way to recover from a USN rollback is to decommission the DC and then rebuild and promote it. Otherwise you will need to recover from a system state backup if once is available, but obviously some Exchange data will be lost.
Hopefully you have another Exchange Server to migrate to so you can demote the DC.
ASKER
I only have a single exchange server, it's not suggested to resize the fsmo in the exchange server ? And decommission the rest of the dc ?
ASKER
i am planning to install another exchange which is a member server with the same window server 2008 R2, and unmount the exchange database from the current production exchange and move the database to the new exchange server and mount it, after that i will discommission the problem exchange and promote it with different server name, is it possible to do in this way ?
Yes, you can do this with pleasure
That is ther only way to do it i think
That is ther only way to do it i think
ASKER
move mailbox from old to new exchange, can not directly copy the database to new exchange to mount it right ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i have installed a new exchange 2013 (member server) when i try to login to ecp, i have below error, do you think this problem is related to the USN Rollback Issue on Exchange Server 2010 ?
Something went wrong message when logging ecp
Something went wrong message when logging ecp
ASKER
How do i fix this, my exchange 2010 getting this error when opening
Its not advisable to demote DC when exchange is installed, it will break Exchange
If you have multiple Exchange servers, you should decommission Exchange server 1st and then demote server forcefully , promote it with some different name again