Right direction on moving the Exchange DC to new DC

In our case, we have only 1 DC server 2003 that also holds the exchange 2003.
We plan to separate into two boxes, one is PDC, one is just Exchange. The
domain name will need to be the same but on the different subnet. What is
the best way to migrate with the minimum of downtime?

Creating a BDC first
Move FSMO to the BDC
Uninstall the Exchange
Demote the PDC??

Thanks,

Mike

Hello MK,

!!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

Small info at the beginning, since w2k there is no longer a PDC/BDC all DC's
are the same and can do the same. The difference are the 5 FSMO roles, but
they can be hold from any existing domain controller.

New Exchange:
- Install the new machine as a member server in your existing domain

- configure a fixed ip and set the preferred DNS server to the old DNS server
only

- install Exchange as Additional exchange server in the same exchange site

- if this is done, you can move all to the new Exchange according to this:
http://support.microsoft.com/kb/822931/

- if the old Exchange is out, you can go on with the new DC or keep the old
server and just uninstall Exchange

- so you have a separate Exchange member server and the DC which is now just
the DC/DNS/GC

For the new DC:

- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)

- run replmon, dcdiag and netdiag on the old machine to check for errors,
if you have some post the complete output from the command here or solve
them first

- Install the new machine as a member server in your existing domain

- configure a fixed ip and set the preferred DNS server to the old DNS server
only

- run dcpromo and follow the wizard to add the 2003 server to an existing
domain

- if you are prompted for DNS configuration choose Yes (also possible that
no DNS preparation occur), then install DNS after the reboot

- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they
appear

- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag on both domain controllers

- if you have no errors, make the new server Global catalog server, open
Active directory Sites and Services and then double-click sitename, double-click
Servers, click your domain controller, right-click NTDS Settings, and then
click Properties, on the General tab, click to select the Global catalog
check box (http://support.microsoft.com/?id=313994)

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

- you can see in the event viewer (Directrory service) that the roles are
transferred, also give it some time

- reconfigure the DNS configuration on your NIC of the 2003 server, preferred
DNS itself, secondary the old one

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473

Demoting the old DC (if needed)

- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC

- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok

- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again

- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever


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

> In our case, we have only 1 DC server 2003 that also holds the
> exchange 2003. We plan to separate into two boxes, one is PDC, one is
> just Exchange. The domain name will need to be the same but on the
> different subnet. What is the best way to migrate with the minimum of
> downtime?
>
> Creating a BDC first
> Move FSMO to the BDC
> Uninstall the Exchange
> Demote the PDC??
> Thanks,
>
> Mike
>

Thank you for the great input.
We have full backup of shadow copy and the information store everyday.

Back to one of the points that you mentioned;
- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC

Is there way to make reconfig once for all to everyone from the centra
point, or is it possible for the client not to notice the changes/differences?




"Meinolf Weber" wrote:

> Hello MK,
>
> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
>
> Small info at the beginning, since w2k there is no longer a PDC/BDC all DC's
> are the same and can do the same. The difference are the 5 FSMO roles, but
> they can be hold from any existing domain controller.
>
> New Exchange:
> - Install the new machine as a member server in your existing domain
>
> - configure a fixed ip and set the preferred DNS server to the old DNS server
> only
>
> - install Exchange as Additional exchange server in the same exchange site
>
> - if this is done, you can move all to the new Exchange according to this:
> http://support.microsoft.com/kb/822931/
>
> - if the old Exchange is out, you can go on with the new DC or keep the old
> server and just uninstall Exchange
>
> - so you have a separate Exchange member server and the DC which is now just
> the DC/DNS/GC
>
> For the new DC:
>
> - On the old server open DNS management console and check that you are running
> Active directory integrated zone (easier for replication, if you have more
> then one DNS server)
>
> - run replmon, dcdiag and netdiag on the old machine to check for errors,
> if you have some post the complete output from the command here or solve
> them first
>
> - Install the new machine as a member server in your existing domain
>
> - configure a fixed ip and set the preferred DNS server to the old DNS server
> only
>
> - run dcpromo and follow the wizard to add the 2003 server to an existing
> domain
>
> - if you are prompted for DNS configuration choose Yes (also possible that
> no DNS preparation occur), then install DNS after the reboot
>
> - for DNS give the server time for replication, at least 15 minutes. Because
> you use Active directory integrated zones it will automatically replicate
> the zones to the new server. Open DNS management console to check that they
> appear
>
> - if the new machine is domain controller and DNS server run again replmon,
> dcdiag and netdiag on both domain controllers
>
> - if you have no errors, make the new server Global catalog server, open
> Active directory Sites and Services and then double-click sitename, double-click
> Servers, click your domain controller, right-click NTDS Settings, and then
> click Properties, on the General tab, click to select the Global catalog
> check box (http://support.microsoft.com/?id=313994)
>
> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)
>
> - you can see in the event viewer (Directrory service) that the roles are
> transferred, also give it some time
>
> - reconfigure the DNS configuration on your NIC of the 2003 server, preferred
> DNS itself, secondary the old one
>
> - if you use DHCP do not forget to reconfigure the scope settings to point
> to the new installed DNS server
>
> - export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473
>
> Demoting the old DC (if needed)
>
> - reconfigure your clients/servers that they not longer point to the old
> DC/DNS server on the NIC
>
> - to be sure that everything runs fine, disconnect the old DC from the network
> and check with clients and servers the connectivity, logon and also with
> one client a restart to see that everything is ok
>
> - then run dcpromo to demote the old DC, if it works fine the machine will
> move from the DC's OU to the computers container, where you can delete it
> by hand. Can be that you got an error during demoting at the beginning, then
> uncheck the Global catalog on that DC and try again
>
> - check the DNS management console, that all entries from the machine are
> disappeared or delete them by hand if the machine is off the network for ever
>
>
> 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
>
> > In our case, we have only 1 DC server 2003 that also holds the
> > exchange 2003. We plan to separate into two boxes, one is PDC, one is
> > just Exchange. The domain name will need to be the same but on the
> > different subnet. What is the best way to migrate with the minimum of
> > downtime?
> >
> > Creating a BDC first
> > Move FSMO to the BDC
> > Uninstall the Exchange
> > Demote the PDC??
> > Thanks,
> >
> > Mike
> >
>
>
>

Hello MK,

Do you use DHCP or fixed ip's? For DHCP you just have to change the scope
options, fixed ip's you have to change by hand or with a script.

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

> Thank you for the great input.
> We have full backup of shadow copy and the information store
> everyday.
> Back to one of the points that you mentioned; - reconfigure your
> clients/servers that they not longer point to the old DC/DNS server on
> the NIC
>
> Is there way to make reconfig once for all to everyone from the centra
> point, or is it possible for the client not to notice the
> changes/differences?
>
> "Meinolf Weber" wrote:
>
>> Hello MK,
>>
>> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
>>
>> Small info at the beginning, since w2k there is no longer a PDC/BDC
>> all DC's are the same and can do the same. The difference are the 5
>> FSMO roles, but they can be hold from any existing domain controller.
>>
>> New Exchange:
>> - Install the new machine as a member server in your existing domain
>> - configure a fixed ip and set the preferred DNS server to the old
>> DNS server only
>>
>> - install Exchange as Additional exchange server in the same exchange
>> site
>>
>> - if this is done, you can move all to the new Exchange according to
>> this: http://support.microsoft.com/kb/822931/
>>
>> - if the old Exchange is out, you can go on with the new DC or keep
>> the old server and just uninstall Exchange
>>
>> - so you have a separate Exchange member server and the DC which is
>> now just the DC/DNS/GC
>>
>> For the new DC:
>>
>> - On the old server open DNS management console and check that you
>> are running Active directory integrated zone (easier for replication,
>> if you have more then one DNS server)
>>
>> - run replmon, dcdiag and netdiag on the old machine to check for
>> errors, if you have some post the complete output from the command
>> here or solve them first
>>
>> - Install the new machine as a member server in your existing domain
>>
>> - configure a fixed ip and set the preferred DNS server to the old
>> DNS server only
>>
>> - run dcpromo and follow the wizard to add the 2003 server to an
>> existing domain
>>
>> - if you are prompted for DNS configuration choose Yes (also possible
>> that no DNS preparation occur), then install DNS after the reboot
>>
>> - for DNS give the server time for replication, at least 15 minutes.
>> Because you use Active directory integrated zones it will
>> automatically replicate the zones to the new server. Open DNS
>> management console to check that they appear
>>
>> - if the new machine is domain controller and DNS server run again
>> replmon, dcdiag and netdiag on both domain controllers
>>
>> - if you have no errors, make the new server Global catalog server,
>> open Active directory Sites and Services and then double-click
>> sitename, double-click Servers, click your domain controller,
>> right-click NTDS Settings, and then click Properties, on the General
>> tab, click to select the Global catalog check box
>> (http://support.microsoft.com/?id=313994)
>>
>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>> (http://support.microsoft.com/kb/324801)
>>
>> - you can see in the event viewer (Directrory service) that the roles
>> are transferred, also give it some time
>>
>> - reconfigure the DNS configuration on your NIC of the 2003 server,
>> preferred DNS itself, secondary the old one
>>
>> - if you use DHCP do not forget to reconfigure the scope settings to
>> point to the new installed DNS server
>>
>> - export and import of DHCP database (if needed)
>> http://support.microsoft.com/kb/325473
>>
>> Demoting the old DC (if needed)
>>
>> - reconfigure your clients/servers that they not longer point to the
>> old DC/DNS server on the NIC
>>
>> - to be sure that everything runs fine, disconnect the old DC from
>> the network and check with clients and servers the connectivity,
>> logon and also with one client a restart to see that everything is ok
>>
>> - then run dcpromo to demote the old DC, if it works fine the machine
>> will move from the DC's OU to the computers container, where you can
>> delete it by hand. Can be that you got an error during demoting at
>> the beginning, then uncheck the Global catalog on that DC and try
>> again
>>
>> - check the DNS management console, that all entries from the machine
>> are disappeared or delete them by hand if the machine is off the
>> network for ever
>>
>> 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
>>> In our case, we have only 1 DC server 2003 that also holds the
>>> exchange 2003. We plan to separate into two boxes, one is PDC, one
>>> is just Exchange. The domain name will need to be the same but on
>>> the different subnet. What is the best way to migrate with the
>>> minimum of downtime?
>>>
>>> Creating a BDC first
>>> Move FSMO to the BDC
>>> Uninstall the Exchange
>>> Demote the PDC??
>>> Thanks,
>>> Mike
>>>

Ps. Is it possible to use the same Exchange name for the new one.

"mk" wrote:

> Thank you for the great input.
> We have full backup of shadow copy and the information store everyday.
>
> Back to one of the points that you mentioned;
> - reconfigure your clients/servers that they not longer point to the old
> DC/DNS server on the NIC
>
> Is there way to make reconfig once for all to everyone from the centra
> point, or is it possible for the client not to notice the changes/differences?
>
>
>
>
> "Meinolf Weber" wrote:
>
> > Hello MK,
> >
> > !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
> >
> > Small info at the beginning, since w2k there is no longer a PDC/BDC all DC's
> > are the same and can do the same. The difference are the 5 FSMO roles, but
> > they can be hold from any existing domain controller.
> >
> > New Exchange:
> > - Install the new machine as a member server in your existing domain
> >
> > - configure a fixed ip and set the preferred DNS server to the old DNS server
> > only
> >
> > - install Exchange as Additional exchange server in the same exchange site
> >
> > - if this is done, you can move all to the new Exchange according to this:
> > http://support.microsoft.com/kb/822931/
> >
> > - if the old Exchange is out, you can go on with the new DC or keep the old
> > server and just uninstall Exchange
> >
> > - so you have a separate Exchange member server and the DC which is now just
> > the DC/DNS/GC
> >
> > For the new DC:
> >
> > - On the old server open DNS management console and check that you are running
> > Active directory integrated zone (easier for replication, if you have more
> > then one DNS server)
> >
> > - run replmon, dcdiag and netdiag on the old machine to check for errors,
> > if you have some post the complete output from the command here or solve
> > them first
> >
> > - Install the new machine as a member server in your existing domain
> >
> > - configure a fixed ip and set the preferred DNS server to the old DNS server
> > only
> >
> > - run dcpromo and follow the wizard to add the 2003 server to an existing
> > domain
> >
> > - if you are prompted for DNS configuration choose Yes (also possible that
> > no DNS preparation occur), then install DNS after the reboot
> >
> > - for DNS give the server time for replication, at least 15 minutes. Because
> > you use Active directory integrated zones it will automatically replicate
> > the zones to the new server. Open DNS management console to check that they
> > appear
> >
> > - if the new machine is domain controller and DNS server run again replmon,
> > dcdiag and netdiag on both domain controllers
> >
> > - if you have no errors, make the new server Global catalog server, open
> > Active directory Sites and Services and then double-click sitename, double-click
> > Servers, click your domain controller, right-click NTDS Settings, and then
> > click Properties, on the General tab, click to select the Global catalog
> > check box (http://support.microsoft.com/?id=313994)
> >
> > - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)
> >
> > - you can see in the event viewer (Directrory service) that the roles are
> > transferred, also give it some time
> >
> > - reconfigure the DNS configuration on your NIC of the 2003 server, preferred
> > DNS itself, secondary the old one
> >
> > - if you use DHCP do not forget to reconfigure the scope settings to point
> > to the new installed DNS server
> >
> > - export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473
> >
> > Demoting the old DC (if needed)
> >
> > - reconfigure your clients/servers that they not longer point to the old
> > DC/DNS server on the NIC
> >
> > - to be sure that everything runs fine, disconnect the old DC from the network
> > and check with clients and servers the connectivity, logon and also with
> > one client a restart to see that everything is ok
> >
> > - then run dcpromo to demote the old DC, if it works fine the machine will
> > move from the DC's OU to the computers container, where you can delete it
> > by hand. Can be that you got an error during demoting at the beginning, then
> > uncheck the Global catalog on that DC and try again
> >
> > - check the DNS management console, that all entries from the machine are
> > disappeared or delete them by hand if the machine is off the network for ever
> >
> >
> > 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
> >
> > > In our case, we have only 1 DC server 2003 that also holds the
> > > exchange 2003. We plan to separate into two boxes, one is PDC, one is
> > > just Exchange. The domain name will need to be the same but on the
> > > different subnet. What is the best way to migrate with the minimum of
> > > downtime?
> > >
> > > Creating a BDC first
> > > Move FSMO to the BDC
> > > Uninstall the Exchange
> > > Demote the PDC??
> > > Thanks,
> > >
> > > Mike
> > >
> >
> >
> >

Hello MK,

You can not run 2 computers the same time with the same name. And for exchange/outlook
there is no need. The clients will normally switch to the new Exchange without
any reconfiguration or problem.

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

> Ps. Is it possible to use the same Exchange name for the new one.
>
> "mk" wrote:
>
>> Thank you for the great input.
>> We have full backup of shadow copy and the information store
>> everyday.
>> Back to one of the points that you mentioned; - reconfigure your
>> clients/servers that they not longer point to the old DC/DNS server
>> on the NIC
>>
>> Is there way to make reconfig once for all to everyone from the
>> centra point, or is it possible for the client not to notice the
>> changes/differences?
>>
>> "Meinolf Weber" wrote:
>>
>>> Hello MK,
>>>
>>> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
>>>
>>> Small info at the beginning, since w2k there is no longer a PDC/BDC
>>> all DC's are the same and can do the same. The difference are the 5
>>> FSMO roles, but they can be hold from any existing domain
>>> controller.
>>>
>>> New Exchange:
>>> - Install the new machine as a member server in your existing domain
>>> - configure a fixed ip and set the preferred DNS server to the old
>>> DNS server only
>>>
>>> - install Exchange as Additional exchange server in the same
>>> exchange site
>>>
>>> - if this is done, you can move all to the new Exchange according to
>>> this: http://support.microsoft.com/kb/822931/
>>>
>>> - if the old Exchange is out, you can go on with the new DC or keep
>>> the old server and just uninstall Exchange
>>>
>>> - so you have a separate Exchange member server and the DC which is
>>> now just the DC/DNS/GC
>>>
>>> For the new DC:
>>>
>>> - On the old server open DNS management console and check that you
>>> are running Active directory integrated zone (easier for
>>> replication, if you have more then one DNS server)
>>>
>>> - run replmon, dcdiag and netdiag on the old machine to check for
>>> errors, if you have some post the complete output from the command
>>> here or solve them first
>>>
>>> - Install the new machine as a member server in your existing domain
>>>
>>> - configure a fixed ip and set the preferred DNS server to the old
>>> DNS server only
>>>
>>> - run dcpromo and follow the wizard to add the 2003 server to an
>>> existing domain
>>>
>>> - if you are prompted for DNS configuration choose Yes (also
>>> possible that no DNS preparation occur), then install DNS after the
>>> reboot
>>>
>>> - for DNS give the server time for replication, at least 15 minutes.
>>> Because you use Active directory integrated zones it will
>>> automatically replicate the zones to the new server. Open DNS
>>> management console to check that they appear
>>>
>>> - if the new machine is domain controller and DNS server run again
>>> replmon, dcdiag and netdiag on both domain controllers
>>>
>>> - if you have no errors, make the new server Global catalog server,
>>> open Active directory Sites and Services and then double-click
>>> sitename, double-click Servers, click your domain controller,
>>> right-click NTDS Settings, and then click Properties, on the General
>>> tab, click to select the Global catalog check box
>>> (http://support.microsoft.com/?id=313994)
>>>
>>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>>> (http://support.microsoft.com/kb/324801)
>>>
>>> - you can see in the event viewer (Directrory service) that the
>>> roles are transferred, also give it some time
>>>
>>> - reconfigure the DNS configuration on your NIC of the 2003 server,
>>> preferred DNS itself, secondary the old one
>>>
>>> - if you use DHCP do not forget to reconfigure the scope settings to
>>> point to the new installed DNS server
>>>
>>> - export and import of DHCP database (if needed)
>>> http://support.microsoft.com/kb/325473
>>>
>>> Demoting the old DC (if needed)
>>>
>>> - reconfigure your clients/servers that they not longer point to the
>>> old DC/DNS server on the NIC
>>>
>>> - to be sure that everything runs fine, disconnect the old DC from
>>> the network and check with clients and servers the connectivity,
>>> logon and also with one client a restart to see that everything is
>>> ok
>>>
>>> - then run dcpromo to demote the old DC, if it works fine the
>>> machine will move from the DC's OU to the computers container, where
>>> you can delete it by hand. Can be that you got an error during
>>> demoting at the beginning, then uncheck the Global catalog on that
>>> DC and try again
>>>
>>> - check the DNS management console, that all entries from the
>>> machine are disappeared or delete them by hand if the machine is off
>>> the network for ever
>>>
>>> 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
>>>> In our case, we have only 1 DC server 2003 that also holds the
>>>> exchange 2003. We plan to separate into two boxes, one is PDC, one
>>>> is just Exchange. The domain name will need to be the same but on
>>>> the different subnet. What is the best way to migrate with the
>>>> minimum of downtime?
>>>>
>>>> Creating a BDC first
>>>> Move FSMO to the BDC
>>>> Uninstall the Exchange
>>>> Demote the PDC??
>>>> Thanks,
>>>> Mike
>>>>

We use DHCP. If we change the dns point to the new dc in the scope option,
do we need to change client's outlook setting to point out to the new
exchange server?

"Meinolf Weber" wrote:

> Hello MK,
>
> Do you use DHCP or fixed ip's? For DHCP you just have to change the scope
> options, fixed ip's you have to change by hand or with a script.
>
> 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
>
> > Thank you for the great input.
> > We have full backup of shadow copy and the information store
> > everyday.
> > Back to one of the points that you mentioned; - reconfigure your
> > clients/servers that they not longer point to the old DC/DNS server on
> > the NIC
> >
> > Is there way to make reconfig once for all to everyone from the centra
> > point, or is it possible for the client not to notice the
> > changes/differences?
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello MK,
> >>
> >> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
> >>
> >> Small info at the beginning, since w2k there is no longer a PDC/BDC
> >> all DC's are the same and can do the same. The difference are the 5
> >> FSMO roles, but they can be hold from any existing domain controller.
> >>
> >> New Exchange:
> >> - Install the new machine as a member server in your existing domain
> >> - configure a fixed ip and set the preferred DNS server to the old
> >> DNS server only
> >>
> >> - install Exchange as Additional exchange server in the same exchange
> >> site
> >>
> >> - if this is done, you can move all to the new Exchange according to
> >> this: http://support.microsoft.com/kb/822931/
> >>
> >> - if the old Exchange is out, you can go on with the new DC or keep
> >> the old server and just uninstall Exchange
> >>
> >> - so you have a separate Exchange member server and the DC which is
> >> now just the DC/DNS/GC
> >>
> >> For the new DC:
> >>
> >> - On the old server open DNS management console and check that you
> >> are running Active directory integrated zone (easier for replication,
> >> if you have more then one DNS server)
> >>
> >> - run replmon, dcdiag and netdiag on the old machine to check for
> >> errors, if you have some post the complete output from the command
> >> here or solve them first
> >>
> >> - Install the new machine as a member server in your existing domain
> >>
> >> - configure a fixed ip and set the preferred DNS server to the old
> >> DNS server only
> >>
> >> - run dcpromo and follow the wizard to add the 2003 server to an
> >> existing domain
> >>
> >> - if you are prompted for DNS configuration choose Yes (also possible
> >> that no DNS preparation occur), then install DNS after the reboot
> >>
> >> - for DNS give the server time for replication, at least 15 minutes.
> >> Because you use Active directory integrated zones it will
> >> automatically replicate the zones to the new server. Open DNS
> >> management console to check that they appear
> >>
> >> - if the new machine is domain controller and DNS server run again
> >> replmon, dcdiag and netdiag on both domain controllers
> >>
> >> - if you have no errors, make the new server Global catalog server,
> >> open Active directory Sites and Services and then double-click
> >> sitename, double-click Servers, click your domain controller,
> >> right-click NTDS Settings, and then click Properties, on the General
> >> tab, click to select the Global catalog check box
> >> (http://support.microsoft.com/?id=313994)
> >>
> >> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
> >> (http://support.microsoft.com/kb/324801)
> >>
> >> - you can see in the event viewer (Directrory service) that the roles
> >> are transferred, also give it some time
> >>
> >> - reconfigure the DNS configuration on your NIC of the 2003 server,
> >> preferred DNS itself, secondary the old one
> >>
> >> - if you use DHCP do not forget to reconfigure the scope settings to
> >> point to the new installed DNS server
> >>
> >> - export and import of DHCP database (if needed)
> >> http://support.microsoft.com/kb/325473
> >>
> >> Demoting the old DC (if needed)
> >>
> >> - reconfigure your clients/servers that they not longer point to the
> >> old DC/DNS server on the NIC
> >>
> >> - to be sure that everything runs fine, disconnect the old DC from
> >> the network and check with clients and servers the connectivity,
> >> logon and also with one client a restart to see that everything is ok
> >>
> >> - then run dcpromo to demote the old DC, if it works fine the machine
> >> will move from the DC's OU to the computers container, where you can
> >> delete it by hand. Can be that you got an error during demoting at
> >> the beginning, then uncheck the Global catalog on that DC and try
> >> again
> >>
> >> - check the DNS management console, that all entries from the machine
> >> are disappeared or delete them by hand if the machine is off the
> >> network for ever
> >>
> >> 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
> >>> In our case, we have only 1 DC server 2003 that also holds the
> >>> exchange 2003. We plan to separate into two boxes, one is PDC, one
> >>> is just Exchange. The domain name will need to be the same but on
> >>> the different subnet. What is the best way to migrate with the
> >>> minimum of downtime?
> >>>
> >>> Creating a BDC first
> >>> Move FSMO to the BDC
> >>> Uninstall the Exchange
> >>> Demote the PDC??
> >>> Thanks,
> >>> Mike
> >>>
>
>
>

Hello MK,

When i moved my exchange to a new server some month ago it goes automatically
to the new server.

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

> We use DHCP. If we change the dns point to the new dc in the scope
> option, do we need to change client's outlook setting to point out to
> the new exchange server?
>
> "Meinolf Weber" wrote:
>
>> Hello MK,
>>
>> Do you use DHCP or fixed ip's? For DHCP you just have to change the
>> scope options, fixed ip's you have to change by hand or with a
>> script.
>>
>> 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
>>> Thank you for the great input.
>>> We have full backup of shadow copy and the information store
>>> everyday.
>>> Back to one of the points that you mentioned; - reconfigure your
>>> clients/servers that they not longer point to the old DC/DNS server
>>> on
>>> the NIC
>>> Is there way to make reconfig once for all to everyone from the
>>> centra point, or is it possible for the client not to notice the
>>> changes/differences?
>>>
>>> "Meinolf Weber" wrote:
>>>
>>>> Hello MK,
>>>>
>>>> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU
>>>> DATA/MACHINE!!!
>>>>
>>>> Small info at the beginning, since w2k there is no longer a PDC/BDC
>>>> all DC's are the same and can do the same. The difference are the 5
>>>> FSMO roles, but they can be hold from any existing domain
>>>> controller.
>>>>
>>>> New Exchange:
>>>> - Install the new machine as a member server in your existing
>>>> domain
>>>> - configure a fixed ip and set the preferred DNS server to the old
>>>> DNS server only
>>>> - install Exchange as Additional exchange server in the same
>>>> exchange site
>>>>
>>>> - if this is done, you can move all to the new Exchange according
>>>> to this: http://support.microsoft.com/kb/822931/
>>>>
>>>> - if the old Exchange is out, you can go on with the new DC or keep
>>>> the old server and just uninstall Exchange
>>>>
>>>> - so you have a separate Exchange member server and the DC which is
>>>> now just the DC/DNS/GC
>>>>
>>>> For the new DC:
>>>>
>>>> - On the old server open DNS management console and check that you
>>>> are running Active directory integrated zone (easier for
>>>> replication, if you have more then one DNS server)
>>>>
>>>> - run replmon, dcdiag and netdiag on the old machine to check for
>>>> errors, if you have some post the complete output from the command
>>>> here or solve them first
>>>>
>>>> - Install the new machine as a member server in your existing
>>>> domain
>>>>
>>>> - configure a fixed ip and set the preferred DNS server to the old
>>>> DNS server only
>>>>
>>>> - run dcpromo and follow the wizard to add the 2003 server to an
>>>> existing domain
>>>>
>>>> - if you are prompted for DNS configuration choose Yes (also
>>>> possible that no DNS preparation occur), then install DNS after the
>>>> reboot
>>>>
>>>> - for DNS give the server time for replication, at least 15
>>>> minutes. Because you use Active directory integrated zones it will
>>>> automatically replicate the zones to the new server. Open DNS
>>>> management console to check that they appear
>>>>
>>>> - if the new machine is domain controller and DNS server run again
>>>> replmon, dcdiag and netdiag on both domain controllers
>>>>
>>>> - if you have no errors, make the new server Global catalog server,
>>>> open Active directory Sites and Services and then double-click
>>>> sitename, double-click Servers, click your domain controller,
>>>> right-click NTDS Settings, and then click Properties, on the
>>>> General tab, click to select the Global catalog check box
>>>> (http://support.microsoft.com/?id=313994)
>>>>
>>>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>>>> (http://support.microsoft.com/kb/324801)
>>>>
>>>> - you can see in the event viewer (Directrory service) that the
>>>> roles are transferred, also give it some time
>>>>
>>>> - reconfigure the DNS configuration on your NIC of the 2003 server,
>>>> preferred DNS itself, secondary the old one
>>>>
>>>> - if you use DHCP do not forget to reconfigure the scope settings
>>>> to point to the new installed DNS server
>>>>
>>>> - export and import of DHCP database (if needed)
>>>> http://support.microsoft.com/kb/325473
>>>> Demoting the old DC (if needed)
>>>>
>>>> - reconfigure your clients/servers that they not longer point to
>>>> the old DC/DNS server on the NIC
>>>>
>>>> - to be sure that everything runs fine, disconnect the old DC from
>>>> the network and check with clients and servers the connectivity,
>>>> logon and also with one client a restart to see that everything is
>>>> ok
>>>>
>>>> - then run dcpromo to demote the old DC, if it works fine the
>>>> machine will move from the DC's OU to the computers container,
>>>> where you can delete it by hand. Can be that you got an error
>>>> during demoting at the beginning, then uncheck the Global catalog
>>>> on that DC and try again
>>>>
>>>> - check the DNS management console, that all entries from the
>>>> machine are disappeared or delete them by hand if the machine is
>>>> off the network for ever
>>>>
>>>> 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
>>>>> In our case, we have only 1 DC server 2003 that also holds the
>>>>> exchange 2003. We plan to separate into two boxes, one is PDC, one
>>>>> is just Exchange. The domain name will need to be the same but on
>>>>> the different subnet. What is the best way to migrate with the
>>>>> minimum of downtime?
>>>>>
>>>>> Creating a BDC first
>>>>> Move FSMO to the BDC
>>>>> Uninstall the Exchange
>>>>> Demote the PDC??
>>>>> Thanks,
>>>>> Mike

Nice.. Thanks!

"Meinolf Weber" wrote:

> Hello MK,
>
> When i moved my exchange to a new server some month ago it goes automatically
> to the new server.
>
> 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
>
> > We use DHCP. If we change the dns point to the new dc in the scope
> > option, do we need to change client's outlook setting to point out to
> > the new exchange server?
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello MK,
> >>
> >> Do you use DHCP or fixed ip's? For DHCP you just have to change the
> >> scope options, fixed ip's you have to change by hand or with a
> >> script.
> >>
> >> 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
> >>> Thank you for the great input.
> >>> We have full backup of shadow copy and the information store
> >>> everyday.
> >>> Back to one of the points that you mentioned; - reconfigure your
> >>> clients/servers that they not longer point to the old DC/DNS server
> >>> on
> >>> the NIC
> >>> Is there way to make reconfig once for all to everyone from the
> >>> centra point, or is it possible for the client not to notice the
> >>> changes/differences?
> >>>
> >>> "Meinolf Weber" wrote:
> >>>
> >>>> Hello MK,
> >>>>
> >>>> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU
> >>>> DATA/MACHINE!!!
> >>>>
> >>>> Small info at the beginning, since w2k there is no longer a PDC/BDC
> >>>> all DC's are the same and can do the same. The difference are the 5
> >>>> FSMO roles, but they can be hold from any existing domain
> >>>> controller.
> >>>>
> >>>> New Exchange:
> >>>> - Install the new machine as a member server in your existing
> >>>> domain
> >>>> - configure a fixed ip and set the preferred DNS server to the old
> >>>> DNS server only
> >>>> - install Exchange as Additional exchange server in the same
> >>>> exchange site
> >>>>
> >>>> - if this is done, you can move all to the new Exchange according
> >>>> to this: http://support.microsoft.com/kb/822931/
> >>>>
> >>>> - if the old Exchange is out, you can go on with the new DC or keep
> >>>> the old server and just uninstall Exchange
> >>>>
> >>>> - so you have a separate Exchange member server and the DC which is
> >>>> now just the DC/DNS/GC
> >>>>
> >>>> For the new DC:
> >>>>
> >>>> - On the old server open DNS management console and check that you
> >>>> are running Active directory integrated zone (easier for
> >>>> replication, if you have more then one DNS server)
> >>>>
> >>>> - run replmon, dcdiag and netdiag on the old machine to check for
> >>>> errors, if you have some post the complete output from the command
> >>>> here or solve them first
> >>>>
> >>>> - Install the new machine as a member server in your existing
> >>>> domain
> >>>>
> >>>> - configure a fixed ip and set the preferred DNS server to the old
> >>>> DNS server only
> >>>>
> >>>> - run dcpromo and follow the wizard to add the 2003 server to an
> >>>> existing domain
> >>>>
> >>>> - if you are prompted for DNS configuration choose Yes (also
> >>>> possible that no DNS preparation occur), then install DNS after the
> >>>> reboot
> >>>>
> >>>> - for DNS give the server time for replication, at least 15
> >>>> minutes. Because you use Active directory integrated zones it will
> >>>> automatically replicate the zones to the new server. Open DNS
> >>>> management console to check that they appear
> >>>>
> >>>> - if the new machine is domain controller and DNS server run again
> >>>> replmon, dcdiag and netdiag on both domain controllers
> >>>>
> >>>> - if you have no errors, make the new server Global catalog server,
> >>>> open Active directory Sites and Services and then double-click
> >>>> sitename, double-click Servers, click your domain controller,
> >>>> right-click NTDS Settings, and then click Properties, on the
> >>>> General tab, click to select the Global catalog check box
> >>>> (http://support.microsoft.com/?id=313994)
> >>>>
> >>>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
> >>>> (http://support.microsoft.com/kb/324801)
> >>>>
> >>>> - you can see in the event viewer (Directrory service) that the
> >>>> roles are transferred, also give it some time
> >>>>
> >>>> - reconfigure the DNS configuration on your NIC of the 2003 server,
> >>>> preferred DNS itself, secondary the old one
> >>>>
> >>>> - if you use DHCP do not forget to reconfigure the scope settings
> >>>> to point to the new installed DNS server
> >>>>
> >>>> - export and import of DHCP database (if needed)
> >>>> http://support.microsoft.com/kb/325473
> >>>> Demoting the old DC (if needed)
> >>>>
> >>>> - reconfigure your clients/servers that they not longer point to
> >>>> the old DC/DNS server on the NIC
> >>>>
> >>>> - to be sure that everything runs fine, disconnect the old DC from
> >>>> the network and check with clients and servers the connectivity,
> >>>> logon and also with one client a restart to see that everything is
> >>>> ok
> >>>>
> >>>> - then run dcpromo to demote the old DC, if it works fine the
> >>>> machine will move from the DC's OU to the computers container,
> >>>> where you can delete it by hand. Can be that you got an error
> >>>> during demoting at the beginning, then uncheck the Global catalog
> >>>> on that DC and try again
> >>>>
> >>>> - check the DNS management console, that all entries from the
> >>>> machine are disappeared or delete them by hand if the machine is
> >>>> off the network for ever
> >>>>
> >>>> 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
> >>>>> In our case, we have only 1 DC server 2003 that also holds the
> >>>>> exchange 2003. We plan to separate into two boxes, one is PDC, one
> >>>>> is just Exchange. The domain name will need to be the same but on
> >>>>> the different subnet. What is the best way to migrate with the
> >>>>> minimum of downtime?
> >>>>>
> >>>>> Creating a BDC first
> >>>>> Move FSMO to the BDC
> >>>>> Uninstall the Exchange
> >>>>> Demote the PDC??
> >>>>> Thanks,
> >>>>> Mike
>
>
>