SBS 2003 Replication issue - no other DCs!
Getting prepped to do a SBS 2003 to SBS 2011 migration and getting an error when running the migration prep tool. The tool cannot upgrade the schema. In looking at the eventvwr on the SBS server there is an error:
This server is the owner of the following FSMO role, but does not consider it valid.
This is the only DC and the DNS of this server points back to itself. How can I correct this so I can move forward with my SBS 2011 migration?
Thanks!
This server is the owner of the following FSMO role, but does not consider it valid.
This is the only DC and the DNS of this server points back to itself. How can I correct this so I can move forward with my SBS 2011 migration?
Thanks!
ASKER
This is the results from the dcdiag....at least the interesting parts. Funny thing is there has never been another DC in the mix. There are two other servers, but they are not domain controllers.
Running enterprise tests on : ds.local
Starting test: Intersite
......................... ds.local passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERV
A Good Time Server could not be located.
......................... ds.local failed test FsmoCheck
Running enterprise tests on : ds.local
Starting test: Intersite
......................... ds.local passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERV
A Good Time Server could not be located.
......................... ds.local failed test FsmoCheck
ASKER
Woops....that appears to be a Windows Time service issue. I have started that and I need to restart the server. More to come!
ASKER
For whatever reason AD thinks there is another DC in the mix. Where can I check to see what machine it thinks it out there?
ASKER
I found an old DC listed in Active Directory Sites and Services. Not sure why it is there. Now what is the cleanest way to remove that?
if thats the only dc currently use
check masters roles with FSMO tools
after u check do a metatag clean up
follow steps 1 and 3 only
http://blog.christophermichaelwebb.com/?p=165
check masters roles with FSMO tools
after u check do a metatag clean up
follow steps 1 and 3 only
http://blog.christophermichaelwebb.com/?p=165
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I cleaned it out via asdiedit, seized the roles to be safe and ran dcdiag. All looks better. Going to reboot the server after hours and make sure all is well.
No idea where that old DC came from.
No idea where that old DC came from.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Then use the "IT Health Scanner" which is more AD centric, but again the feedback the tool provides helps find the proper KB articles.
finally, as the migration document states, you should run the dcdiag stuff and check for those errors. DCDiag would flag these errors as well, so you shouldn't actually even *be* at the migration preparation state yet.
-Cliff