Solved

Splitting out Domain from SBS 2003

Posted on 2009-07-15
3
246 Views
Last Modified: 2012-05-07
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
0
Comment
Question by:Brizo
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 24857828
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
 

Author Comment

by:Brizo
ID: 24857933
Am wanting to goto seperate domains for different offices.

0
 
LVL 96

Accepted Solution

by:
Lee W, MVP earned 500 total points
ID: 24861444
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

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Know what services you can and cannot, should and should not combine on your server.
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
Suggested Courses

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question