Re: Exchange install on different server

Tech-Archive recommends: Fix windows errors by optimizing your registry

Steve and Anna,

Thanks so much for the responses. I've read about "Swing migration", but
wasn't sure how it would work. I do have an open license of SBS 2003, so
could I purchase new HW, install my copy of SBS 2003 on it, run the "swing"
and after proving everything is working, take down the old SBS machine and
rebuild it into somethign different without breaking any licensing rules?

Thanks,
Mike


"Anna Clark" wrote:

Hi Mike:

Another vote for migrating to the newer box. Be aware that you may not move
SBS OEM from the first computer to the second one. Only retail or Open
License.

But, a new Open License copy of SBS R2 would be less expensive than
Server+exchange.

Steve is right on: Swing Migration is the way to do this.

Perhaps you could use the old server, + your additional copy of Server as a
TS or file server. If you store anything on it, get a second drive, even if
you use software RAID1.

--
Regards:

Anna Clark
Please do post the conclusion or solution
to your issue so that others may benefit.

"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:uAlqc$EVHHA.528@xxxxxxxxxxxxxxxxxxxxxxx
Unless you're running SQL the current 2.8 GHz SBS should be fine if you
can increase the RAM to at least 2 GB or more and put in larger RAIDed
drives. Migrating to a new box can also be done with minimal down time and
no impact on your 35 users by using a swing migration
(www.sbsmigration.com) - its well worth the cost for the comprehensive
documentation, tools, and support you receive.

"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:19EAEC49-72DC-49CF-A4F1-2AB3AC923E7E@xxxxxxxxxxxxxxxx
Steve,

Thanks for the note. I would prefer to keep it on the SBS server, but
didn't want to go through the pain of setting up a new SBS server and
having
to migrate all users. I only have about 35 users, but that's a lot of
time
for me. But maybe my best move is to purchase a new more beefed up
server
and install SBS and do it that way. Do you agree?

Mike


"Steve" wrote:

By installing a separately licensed copy of Exchange on a different
server
you lose the integrated wizard setup that SBS provides (of course its
also a
lot more expensive for that 2nd copy of Exchange and the licenses). You
will
find it much more difficult to setup OWA and/or Outlook via RPC/HTTP.
How
many users do you have accessing the current SBS and does it have ISA or
SQL
installed? I'd recommend beefing up the current SBS with more memory and
hard drives (RAID) rather than installing Exchange on the other server.

"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:98AACC49-6418-42A7-8870-EC3A17B014AB@xxxxxxxxxxxxxxxx
Thanks for the note. As I said in my original post, the SBS box is an
older
machine (2.8Ghz, single 80Gb EIDE HD), and has only 11Gb free at this
point.
My other server is a 3.2Ghz Zeon, 3-SCSI 36Gig 10K drives(raid 5), and
would
seem like a better box to run Exchange on. If you think differently,
let
me
know. I haven't done any of this yet, so I'm open to ideas. I have
also
never ran exchange either, so I'm completely looking for advice.

Mike


"OneInTen" wrote:

By separate copy you do you mean MS Exchange 2003 Standard? Not the
one
included in the SBS package? If yes, then run the setup program on
the
new
box which has to be a member server jointed in the SBS domain.

As far as Exchange on the SBS box goes, you can either uninstall it
or go
to
the Services panel and disable all the Exchange services.

I'm not sure why you want to go this way, since you already have
Exchange
installed on the SBS box


"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D58A7FB9-7AEE-4AED-9B37-200B7E068A0D@xxxxxxxxxxxxxxxx
Hi,
Thanks for the response. SBS 2003 includes Exchange 2003, and I
was
going
to install Exchange 2003 on the other server. I have a separate
copy
of
Exchange 2003 to install on the other server. Does that make
sense?
Can
I
not do that?

Mike

"OneInTen" wrote:

Which version of Exchange do you plan to install on the other
server?
If
you are thinking of installing the one that comes with SBS, you
can't
do
it.
It has to be installed on the same box as SBS.


"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C807982-43CE-4A39-B504-B8B9018803FF@xxxxxxxxxxxxxxxx
Hi,

I have SBS2003 installed on one of my servers, and along with it
Exchange
is
installed. I'm not currently using Exchange for e-mail, but
need to
do
so.
The SBS machine is a bit older and slower, as well as has less
disk
space
than another server on my network. I want to install Exchange
on
another
server, so do I need to "disable" Exchange on the SBS box before
installing
on the other server? I know Exchange creates mailbox stores,
and I
suspect
the install will detect Exchange installed on another box in the
domain,
and
wasn't sure if there was good way to do this?

Thanks,
Mike















.

Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 + Exchange setup checklist
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... How to Use the Windows SBS 2003 BPA ... To use the native ability of SBS Exchange to host your own mail, ... Install or update real-time antivirus for Exchange - many like Trend's ...
    (microsoft.public.windows.server.sbs)
  • Re: how to safely remove exchange from sbs 2003
    ... Windows Sharepoint Services Central Administration, Server Configuration, ... Exchange is the single most integrated part of SBS. ... SBS install' and 'install three times'. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange install on different server
    ... I do have an open license of SBS 2003, ... Perhaps you could use the old server, + your additional copy of Server as a ... and install SBS and do it that way. ... hard drives rather than installing Exchange on the other server. ...
    (microsoft.public.windows.server.sbs)
  • Re: remove exchange
    ... I'm wondering if SBS was not installed properly? ... There is another product called Windows Server 2003 for Small Business ... Component Name: Exchange Server, Action: Reinstall. ... this existing install was working prior to my assuming this ...
    (microsoft.public.windows.server.sbs)