Charlie,
Clients locate DC by using DNS so if you setup new DC with new name and IP
address clients would be able to find them using DNS server (of course DNS
IP address would have to stay the same or if you use DHCP you could even
change that without going to the clients).
Steps for the upgrade would be:
* prepare domain for Windows 2003 DC (adprep /forestprep and adprep
/domainprep)
* install Windows 2003 server and update it with all the latest updates.
Once patched up, join it to domain and run dcpromo on it. This will be first
Windows 2003 server in domain
* make sure that new Windows 2003 server is DNS server for your active
directory. Use Active Directory integrated zones
* move FSMO roles to Windows 2003 DC
* move any other services that you might have running on Windows 2000 server
* run DCPromo on Windows 2000 server. this will remove the AD service from
the server
* remove the server from the network
* install new Windows 2003 server on the network (with the name and IP that
you want). Patch it up and join it to domain
* run DCPromo on the server
* move the FSMO roles to this server
* make sure DNS is installed and configured to use Active Directory
integrated zones
* if necessary remove the temporary DC from the network
Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
http://support.microsoft.com/?id=255504
How To View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/default...uct=winsvr2003
Upgrading Windows 2000 Domains to Windows Server 2003 Domains
http://www.microsoft.com/resources/d...n_overview.asp
Mike
"Charlie" <(E-Mail Removed)> wrote in message
news:EEBEE4EB-CF28-406D-A048-(E-Mail Removed)...
>I need the same name and ip address because I have 200 clients that are
> pointing at that name and address and I don't have the time to change them
> over to the new DC right away.
> You're way of changing over to the new hardware sounds great! Thank you.
> Is
> there any thing on Microsofts web site that you know of that describes
> doing
> it that way.
>
> "Miha Pihler" wrote:
>
>> Hi Charlie,
>>
>> If you don't mind I have a question. Why do you need same name and IP
>> address of your DC? Company policy or some other reason?
>>
>> Ok. Here is what I would do. I would setup temporary DC named e.g.
>> DC-Temp1.
>> This could be Windows 2003 DC that you added according to the process of
>> upgrading domain. Now with this temporary DC on-line, you could remove
>> old
>> Windows 2000 DC. Now with removed Windows 2000 DC, you can either setup
>> new
>> Windows 2003 DC with same name and IP address as old Windows 2000 server
>> or
>> rename temporary DC and change it's IP address.
>> You can then repeat this process for all other DCs in your environment.
>>
>> How to remove Windows 2000 DC. Best this you can do is first run DCPromo
>> on
>> Windows 2000 and remove the active directory service from the server.
>> Once
>> this is done, you can simply disjoin the computer from domain (join it to
>> workgroup). Before you disjoin the computer from domain, make sure you
>> know
>> local administrator password or you will not be able to logon back to
>> Windows 2000.
>>
>> I hope this helps,
>>
>> Mike
>>
>> "Charlie" <(E-Mail Removed)> wrote in message
>> news:6A6A550C-0628-4E2B-8A19-(E-Mail Removed)...
>> >I have a windows 2000 network with several DCs running AD and one
>> >exchange
>> > server.
>> > I need to replace the old DCs with new machines and running windows
>> > 2003
>> > server. I need to use the same names and ip address on the new machines
>> > as
>> > were on the old machines. I also hope to pull AD in on the first new
>> > machine
>> > and then keep adding new machines.
>> > Can some one tell me where to find something about this on Microsofts
>> > web
>> > site?
>>
>>
>>
Similar Threads
Linear Mode
