J
Jeroen Jordens
Hi,
There seems to have gone something horribly wrong with AD.
The Schema master role has been corrupted somehow. When I
view the roles on either one of the 3 servers I see the
schema listed as:
Schema - CN="NTDS Settings DEL:4eac4dd0-e48d-4663-9a72-
180e1ab2782c",CN="SKC1 DEL:8901b15b-b2a1-4485-9dea-
ffab6743dfb8",CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=stkevins,DC=local
The other 4 roles are fine.
This role cannot be seized either.
This, I suspect, is causing a heap of issues that I am
trying to solve.
Can someone tell me if there is hope, maybe through
something like ADSI edit?
Cheers,
Jeroen
There seems to have gone something horribly wrong with AD.
The Schema master role has been corrupted somehow. When I
view the roles on either one of the 3 servers I see the
schema listed as:
Schema - CN="NTDS Settings DEL:4eac4dd0-e48d-4663-9a72-
180e1ab2782c",CN="SKC1 DEL:8901b15b-b2a1-4485-9dea-
ffab6743dfb8",CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=stkevins,DC=local
The other 4 roles are fine.
This role cannot be seized either.
This, I suspect, is causing a heap of issues that I am
trying to solve.
Can someone tell me if there is hope, maybe through
something like ADSI edit?
Cheers,
Jeroen