Dead Windows Server 2003 R2 Domain Controller on DC1 - FSMO Roles Issue - Urgent Help!
guys, had server crash on dc1 - beamnt.com. got replication dc2 - beamnt2.com, global catalog on replication of both active directory , dns.
i unable restore dc1 tape drive faulty..
my fsmo 5xroles on dc1, , 30 users join domain. still able use dc2 function on dhcp/dns/ad problem fsmo roles, affect users pc join domain if able somehow restore fsmo roles.
how savage this? please me.
hi need seize them; you'll find procedure here
seize fsmo roles using ntdsutil utility, follow these steps:1. log on windows 2000 server-based or windows server 2003-based member computer or domain controller located in forest fsmo roles being seized. recommend log on domain controller assigning fsmo roles to. logged-on user should member of enterprise administrators group transfer schema or domain naming master roles, or member of domain administrators group of domain pdc emulator, rid master , infrastructure master roles being transferred.
2. click start, click run, type ntdsutil in open box, , click ok.
3. type roles, , press enter.
4. type connections, , press enter.
5. type connect server servername, , press enter, servername name of domain controller want assign fsmo role to.
6. at server connections prompt, type q, , press enter.
7. type seize role, role role want seize. list of roles can seize, type ? @ fsmo maintenance prompt, , press enter, or see list of roles @ start of article. example, seize rid master role, type seize rid master. 1 exception pdc emulator role, syntax seize pdc, not seize pdc emulator.
8. at fsmo maintenance prompt, type q, , press enter gain access ntdsutil prompt. type q, , press enter quit ntdsutil utility
post provided no warranties or guarantees, , confers no rights.
~~~
questo post non fornisce garanzie e non conferisce diritti
Windows Server > Directory Services
Comments
Post a Comment