Exchange 2013 DAG Server Repair

I've setup a 3 server Exchange 2013 DAG.  One of the servers failed due to faulty hardware and had to be completely scrapped.  I'm following the guide to recover the server as seen here:

On the following step I get the following error:

[PS] C:\>Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer SERVER3
The fully qualified domain name for node 'SERVER3' could not be found.
    + CategoryInfo          : NotSpecified: (:) [Remove-DatabaseAvailabilityGroupServer], AmGetFqdnFailedNotFoundExcep
    + FullyQualifiedErrorId : [Server=SERVER1,RequestId=1871d2ec-1356-4541-9860-e3727f04c809,TimeStamp=4/21/2018 1:09:43
   PM] [FailureCategory=Cmdlet-AmGetFqdnFailedNotFoundException] 49FD7853,Microsoft.Exchange.Management.SystemConfigu
    + PSComputerName        :

Open in new window

What should my next step be in this scenario?

There are similar errors with the name of the DAG displayed but I've never seen an error where the name of the server you're trying to replace shows up as the error.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hasin Ahmed ChoudharyExchange AdministratorCommented:
Is server3 the one which has failed. By any chance have you deleted the computer object for server3..?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TechnicalSquidAuthor Commented:
Yes Hasin, that's exactly what happened.  When I rejoined the new server to the domain the error went away.

Now I have a new error about cluster clean up but I assume that it's safe to ignore because the old SERVER3 is irrecoverably gone and this is a new SERVER3 which doesn't have clustering service installed, hence doesn't need cleanup.

Do you concur?  Here's the error in question

[PS] C:\>cluster node SERVER3 /forcecleanup

Attempting to clean up node 'SERVER3' ...
The first error encountered is shown below. For a complete list of errors
and suggestions for recovery, see the Failover Clustering application event
log using Event Viewer on the node.

System error -2147221164 has occurred (0x80040154).
Class not registered

Open in new window

TechnicalSquidAuthor Commented:
I'm going to keep following the MS article to recover the server.

Next going to install Exchange, same CU as production using "Setup /m:RecoverServer" switch
SD-WAN: Making It Work for You

As bandwidth requirements and Internet costs grow, businesses naturally want to manage budgets by reducing reliance on their most expensive connection types. Learn more about how to make SD-WAN work for your business in our on-demand webinar!

Hasin Ahmed ChoudharyExchange AdministratorCommented:
If AD deleted the AD project and re-add the server, that means that it will be counted as a new server.  If you try to recover the server, i doubt if that will be successful.

In such case, what option you have left is 1) Build new server with new name to avoid conflict
                                                                            2) Add to DAg and copies.
TechnicalSquidAuthor Commented:
Looks like adding it back with the same name and /m:RecoverServer did the trick.  There were no issues adding back to DAG.  Now I'm finishing seeding all the DBs and it's going well so far except sometimes it just stops and leaves the DB in seeding state.  Luckily if I remove the replicate and retry the seeding process, it picks up from where it stopped/crashed.
TechnicalSquidAuthor Commented:
Adding computer account back into AD worked in production and failed in test.  In test only 1 of the 3 servers and the witness were restored so it's not a 1-to-1 situation.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Database Availability Group (DAG)

From novice to tech pro — start learning today.