| David Sengupta [MVP] 2002-10-05, 8:39 pm |
| Options for migration: do it yourself or get a consultant. Either way get a
copy of Kieran and Donald's book:
http://www.amazon.com/exec/obidos/A...stems/102-39333
04-0104951
Post-migration support requirements: depend on (i) what kind of
infrastructure you deploy i.e. central vs. distributed, (ii) SLAs, (iii) how
static your environment will be, (iv) what Exchange-related functions you'll
be implementing i.e. IM, Conferencing, Workflow 3rd party or in-house,
DM/RM, etc. Typically Exchange is extremely robust and reliable ... you'll
need to make sure you have a good change control system as per your normal
environment so that latest SPs/hotfixes are applied, etc. You could
theoretcially combine Exchange admin function with other network admin roles
i.e. Active Directory & DNS, etc.
--
David Sengupta M.T.S., B.Sc., MVP, MCSE, MCSE 2000, CCA Ottawa, Canada
Exchange Diagnostics: Quest Spotlight on Exchange
http://www.quest.com/spotlight_exchange
Exchange Management: http://www.microsoft.com/mom
Exchange FAQ - http://www.swinc.com/resource/exch_faq.htm
"Petey" <Peterav@attbi.com> wrote in message
news:3D77C50B.FF411C06@attbi.com...
> Our corp. was thinking about going to Exchange from a generic mail
> system. We are currently a novell shop by are thinking about going all
> Microsoft. Would we need to hire a full time tech to manage Exchange
> every day? We have about 500 users at about 12 remote locations. We
> are also looking at Domino and Groupwise(if we stay novell). Also, are
> there any banwidth limitations when going from 1 branch to another?
> Some of our remote branches have 56k frame connections.
>
> Thanks
>
|