• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 304
  • Last Modified:

How to minimize client side change when separating Exchange 2003 from domain controller?

Current environment:
Head office (HO):
Windows 2003 DC with DNS and Exchange 2003 standard on the same box (dc-ex).
Site replication: HO-A, HO-B

Site A: Windows 2003 DC with DNS (dc-a)
Site B: Windows 2003 Dc with DNS (dc-b)

Goal: separate Exchange 2003 and dc role s on dc-ex and minimize re-configuration on user end - Outlook configuration.

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23505721.html

The above link shows the only way to separate it is to install a new Exchange server, migrate mailboxes over, remove Exchange from dc-ex.

The above method will end up with a new Exchange 2003 with different name, which requires reconfigure all Outlook.

Q#1. Which server does Outlook point to when the old Exchange and new one co-exist?
Q#2. Any quick way to reconfigure Outlook to point to the new server?

Thanks.
0
richtree
Asked:
richtree
  • 3
  • 2
3 Solutions
 
davorinCommented:
Outlook points to the server on which resides the clients mailbox. The change should outlook find out automatically form AD property, if the computer does part of the AD. RPC-over-HTTP settings does not change automatically.

In exchange 2007/2010 and outlook 2007/2010 environment it can be a great help to you autodiscovery feature.

0
 
richtreeAuthor Commented:
Will Outlook 2003 automatically point to the new Exchange 2010 server after I move its mailbox from old Exchange 2003 server?
0
 
davorinCommented:
If you have outlook AND exchange 2007 or newer, than you can use autodiscovery feature.
If you have outlook OR exchange older of version 2007, then you can not use autodiscovery. (Lets say outlook 2003 clients connecting to exchange 2007/2010 or Outlook 2007/2010 clients connecting to Exchange 2003.)

If you are using any combination that is not capable of autodiscovery, (outlook 2003 or older connecting to any version of exchange OR any version of outlook connecting to exchange prior the version 2007) then the outlook client that does part of AD is still capable of automatically changing the settings to connect to correct server. But this is not called autodiscovery. For this setting you have an property that is written in AD and when you move mailbox to new server the setting is changed to new value.
If you plan to use outlook 2003 with exchange 2007/2010, then you will also need to change the RPC encryption level (at client side let say via GPO or at server side).
http://blogs.msexchange.org/walther/2009/08/30/exchange-2010-and-outlook-2003-clients-connection-issues/

So, when you will move mailbox from one exchange 2003 server to another exchange 2003 server, the mailbox at that time will not be accessible and at client side all you have to do is to exit outlook and open it again. Moving mailboxes at newer versions of exchange (source and destination server 2007 or newer) is even simpler. Users don't even notice that the mailbox is moved while they are using it.

0
 
richtreeAuthor Commented:
Thanks a lot. I will post a more detailed structured questions separately.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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