Re: Windows cannot verify >>>
- From: "WANNABE" <SameAsB4>
- Date: Mon, 11 Jun 2007 09:44:44 -0500
YES, all very helpful thank you!!!
IMO >of course> :-) how blind am I ...
AS 4 the meta data cleanup that web link looks like it should explain the steps
I need 2 take..
THANKS AGAIN!!!!
============================================
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:288E65AA-5BBF-4F37-994D-FFF810ECDD37@xxxxxxxxxxxxxxxx
IMO=In my opinion.
You use dcpromo to promote a Server to DC, and you also use dcpromo to
demote a DC to a normal member server.
In situations where you don't use the dcpromo to remove a particular DC (for
example the server died or burned whatever....) you need to remove existing
AD references to that dead DC manually, this process is called metadata
cleanup, to perform metadata cleanup check:
http://support.microsoft.com/kb/216498/en-us
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"WANNABE" <SameAsB4> wrote in message
news:eFn4hHDrHHA.4108@xxxxxxxxxxxxxxxxxxxxxxx
OK, I've come a long way baby, GC = Global Catalog 'du' Still looking for
IMO...
I was able to change the GC to the current server, via properties /
general tab
GC check box... and I see the message in the event logs that after 5
minutes
the new server is the GC. and once again I can create user accounts. Can
someone PLEASE explain "Like you are talking to an idiot" how this is done
>>
"perform metadata cleanup and seize any FSMO roles held by that DC", I'm
pretty
sure this is what I need to do next because the OLD DC is powered off,
retired.
(see previous reply post for description of this network)
AND What does this mean > "IMO is a good practice to have at least 1
DC/GC or
more per site" It might help if I knew what IMO was?
THANK YOU AGAIN FOR ANY AND ALL HELP PROVIDED!!!!
===================================================
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:8B526688-9DBC-44C3-BD57-F02F6D883CFF@xxxxxxxxxxxxxxxx
Hi
You can use Ative Drectory Sites and Services and under Ntds settings
properties you can check what DCs are GCs, you can alse other tools like
replmon or repadmin....
Regarding to FSMO placement and GC have a look at:
http://support.microsoft.com/kb/223346/en-us
If you're sure that the server is dead and was properly removed from AD,
you
can just rightclick the server on Active directory and Services and delete
that server. If the server wasn't removed from Ad using dcpromo, you ned
to
perform metadata cleanup and seize any FSMO roles helded by that DC.
Make sure that you have at least 1 DC/GC in your forest, IMO is a good
practice to have at least 1 DC/GC or more per site.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"WANNABE" <SameAsB4> wrote in message
news:%23f4XBs8qHHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
I have found the old server listed under servers in the Active directory
Sites
and Services. Can I just delete the old server? Or what must I do to
remove it
from the system??
=================================================
"WANNABE" <SameAsB4> wrote in message
news:e4sYdC8qHHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
that the user name is unique because the following error occurred while
contacting the global catalog: the server is not operational.
That is the message I got when I created a new user. The user account is
still
created but the rest of the message tells me "but the user can log on
only
after
the user name is verified to be unique. Make sure the global catalog is
available." What is the global catalog and hoe do I manage this? I do
see
reference to what was the DNS server (which has since been shutdown, as
this
server is the replacement) in the event logs. This may be a second
question or
it may be relevant to the initial issue, but what else do I need to do to
stop
this server from looking for the original server??
THANK YOU TO ANYONE WHO CAN HELP, I REALLY APPRECIATE ALL HELP!!!
.
- References:
- Windows cannot verify >>>
- From: WANNABE
- Re: Windows cannot verify >>>
- From: WANNABE
- Re: Windows cannot verify >>>
- From: Jorge Silva
- Re: Windows cannot verify >>>
- From: WANNABE
- Re: Windows cannot verify >>>
- From: Jorge Silva
- Windows cannot verify >>>
- Prev by Date: Re: ADAM And ACLs
- Next by Date: Re: Raise Domain Functional Level
- Previous by thread: Re: Windows cannot verify >>>
- Next by thread: Re: Groups
- Index(es):
Relevant Pages
|
