Windows Server 2003 for Small Business Server 2003

There are two flavors of SBS 2003, Standard and Premium and the difference between those two platforms is that Premium contains ISA Server 2000, SQL Server 2000, and Front Page 2003.  They both contain the basic 2003 Server platform with Sharepoint and Exchange.

You will love SBS 2003 as an integrated platform to run all these applications rather than to have six different services running one one or more boxes, the wizards make this a snap to setup.  You should be up and running with the OEM version in about 15 minutes.

You are correct in that the SBS 2003 box can be the ONLY domain controller in the Forest, that's why it's called "Small" Business Server for company with up to 50 PC's and a hard limit of 75.

There are only two new versions of SBS 2003 and neither can have additional domain controllers in the forest but can support as many other non-DC servers as you wish to add.  I have spent a great deal of time with this platform this year and wouldn't trade the product for anything MS has.

Message Edited by jmwills on 08-24-2004 09:18 PM

Ok..., does it means that I would have to choose Windows Server 2003 rather than SBS 2003 to manage several distincts companies (=domains) on the same server ...?

...and quid of the version I have (Windows server 2003 for small server business) compared to the SBS 2003 SE, is this version exists really ?

 

Thank you

Hi,

 

Thanks for your response...but it seems that a 3dr versions exists with restrictions / SBS 2003 (http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/generalfaq.mspx)...

and this version couldn't manage several domains, that which I would need to manage several disctincts companies (<> domains) on the same server.

 

Thank you for your help.

 

 

You are confusing one prduct with two names, Windows Server 2003 for Small Business IS Small Business Server 2003 and yes you will need multiple copies of Windows Server 2003 in orders to control multiple domains.

No, I said SBS 2003 can be the only Domain Control in the forest.  You can have other servers, they just CAN NOT BE Domain Controllers.

It is possible that I make full with confusions on many sujes because I begin on Windows server 2003... and it is far from being easy !

For SBS 2003 and Windows Server 2003 for Small Business Server 2003, if there are same versions, It's OK for me...nevertheless on the MS site they appeared as differents (?)

 

To answer to my need, you said that, even with Windows server 2003, only 1 server can't manage  two roots domains ?

Hi,

To be sure to reach the aimed objective, here is the summary of my need : to be able to share applications, peripherals, centralized messaging / fax, centralized back-ups within a network managed by a server which can accomodate several differents companies.

The main purpose is to be able to manage, without too much complexity, two different legal structures (with different domain namies and separate messaging), sharing certain material (printers / fax / scanner / back-ups, ...) and software (multi-companies accounting software, centralized fax, centralized back-ups, certain contacts of phone book, ...) resources managed by a centralized distribution over multi-companies.

In that case, which OS agrees best ?

Finally, if SBS 2003 and Windows server 2003 for Small Business Server are the same product, what are the limitations mentioned (and reproduced hereafter) by Microsoft on its US site (http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/generalfaq.mpsx) for Windows server 2003 for Small Business Server?

"Q : What is Windows server 2003 for Small Business Server ?

A : Windows server 2003 for Small Business Server is designed for partners who want to deliver a server solution based on Windows Server 2003 as part of their product offering. It provides the same version of Windows Server 2003 that is used by Windows Small Business Server 2003, but it has none of the added features included in the standard edition or premium edition of Windows Small Business Server 2003.

Windows server 2003 for Small Business Server has the following restrictions :

• Only one computer in a domain can be running Windows server 2003 for Small Business Server.
• Windows server 2003 for Small Business Server must be the root of the Active directory forest.
• Windows server 2003 for Small Business Server cannot trust any other domains.
• A Windows server 2003 for Small Business Server domain cannot have any child domains.
• Each additionnal server must have a Windows server 2003 for Small Business Server client access licence (CAL). You can use CALs for each user or for each device."

Thank You

You are quoting the differences between the Standard and Premium Editon of SBS 2K3.  There are only two flavors, period.

To accomplish what you want, you will need to go with Server 2003.  Do you want to share between the two domains or separately?

Hi,

"You are quoting the differences between the Standard and Premium Editon of SBS 2K3.  There are only two flavors, period."

In this case, what does it means "(Windows Server 2003 for Small Business Server 2003) ...but it has none of the added features included in the standard edition or premium edition of Windows Small Business Server 2003." ?

"To accomplish what you want, you will need to go with Server 2003.  Do you want to share between the two domains or separately?"

Both. I would like that these domains are separated because they are different legal structures (www.companyA.com and www.companyB.com) but I would also like to manage them together because they have to share common resources (muti-companyaccounting Software, fax, back-ups, certain contacts of the phone book).

Furthermore if I evolve towards Windows Server on 2003, which softwares I have to add to have all the features which I had on SBS on 2003 ?

Finally, does it exists bridges to change from SBS 2003 to Server 2003 or it is necessary to re-pay a full Server 2003 ?

 

Thank you

The document on this page should be on interest to you:

http://www.microsoft.com/windowsserver2003/sbs/evaluation/reviewerguide.mspx

 

Where are you getting these terms? 

You can manage both domains remotely as the administrator and users from either Doamin could log into the other domain as long as they are authenticated, they will just have to be using the other domain name.  Example you have user #1 on Domain A who wants to use resources on Domain B.  He will have to log off Domian A and log into Domain B.  Or possibly a third way would use this screnario and have a third domain for all user to share documents but theta would require two ISP connections at one of the locations.

The beauty of SBS is that you can share documents thru team sites (share poitn sites) and restrict access as needed.  Fax documents can be directed to certain shared folders, etc.  How many users on each site?  I would be willing to help for a fee.

Let me run this scenario by one of my mentors.

You can see the external interface of my server here:  www.carolinacomputers.us

 

Message Edited by jmwills on 08-25-2004 01:32 PM

What do you mean by 3 & 2 Post offices?  How many users per site becasue there is a limit to the number of users SBS can support.  If you are thinking of some Linux based system, the upfront may be attractive but there is no way Linux can compete with the ease of setup of SBS, unless you are a total Geek.

How many users on each site ?

I would have of to begin there : the first company of 3 post offices, the second of 2 post offices ! Both in the same office! With not enough means... But I wanted to make that cleanly and evolutionary, then I bought a server to recreate a professional environment (other than with XP) and to explore network features (applications / fax / messaging sharing, centralized back-ups, ...) ...but I am far from having arrived.

Okay nightbird this is the offical sccop.  One can run two SBS boxes, one for each domain, but usera from A will have to log off their desktop to log on actively into B.  They could however use Remote Web Workplace ti share resources and files.

The reason for this is that SBS was desgined not to have trust delegation built in its Active Directory.  No other way around this.