Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 226
  • Last Modified:

switching to a new Exchange hardware by moving mailboxes: what happens to Outlook Web Access?

After reading recommendations here, I've opted while upgrading hardware to add the new computer to the network as a second Exchange server, and move the mailboxes from the old to the new. The question is: what happens to Outlook Web Access for those accounts which have been moved to the new server? DNS points to the old server for the OWA connection. I'm seeing "The page cannot be displayed" when I try to access through OWA a test account that I have moved. How are other admins who are gradually moving accounts as the method of upgrade dealing with this?
0
hyogurt
Asked:
hyogurt
  • 3
  • 2
  • 2
2 Solutions
 
dynamitedotorgCommented:
You either need to allow access to both mail servers or put a Front End server in place.

The FE server will allow OWA access irrespective of which mailserver actually holds the mailbox.
0
 
SembeeCommented:
If you aren't moving everything across in one hit, then I usually stand up a temporary Exchange 2003 standard edition server and set it as a frontend. Then point the incoming OWA traffic at that.
I used to suggest using the evaluation edition of Exchange 2003, but Microsoft have pulled the download in prep for Exchange 2007, so that option isn't available to you.

Simon.
0
 
hyogurtAuthor Commented:
Well, the first option (access to both mail servers) is tricky, because it means adding a new DNS record (and firewall forwarder) and distributing the address to those who have moved, or are being moved, or are about to be moved.

And the second option is tricky because it requires a whole new server.

Is there a way to jig the server roles temporarily, e.g., make the old server a Front End server so it distributes mail to both servers, and then, when that server is retired, restore the old heirarchy so the new server exists on its own?
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
dynamitedotorgCommented:
How quickly can you move all the mailboxes across? If you can move them all in one go then a judicious bit of swapping around will keep everything working.
0
 
hyogurtAuthor Commented:
I'm not sure how quickly they would go...it's only about 30GB of data, and the new hardware is quick (3.0Ghz dual-core Xeon), and it's through gigabit Ethernet, but the old server is a bit of a pig, a 933Mhz Pentium III. I was hoping to do it slowly and carefully, avoid a mad dash, but that may be the only way.

Although the temporary Front End server seems like a good idea. I mean it could just be a Celeron or some punk little piece of hardware, correct?
0
 
dynamitedotorgCommented:
For short term use the FE server needn't be anything special as long as it's got decent connectivity to the back end servers. Actual spec will depend somewhat on how many concurrent users you expect to use it.
0
 
SembeeCommented:
Depends how many users. I have run frontends on PIII 700's before. I have one that I take to clients for just that reason. It needs to be able to run Windows 2003 SP1, so anything bought in the last three years or so with a decent amount of RAM will be fine.

Treat it as any other Exchange server though - patch it, service pack it etc. When you have finished with it, remove Exchange using add/remove programs, reboot and then drop it from the domain and reboot. Just because it is a temp server doesn't mean standards should slip - that is how attackers get in.

Simon.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now