Re: How to remove vestage DNS entries?



"Ace Fekay [MVP]" wrote:

> In news:BCD24176-D78F-4ADA-B18A-C15A7B77D3B7@xxxxxxxxxxxxx,
> Devonshire <Devonshire@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I
> then commented about below:
> > "Ace Fekay [MVP]" wrote:
> >
> >> In news:ABFB6181-6183-4999-9715-660DDFD36A25@xxxxxxxxxxxxx,
> >> Devonshire <Devonshire@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post,
> >> which I then commented about below:
> >>> I started a Server 2003 Std install and started to create a
> >>> domain.local entry and changed my mind.
> >>
> >> How far in the dcpromo process were you when you "changed your mind"?
> >> Did the process complete and you then demoted it and then
> >> re-promoted it choosing the new name?
> >
> > The process did not complete because I canceled the operation just
> > after entering the domain.local name that it suggested as a default.
> > The exact steps as I remember it:
> >
> > I entered the domain.local and pressed next. I then canceled, which
> > it complied with. I rebooted and was back as a member of the existing
> > domain (a "member" being just an ordinary client computer on the
> > existing server's domain).
>
> Ok, that's good.
>
> >
> >>> I then joined an existing
> >>> domain (syntax was" domain.com") transferred all the files to the
> >>> new file server and then successfully promoted my new server to
> >>> primary domain controller and finally shut down the old server.
> >>
> >> How did you "shutdown" the old server? Did you properly demoted it
> >> or just unplugged it like the way we used to do with an old NT4
> >> server? I guess if you were trashing the old server and completely
> >> eliminating the domain.com AD domain, then it wouldn't really matter.
> >
> > I went throughthe process of connecting to the older domain
> > controller and transferring the information (I believe this is the
> > promotion process). By promoting the new server, the old server was
> > converted to a secondary domain controller. I then simply
> > disconnected the network cable and turned the power off.
>
> Ok, maybe I might be missing something. It appears you are talking about an
> NT4 machine you pulled the plug on.
>
> If it's not an NT4 DC, the plugged can't just be simply "pulled" with
> Windows 2000 and 2003 DCs. THey have to properly demoted using dcpromo.exe.
> You just select to demote the machine from a DC to a member server. If you
> did this, then I would suggest to plug it back in and demote it, as long as
> the plug wasn't pulled on it more than 60 days ago (the default tombstone
> lifetime of a deleted record in the AD database). If longer than the
> tombstone lifetime, the old server can't be brought back up and would need
> to get wiped clean and reinstalled. Then a Metadata cleanup will be required
> to clean it's old reference out of the AD database.

It was a Windows 2000 server. I downloaded and installed a utility to
enable it to be in the newer WIN2003 server forest (I can't remember the
exact name of it, but otherwise the new server couldn't connect to the old
WIN2000 Server's DC). That utility patch was successful. Then I did the
formal DCPromo and every step was successful. (My brother-in-law who actually
does this stuff everyday was there at every step).

> >> btw- "Primary Domain Controllers" (PDCs) don't exist in Windwos 2000
> >> or 2003. There is a FSMO role that one of the servers hold and
> >> emulate an NT4 PDC, (that performs other functions as well). NT4's
> >> PDC was the ONLY writable database in the domain. All Win2000 and
> >> 2003 DCs are exact master writable replicas meaning anyone can
> >> change anything in AD on any one of the servers at any given time
> >> and depending on what type of data got changed, will replicate to
> >> the domain and/or to the forest.
> >>
> >>>
> >>> The problem is that the DNS event log keeps reporting event 4007
> >>> over and over which is looking for that original domain.local zone
> >>> which does not exist as far as I can tell otherwise. How do I
> >>> clean this up and stop the error messages?
> >>
> >> Was the zone AD Integrated? If so, check in ADSI Edit to see if it
> >> still exists.
> >
> > AD "Sites and Services" still lists the old server under "Sites" by
> > names and has a NTDS Settings entry just like the new server.
>
> That can be deleted if the server is truly "gone" and after you performed a
> Metadata cleanup.
>
> Also, have you looked in ADSI Edit and looked in the app partitions for the
> existence of the "domain.local" zone?
>
> Here's more info about Metadata cleanups below. I hope that is helpful and
> understood what occured and what needs to be done to rectify this.

I will look into the Metadata cleanup, thanks.
>
> Clean up server metadata Active Directory 2003:
> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Operations/012793ee-5e8c-4a5c-9f66-4a486a7114fd.mspx
>
> Ace
>
>
>
>
.

Relevant Pages

  • Re: can I just delete a crashed DC?
    ... If it will never come back and you can not repair then you have to run metadata cleanup according to this: ... So if you are not over the tombstone lifetime you can also reconnect it and demote it. ... the server in question was taken offline weeks ago, ...
    (microsoft.public.windows.server.active_directory)
  • RE: force removal of Domain controllers from AD
    ... Unfortunately a collegue of mine previously removed site ... metadata cleanup: s o t ... to delete from depth of structure until including server name). ... chech the fsmo roles and reseize what is necessary. ...
    (microsoft.public.windows.server.active_directory)
  • RE: force removal of Domain controllers from AD
    ... metadata cleanup: s o t ... select operation target: list sites ... to delete from depth of structure until including server name). ... chech the fsmo roles and reseize what is necessary. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Removing a child domain from the parent
    ... I successfully removed the server with the ... I am trying to run the metadata cleanup. ... server connections: connect to server app1 ... metadata cleanup: select operation target ...
    (microsoft.public.windows.server.setup)
  • RE: using ntdsutil to remove a DC from AD
    ... Also, we you remove the server, If you got "Element not found error" this ... metadata cleanup: select target operation ... select operation target: list domains ... Not connected to a server - use "Connections" ...
    (microsoft.public.windows.server.dns)