New server and Exchange 2007

  • Thread starter Thread starter ats@jbex
  • Start date Start date
A

ats@jbex

Guest
I am looking to put a new Domain Controller onto my network and am looking
for advice/tutorials/step by step instructions even to add teh server and
transfer all teh jobs from it to the new one i.e. DHCP, DNS etc.

I am also looking to put a new Exchange 2007 box in to replace my current
Exchange 2003 box. I am looking for specs for the server and for the best
method of setting it up and transferring mailboxes etc to it.

Once these jobs are both done, I need to completely remove the 2 current
servers from teh domain. Again, I need some instructions on this as well.

TIA
--
ats@jbex

All the power's in the hands
Of people rich enough to buy it
While we walk the street
Too chicken to even try it

The Clash - White Riot
 
Re: New server and Exchange 2007

Hello allen@allenjones.NOSPAM.co.PLEASE.uk,

Let's do it on 2 parts, first domain upgrade to new server:

Part1:

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

- 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

- run adprep /forestprep and adprep /domainprep from the 2003 installation
disk against the 2000 server, with an account that is member of the Schema
admins, to upgrade the schema to the new version

- 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 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

Part2:
Exchange should NOT be installed on a Domain controller:
http://technet.microsoft.com/en-us/library/aa997407.aspx

For upgrading:
http://support.microsoft.com/kb/555854

http://technet.microsoft.com/en-us/library/aa996719.aspx

http://technet.microsoft.com/en-us/library/bb124008(EXCHG.80).aspx


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

> I am looking to put a new Domain Controller onto my network and am
> looking for advice/tutorials/step by step instructions even to add teh
> server and transfer all teh jobs from it to the new one i.e. DHCP, DNS
> etc.
>
> I am also looking to put a new Exchange 2007 box in to replace my
> current Exchange 2003 box. I am looking for specs for the server and
> for the best method of setting it up and transferring mailboxes etc to
> it.
>
> Once these jobs are both done, I need to completely remove the 2
> current servers from teh domain. Again, I need some instructions on
> this as well.
>
> TIA
>
> All the power's in the hands
> Of people rich enough to buy it
> While we walk the street
> Too chicken to even try it
> The Clash - White Riot
>
 
Re: New server and Exchange 2007

On Tue, 17 Jun 2008 20:50:55 +0000 (UTC), Meinolf Weber wrote:

> Hello allen@allenjones.NOSPAM.co.PLEASE.uk,
>
> Let's do it on 2 parts, first domain upgrade to new server:
>
> Part1:
>
> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
>
> - 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
>
> - run adprep /forestprep and adprep /domainprep from the 2003 installation
> disk against the 2000 server, with an account that is member of the Schema
> admins, to upgrade the schema to the new version
>
> - 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 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
>
> Part2:
> Exchange should NOT be installed on a Domain controller:
> http://technet.microsoft.com/en-us/library/aa997407.aspx
>
> For upgrading:
> http://support.microsoft.com/kb/555854
>
> http://technet.microsoft.com/en-us/library/aa996719.aspx
>
> http://technet.microsoft.com/en-us/library/bb124008(EXCHG.80).aspx
>
>
> 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
>
>> I am looking to put a new Domain Controller onto my network and am
>> looking for advice/tutorials/step by step instructions even to add teh
>> server and transfer all teh jobs from it to the new one i.e. DHCP, DNS
>> etc.
>>
>> I am also looking to put a new Exchange 2007 box in to replace my
>> current Exchange 2003 box. I am looking for specs for the server and
>> for the best method of setting it up and transferring mailboxes etc to
>> it.
>>
>> Once these jobs are both done, I need to completely remove the 2
>> current servers from teh domain. Again, I need some instructions on
>> this as well.
>>
>> TIA
>>
>> All the power's in the hands
>> Of people rich enough to buy it
>> While we walk the street
>> Too chicken to even try it
>> The Clash - White Riot
>>


Thanks for this. I have printed a hard copy of it for when I need to get
started.
--
ats@jbex

Those who died are justified, for wearing the badge, they're the chosen
whites
You justify those that died by wearing the badge, they're the chosen whites

Rage Against The Machine - Killing In The Name
 
Back
Top