Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.
-
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Getting this error that is keeping AD DC from starting. On a restore of an AD DC during a total loss of environment.
Just force seize all the roles and be done?
-
@JaredBusch said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Getting this error that is keeping AD DC from starting. On a restore of an AD DC during a total loss of environment.
Just force seize all the roles and be done?
Can't, it has them and it won't use them.
-
Did this, but it still won't start.
-
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Did this, but it still won't start.
My limited input is to verify DNS. Wish I had more.
-
@JaredBusch said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Getting this error that is keeping AD DC from starting. On a restore of an AD DC during a total loss of environment.
Just force seize all the roles and be done?
I went through that just in case, but it didn't work. Same error.
-
@pmoncho said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Did this, but it still won't start.
My limited input is to verify DNS. Wish I had more.
DNS can't sync, it is on and works, but sees AD as failed.
-
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@pmoncho said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Did this, but it still won't start.
My limited input is to verify DNS. Wish I had more.
DNS can't sync, it is on and works, but sees AD as failed.
Is this the only DC ?
-
@dafyre said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@pmoncho said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Did this, but it still won't start.
My limited input is to verify DNS. Wish I had more.
DNS can't sync, it is on and works, but sees AD as failed.
Is this the only DC ?
Restored because crypto was mentioned elsewhere. NO idea if the only one.
-
@dafyre said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@pmoncho said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
Did this, but it still won't start.
My limited input is to verify DNS. Wish I had more.
DNS can't sync, it is on and works, but sees AD as failed.
Is this the only DC ?
There are two, we only had one powered on. Just turned the second on to see what it was seeing.
-
Might be just abandoning the old one. A fresh Windows 2019 AD DC is already part way installed.
-
Found ransomware on the restore. Appears to have happened yesterday at noon. Their restore was from after the infection. So that might be the issue. It might be encrypting.
-
@scottalanmiller Did they have any backups?
-
@jmoore said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller Did they have any backups?
After yesterday at noon. He said that.
-
@jmoore said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller Did they have any backups?
It's in the title
-
@JaredBusch
@murpheous
Your both right, i skimmed a little too quickly there. -
@jmoore said in Restoring 2012 R2 AD DC: This server is the owner of the following FSMO role, but does not consider it valid.:
@scottalanmiller Did they have any backups?
Yup, lots of them.
-
So we did an older restore and the issue was resolved. This error was caused by ransomware.
