Splitting out Domain from SBS 2003

Hi

I am in the process of breaking out the SBS2003 domain i have into a bigger one due to growth etc. we have the following:

Small Business Server 2003
Dynamics CRM 4 on Same server
Exchange Server on same Server
SQL Server 2008 on same server

What i want to do is migrate to a full blown 2008 DC and seperate the exchange server and SQL as well.

This will also let me change to a different IP range as well.

Can anyone help with what will be needed to do this or how it is done as i have only used small business server and a few normal 2003 servers attached for other things

Cheers

Bri
BrizoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Why are you doing this?

Did you exceed the 75 user limit?

SBS supports up to 75 users.  You CAN have additional servers (Exchange MUST remain on the SBS server, but other than that, you can separate everything else if you want - you can even have additional domain controllers - The restriction is that SBS MUST be the FSMO MAster DC - that's it.)

If you are exceeding the 75 user limit then you should be looking at EBS - Essential Business Server which has a 250 user limit.

If you insist on moving away, you are best off getting the transition pack for SBS 2003 - this should equalize your licensing costs - otherwise, you have to start over and your entire licensing investment in SBS is essentially wasted money.  And keep in mind, if you move away from SBS, you lose certain things like the SBS Reporting and Remote Web Workplace.
0
BrizoAuthor Commented:
Am wanting to goto seperate domains for different offices.

0
Lee W, MVPTechnology and Business Process AdvisorCommented:
This is generally not a good idea.  Who advised you to do this?  Active Directory is designed NOT TO NEED multiple domains since you can group users and systems into OUs and delegate administrative control over those OUs.  By creating separate domains per site you are over complicating your network.  I would recommend simply putting a domain controller in each site and then define the sites in Sites and Services.  

Basically, you are:
*Increasing the complexity of the network, meaning you could have more network problems.
*Increasing the complexity increases the management costs
*Increasing the licensing costs since you no longer will have SBS discounts on things
*Increasing the difficulty of users connecting to you remotely since you will no longer have supported Remote Web Workplace setups.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.