Re: OWA2007 Question

Hi again
as a little round up:

you have to distinguish between
a) mail sent to you by your external mailpartners using SMTP
and
b) mail acces of your users using OWA and Activesync for example

a)
as Mark told you, you don't have to change the MX records as long as the old
server is up and running
whenever you plan to remove the old box you have to switch your firewall
rules to transmit SMTP to the new Exchange Server

b) as I wrote in my first post, if the new Exchange server hosts all 3 roles
there is no smart way to migrate OWA.
- create a new DNS record for a new OWA name at a different public IP address
- request a new certificate for the new OWA name and secure the OWA web site
- create a new firewall rule to allow access the new Exchange server using SSL
- distribute the new OWA name to your users
- when a mailbox is moved the user must use the new OWA URL name and
probably has to reconfigure his ActiveSync profile at the PDA

Henry


"Mark Arnold [MVP]" wrote:

On Tue, 4 Aug 2009 02:43:01 -0700, Zoey
<Zoey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

There will be one server that will have the 3 roles (I will be doing a
typical install).

I think what needs to happen (and this is what i'm trying to confirm here)
is I need to add another mx record to the public ip address that hosts our mx
record. Right now the mx record is defined for the server name of our
exchange2003 server. When we install Exchange2007, this will be a new server
name. If I move a mailbox over to exchange2007, and then try and hit owa from
that mailbox, it won't know where to go.

As you have read from other posts....
If the CAS and MB are on the same box you cannot use the 2007 server
to access 2003 mailboxes.
So, use a second 2007 box, virtualized, temporary, whatever, to be the
CAS. You can juggle the roles later.

As for the MX records. You need to do nothing to the global DNS. Make
sure that the 2003 and 2007 boxes are exchanging messages internally,
properly. All mail coming into the 2003 box (as is the case now) that
is destined for mailboxes that have been moved to 2007 or are on new
mailboxes created solely on the 2007 box will be sent to the 2007 box.

Read up on some co-existence with 2003 papers (on msexchange.org and
technet.microsoft.com) to make sure you have got the send/receive
connectors on the 2007 box and the RG connector on the 2003 box
working properly. If you set the server up with the defaults and
answered the questions correctly you won't need to do much.

.

Relevant Pages

  • RE: OWA Not working Page not Found
    ... I get a "page not found" after i login to OWA. ... Share point is installed on the server, but not the IIS default website. ... obtain the latest service pack for Exchange Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant access/manage internal website + wheres my email?
    ... If you used to configure Outlook connected with Exchange Server, ... Group to the mailbox of the user in the regular storage group. ... By default the POP3 service in SBS 2003 is disabled. ...
    (microsoft.public.windows.server.sbs)
  • RE: OWA Not working Page not Found
    ... This issue occurs if the user account that you used to log on to OWA ... obtain the latest service pack for Exchange Server ... This problem may occur after you install Microsoft Windows SharePoint ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange "Light" setup opinions wanted...
    ... Monitoring the Exchange server. ... To download POP3 E-mails for ISP and router to user's mailbox, ... Info 4: Monitoring the Exchange server. ...
    (microsoft.public.windows.server.sbs)
  • OWA problems after changing default SMTP E-Mail Addresses for our site (exchange 2003 on windows
    ... I believe a reboot of the exchange server is what helped the situation) ... it seems to have partially broken OWA as well. ... I was researching getting another Verisign certificate for the ... Exchange server in some way I'm not aware of. ...
    (microsoft.public.exchange.admin)
Loading