PDA

View Full Version : AD FSMO roles corrupt

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

Richard McCall [MSFT]
Have you tried using NTDSUTIL to seize the schema role. The server SKC1 has
had it machine account deleted. If SKC1 is still up you have two option.
Authoritative restore or dcpromo forceremoval and metadatacleanup.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
"Jeroen Jordens" wrote in message
news:469701c3e486$5f01a600$a301280a@phx.gbl...
> 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
>


Jeroen Jordens
Thank you. This worked like a charm, I'm very gratefull.

Regards,

Jeroen



>-----Original Message-----
>Have you tried using NTDSUTIL to seize the schema role.
The server SKC1 has
>had it machine account deleted. If SKC1 is still up you
have two option.
>Authoritative restore or dcpromo forceremoval and
metadatacleanup.
>
>--
>Richard McCall [MSFT]
>
>"This posting is provided "AS IS" with no warranties, and
confers no
> rights."
>"Jeroen Jordens" wrote in
message
>news:469701c3e486$5f01a600$a301280a@phx.gbl...
>> 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
>>
>
>
>.
>