<div>
<div class="content wysiwyg-content">
I am in the middle of migrating from a mixed Exchange 2003/2007 environment to 2010 (one CAS one Mailbox). &nbsp;The 2007 is the CAS and the 2003 server holds the mailboxes. &nbsp;Internally the 2007 server is called mail.domain.com and the 2010 is owa.domain.com. &nbsp;I have been able to change all of the URL's etc. so that now mail.domain.com is the 2010 server and owa.domain.com is the 2007 server, but I have one small problem. &nbsp;If I create a new MAPI profile and enter in the name of an employee who has a mailbox on the 2010 server, it is resolving to owa.domain.com, not mail.domain.com. &nbsp;I must be missing something. &nbsp;The CAS Array name is mail.domain.com, all of the proper URL'S are changed and working.
</div>
</div>


I am in the middle of migrating from a mixed Exchange 2003/2007 environment to 2010 (one CAS one Mailbox).  The 2007 is the CAS and the 2003 server holds the mailboxes.  Internally the 2007 server is called mail.domain.com and the 2010 is owa.domain.com.  I have been able to change all of the URL's etc. so that now mail.domain.com is the 2010 server and owa.domain.com is the 2007 server, but I have one small problem.  If I create a new MAPI profile and enter in the name of an employee who has a mailbox on the 2010 server, it is resolving to owa.domain.com, not mail.domain.com.  I must be missing something.  The CAS Array name is mail.domain.com, all of the proper URL'S are changed and working.

Changing Exchange 2010 Server name

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.