Solved

How to use only the Exchange component of SBS 2003 in an existing W2K Server domain?

Posted on 2007-11-20
3
208 Views
Last Modified: 2010-03-06
We currently have a Windows 2000 Server domain that is functioning well. However we are not running Exchange on that server. Through a recent acquisition a server running SBS 2003 is now available. We would like to use the Exchange only features of this server. Would setting it up on a separate domain be the most feasible solution or could we integrate it somehow into our existing 2000 network without changing our existing server and its roles?
0
Comment
Question by:michaelh60
3 Comments
 
LVL 104

Assisted Solution

by:Sembee
Sembee earned 250 total points
ID: 20321099
You can't use a trust with an SBS Server, so any kind of pass through authentication isn't going to work. Users will need to maintain two sets of usernames and passwords.

You could put the SBS Server in the existing domain, but you would have to move all domain roles to that new machine. You would also need to ensure that you have enough SBS CALs. Remember that SBS is hard limited to 75 users and that is hard enforced. Another option would be to purchase ea transition pack for SBS which turns it in to the full products and then introduce that in to the existing domain. Although for full feature set you need a Windows 2003 GC/DC (preferably on a separate machine - with Exchange on a member server).

Simon.
0
 
LVL 74

Assisted Solution

by:Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy earned 250 total points
ID: 20321129
You cannot just use a component of SBS 2003 without using the entire server as it was designed to be deployed, which is described here:  http://support.microsoft.com/kb/842690

You most definitely cannot set it up on a separate domain because SBS doesn't support trust relationships.  You also cannot integrate it into your existing Win2K network without changing your existing server's roles because the SBS is required to be the root of the domain forest and must hold all FSMO roles.  It also must provide your network's DNS and ideally DHCP.

Jeff
TechSoEasy

0
 

Accepted Solution

by:
michaelh60 earned 0 total points
ID: 20798397
Sorry I didn't file an update earlier.

I was able to get it to work. We maintain a separate ".local" domain with the same usernames and passwords as the main domain. DHCP and DNS are disabled and only exchange is running. My users are able to logon to the primary domain and when Outlook is started it points to the Exchange server and accesses e-mails etc. like it's supposed to. We've been running for two months now and it's great.

Thanks everyone for your advice and willingness to help.

Moderator: Please close this item.
0

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

743 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now