Exchange Server

Paul · Guest

Hello,

I have Exchange 2003/Outlook 2003. I originally set up all the mail clients
to point to server.domain.local as the exchange server in Outlook. Now, I
want to migrate to mail.domain.local as the server name in preparation for
moving exchange to a new server. mail.domain.local points to the same
server as server.domain.local in DNS right now, but will eventually point to
the new server once it comes online.

The problem is, when I edit the properties of the Exchange Account in
Outlook to point to mail.domain.local, it keeps reverting back to
server.domain.local when I go back to look at it.

I set up the mail domain first as an Alias (CName) in DNS, and then tried it
as its own Host (A) record. Neither works.

Does any have any ideas on how to get it to stick?

Thanks,

-Paul

Ben Winzenz [Exchange MVP · Guest

Outlook doesn't rely on DNS records here for the server. They actually
resolve to the server name where the mailboxes are homed. Simply adding an
A record or CNAME record won't change that here. If you are going to be
moving Exchange to a new server, as long as the Outlook clients are setup in
MAPI mode, when you move the mailboxes to the new server, Outlook will
automatically update the profile to reflect the new server name.

--
Ben Winzenz
Exchange MVP

"Paul" <a@b.com> wrote in message
news:ecGijLl$EHA.3368@TK2MSFTNGP10.phx.gbl...

brandon · Guest

MAPI clients are smart enough to find the server where the user's mailbox is
stored (which is what you're seeing). You won't need to change them when
migrating to a new server. Migrate a mailbox to a new server, and Outlook
will find it without intervention.

"Paul" <a@b.com> wrote in message
news:ecGijLl$EHA.3368@TK2MSFTNGP10.phx.gbl...

Paul · Guest

That's good to know. Do you have any idea how it does that? Does it just
start polling the network until an exchange server responds?

Thanks,

-Paul

"brandon" <spam@isno.thx> wrote in message
news:u4SQeYl$EHA.2568@TK2MSFTNGP11.phx.gbl...

Ben Winzenz [Exchange MVP · Guest

It's automagic :-)

Actually, what happens is something along the lines of the Outlook client
attempts to connect to the old server, the old server then refers Outlook to
the new server. It's somewhat more technical than that, but that's a basic
overview of how it works. So in order for this to work, the old server does
have to be online when the Outlook client connects, otherwise you have to
manually change the profile and point it to the new server.

--
Ben Winzenz
Exchange MVP

"Paul" <a@b.com> wrote in message
news:%23qYBsRo$EHA.3616@TK2MSFTNGP11.phx.gbl...

Paul · Guest

Thanks, Ben. Well, I kind of like my "design" better. But I guess Exchange
has been around for a long time.

Do you know if there are any ramifications of leaving the old server online
in the following case: I am upgrading a Exchange Standard Edition on a W2K3
SBS server to Exchange Enterprise on a different server running W2K3. I had
intended to disable the Standard Edition altogether once the Enterprise was
online. I had some concern that the two servers wouldn't get along with
each other.

Thanks again,

-Paul

"Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom> wrote
in message news:e%23etYrp$EHA.3376@TK2MSFTNGP12.phx.gbl...

Pat Cai [MSFT] · Guest

Hi Paul,

My understanding of your concern is: Currently you are hosting an Exchange
server A (the standard edition), and you want to replace it with Exchange
server B (enterprise edition). If I have misunderstood anything, please
feel fee to let me know.

The workaround I recommend is as below:

1. Join Exchange server B to the existing oganization that contains server
A currently. It must be specified during the installation of the new
server. You are supposed to put the two servers in the same domain.
2. Move all the mailboxes from server A to server B. In this step, all the
Outlook MAPI clients will be redirected to server B automatically.
3. After all the data has been transfered to server B, remove server A from
the oganization.

Here are some documents for your reference:

822892 Move Mailbox improvements in Exchange 2003
http://support.microsoft.com/?id=822892

822931 How to remove the first Exchange Server 2003 computer from the
http://support.microsoft.com/?id=822931

Exchange Server 2003 Deployment Guide
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/depguide.
mspx

Exchange Server 2003 Deployment Methodologies (Upgrade, Migration, and
Coexistence)
http://download.microsoft.com/download/f/3/d/f3d76b64-2c16-4948-afab-3232c2d
f285c/WC021203.exe

Hope the information helps.

Regards,

Pat Cai
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Paul · Guest

Pat,

Thanks, Those are good references. The only concern I have, which might
not be appropriate for this forum, is that the standard exxchange server is
running under the Windows 2003 Small Business Server, which, for various
reasons, likes to throw monkey wrenches into what are normally simple
changes. I will read through all the references.

I appreciate your time.

-Paul

"Pat Cai [MSFT]" <v-patcai@online.microsoft.com> wrote in message
news:mqE75Yr$EHA.3360@cpmsftngxa10.phx.gbl...

Ben Winzenz [Exchange MVP · Guest

There shouldn't be any worries about the 2 servers not getting along. The
fact that you are running SBS may throw some kink into the plan, but not
from an Exchange/Outlook perspective. You may want to post in the SBS
newsgroup for details on how to remove/disable Exchange on SBS (most of us
in here haven't worked with it extensively). The only other comment I have
is that you don't have to leave the old server online forever, just until
the mailboxes are moved and the Outlook clients redirected. You also have
to make sure that you re-home all public folders. That is a critical step
that many people forget to do, and will cause big problems. I believe that
this is detailed in the KB article that Pat included about removing the
first Exchange server.

--
Ben Winzenz
Exchange MVP

"Paul" <a@b.com> wrote in message
news:%23B%23%23cQq$EHA.612@TK2MSFTNGP09.phx.gbl...

Pat Cai [MSFT] · Guest

I would like to clarify the current situation.

The first problem in your first post is: When you redirect the Outlook
profile to the new server, they will be automatically rolled back to point
to the previous server if it is online. This problem may be caused by that
you are using a SBS2003 domain. As it contains the default Exchange server,
you can't control who is the default if you added an additional Exchange
into the domain because the SBS logon scripts always set Outlook as the
default (which cover many customer scenarios). If you don't want your
changes to roll back, then you have to stop the logon script running for
the user account you user. You don't have to delete the logon script,
simply go to AD Users and Computer, remove SBS_LOGIN_SCRIPT.bat from the
Profile tab.

1) Server Management -> Client Computers
2) Right-click the client machine, then View Computer Settings
3) Expand Client Setup Configuration, right-click Configure Outlook Profile
Information and select Change.

Alternatively, there is a REG value that can be created on the client under
the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\smallbusinessserver\clientsetup.

The value is called NoTransportOrder (by default, it does not exist) which
when set to 1 will make it so that the outlook transport order code does
not run with applauncher for just these instances where people don't want
to have the default transport order changed each time. As a result, if you
change the Outlook profile, it will not be reverted even the user re-logons.

Since this problem is more likely to be related with SBS, as Ben's opinion,
it would be best if you could submit this question onto SBS newsgroup. So
that you would receive other user's experience sharing and the right
Engineer can help you resolve the problem in a more timely and efficient
manner.

For the concern in your latest post, is it possible to remove the Exchange
standard edition installed by default on SBS. Hope I didn't have anything
misunderstood. The answer is yes. Just perform the removing steps in the KB
articles I provided in my latest post. Don't forget to replica public
folder. Thanks to Ben's supplement and this point is also mentioned in the
KB 822931.

For the concern whether the two Exchange servers in your domain can be
working together properly, the answer is also Yes. Based on my experience,
it is a doable solution and no incompatible problem exists.

Hope the information helps. If you have any further concerns, please feel
free to post here.

Regards,

Pat Cai
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Exchange Server Forum Index -> Administration	All times are GMT
Page 1 of 1