<div>
@ Chris-Dent<br />
Thanks for the article and the heads up.<br />
I was wondering about the Domain Name issue, you explained that very precisely.<br />
<br />
@ RobWill<br />
SBS Migration is not what I was after, and therefore your explanations made sure I made the correct descision.<br />
<br />
Interestingly enough, I had a 20 min phone call (pre-sales technical expert) with a leading brand company, who said it would be a possible solution to my DR requirements....<br />
Anyway....I didn't believe him and I am glad that I &quot;asked the experts&quot;<br />
Thanks for understanding my issue and answering quickly.<br />
<br />
@RobWill - You are correct I am better off with the Server 2003 route, however I was trying to avoid the BANDWIDTH constraint that I have due to replication between the 2 sites.<br />
I think that is a new question and not an SBS issue.<br />
Many, Many thanks guys.<br />
Miff<br />

</div>


<div>
Thanks for your valued opinions.<br />
Miff
</div>


<div>
Thanks Miffanwee. Good luck with your project.<br />
Cheers !<br />
--Rob
</div>


<div>
<br />
Good luck Mif :)<br />
<br />
Chris<br />

</div>


<div>
<div class="content wysiwyg-content">
Hi experts.<br />
<br />
I have a requirement to join a Small Business Server to an existing DOMAIN.<br />
I understand the 50 User limit and this is fine, so I want to know the following...<br />
1) Is it ok to join a SBS server to an existing domain<br />
2) What type of replication takes place, bearing in mind it would be DOMAIN B (sbs) joining DOMAIN A server 2003 AD) obviously different Domain Names for each.<br />
3) Are there any pitfalls?<br />
<br />
My constraints are...<br />
1) BANDWIDTH between 2 sites for SBS and existing Domain is 2MEG MAX, no chance of upgrade because of distance from telephone exchange.<br />
2) I would also like to RESTORE Exchange 2003 (full Product) to the SBS in case of emergency.<br />
e.g. Domain A Exchange server 2003 onto SBS Domain Exchange product.<br />
<br />
Is number 2 even possible?<br />
<br />
Your thoughts greatly appreciated.<br />
I am aware that this is a loaded question (or 2) and I am happy to open another question if need be but I was trying to paint a bigger picture.<br />
Regards<br />
Miff<br />

</div>
</div>


Hi experts.

I have a requirement to join a Small Business Server to an existing DOMAIN.
I understand the 50 User limit and this is fine, so I want to know the following...
1) Is it ok to join a SBS server to an existing domain
2) What type of replication takes place, bearing in mind it would be DOMAIN B (sbs) joining DOMAIN A server 2003 AD) obviously different Domain Names for each.
3) Are there any pitfalls?

My constraints are...
1) BANDWIDTH between 2 sites for SBS and existing Domain is 2MEG MAX, no chance of upgrade because of distance from telephone exchange.
2) I would also like to RESTORE Exchange 2003 (full Product) to the SBS in case of emergency.
e.g. Domain A Exchange server 2003 onto SBS Domain Exchange product.

Is number 2 even possible?

Your thoughts greatly appreciated.
I am aware that this is a loaded question (or 2) and I am happy to open another question if need be but I was trying to paint a bigger picture.
Regards
Miff


Joining SBS to existing Domain

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).