Re: Exchange 2000 to Exchange 2003 migration

From: Randy Campbell [MSFT] (randycam_at_online.microsoft.com)
Date: 04/06/04 

Date: Tue, 6 Apr 2004 18:53:36 -0400

Hi Patrick,

You know I have to be biased and tell you to migrate to Exchange 2003 and
Windows 2003!! :) Seriously, as you mentioned, many more features and the
updates for OWA is clearly one of the top features for migrating as well.

If you followed the Deployment Guide, I can't see any reason for not
supporting the environment. 

-- 
Randy Campbell
Microsoft PSS
Please do not send email directly to this alias.  This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patrick" <patrick@removethis.finband.com> wrote in message
news:1054CE91-A1F7-40C7-84A4-7A5932DBFBF2@microsoft.com...
>
> Hi,
> Good to know I'm not loosing my mind yet  :)
> If I can follow up this with another question? The other thing that is
under consideration is to just install new exchange 2000 servers and start
moving mailboxes to them. In other words doing what I have proposed but
skipping the Exchange and Windows 2003 bit. What I have against this is that
with the same effort and time we would be able to provide a more stable
platform and new features than just solving performance problems. What would
you do in my shoes?
>
> Another question would be, is there any reason why Microsoft would not
give any support to an environment which has followed my proposed plan and
following the Exchange 2003 deployment guide?
>
> -Patrick
>
>      ----- Randy Campbell [MSFT] wrote: -----
>
>      Hi Patrick,
>
>      You are not totally crazy at all (at least with this post)  :)
>
>      Check out the following white paper (this will be beneficial to you
and your
>      company all the way around):
>
>
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/depguide.mspx
>
>      Good luck Patrick!
>
>      -- 
>      Randy Campbell
>      Microsoft PSS
>
>      Please do not send email directly to this alias.  This alias is for
>      newsgroup purposes only.
>
>      This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
>      "Patrick" <patrick@removethis.finband.com> wrote in message
>      news:E9C360F1-2B74-487C-AE15-CDE566E11F57@microsoft.com...
>      > Hi,
>      >> I need a little bit of advice concerning a situation I have.
>      >> The environment is as follows:
>      >> 1 DC/GC/DNS
>      >> 5 backend servers of which 2 are also DC and GC (I know bad idea)
>      >> 2 frontend servers
>      >> All servers are W2k sp4 and E2k sp3 with appropriate hotfixes and
about
>      2000 - 2500 users per server.
>      >> The domain is a pure resource domain with no AD problems. The
users are
>      still authenticating separately to the resource domain but there is a
>      project in progress to start using single sign on with trusts. The
users of
>      this domain have experienced some performance problems in the past
and the
>      backup and restore times are way too high right now. We got
permission for
>      new hardware so that is not a problem. It is imperative that the
downtimes
>      in e-mail services are held to an absolute minimum and it's very
important
>      to start resolving these performance problems fast.
>      >> Here is what I have proposed very simply:
>      >> install 2 new DC/GC/DNS servers, windows 2003
>      > install 2 new frontend servers E2k3
>      > install new backend servers and start moving users to the new
servers.
>      > when all users are moved to new servers move first server in site
roles to
>      one of the new servers.
>      > move all FSMO roles to one of the new DC:s
>      > Start decommissioning the old servers
>      > Raise domain, forest and exchange levels to 2003
>      >>> Now we had a consultant in for a quick look and here is what he
proposed:
>      >> Create a totally new domain which is native 2003.
>      > Start migrating users, contacts and groups to the new domain.
>      >>> Now, am I totally crazy or have I missed something, will this not
cause:
>      >> Much longer breaks of e-mail services.
>      > A lot more of planning and work
>      > Migration will take a lot longer
>      > Client side configurations will have to be made to all clients
(that's a
>      lot of clients to go through)
>      >>> I don't know what to do with this, my managers want to go with
the plan
>      that the consultant proposed and I can't seem to make them see the
>      situation.
>      >> If you have any advice or suggestions regarding this please let me
know.
>      Or if I am totally wrong in this let me know in no uncertain terms
that I'm
>      an idiot  J
>      >>>> Thanks,
>      >> Patrick
>      >

Relevant Pages

  • Re: Exchange 2000 to Exchange 2003 migration
    ... the Exchange and Windows 2003 bit. ... new features than just solving performance problems. ... > Good luck Patrick! ... >> install new backend servers and start moving users to the new servers. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2000 to Exchange 2003 migration
    ... is there any reason why Microsoft would not give any support to an environment which has followed my proposed plan and following the Exchange 2003 deployment guide? ... Good luck Patrick! ... to start resolving these performance problems fast. ... > install new backend servers and start moving users to the new servers. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2000 to Exchange 2003 migration
    ... is there any reason why Microsoft would not give any support to an environment which has followed my proposed plan and following the Exchange 2003 deployment guide? ... Good luck Patrick! ... to start resolving these performance problems fast. ... > install new backend servers and start moving users to the new servers. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2000 to Exchange 2003 migration
    ... is there any reason why Microsoft would not give any support to an environment which has followed my proposed plan and following the Exchange 2003 deployment guide? ... Good luck Patrick! ... to start resolving these performance problems fast. ... > install new backend servers and start moving users to the new servers. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2000 to Exchange 2003 migration
    ... is there any reason why Microsoft would not give any support to an environment which has followed my proposed plan and following the Exchange 2003 deployment guide? ... Good luck Patrick! ... to start resolving these performance problems fast. ... > install new backend servers and start moving users to the new servers. ...
    (microsoft.public.exchange.admin)