Hello Jason,
The list sounds good for me. Personnaly i would also restart both DC's. And
for Exchange check the Recipients update service that your DC's still in
there after the reboot.
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
> Hi..
>
> I need to change my offices LAN Ipaddressing scheme from a
> 192.168.100.X subnet to a 172.17.19.X subnet. I was just wondering on
> the best order to make the changes. This will be done outside work
> hours with no clients on.
>
> We have 4 2003 servers and one NT4 Server. All on static IP adresses.
>
> server1 is a PDC running Wins/DNS/DHCP
> server2 is running exchange 2003 and ISA2000 in cached only mode
> server3 A file server and is also a domain controller
> server4 runs SQL2005 standard edition.
> Server5 NT4 Server
> I have already created a new DHCP scope for the clients.
>
> Does this sound ok.
>
> 1. Change static ip address including new dns server, wins server and
> gateway details of Servers 5 and 4 and 2 and shut them down.
> 2. Change the IP address details on the Server1 PDC
> Add new reserve lookup zone on PDC dns.
> Remove old reserve lookup zone on PDC dns
> Restart netlogon service.
> 3. Change the IP address details on Server 3 the other domain
> controller and
> restart netlogon service.
> 4. Start the other Servers.
> 5. Activate the new DHCP scope
> Does the above sound ok or is it best to restart the PDC and 2nd
> domain controller too ?
>
> I dont think the SQL or exchange server or ISA in cached mode will be
> effected really by the IP address change.
> thanks for any responses.