Re: Transfer of user licenses from SBS to Enterprise
- From: "kj" <kj@xxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 09:13:40 -0700
"Femi" <Femi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8F7B9C86-0431-45F1-8EB0-322572B519C2@xxxxxxxxxxxxxxxx
Wow!!!
Thanks or that piece there!
Really motivating and thought provoking.
I actually had to re-think the resons behind this "upgrade" (downgrade by
ur
standards).
I the reasons behind this thought have been trashed out in your piece.
Poor server performnce which can be attributed to the quality of the
equipment. We have already made plans to upgrade the present hardware to
operate with 2 processors, and also increase the RAM from 512MB to 2GB.
I also plan to strip the SBS bare of everything except the exchange and
AD.
Another reason is my company has 4 sub-companies (4 domains) and we wanna
be
able to host all 4 domains (Email domains and AD domians) on the SBS. How
possible is this?
Not possible with SBS remaining in the picture. You will not be able to
create any additional AD domains while SBS remains.
You will need to either Transition Pack out of SBS to Standard Windows or
Migrate existing object to a new Forest and new domains.
If you have a NON OEM version of SBS2003 then you could Migrate to a new
"beefier" server more suited to your companies performance needs and keep
the benefits of SBS. Although the AD domains restriction still remain.
If your domain requirements are "security" related, then understand that
Microsoft now concedes that AD "Domains" are "management boundaries" and the
true "Security Boundary" is the Forest. So, you'd need four FORESTS to
completely isolate these companies from a security perspective. Likely
ridiculous to have four Forests for 45 users, but then so would four
Domains.
http://www.microsoft.com/technet/security/prodtech/windowsserver2003/w2003hg/s3sgch02.mspx
"The forest is the true security boundary of your network environment. This
guide recommends that you create separate forests to keep your environment
secure from potential compromise by administrators of other domains. This
approach also helps ensure that the compromise of one forest does not
automatically lead to the compromise of the entire enterprise.
A domain is a management boundary of Active Directory, not a security
boundary. With an organization of well-intentioned individuals, a domain
boundary will provide autonomous management of services and data within each
domain of the organization. Unfortunately, with regard to security,
isolation is not so simple to achieve. A domain, for example, will not
completely isolate an attack from a rogue domain administrator. This level
of separation can only be achieved at the forest level."
---
/kj
"SuperGumby [SBS MVP]" wrote:
which motivates me to ask:
Why is the OP moving away from SBS? Are they hitting an SBS limitation?
(with 45 users there's still a _lot_ of room to grow)
Call me biased but I would consider a move from SBS to Enterprise Server
a
downgrade. You get _down_ because of OS cost. You get _down_ because you
then need to license applications individually. You get _down_ because,
though the SBS features are retained through a 'transition' should you
ever
need to reinstall the server(s) you are no longer entitled to SBS
specific
components (RWW!!!!!!!!, nor Companyweb [but hey, it's just a sharepoint
site]). You get _down_ because, as the OP is finding out, SBS CALs not
only
cover access to SBS but _all_ additional Windows servers in an SBS
domain,
they differ from Windows Server CALs. You get _down_ because that
Enterprise
Server may be R2 but it doesn't have an WSUS console, nor expanded CAL
rights.
The OP _must_ have a good reason for suggesting this, I'd like to hear
it.
HINT: If the motivation is that you think the performance of the SBS is
bad
(due to load or whatever other reason) STRIP SBS BARE. Get another server
to
act as fileserver, get a seperate firewall, create a sharepoint site on
another server, add an SQL server for your LOB app, BUT KEEP Exchange ON
SBS, and SBSMonitoring, and come R2 SBS integrated WSUS. If the server is
still performing badly you underspec'd the server, getting a new one and
moving tasks OFF SBS, unless you are hitting an SBS limitation, is SHEER
LUNACY. Buying a better box and either 'forklifting' or 'migrating'
(www.sbsmigration.com) the current system to it makes a LOT more sense.
"sam cogan" <samcogan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:12F6222A-56D1-4580-AA23-7AEEC909B20D@xxxxxxxxxxxxxxxx
If you are changing from SBS to seperate components (server, exchange,
ISA,
SQL) Then you cannot just move your licences, these licences are
specific
to
SBSm you will need seperate CALS for server, exchange etc. Microsoft
does
offer a transition pack to aid in the move, which may help reduce the
cost.
--
Sam Cogan, MCSE, MCSA, MCSA:Messaging, MCP, A+, N+
"Femi" wrote:
Hi,
I have an SBS 2003 server, but will be upgrading to enterprise 2003
very
soon. I hae 45 userlicenses installed on the SBS already, but wish to
find
out how to go about transferring/moving those licenses onto the new
enterprise server.
I saw an option on the sbs server to backup licenses, but i am not
sure
if
this is the appropriate way to go about moving the licenses.
.
- References:
- Re: Transfer of user licenses from SBS to Enterprise
- From: SuperGumby [SBS MVP]
- Re: Transfer of user licenses from SBS to Enterprise
- From: Femi
- Re: Transfer of user licenses from SBS to Enterprise
- Prev by Date: Re: Email headers being stripped
- Next by Date: Re: Probelm with Exchange Sync / Outlook
- Previous by thread: Re: Transfer of user licenses from SBS to Enterprise
- Next by thread: How many Licences do I need?
- Index(es):
Relevant Pages
|
Loading
