Re: primary domain controller is down
- From: Marco <Marco@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Jun 2006 02:28:02 -0700
""Frank Röder [MVP]"" wrote:
Marco schrieb:
My platform is window 2003 sevrer with SP1 installed.
I could see, the command line 'ntdsutil' automatically do the metadata clean
up.
follow this article to perform the metadata cleanup:
https://mvp.support.microsoft.com/default.aspx?scid=kb;en-us;216498
If i unstand what you said, i we perform this to delete a domain controller
because reading this document, it tells delete a server (this can be a server
memebr not a domain controller isnt it?)
thanks for your reply.
I can post any unbelieve question but how it's critical i want to be sure.
thans kor all
.
is a problem that the global catalog is not checked?
i seized 4 roles:rid master,pdc,domain,schema
a error message diplayed : win 32 error 0x20af(the current fsmo holder could
not be contacted)
transfer failed....
However,the result changed
you tried to transfer the fsmo roles with the "mmc"?
Follow this article:
1. Log on to a Windows 2000 Server-based or Windows Server 2003-based
member computer or domain controller that is located in the forest where
FSMO roles are being seized. We recommend that you log on to the domain
controller that you are assigning FSMO roles to. The logged-on user
should be a member of the Enterprise Administrators group to transfer
schema or domain naming master roles, or a member of the Domain
Administrators group of the domain where the PDC emulator, RID master
and the Infrastructure master roles are being transferred.
2. Click "Start", click "Run", type "ntdsutil" in the Open box, and then
click OK.
3. Type "roles", and then press ENTER.
4. Type "connections", and then press ENTER.
5. Type "connect to server servername", and then press ENTER, where
servername is the name of the domain controller that you want to assign
the FSMO role to.
6. At the server connections prompt, type "q", and then press ENTER.
7. Type "seize role", where role is the role that you want to seize. For
a list of roles that you can seize, type ? at the fsmo maintenance
prompt, and then press ENTER, or see the list of roles at the start of
this article. For example, to seize the RID master role, type seize rid
master. The one exception is for the PDC emulator role, whose syntax is
seize pdc, not seize pdc emulator.
8. At the fsmo maintenance prompt, type q, and then press ENTER to gain
access to the ntdsutil prompt. Type q, and then press ENTER to quit the
Ntdsutil utility.
do this for all *five* fsmo roles!
after the procedure, check if the domain is functional.
execute "dcdiag" and "netdiag" on the existing dc.
--
Viele Grüße
Frank Röder
MVP Windows Server System - Directory Services
"Ex oriente lux"
- Follow-Ups:
- Re: primary domain controller is down
- From: "Frank Röder [MVP]"
- Re: primary domain controller is down
- References:
- Re: primary domain controller is down
- From: Jorge Silva
- Re: primary domain controller is down
- From: Marco
- Re: primary domain controller is down
- From: "Frank Röder [MVP]"
- Re: primary domain controller is down
- Prev by Date: Re: A real tough one with DCPromo
- Next by Date: Re: Role Based Access in Windows 2003
- Previous by thread: Re: primary domain controller is down
- Next by thread: Re: primary domain controller is down
- Index(es):
Relevant Pages
|