Solved

Exchange Internal OWA URL change

Posted on 2013-12-12
2
854 Views
1 Endorsement
Last Modified: 2014-01-01
Hi Experts,

Main Server : Exchange 2007 on windows server 2008
Front End Server : Windows Server 2003 R2

We installed a new front end mail server in preparation for a move to a new site(SRV22).

We arent ready to use it yet but will be in a few months... our current front end mail server (SRV9) is still going to be operational until then...

However it would seem that SRV22 has managed to get itself in the auto configuration as the Internal OWA URL, instead of SRV9.

As a result nobody can set out of office as it tries to use SRV22.

When I look at the auto configuration on any client the external OWA URL is correct, however the internal OWA URL has SRV22 in it... https://SRV22.xxxx.com/owa

Can anyone advise me what I can do to change this please?

Thanks

Gardman
1
Comment
Question by:gardmanIT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39713714
It isn't OWA that is the problem. It is Autodiscover.

get-clientaccessserver | select identity, autodiscoverserviceinternalURI

That information is published to the domain by all client access servers. Therefore it should be the same.

You need to change it on the new server to match the old server.

My guide for Exchange 2010 works for 2007 as well - just ignore the ECP bits.
http://semb.ee/hostnames

Simon.
0
 
LVL 4

Author Closing Comment

by:gardmanIT
ID: 39750394
Absolutely correct, i needed to fire up the new server again and edit it on their first.

Thanks
0

Featured Post

Business Impact of IT Communications

What are the business impacts of how well businesses communicate during an IT incident? Targeting, speed, and transparency all matter. Find out more in this infographic.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
Phishing attempts can come in all forms, shapes and sizes. No matter how familiar you think you are with them, always remember to take extra precaution when opening an email with attachments or links.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video discusses moving either the default database or any database to a new volume.

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question