Re: Windows 2003 Server Replacement Problems

Tech-Archive recommends: Fix windows errors by optimizing your registry


"dayusmc" <dayusmc.3pmevd@xxxxxxxxxxxxx> wrote in message news:dayusmc.3pmevd@xxxxxxxxxxxxxxxx

I only have 1 DC on the network (Except for the New one), It is Windows
2003 Enterprise Edition, I do have exchange installed on the current PDC
but I do not use it. I want to remove the Current PDC and promote the
new DC to PDC and than remove the old one. I have to go to the site to
get an ipconfig from the machines. So do I just build the new machine on
the network and join it to the domain like any other workstation? I
think that I am unsure of the little things that I have to do, like when
do I add the Domain Controller role to the new machine? If I run dcpromo
on the current PDC what will happen? Thanks for the input- I guess I
have to wait for the Captian untill I am done!! This is a Pain in the
ass!!!


--
dayusmc


It's not that bad. Hang in there.

If you only have the one, no problem.

Install Windows 2003 on the new server. Don;t bother joiing it to the domain.
Provide a static IP config to the new server
Make sure the DNS settings on the new server are only using the current DC.
Make sure on the current DC that it is only using itself for DNS. (no ISP DNS, please, just itself)
Make sure the current DC is not mutihomed.
Make sure the current AD domain name is not a single lable name (domain vs the required format of domain.net, domain.com, etc).
Install DNS on the new server. DO NOT add any zones. Leave it empty
Run dcpromo from a Run line.
Tell it this will be a replica DC to a current domain
Choose the current domain name
Go with the defaults for the rest of the options. Choose a restore password, you can use the current admin password
Once complete, restart
Make this DC a GC (in AD Sites and Services)
Go into IP properties, remove the 127.0.0.1 address
Make sure the current DC is still set as the first entry
Make the new server's IP as the second entry
Check DNS on the original sever.
Make sure the new server gets registered into the SRV records, A record and (same as parent) record.
Check ADUC, Domain Controllers OU to make sure an account exists for the new DC.
If you are currently using WINS, install WINS
Run Windows update to get it caught up. restart, Run again to get whatever is left over
Once restarted and all is ok..
Transfer all FSMO roles to the new DC (see instructions at http://support.microsoft.com/kb/324801)
Check ALL event logs making sure no errors on both servers.
Go into Sites and Services, and force a replication. Make sure no errors popup or in the event log.
On the new DC, change the DNS order so the new one is the first in the list now. Remove the old DC's IP
On the old DC, point to the new DC in DNS. Run ipconfig /registerdns, then restart the netlogon service.
Check to make sure no errors in the event logs.
Once satisfied, run dcromo on the old server. DO NOT choose "This is the Last DC in the Domain"
Restart when complete
After the restart, go into Sites and Services on the new DC and delete the old server name if you see it.
Check ADUC, Domain Controllers OU to make sure it was removed. Check Computers Container, and you should find it there.
If you do not use Exchange, NOW is the time to uninstall it. Go into Add/Remove to uninstall it.
You will more than likely prompt you for the original installation CD to completely remove it.

I would suggest to rebuild the old machine and install it as a replica DC. It is recommended for each domain to have a minimum of two DCs for fault tolerance. Once you promote it, make it a GC,.

If you still want Exchange, I would suggest to get a separate server to install it on. I usually pickup used servers off of eBay for dirt cheap. So if $200 - $300 is within budget, you can find a decent Dell 1850 rack dual Xeon 3.0 with a PERC4, 2 gigs Ram, pizza box. There are tower server equivalents. Matter of fact, I just setup two startup companies with 5 of these servers at each place. All under $1500.00. They work like a charm.

I hope that helps!

Ace

.

Relevant Pages

  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
    ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... you can check the version with "schupgr" in a command prompt. ...
    (microsoft.public.windows.server.setup)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... dynamic updates and create PTR records in DNS. ... tracking is easier from the server. ... I don't install dhcp on the servers, ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
    ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... and "netshell dhcp restore" command ...
    (microsoft.public.windows.server.setup)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... The only time I have seen the connectcomputer error you mentioned about DNS ... I don't install dhcp on the servers, ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)