Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Windows server 2003 on new hardware to replace Windows 2000 DC

Reply
Thread Tools Display Modes

Windows server 2003 on new hardware to replace Windows 2000 DC

 
 
Always Learning
Guest
Posts: n/a

 
      02-09-2005
Hello everyone,

Could someone help find a good read on replacing Windows 2000 Domain
Controller. I want to setup Windows server 2003 on a new Server and
eventually replace the older server currently the DC.

Current Environment:
We already have Windows 2003 server with Exchange 2003 in an existing
Windows 2000 Domain Controller.


Thanks in advance.
 
Reply With Quote
 
 
 
 
Miha Pihler [MVP]
Guest
Posts: n/a

 
      02-09-2005
Hi,

Microsoft has a good step-by-step guide on how to upgrade Windows 2000 to
Windows 2003 domain.

Upgrading Windows 2000 Domains to Windows Server 2003 Domains
http://www.microsoft.com/resources/d...n_overview.asp

In general, you have to prepare the forest and domain (adprep /forestprep
and adprep /domainprep) and then run a dcpromo on your new Windows 2003
server. After you finish these steps you will have Windows 2003 domain and
first Windows 2003 domain controller in your forest.

Pay special attention to this part of the guide...
Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in
Windows 2000 Forests That Contain Exchange 2000 Servers
http://support.microsoft.com/kb/314649

Before you remove Windows 2000 domain controller make sure that you move all
FSMO roles and global catalog to any new domain controller. Here is how:

Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
http://support.microsoft.com/kb/255504

How to view and transfer FSMO roles in Windows Server 2003
http://support.microsoft.com/?id=324801

How To Create or Move a Global Catalog in Windows 2000
http://support.microsoft.com/?kbid=313994

You will probably also want for your new server to be a DNS server for your
Active Directory domain. Since your new server will have new IP address, you
will have to do some reconfiguration of your client to point to new
preferred DNS server. If you have DHCP server setup, this shouldn't be a
problem. If you don't use DHCP server, you can still write a script that
will do this change for you on your clients.


I hope this helps,

--
Mike
Microsoft MVP - Windows Security


"Always Learning" <> wrote in
message news768E8F3-62CD-4B70-9677-...
> Hello everyone,
>
> Could someone help find a good read on replacing Windows 2000 Domain
> Controller. I want to setup Windows server 2003 on a new Server and
> eventually replace the older server currently the DC.
>
> Current Environment:
> We already have Windows 2003 server with Exchange 2003 in an existing
> Windows 2000 Domain Controller.
>
>
> Thanks in advance.



 
Reply With Quote
 
Scott Napolitan [MSFT]
Guest
Posts: n/a

 
      02-09-2005
Always Learning wrote:
> Hello everyone,
>
> Could someone help find a good read on replacing Windows 2000 Domain
> Controller. I want to setup Windows server 2003 on a new Server and
> eventually replace the older server currently the DC.
>
> Current Environment:
> We already have Windows 2003 server with Exchange 2003 in an existing
> Windows 2000 Domain Controller.
>
>
> Thanks in advance.

The easiest way to do this is to install the new server as a new DC in
the Domain and then simply decomission the old one whenever you want.
One thing to consider however is that your old DC will get almost no
traffic once the new one is installed.

--
Legal Disclaimer:
This posting is provided "AS IS" with no warranties, and confers no
rights. Use of included script samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm Please do not
send e-mail directly to this alias. This alias is for newsgroup purposes
only.
 
Reply With Quote
 
Always Learning
Guest
Posts: n/a

 
      02-09-2005
Thank you for your quick response. I have one more question. I already have
Windows server 2003 (not domain controller) and Exchange 2003 the same
server. So, I already ran forest and domain (adprep /forestprep and adprep
/domainprep) and I also ran the fix for the mangled attributes. Would I need
to run these steps again or bypass and run dcpromo.

> Hi,
>
> Microsoft has a good step-by-step guide on how to upgrade Windows 2000 to
> Windows 2003 domain.
>
> Upgrading Windows 2000 Domains to Windows Server 2003 Domains
> http://www.microsoft.com/resources/d...n_overview.asp
>
> In general, you have to prepare the forest and domain (adprep /forestprep
> and adprep /domainprep) and then run a dcpromo on your new Windows 2003
> server. After you finish these steps you will have Windows 2003 domain and
> first Windows 2003 domain controller in your forest.
>
> Pay special attention to this part of the guide...
> Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in
> Windows 2000 Forests That Contain Exchange 2000 Servers
> http://support.microsoft.com/kb/314649
>
> Before you remove Windows 2000 domain controller make sure that you move all
> FSMO roles and global catalog to any new domain controller. Here is how:
>
> Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
> http://support.microsoft.com/kb/255504
>
> How to view and transfer FSMO roles in Windows Server 2003
> http://support.microsoft.com/?id=324801
>
> How To Create or Move a Global Catalog in Windows 2000
> http://support.microsoft.com/?kbid=313994
>
> You will probably also want for your new server to be a DNS server for your
> Active Directory domain. Since your new server will have new IP address, you
> will have to do some reconfiguration of your client to point to new
> preferred DNS server. If you have DHCP server setup, this shouldn't be a
> problem. If you don't use DHCP server, you can still write a script that
> will do this change for you on your clients.
>
>
> I hope this helps,
>
> --
> Mike
> Microsoft MVP - Windows Security
>
>
> "Always Learning" <> wrote in
> message news768E8F3-62CD-4B70-9677-...
> > Hello everyone,
> >
> > Could someone help find a good read on replacing Windows 2000 Domain
> > Controller. I want to setup Windows server 2003 on a new Server and
> > eventually replace the older server currently the DC.
> >
> > Current Environment:
> > We already have Windows 2003 server with Exchange 2003 in an existing
> > Windows 2000 Domain Controller.
> >
> >
> > Thanks in advance.

>
>
>

 
Reply With Quote
 
Always Learning
Guest
Posts: n/a

 
      02-09-2005
Thanks. If I go this route what would happen to the current Active Directory
Users, groups, etc. Can you replicate from the exisit DC to the new DC?

"Scott Napolitan [MSFT]" wrote:

> Always Learning wrote:
> > Hello everyone,
> >
> > Could someone help find a good read on replacing Windows 2000 Domain
> > Controller. I want to setup Windows server 2003 on a new Server and
> > eventually replace the older server currently the DC.
> >
> > Current Environment:
> > We already have Windows 2003 server with Exchange 2003 in an existing
> > Windows 2000 Domain Controller.
> >
> >
> > Thanks in advance.

> The easiest way to do this is to install the new server as a new DC in
> the Domain and then simply decomission the old one whenever you want.
> One thing to consider however is that your old DC will get almost no
> traffic once the new one is installed.
>
> --
> Legal Disclaimer:
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Use of included script samples are subject to the terms
> specified at http://www.microsoft.com/info/cpyright.htm Please do not
> send e-mail directly to this alias. This alias is for newsgroup purposes
> only.
>

 
Reply With Quote
 
Miha Pihler [MVP]
Guest
Posts: n/a

 
      02-09-2005
> Thank you for your quick response. I have one more question. I already
> have
> Windows server 2003 (not domain controller) and Exchange 2003 the same
> server. So, I already ran forest and domain (adprep /forestprep and
> adprep
> /domainprep) and I also ran the fix for the mangled attributes. Would I
> need
> to run these steps again or bypass and run dcpromo.


If you already run adprep and the fix, then all you need to do is run
dcpromo and select add additional server to existing domain in the dcpromo
wizard.
All information will be replicated to your new domain controller. Still FSMO
roles will stay where they are until you move them. Also your new server
will not be a global catalog by default -- but you can change this manually.

Another task that you might want to do is move DNS zones. Best way to do
this is to configure them to be Active Directory Integrated (if they are not
already). This will make them replicate to all your domain controllers in
your domain.

--
Mike
Microsoft MVP - Windows Security

<snip>


 
Reply With Quote
 
Always Learning
Guest
Posts: n/a

 
      02-09-2005
Thanks for all your help!!!

"Always Learning" wrote:

> Hello everyone,
>
> Could someone help find a good read on replacing Windows 2000 Domain
> Controller. I want to setup Windows server 2003 on a new Server and
> eventually replace the older server currently the DC.
>
> Current Environment:
> We already have Windows 2003 server with Exchange 2003 in an existing
> Windows 2000 Domain Controller.
>
>
> Thanks in advance.

 
Reply With Quote
 
Always Learning
Guest
Posts: n/a

 
      02-09-2005
Thanks for all your help!!!

"Miha Pihler [MVP]" wrote:

> > Thank you for your quick response. I have one more question. I already
> > have
> > Windows server 2003 (not domain controller) and Exchange 2003 the same
> > server. So, I already ran forest and domain (adprep /forestprep and
> > adprep
> > /domainprep) and I also ran the fix for the mangled attributes. Would I
> > need
> > to run these steps again or bypass and run dcpromo.

>
> If you already run adprep and the fix, then all you need to do is run
> dcpromo and select add additional server to existing domain in the dcpromo
> wizard.
> All information will be replicated to your new domain controller. Still FSMO
> roles will stay where they are until you move them. Also your new server
> will not be a global catalog by default -- but you can change this manually.
>
> Another task that you might want to do is move DNS zones. Best way to do
> this is to configure them to be Active Directory Integrated (if they are not
> already). This will make them replicate to all your domain controllers in
> your domain.
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> <snip>
>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How could I do?? (updates) Corsair Windows 64 Bit 5 06-17-2007 03:57 PM
Bad_Pool_Caller Windows Server 4 06-04-2005 01:32 AM
Help! Removing Windows Server 2003 server from Windows 2000 Server domain! Trond A. Tømte Windows Server 2 02-09-2005 06:00 AM
Re: DHCP not working on Windows 2003 Server Joseph J. Hand Windows Server 1 10-08-2004 05:16 PM
Windows 2003 Server can't see members of Windows 2000 Domain Ronan Windows Server 0 06-17-2004 10:48 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59