Re: Replacing Win2000 Domain controllers

Hello SilvrT,

Normally you can rename a computer in the domain without any problem, maybe the account did not have the correct rights in AD. Anyway ofcourse you can remove it and add it again if you have problems. If you remove it give time for replication and also check that all entries from the DNS management console are deleted and also from the DNS zone properties under the Name server tabs, if it was a DNS server.

If you have run adprep command and moved the FSMO roles after it, it should be fine. But check with adsiedit.msc from the support tools, that you have to install from the installation disk\support\tools.
Start adsiedit and go to Schema, on the right pane you see CN=Schema,........... rightclick it, open properties and in 2003 server scroll down in the list to "objectVersion", the number under Value will show you the Schema version, 13 server 2000, 30 server 2003 and 31 server 2003 R2. In 2000, select for the view BOTH and selct the property to view "objectVersion", under the attribute Values you can see the Version from the Schema.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

demoting OK, removing not necessary. If it is demoted without errors
and
it is moved to Computers Container, just give some time for
replication and
i would also check DNS console if it was DNS server and you
deinstalled it.
If it is demoted you can rename without problem in the domain.
hmmmmm... well, I've tried renaming computers in the domain before and
I wasn't able to. I had to disjoin them first, reboot, change the
name, reboot, join the domain, and reboot again. Was it maybe because
I was logged onto them within the domain rather than to the local PC?

Adprep has to be run before promoting the first 2003 DC on the schema
master.- Hide quoted text -

Yes, I would already have done this when I left the "old" ccentre2 in
the forest and moved the FSMO roles, etc to it but in my scenario, I
take this box out and replace it with the "old" ccentre1 box which is
still running Win2000 server (and will remain to do so) and wouldn't I
have to run adprep, etc against it then?



.

Relevant Pages

  • Re: No DC in Active Directory
    ... I still show no computers or DCs in AD Computers and Users on Srvr1 and they ... The primary DC points to itself as the DNS. ... The second server ... the first server now shows no DCs in the Active Directory ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client computer internet connection problems
    ... subnet, Default Gateway, correct DNS entry/ies). ... his TCP/IP Configuration settings then he is not going to be able to join ... O*N*L*Y the internal DNS Server IP Address..... ... join the computers to my server domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharing a drive on my computer with others
    ... SBS 2003 needs to manage DNS and really likes to manage DHCP, ... You need to use the wizards on the SBS server to get it all working properly. ... I can't ping any of the computers within the domain. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Error adding computers to domain
    ... > add Windows 2000 computers to a domain. ... > all because that function isn't necessary on that server. ... While not required by the server, the clients would certainly see a benefit. ... ever use an ISP's DNS server. ...
    (microsoft.public.win2000.advanced_server)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)