AD/2000 schema extension to host AD/2003 Domain Controller

[Thomas Kuborn]

Dear Ng,

When I performed an "adprep /forestprep" on the DC owning the schema role, I
got the following error :
ERROR: Failed to transfer the schema FSMO role: 52 (Unavailable)

I was running the command using the Administrator account which is part of
the Schema Admin group.
I had installed the AD schema snapin & checked "the schema can be modified
on this DC " ... no luck :-(

Anyone had an idea why this did NOT work & started to work for no apparent
reason ???

- Thomas -

 

[Dean Wells [MVP]]

Dear Ng,

When I performed an "adprep /forestprep" on the DC owning the schema
role, I got the following error :
ERROR: Failed to transfer the schema FSMO role: 52 (Unavailable)

I was running the command using the Administrator account which is
part of the Schema Admin group.
I had installed the AD schema snapin & checked "the schema can be
modified on this DC " ... no luck :-(

Anyone had an idea why this did NOT work & started to work for no
apparent reason ???

- Thomas -

Are you running the command on the Schema FSMO?

 

[Dean Wells [MVP]]

Are you running the command on the Schema FSMO?

Read the post Dean, read the post ... doh!

Since you've already told me you're running the command on the console
of the Schema FSMO, it's likely that the error is caused by something
known as INITSYNC ... a requirement for any Domain Controller holding a
FSMO role to replicate before offering any of the services associated
with that FSMO.

What service pack are you running? SP3 or 4 (3 I believe) introduced
INITSYNC across all FSMOs.

How many DCs do you have and did you attempt to perform this operation
offline?

If you did perform it offline, bring the DC back online again (assuming
you've made no other potentially destructive changes), force it to
replicate and repeat your procedure (you can take it offline again once
a full replication cycle has occurred).

Dean