Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 613
  • Last Modified:

transfer of fsmo roles

i happen to transfer fsmo roles from a windows 2003 32 bit server std to a windows 2008 64 bit
std server.this was successful but some domain controls see the new server with the fsmos roles but some member servers report error under fsmo roles.i have rebooted these servers showing the error but still cant show any changes.can some please help me see what am missing to make the others server point to the new operations mater.

thanks Emma
0
MRCUGANDA
Asked:
MRCUGANDA
  • 2
1 Solution
 
ScovndrelCommented:
It sounds like a DNS or replication issue.

Check your DNS settings on the servers that do not see the correct FSMO role holders. Make sure they are pointing to the same DNS servers as the ones that are working properly.

Also, use Active Directory Sites and Services, expand to the replication objects, right-click them, and choose to Replicate Now. Do that for all of them. If you get error messages when yo do that, you have some troubleshooting to do.

Try using repadmin /showreps (you'll need the Windows Server Support Tools package installed) to examine the replication status.
0
 
SommerblinkCommented:
Agreeded.

Sounds like you had a preexisting AD problem.

I would recommend the above, plus going through event viewer for all your DCs and see if there are errors there that may point towards your problem.
0
 
ScovndrelCommented:
What astonishes me is that it's even necessary to remind people to do that. But you're right, the event logs might have some good clues.

Also DCDiag and NetDiag in the Windows 2003 Support Tools package are good things to run. You can copy them over to the 2008 server and run them there as well.

Netdiag is deprecated in 2008. Its functions are integrated into the Netlogon service, but you can still copy the .exe from a 2003 server and run it explicitly to look for clues.

0
 
MRCUGANDAAuthor Commented:
thanks so much for your response.10 mins after i posted i found out it was a dns issue.pointing the other memeber server's dns to the master dns server worked just fine.

thanks again
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now