Re: Adding Dedicated Exchange 2003 Server to SBS 2003 Network

R2 changes the CAL rights significantly. You do not need Server CALs, Exchange CALs or SQL CALs for secondary versions of the products that are part of your core SBS. So your second Exchange server would not require CALs, nor would the server it runs on.

But from what else you're saying, I think you're still in Transition Pack territory.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Ken Sheppard" <ksheppard31@xxxxxxxxxxx> wrote in message news:%23Jbjo5JsIHA.1952@xxxxxxxxxxxxxxxxxxxxxxx
Thanks to you both for your input, Charlie and Chris.

Charlie, you mentioned that if we were at SBS R2, we could transition those SBS CALs to the new Exchange server. Is this not possible pre-R2? And if we did transition the SBS server, how would this make the 2nd Exchange server any easier? The cost part is just not part of my equation in the decision making. The budget is there.

Keep in mind, that the client is a RAPIDLY growing investment firm. Money is clearly not the issue. The issue is truly more time sensitive. I'd love to use the new EBS, but it's just not in their time line now. So the costing reasons that Microsoft has decided to not research what I need to do really is not surprising to me. My goal and current needs just doesn't fit into the typical SBS scenario.

Oh, well.

Ken


"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:26A7E22F-14ED-4C36-A461-8C2871890AFC@xxxxxxxxxxxxxxxx
Honestly, I think you're better off running the Transition Pack at this point. By doing so, you'll be then able to move Exchange - it will no longer be tied to the SBS box. You'll have the requisite reconfiguration pain inherent in moving Exchange, but that's going to be there regardless.

The alternative would be to upgrade to SBS R2, and install Exchange on a second server. Now your SBS CALs would give you CAL rights to that second Exchange server as well.

Finally, like Chris, I think you're going to find yourself a much better fit with EBS when it's available. You can do either of these moves at this point, and then start planning your transition to EBS when you're ready. The migration path from SBS to EBS should be quite well designed and documented, since this is a key scenario they want to push.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Ken Sheppard" <ksheppard31@xxxxxxxxxxx> wrote in message news:uewISAIsIHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for your reply, Chris. Honestly, it's not the money. The partners at the client want a dedicted Exchange server.

I know that my SBS wizards will break related to Exchange, but can't I simply add the new Exchange server and set the SBS Exchange as the perimeter Exchange server with all of the IS hosted on the dedicated Exchange server. Somewhat of a cluster or replication partner with Exchange.

I have looked at the new Essential Business Server, but I cannot wait. Plus, it's been my experience that Microsoft NEVER releases a product when they say they will release a product.

Thanks.

Ken
"Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:%23BLKx4HsIHA.1768@xxxxxxxxxxxxxxxxxxxxxxx
While you could install a second, standard Exchange Server in an SBS environment, not sure what the value would be
Because you are not at R2 for SBS, you would also have to buy cals for it.

Are you proposing to stop using the Exchange in SBS? You realize you'd be breaking wizards, etc.
At that point you'd be better with the transition pack

Or return the transition pack and wait 6 months or so for Essential Business Server 2008 (SBS 's Big Brother), which also has lots of automation, wizards, etc and allows up to 300 desktops. But it does require 3 64 bit servers (Exchange 2007 is 64 bit only and two servers have this piece.

-- Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Ken Sheppard" <ksheppard31@xxxxxxxxxxx> wrote in message news:8FB18E45-4238-4FD8-8E56-E53428898EAD@xxxxxxxxxxxxxxxx
I'm currently running SBS 2003 Premium (not R2). We have 65 SBS CALs, so
we're getting closer to the 75 limit. We have just recently purchased the
SBS 2003 Premium Transition Pack and upgrade CALs, but we have not actually
performed the transition install yet.

My question is can we legally install Exchange 2003 on another member server
running Windows 2003 R2 server? I have ordered the Exchange 2003 CD/DVD
media to go along with my Transition Packs. It seems like I'm covered both
ways, but these licensing questions are way, way above my paygrade.

And the reason we have not actually installed the Transition Pack yet is
because we don't currently need it. The sole reason we purchased it was
because the older SKUs for pre-R2 SBS Transitions Packs are discontinued and
hard to locate. I listened to a podcast related to the SBS Transition Pack
install process and it addressed not actually installing the TP--it implied
that you simply needed to purchase it to be in compliance.

Thanks for any suggestions.

Ken



.

Relevant Pages

  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Easy to use second 2000 Server for Exchange?
    ... Existing Exchange 2000 server - therefore have the CALs - so no new ones are ... Frank McCallister SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email for second domain
    ... The Microsoft Exchange MTA Stacks service is normally disabled on Exchange 2003 Servers on SBS 2003. ... You can safely ignore the MTA warning messages on the SBS 2003 server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Configuring exchange 2003 in SBS
    ... As I know, this is not related to per user mailbox, it refer to the mailbox ... store on the whole Exchange server. ... This newsgroup only focuses on SBS technical issues. ... What minimum requirement if I want this server for a fileserver? ...
    (microsoft.public.windows.server.sbs)
Loading