Re: Adding SBS 2003 to an existing Win2003 AD domain with another AD domain controller
- From: "Leonid S. Knyshov" <lknyshov@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Mar 2006 15:53:47 -0800
<sjanderson1@xxxxxxxxx> wrote in message
news:1142637404.659643.60150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
My disclaimer - I'm not a Windows or networking guru. I'm more of a
SQL and business applications guru, but got "volunteered" into this
mission by my boss. So if the following is newbie in nature for SBS,
you'll know why.
My goals are to:
1) Move the SQL databases for our other business apps and CRM to the
new SBS
2) Move Exchange to the SBS since the old Exchange box that predates my
involvement does not have a RAID array.
Lots of questions - one answer that you've already found.
http://support.microsoft.com/default.aspx?scid=kb;en-us;884453
Before you do this, however, ask yourself if SBS is the best choice. You
have a very significant investment in CALs for Exchange and Win2003 already.
Those CALs will be essentially wasted money as soon as you let SBS take
over.
I do not believe that SBS is an appropriate choice for this network given
your scenario. Obtain a refund from Dell for that license or call it lesson
learned.
My approach would be:
1. Obtain Windows Server 2003 volume license (to make things easier...)
2. Install a new instance of Exchange on it and join it to the existing
organization. I specifically do not recommend making it a domain controller.
As you will be migrating to it from the old machine and thus transferring
that Exchange instance license, it doesn't need a new license, provided that
the old machine is decommissioned quickly.
3. Follow the published procedure to move data from old Exchange (replicate
public folders, and use the move mailbox wizard, pretty much) and
decommission old Exchange. http://support.microsoft.com/kb/822931/en-us
This approach is far less intrusive than converting to SBS and frankly SBS
is not a good idea for your network.
If you want to move SQL databases to the new Exchange server, it depends on
its load. I'd throw them on a dedicated server. You can add another instance
of SQL server on another server that will share your existing SQL CALs,
unless you are using the per-processor licensing. If you have a very high
powered machine, then it may make sense to add some more SQL instances to
the box.
Structure the array as RAID1 for system and translogs, RAID1 or RAID10 for
Exchange/SQL data
Do install Exchange SP2 to get higher Exchange store limits and lots of
other improvements.
--
Leonid S. Knyshov, CEO
Crashproof Solutions, LLC - http://www.crashproofsolutions.com
MCP Exchange 2003/Small Business Server 2003, CCNA, SCSA 8, NCIE
Microsoft Small Business Specialist Partner
.
- Follow-Ups:
- References:
- Prev by Date: Re: sbs2003 lost TCPIP !!
- Next by Date: SBS 2003 Standard to Premium Upgrade -- HELP!!
- Previous by thread: Adding SBS 2003 to an existing Win2003 AD domain with another AD domain controller
- Next by thread: Re: Adding SBS 2003 to an existing Win2003 AD domain with another AD domain controller
- Index(es):
Relevant Pages
|
