Re: How to bring SBS 2003 network into a Win2003 AD network?
From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] (sbradcpa_at_pacbell.net)
Date: 11/21/04
- Next message: attila: "Installing RAID 1"
- Previous message: Marina Roos [SBS-MVP]: "Re: Advice on the Pros and Cons of ISA"
- In reply to: Matt: "Re: How to bring SBS 2003 network into a Win2003 AD network?"
- Next in thread: Mark Mulvany MCT: "Re: How to bring SBS 2003 network into a Win2003 AD network?"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 21 Nov 2004 08:14:18 -0800
Make sure on that "two SBS servers" as SBS doesn't normally do that nor
like it.
Matt wrote:
> Chad A. Gross [SBS MVP] wrote:
>
>> Hi Matt -
>>
>> First - Company A has 30 users, and Company B has 15. At a combined
>> user base of 45 users, you're still within the SBS space, since we can
>> go up to 75 users. And 8 Servers for 30 users??? What on earth are
>> those users doing? :^)
>
>
> I'm still (and will continually be) learning. And, of course, I didn't
> design the network.
>
> Well, a majority of the users on Company A are using windows-based
> terminals over either RDP or ICA connections, thus we have two terminal
> servers to spread the load and to provide redundancy. I'm not really
> convinced we need as many servers as we have, but for now... 8-)
>
>> Second - Company B has two SBS servers? Are you 100% about this? Do
>> they have two locations with an SBS at each location?
>
>
> Company B has one location and two servers. Perhaps one isn't running
> everything.
>
>> Here's the skinny on SBS: It has a few product-specific limitations
>> that are in place to make sure that it is utilitzed by small
>> businesses, and not used as a departmental or branch-office server by
>> larger businesses. These limitations are:
>>
>> SBS *MUST* be the root of the AD Forest and hold all FSMO roles.
>> SBS only allows a single AD Domain (child domains aren't permitted
>> either).
>> All component applications (Windows, Exchange, SQL, ISA) must be
>> installed on a single server.
>> SBS allows a maximum of 75 users OR devices.
>
>
> I really won't be surprised if we surpass 75 users in the next couple of
> years.
>
>> SBS licensing is NOT for concurrent connections. A user or device
>> consumes a CAL when they first authenticate with the server, and
>> retain that CAL until such time that they will no longer have a future
>> need to authenticate with the server (e.g. user leaves the company or
>> device is decommissioned).
>>
>> We do have some benefits - a single SBS CAL includes access to all
>> component applications (Windows, Exchange & SQL). In addition, SBS
>> CALs are effectively Per Seat (even User CALs) in that a single SBS
>> CAL allows a client to access both the SBS and any member servers in
>> the SBS domain.
>
>
> Is this similar to per-user licensing in a 2003 AD?
>
>> The reason I asked about the two SBS servers, is because of the
>> restriction with SBS that it be the root of the AD Forest and hold all
>> FSMO roles. For this reason, you can't have two SBS servers in the
>> same domain.
>
>
> Ahhh. I must assume in our case that the older server is just a member
> server.
>
>> As for integrating this into your existing environment, there's no way
>> to join a previously set up SBS to an existing AD domain.
>
>
> I see. What about the Transition Pack that was(is?) available for SBS
> 2000 networks? If there is one for 2003, does that provide any kind of
> a path for joining to an existing AD domain?
>
> We can join an SBS
>
>> to an existing domain during the installation of SBS - but when
>> completed, it will still have to be the root of the AD forest & hold
>> all FSMO roles. Therefore, in order to join an SBS to your domain,
>> you'll have to reinstall the SBS - however, doing so will result in
>> the SBS being the top dog in your AD, and your entire LAN will be
>> subject to SBS licensing, meaning you'd have to acquire the
>> appropriate number of SBS CALs.
>
>
> If you don't want to do
>
>> this, then you'll have to just scrap SBS and acquire vanilla Windows
>> Server to load on those boxes.
>
>
> I see. Then we'd have to use exmerge and so forth to transfer mailboxes
> if we wanted to join Company B's network to ours.
>
>> I'm obviously not familiar with your organization or it's requirements
>> - but from where I'm sitting, it seems that 8 servers for 30 users is
>> a little bit of overkill (I've got a 30 user site that is just putting
>> in their second server for file/print duty, behind their current SBS).
>
>
> Well, we do have two 2k3 Web Edition servers mainly just acting as
> firewalls, VPN servers and running Sophos Mailmonitor on incoming mail.
> I'm not convinced it's necessary to have two separate boxes doing that
> duty. I'm doing what I can to get up the learning curve to find better
> ways of doing what we're doing.
>
> Also, one domain controller is quite old and does nothing but serve as a
> domain controller. Another box is rather underpowered and serves only
> as a print server. We plan to replace both of those boxes with one,
> consolidating those duties (and perhaps others, if it makes sense).
>
> When you consider that our two terminal servers each replace 8-10
> desktop machines, I think we're seeing a significant reduction in our
> support costs, considering the alternative. I see that we can run
> terminal servers in an SBS 2003 network, though.
>
> What if I wanted/(needed?) more than one server running Exchange? Or, a
> different server running SQL? Does an SBS 2003 network concentrate more
> potential points of failure in one box? I'm certainly open to
> considering that some of these questions/concerns may not be as
> important as they might seem.
>
> Depending on your
>
>> requirements, there is a very good chance that an SBS-based network
>> could be very beneficial to you, allow you to reduce the number of
>> servers you currently have in production, and lower your IT support
>> costs.
>
>
> I'm open to suggestions, so I appreciate your comments. If there's a
> book on the topic that I should read, I'm open to those suggestions as
> well.
>
> Matt
-- http://www.sbslinks.com/really.htm http://www.msmvps.com/bradley https://www.ecora.com/ecora/jump/pm99.asp
- Next message: attila: "Installing RAID 1"
- Previous message: Marina Roos [SBS-MVP]: "Re: Advice on the Pros and Cons of ISA"
- In reply to: Matt: "Re: How to bring SBS 2003 network into a Win2003 AD network?"
- Next in thread: Mark Mulvany MCT: "Re: How to bring SBS 2003 network into a Win2003 AD network?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
