Re: Exchange 2003 upgrade

From: Bob Christian (BobChristian_at_removethis.gmail.com)
Date: 08/09/04


Date: Mon, 9 Aug 2004 15:50:19 -0400

As an aside, moving a small organization from 5.5 to 2003 utilizing the
swing method was relatively painless.

The only major gotcha I had was with security permissions within Exchange
System Manager. We ran the forestprep and domain prep with a different
account than the one we were going to setup our server with. We created a
security group for our service accounts, assigned it permissions in E2K3
ESM, and we were good to go.

"Mark" <anonymous@discussions.microsoft.com> wrote in message
news:2c3101c47e21$a0c8c7f0$a401280a@phx.gbl...
> Hello, I'm preparing to upgrade from Exchange 2000 SP4 to
> Exchange 2003. I have ran all of the prep tools and have
> researched everything I could think of, has anyone had
> any major probelms just running the upgrade?? It looks
> very straight forward but!
>
> Any help or advise would be greatly taken.
>
> Mark



Relevant Pages

  • Re: Service accounts best practices
    ... FYI - I just saw these links on the GRC Security ... > The Services and Service Accounts Security Planning Guide ... >> Best way to give DB Admins access to Enterprise Admin. ... >> Best way to give Backup Operators access. ...
    (microsoft.public.win2000.security)
  • Re: Service accounts with password expiration
    ... including service accounts. ... Is it really a security recommendation? ... this requirement comes from security folks that probably ... combined with a large does of neck-leather safeguarding that goes ...
    (microsoft.public.security)
  • Re: Connecting to SSAS from Network Service account
    ... its recommanded to use a domain user account instead of service accounts. ... Try to add the $BSCMservername in the "users" authorized to access your cubes. ... and if you delegate the security you have to setup the kerberos delegation correctly. ...
    (microsoft.public.sqlserver.olap)