Move Domain Controller to New Server - SBS 2003 to Standard 2003 x64

[Guest embj13@gmail.com]

Hello everyone,

 

I have a server currently setup that runs SBS 2003. I've built a new

server to replace the old one because it is about four years old, and

I wanted something that provided a little bit more reliability. So,

I've got the new server up and running with Server 2003 R2 Standard

x64 installed. What I'm wanting to do is completely migrate everything

over from SBS to the new server.

 

Here's what is already done:

I've got the new server running as a domain controller with the DNS

server already installed. It is currently receiving replicated

information from the SBS box. I've successfully installed Exchange

2007 on the new server and have gotten all of the mailboxes moved over

from SBS. As far as I know, everything dealing with Exchange is

working properly.

 

I've been doing a lot of reading around on various newsgroups and

forums about how to go about doing this. This is what has me confused;

I'm not sure how to go about decommissioning the SBS box as a domain

controller. I know that I need to transfer the FSMO roles over and

make the new server a global catalog before I can decommission the old

box. From instructions that I've found on Technet (http://

technet2.microsoft.com/windowsserver/en/library/b96e3f0a-

bf98-4a80-8718-dd80dc1071fd1033.mspx?mfr=true), I'm pretty sure about

how to go about moving those over to the new DC. The only thing that

I'm not sure about and really couldn't find any information on was how

to transfer DHCP over and at what point it should be done. In regards

to DNS, should I go ahead and set the SOA to the new server?

 

After all of that, there's still one other thing that comes into

play...ISA Server that's on the SBS box. How would it be affected?

Would I still be able to route everything through that box once

everything is moved over to the new DC?

 

After I get all of that done, I would like to get rid of ISA Server on

the SBS box, so I can get rid of that server in its entirety. I'd like

to install ISA Server 2006 on a virtual server (using VS 2005 R2). I

know this isn't the ideal way of having it, but it seems the most

logical without having to have a separate server. I know this is a big

task, but can anyone offer me any suggestions on how to go about doing

this?

 

Thanks.

[Guest Mathieu CHATEAU]

Re: Move Domain Controller to New Server - SBS 2003 to Standard 2003 x64

 

Hello,

 

you may check this too:

How to upgrade Small Business Server Domain Environment to regular Windows

2003 Domain

http://support.microsoft.com/kb/555073/en-us

or

http://www.sbsmigration.com/

 

For the DHCP, you can backup/restore from the MMC or use netsh

http://technet2.microsoft.com/WindowsServer/en/Library/df9ecef3-7d85-49e6-a2aa-ff84a5bd3a391033.mspx

dump

netsh dhcp server 192.168.0.1 dump > C:\Dhcp\Dhcpcfg.dmp

 

Installing ISA on another machine is good, a VM is ok if the network traffic

isn't too heavy. Will this VM being running on this new server ?

 

You will clean the dns after removing the SBS. Take care that all domain

members point to your new dns server before

 

--

Cordialement,

Mathieu CHATEAU

http://lordoftheping.blogspot.com

 

 

<embj13@gmail.com> wrote in message

news:1189481721.190386.168360@22g2000hsm.googlegroups.com...

> Hello everyone,

>

> I have a server currently setup that runs SBS 2003. I've built a new

> server to replace the old one because it is about four years old, and

> I wanted something that provided a little bit more reliability. So,

> I've got the new server up and running with Server 2003 R2 Standard

> x64 installed. What I'm wanting to do is completely migrate everything

> over from SBS to the new server.

>

> Here's what is already done:

> I've got the new server running as a domain controller with the DNS

> server already installed. It is currently receiving replicated

> information from the SBS box. I've successfully installed Exchange

> 2007 on the new server and have gotten all of the mailboxes moved over

> from SBS. As far as I know, everything dealing with Exchange is

> working properly.

>

> I've been doing a lot of reading around on various newsgroups and

> forums about how to go about doing this. This is what has me confused;

> I'm not sure how to go about decommissioning the SBS box as a domain

> controller. I know that I need to transfer the FSMO roles over and

> make the new server a global catalog before I can decommission the old

> box. From instructions that I've found on Technet (http://

> technet2.microsoft.com/windowsserver/en/library/b96e3f0a-

> bf98-4a80-8718-dd80dc1071fd1033.mspx?mfr=true), I'm pretty sure about

> how to go about moving those over to the new DC. The only thing that

> I'm not sure about and really couldn't find any information on was how

> to transfer DHCP over and at what point it should be done. In regards

> to DNS, should I go ahead and set the SOA to the new server?

>

> After all of that, there's still one other thing that comes into

> play...ISA Server that's on the SBS box. How would it be affected?

> Would I still be able to route everything through that box once

> everything is moved over to the new DC?

>

> After I get all of that done, I would like to get rid of ISA Server on

> the SBS box, so I can get rid of that server in its entirety. I'd like

> to install ISA Server 2006 on a virtual server (using VS 2005 R2). I

> know this isn't the ideal way of having it, but it seems the most

> logical without having to have a separate server. I know this is a big

> task, but can anyone offer me any suggestions on how to go about doing

> this?

>

> Thanks.

>

[Guest embj13@gmail.com]

Re: Move Domain Controller to New Server - SBS 2003 to Standard 2003 x64

 

On Sep 11, 2:29 am, "Mathieu CHATEAU" <gollum...@free.fr> wrote:

> Hello,

>

> you may check this too:

> How to upgrade Small Business ServerDomainEnvironment to regular Windows

> 2003Domainhttp://support.microsoft.com/kb/555073/en-us

> orhttp://www.sbsmigration.com/

>

> For the DHCP, you can backup/restore from the MMC or use netshhttp://technet2.microsoft.com/WindowsServer/en/Library/df9ecef3-7d85-...

> dump

> netsh dhcp server 192.168.0.1 dump > C:\Dhcp\Dhcpcfg.dmp

>

> Installing ISA on another machine is good, a VM is ok if the network traffic

> isn't too heavy. Will this VM being running on this new server ?

>

> You will clean the dns after removing the SBS. Take care that alldomain

> members point to your new dns server before

>

> --

> Cordialement,

> Mathieu CHATEAUhttp://lordoftheping.blogspot.com

>

> <emb...@gmail.com> wrote in message

>

> news:1189481721.190386.168360@22g2000hsm.googlegroups.com...

>

>

>

> > Hello everyone,

>

> > I have a server currently setup that runs SBS 2003. I've built a new

> > server to replace the old one because it is about four years old, and

> > I wanted something that provided a little bit more reliability. So,

> > I've got the new server up and running with Server 2003 R2 Standard

> > x64 installed. What I'm wanting to do is completely migrate everything

> > over from SBS to the new server.

>

> > Here's what is already done:

> > I've got the new server running as adomaincontrollerwith the DNS

> > server already installed. It is currently receiving replicated

> > information from the SBS box. I've successfully installed Exchange

> > 2007 on the new server and have gotten all of the mailboxes moved over

> > from SBS. As far as I know, everything dealing with Exchange is

> > working properly.

>

> > I've been doing a lot of reading around on various newsgroups and

> > forums about how to go about doing this. This is what has me confused;

> > I'm not sure how to go about decommissioning the SBS box as adomain

> >controller. I know that I need to transfer the FSMO roles over and

> > make the new server a global catalog before I candecommissionthe old

> > box. From instructions that I've found on Technet (http://

> > technet2.microsoft.com/windowsserver/en/library/b96e3f0a-

> > bf98-4a80-8718-dd80dc1071fd1033.mspx?mfr=true), I'm pretty sure about

> > how to go about moving those over to the new DC. The only thing that

> > I'm not sure about and really couldn't find any information on was how

> > to transfer DHCP over and at what point it should be done. In regards

> > to DNS, should I go ahead and set the SOA to the new server?

>

> > After all of that, there's still one other thing that comes into

> > play...ISA Server that's on the SBS box. How would it be affected?

> > Would I still be able to route everything through that box once

> > everything is moved over to the new DC?

>

> > After I get all of that done, I would like to get rid of ISA Server on

> > the SBS box, so I can get rid of that server in its entirety. I'd like

> > to install ISA Server 2006 on a virtual server (using VS 2005 R2). I

> > know this isn't the ideal way of having it, but it seems the most

> > logical without having to have a separate server. I know this is a big

> > task, but can anyone offer me any suggestions on how to go about doing

> > this?

>

> > Thanks.- Hide quoted text -

>

> - Show quoted text -

 

Thanks for your reply. I've read about the migration and transition

kits, but they come with some hefty price tags. I've already got

licenses for the other software through the MAPS that I subscribe to.

I've already shelled out about $800 for the components for the new

server, and that's about my ceiling. I may have to spend another $125

to upgrade to 4GB of RAM if 2GB won't cut it. I'm trying to wait it

out and see how well everything runs with only 2GB. It's not really

too much of a mission critical server, so if something screws up, it's

not the end of the world. It's just a home server that I run to host a

few email accounts, file shares, run a couple of web sites on, and use

as a firewall/router. There are only about 10 or so computers hooked

up to it, and they won't all be being used at the same time, so I

think ISA would probably run alright on VS.

 

I just got the DHCP server setup and authorized on the new server. I

already updated the DHCP scope options to point to the new server for

DNS/WINS, so all the clients should be set once their IPs are renewed.

I'm hoping that I'll be good to go from this point. I've got the WINS

server setup on the new one, and both are replicating between each

other. I'm guessing that once I've decommissioned the old DC, I'll be

able to just uninstall WINS on the old server and delete the

replication partner from the new one? I'm going to work on

transferring the FSMO roles over now and hope for the best.