New Server (Hardware Upgrade), SBS 2003 to SBS 2003 Same Domain Na

Hi, I am looking put a replacement server online for a hardware upgrade. I
want to use all of my existing licensing from the existing SBS 2003 server
and migrate all user accounts, exchange mailboxes, and SQL databases to the
new one. Ultimately, I want to keep the same domain name on the new box as
well. I am then going to pull the existing 2003 SBS server out of line
permanently. Can this be done? It is my understanding that you cannot have
2 domain controllers with the same domain name on the same network. I am
willing to configure the new server offline, but how will I migrate over if I
can't use the network?

Any help would be greatly appreciated.

Thank You,

Vinny

Hello vcapone,

As you said you can not have two domains with the exact same name. But for
the hardware change itself better post to:
microsoft.public.windows.server.sbs

There are the experts for SBS, because in SBS a lot is different.

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 am looking put a replacement server online for a hardware
> upgrade. I want to use all of my existing licensing from the existing
> SBS 2003 server and migrate all user accounts, exchange mailboxes, and
> SQL databases to the new one. Ultimately, I want to keep the same
> domain name on the new box as well. I am then going to pull the
> existing 2003 SBS server out of line permanently. Can this be done?
> It is my understanding that you cannot have 2 domain controllers with
> the same domain name on the same network. I am willing to configure
> the new server offline, but how will I migrate over if I can't use the
> network?
>
> Any help would be greatly appreciated.
>
> Thank You,
>
> Vinny
>

Hello Vcapone,
Yes, this is possible and you can have more than one domain controllers in
the same domain but you cannot have more than one domain controller with the
same name in a domain, each domain controller should have a unique name. So
your new server will have to get a different name if you decide to migrate
using the simple and probably the best way.

It is not always advisable to have AD and Exchange in the same server. But,
put that aside, here are some guidelines to help you migrate from one server
to the other. I am assuming your brand new server is windows server 2003 as
well.

**NB: Please Make sure you research your SQL Server compartibility with new
hardware before you begin migration**

1 - Prepare your new hardware, do RAID configuration as needed, install w2k3
OS.
2- Configure a fixed IP address and make sure DNS is pointing to the old
w2k3. Make show you can ping old server from new and vice versa and do
nslookup etc
3 - Start, run, type dcpromo and enter, promote server in existing domain,
if prompted select yes to make it a an ad integrated dns server as well.
4 -After server have been successfully promoted as a domain controller, give
it some time to complete initialization and replication. verify that server
is functioning properly as a domain controller by doing a dcdiag /q to look
for any errors, do a repadmin /showreps and look for any errors (this might
need for you to install w2k3 support tools which is also in the CD), do a
net share to make sure sysvol is now being shared etc.
5- Verify that DNS was properly installed in new server, open DNS console
and verify settings, forward lookup zones and comapre with old server, do
any adjustment as needed. If DNS is ok, change DNS of new server to point to
itself as primary dns, do nslookup etc to test.
6 -Transfer (NOT SEIZE) all 5 FSMO roles from old to new server and verify
that roles have been transfered
7 - Install and import DHCP database from old to new check that it was
success
8 - Install land migrate exchange from old to new. see steps and ideas here
http://windowsitpro.com/article/arti...ew-server.html
http://technet.microsoft.com/en-us/l.../bb124429.aspx
9 - If exchange migration is successful, power off old server for atleast a
week, make sure users are authenticating, and everything is working well
with new server
10 - Bring back old server online and decommission. run dcpromo and demote
server, remove from domain and shutdown



--
Isaac Oben [MCTIP:EA, MCSE]
"vcapone" <> wrote in message
news:4B68930D-25B8-4FFE-AEDC-...
> Hi, I am looking put a replacement server online for a hardware upgrade.
> I
> want to use all of my existing licensing from the existing SBS 2003 server
> and migrate all user accounts, exchange mailboxes, and SQL databases to
> the
> new one. Ultimately, I want to keep the same domain name on the new box
> as
> well. I am then going to pull the existing 2003 SBS server out of line
> permanently. Can this be done? It is my understanding that you cannot
> have
> 2 domain controllers with the same domain name on the same network. I am
> willing to configure the new server offline, but how will I migrate over
> if I
> can't use the network?
>
> Any help would be greatly appreciated.
>
> Thank You,
>
> Vinny

Thank you.

Will the following steps work for SBS? You stated that Exchange and AD
shouldn't be on the same box, but SBS has Exchange incorporated. STD Windows
2003 Server doesn't therefore leaving you that option.

One more thing. I'm sorry but the only thing I don't understand is the
statement FSMO roles.

Thank you.
Vinny

"Isaac Oben [MCITP,MCSE]" wrote:

> Hello Vcapone,
> Yes, this is possible and you can have more than one domain controllers in
> the same domain but you cannot have more than one domain controller with the
> same name in a domain, each domain controller should have a unique name. So
> your new server will have to get a different name if you decide to migrate
> using the simple and probably the best way.
>
> It is not always advisable to have AD and Exchange in the same server. But,
> put that aside, here are some guidelines to help you migrate from one server
> to the other. I am assuming your brand new server is windows server 2003 as
> well.
>
> **NB: Please Make sure you research your SQL Server compartibility with new
> hardware before you begin migration**
>
> 1 - Prepare your new hardware, do RAID configuration as needed, install w2k3
> OS.
> 2- Configure a fixed IP address and make sure DNS is pointing to the old
> w2k3. Make show you can ping old server from new and vice versa and do
> nslookup etc
> 3 - Start, run, type dcpromo and enter, promote server in existing domain,
> if prompted select yes to make it a an ad integrated dns server as well.
> 4 -After server have been successfully promoted as a domain controller, give
> it some time to complete initialization and replication. verify that server
> is functioning properly as a domain controller by doing a dcdiag /q to look
> for any errors, do a repadmin /showreps and look for any errors (this might
> need for you to install w2k3 support tools which is also in the CD), do a
> net share to make sure sysvol is now being shared etc.
> 5- Verify that DNS was properly installed in new server, open DNS console
> and verify settings, forward lookup zones and comapre with old server, do
> any adjustment as needed. If DNS is ok, change DNS of new server to point to
> itself as primary dns, do nslookup etc to test.
> 6 -Transfer (NOT SEIZE) all 5 FSMO roles from old to new server and verify
> that roles have been transfered
> 7 - Install and import DHCP database from old to new check that it was
> success
> 8 - Install land migrate exchange from old to new. see steps and ideas here
> http://windowsitpro.com/article/arti...ew-server.html
> http://technet.microsoft.com/en-us/l.../bb124429.aspx
> 9 - If exchange migration is successful, power off old server for atleast a
> week, make sure users are authenticating, and everything is working well
> with new server
> 10 - Bring back old server online and decommission. run dcpromo and demote
> server, remove from domain and shutdown
>
>
>
> --
> Isaac Oben [MCTIP:EA, MCSE]
> "vcapone" <> wrote in message
> news:4B68930D-25B8-4FFE-AEDC-...
> > Hi, I am looking put a replacement server online for a hardware upgrade.
> > I
> > want to use all of my existing licensing from the existing SBS 2003 server
> > and migrate all user accounts, exchange mailboxes, and SQL databases to
> > the
> > new one. Ultimately, I want to keep the same domain name on the new box
> > as
> > well. I am then going to pull the existing 2003 SBS server out of line
> > permanently. Can this be done? It is my understanding that you cannot
> > have
> > 2 domain controllers with the same domain name on the same network. I am
> > willing to configure the new server offline, but how will I migrate over
> > if I
> > can't use the network?
> >
> > Any help would be greatly appreciated.
> >
> > Thank You,
> >
> > Vinny
>
>

Hello Vcapone,
Like Meinolf said, you will get a better advise if you use the
microsoft.public.windows.server.sbs forum.
FSMO = Flexible Single Master Operations roles

--
Isaac Oben [MCTIP:EA, MCSE]
"vcapone" <> wrote in message
news:7C1D5BC2-68A7-4DD7-AF82-...
> Thank you.
>
> Will the following steps work for SBS? You stated that Exchange and AD
> shouldn't be on the same box, but SBS has Exchange incorporated. STD
> Windows
> 2003 Server doesn't therefore leaving you that option.
>
> One more thing. I'm sorry but the only thing I don't understand is the
> statement FSMO roles.
>
> Thank you.
> Vinny
>
> "Isaac Oben [MCITP,MCSE]" wrote:
>
>> Hello Vcapone,
>> Yes, this is possible and you can have more than one domain controllers
>> in
>> the same domain but you cannot have more than one domain controller with
>> the
>> same name in a domain, each domain controller should have a unique name.
>> So
>> your new server will have to get a different name if you decide to
>> migrate
>> using the simple and probably the best way.
>>
>> It is not always advisable to have AD and Exchange in the same server.
>> But,
>> put that aside, here are some guidelines to help you migrate from one
>> server
>> to the other. I am assuming your brand new server is windows server 2003
>> as
>> well.
>>
>> **NB: Please Make sure you research your SQL Server compartibility with
>> new
>> hardware before you begin migration**
>>
>> 1 - Prepare your new hardware, do RAID configuration as needed, install
>> w2k3
>> OS.
>> 2- Configure a fixed IP address and make sure DNS is pointing to the old
>> w2k3. Make show you can ping old server from new and vice versa and do
>> nslookup etc
>> 3 - Start, run, type dcpromo and enter, promote server in existing
>> domain,
>> if prompted select yes to make it a an ad integrated dns server as well.
>> 4 -After server have been successfully promoted as a domain controller,
>> give
>> it some time to complete initialization and replication. verify that
>> server
>> is functioning properly as a domain controller by doing a dcdiag /q to
>> look
>> for any errors, do a repadmin /showreps and look for any errors (this
>> might
>> need for you to install w2k3 support tools which is also in the CD), do a
>> net share to make sure sysvol is now being shared etc.
>> 5- Verify that DNS was properly installed in new server, open DNS console
>> and verify settings, forward lookup zones and comapre with old server, do
>> any adjustment as needed. If DNS is ok, change DNS of new server to point
>> to
>> itself as primary dns, do nslookup etc to test.
>> 6 -Transfer (NOT SEIZE) all 5 FSMO roles from old to new server and
>> verify
>> that roles have been transfered
>> 7 - Install and import DHCP database from old to new check that it was
>> success
>> 8 - Install land migrate exchange from old to new. see steps and ideas
>> here
>> http://windowsitpro.com/article/arti...ew-server.html
>> http://technet.microsoft.com/en-us/l.../bb124429.aspx
>> 9 - If exchange migration is successful, power off old server for atleast
>> a
>> week, make sure users are authenticating, and everything is working well
>> with new server
>> 10 - Bring back old server online and decommission. run dcpromo and
>> demote
>> server, remove from domain and shutdown
>>
>>
>>
>> --
>> Isaac Oben [MCTIP:EA, MCSE]
>> "vcapone" <> wrote in message
>> news:4B68930D-25B8-4FFE-AEDC-...
>> > Hi, I am looking put a replacement server online for a hardware
>> > upgrade.
>> > I
>> > want to use all of my existing licensing from the existing SBS 2003
>> > server
>> > and migrate all user accounts, exchange mailboxes, and SQL databases to
>> > the
>> > new one. Ultimately, I want to keep the same domain name on the new
>> > box
>> > as
>> > well. I am then going to pull the existing 2003 SBS server out of line
>> > permanently. Can this be done? It is my understanding that you cannot
>> > have
>> > 2 domain controllers with the same domain name on the same network. I
>> > am
>> > willing to configure the new server offline, but how will I migrate
>> > over
>> > if I
>> > can't use the network?
>> >
>> > Any help would be greatly appreciated.
>> >
>> > Thank You,
>> >
>> > Vinny
>>
>>

Hello Isaac Oben [MCITP,MCSE],

Maybe i missed something but the OP will install a new SBS server to the
domain. So he will have two SBS servers in one domain which is not possible
as far as i know.

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


> Hello Vcapone,
> Yes, this is possible and you can have more than one domain
> controllers in
> the same domain but you cannot have more than one domain controller
> with the
> same name in a domain, each domain controller should have a unique
> name. So
> your new server will have to get a different name if you decide to
> migrate
> using the simple and probably the best way.
> It is not always advisable to have AD and Exchange in the same server.
> But, put that aside, here are some guidelines to help you migrate from
> one server to the other. I am assuming your brand new server is
> windows server 2003 as well.
>
> **NB: Please Make sure you research your SQL Server compartibility
> with new hardware before you begin migration**
>
> 1 - Prepare your new hardware, do RAID configuration as needed,
> install w2k3
> OS.
> 2- Configure a fixed IP address and make sure DNS is pointing to the
> old
> w2k3. Make show you can ping old server from new and vice versa and do
> nslookup etc
> 3 - Start, run, type dcpromo and enter, promote server in existing
> domain,
> if prompted select yes to make it a an ad integrated dns server as
> well.
> 4 -After server have been successfully promoted as a domain
> controller, give
> it some time to complete initialization and replication. verify that
> server
> is functioning properly as a domain controller by doing a dcdiag /q to
> look
> for any errors, do a repadmin /showreps and look for any errors (this
> might
> need for you to install w2k3 support tools which is also in the CD),
> do a
> net share to make sure sysvol is now being shared etc.
> 5- Verify that DNS was properly installed in new server, open DNS
> console
> and verify settings, forward lookup zones and comapre with old server,
> do
> any adjustment as needed. If DNS is ok, change DNS of new server to
> point to
> itself as primary dns, do nslookup etc to test.
> 6 -Transfer (NOT SEIZE) all 5 FSMO roles from old to new server and
> verify
> that roles have been transfered
> 7 - Install and import DHCP database from old to new check that it was
> success
> 8 - Install land migrate exchange from old to new. see steps and ideas
> here
> http://windowsitpro.com/article/arti...-move-exchange
> -server-to-a-new-server.html
> http://technet.microsoft.com/en-us/l.../bb124429.aspx
> 9 - If exchange migration is successful, power off old server for
> atleast a
> week, make sure users are authenticating, and everything is working
> well
> with new server
> 10 - Bring back old server online and decommission. run dcpromo and
> demote
> server, remove from domain and shutdow

Meinolf,

Thanks for the clarification. I missed the SBS part.
--
Isaac Oben [MCTIP:EA, MCSE]

"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news: .com...
> Hello Isaac Oben [MCITP,MCSE],
>
> Maybe i missed something but the OP will install a new SBS server to the
> domain. So he will have two SBS servers in one domain which is not
> possible as far as i know.
>
> 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
>
>> Hello Vcapone,
>> Yes, this is possible and you can have more than one domain
>> controllers in
>> the same domain but you cannot have more than one domain controller
>> with the
>> same name in a domain, each domain controller should have a unique
>> name. So
>> your new server will have to get a different name if you decide to
>> migrate
>> using the simple and probably the best way.
>> It is not always advisable to have AD and Exchange in the same server.
>> But, put that aside, here are some guidelines to help you migrate from
>> one server to the other. I am assuming your brand new server is
>> windows server 2003 as well.
>>
>> **NB: Please Make sure you research your SQL Server compartibility
>> with new hardware before you begin migration**
>>
>> 1 - Prepare your new hardware, do RAID configuration as needed,
>> install w2k3
>> OS.
>> 2- Configure a fixed IP address and make sure DNS is pointing to the
>> old
>> w2k3. Make show you can ping old server from new and vice versa and do
>> nslookup etc
>> 3 - Start, run, type dcpromo and enter, promote server in existing
>> domain,
>> if prompted select yes to make it a an ad integrated dns server as
>> well.
>> 4 -After server have been successfully promoted as a domain
>> controller, give
>> it some time to complete initialization and replication. verify that
>> server
>> is functioning properly as a domain controller by doing a dcdiag /q to
>> look
>> for any errors, do a repadmin /showreps and look for any errors (this
>> might
>> need for you to install w2k3 support tools which is also in the CD),
>> do a
>> net share to make sure sysvol is now being shared etc.
>> 5- Verify that DNS was properly installed in new server, open DNS
>> console
>> and verify settings, forward lookup zones and comapre with old server,
>> do
>> any adjustment as needed. If DNS is ok, change DNS of new server to
>> point to
>> itself as primary dns, do nslookup etc to test.
>> 6 -Transfer (NOT SEIZE) all 5 FSMO roles from old to new server and
>> verify
>> that roles have been transfered
>> 7 - Install and import DHCP database from old to new check that it was
>> success
>> 8 - Install land migrate exchange from old to new. see steps and ideas
>> here
>> http://windowsitpro.com/article/arti...-move-exchange
>> -server-to-a-new-server.html
>> http://technet.microsoft.com/en-us/l.../bb124429.aspx
>> 9 - If exchange migration is successful, power off old server for
>> atleast a
>> week, make sure users are authenticating, and everything is working
>> well
>> with new server
>> 10 - Bring back old server online and decommission. run dcpromo and
>> demote
>> server, remove from domain and shutdown
>
>

Hello Vcapone,

Please disregard my below post. I missed your note that you have an SBS
which you need upgrade to another SBS. Only ONE SBS server can exist in the
same domain.

--
Isaac Oben [MCTIP:EA, MCSE]
"Isaac Oben [MCITP,MCSE]" <> wrote in message
news:%...
> Hello Vcapone,
> Yes, this is possible and you can have more than one domain controllers in
> the same domain but you cannot have more than one domain controller with
> the same name in a domain, each domain controller should have a unique
> name. So your new server will have to get a different name if you decide
> to migrate using the simple and probably the best way.
>
> It is not always advisable to have AD and Exchange in the same server.
> But,
> put that aside, here are some guidelines to help you migrate from one
> server
> to the other. I am assuming your brand new server is windows server 2003
> as
> well.
>
> **NB: Please Make sure you research your SQL Server compartibility with
> new hardware before you begin migration**
>
> 1 - Prepare your new hardware, do RAID configuration as needed, install
> w2k3
> OS.
> 2- Configure a fixed IP address and make sure DNS is pointing to the old
> w2k3. Make show you can ping old server from new and vice versa and do
> nslookup etc
> 3 - Start, run, type dcpromo and enter, promote server in existing domain,
> if prompted select yes to make it a an ad integrated dns server as well.
> 4 -After server have been successfully promoted as a domain controller,
> give
> it some time to complete initialization and replication. verify that
> server
> is functioning properly as a domain controller by doing a dcdiag /q to
> look
> for any errors, do a repadmin /showreps and look for any errors (this
> might
> need for you to install w2k3 support tools which is also in the CD), do a
> net share to make sure sysvol is now being shared etc.
> 5- Verify that DNS was properly installed in new server, open DNS console
> and verify settings, forward lookup zones and comapre with old server, do
> any adjustment as needed. If DNS is ok, change DNS of new server to point
> to
> itself as primary dns, do nslookup etc to test.
> 6 -Transfer (NOT SEIZE) all 5 FSMO roles from old to new server and verify
> that roles have been transfered
> 7 - Install and import DHCP database from old to new check that it was
> success
> 8 - Install land migrate exchange from old to new. see steps and ideas
> here
> http://windowsitpro.com/article/arti...ew-server.html
> http://technet.microsoft.com/en-us/l.../bb124429.aspx
> 9 - If exchange migration is successful, power off old server for atleast
> a
> week, make sure users are authenticating, and everything is working well
> with new server
> 10 - Bring back old server online and decommission. run dcpromo and demote
> server, remove from domain and shutdown
>
>
>
> --
> Isaac Oben [MCTIP:EA, MCSE]
> "vcapone" <> wrote in message
> news:4B68930D-25B8-4FFE-AEDC-...
>> Hi, I am looking put a replacement server online for a hardware upgrade.
>> I
>> want to use all of my existing licensing from the existing SBS 2003
>> server
>> and migrate all user accounts, exchange mailboxes, and SQL databases to
>> the
>> new one. Ultimately, I want to keep the same domain name on the new box
>> as
>> well. I am then going to pull the existing 2003 SBS server out of line
>> permanently. Can this be done? It is my understanding that you cannot
>> have
>> 2 domain controllers with the same domain name on the same network. I am
>> willing to configure the new server offline, but how will I migrate over
>> if I
>> can't use the network?
>>
>> Any help would be greatly appreciated.
>>
>> Thank You,
>>
>> Vinny
>

Hello Isaac Oben [MCITP,MCSE],

Have to correct myself, there is a way for moving to new hardware according
to this article:
http://technet.microsoft.com/en-us/l.../cc719896.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


> Hello Vcapone,
> Yes, this is possible and you can have more than one domain
> controllers in
> the same domain but you cannot have more than one domain controller
> with the
> same name in a domain, each domain controller should have a unique
> name. So
> your new server will have to get a different name if you decide to
> migrate
> using the simple and probably the best way.
> It is not always advisable to have AD and Exchange in the same server.
> But, put that aside, here are some guidelines to help you migrate from
> one server to the other. I am assuming your brand new server is
> windows server 2003 as well.
>
> **NB: Please Make sure you research your SQL Server compartibility
> with new hardware before you begin migration**
>
> 1 - Prepare your new hardware, do RAID configuration as needed,
> install w2k3
> OS.
> 2- Configure a fixed IP address and make sure DNS is pointing to the
> old
> w2k3. Make show you can ping old server from new and vice versa and do
> nslookup etc
> 3 - Start, run, type dcpromo and enter, promote server in existing
> domain,
> if prompted select yes to make it a an ad integrated dns server as
> well.
> 4 -After server have been successfully promoted as a domain
> controller, give
> it some time to complete initialization and replication. verify that
> server
> is functioning properly as a domain controller by doing a dcdiag /q to
> look
> for any errors, do a repadmin /showreps and look for any errors (this
> might
> need for you to install w2k3 support tools which is also in the CD),
> do a
> net share to make sure sysvol is now being shared etc.
> 5- Verify that DNS was properly installed in new server, open DNS
> console
> and verify settings, forward lookup zones and comapre with old server,
> do
> any adjustment as needed. If DNS is ok, change DNS of new server to
> point to
> itself as primary dns, do nslookup etc to test.
> 6 -Transfer (NOT SEIZE) all 5 FSMO roles from old to new server and
> verify
> that roles have been transfered
> 7 - Install and import DHCP database from old to new check that it was
> success
> 8 - Install land migrate exchange from old to new. see steps and ideas
> here
> http://windowsitpro.com/article/arti...-move-exchange
> -server-to-a-new-server.html
> http://technet.microsoft.com/en-us/l.../bb124429.aspx
> 9 - If exchange migration is successful, power off old server for
> atleast a
> week, make sure users are authenticating, and everything is working
> well
> with new server
> 10 - Bring back old server online and decommission. run dcpromo and
> demote
> server, remove from domain and shutdow

In news: .com,
Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>, posted the following:
> Hello Isaac Oben [MCITP,MCSE],
>
> Have to correct myself, there is a way for moving to new hardware
> according to this article:
> http://technet.microsoft.com/en-us/l.../cc719896.aspx
>


Meinolf,

Just to add, there's a swing migration method the following link outlines.
I've used this method twice successfully for customers.

SBSmigration.com - How Swing Migration WorksSwing Migration is a process to
accomplish either a version upgrade or server
www.sbsmigration.com/pages/64/

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer


For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.