Did You Know 3: AD Schema Troubleshooting Flow

This is not something new and the are many methods that are circulating around the internet to troubleshoot the issue. Here are some of the personal finding and preference to resolve the issue. 

Problem: 

Upon extending the schema, you saw error code 8202 in the log file. And you realise that the AD schema extension is not complete

Steps: 

1) Make you that the AD account your are using has Enterprise Admin and Schema Admin rights. 

2) Ensure that the replication partners are all there in AD. This can be easily achieve when you go into the console of "AD sites and services" Make sure all the DC are replication partners this is to ensure that the extension is replicated across the DC

3) Ensure that the DC you are working at has the Schema master FMSO roles or else you will hit the above error as well.  Fire up the command prompt as administrator in your DC and key the following: netdom /query fmso You must ensure that the DC holds the Schema Master FMSO role. 

Conclusion:

While people have argument to say that the AD schema extension can be done on site server. Base on my personal experience it would be best to do it on a DC with Schema Master FMSO role. Make sure you go through the above checkpoint so that you won't get the error. 

Happy reading!

SY