Migrate Exchange Server

Dear all,
I am in this situation
Domain A (AD and Exchange 2003)
Domain B (AD and Exchange 2010) two domain is in trust
must I migrate the server exchange with the domain A to domain B, the mailbox are already going on the Exchange DB of domain B, to make the migration of the server I can use simply the migration computer (ADMT) , or it is necessary to do differently?
the migration is necessary to make the backups of the old mailbox from Exchange DB 2003.
thank you very much

Hi Willis,
This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
" was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

HT4796 Is it possible to migrate Exchanger Server mailboxes to an apple enviornment?

I would like to find out if it's possible to migrate Exchange 2007 Server Mailboxes to an Apple Environment. If the answer is yes, does anybody knows how this can be achieved? What tools and methods will be used and are there any requirements in terms of H/W, S/W, O/S, etc...

You could connect your old MacBook to your TV with an adapter cable and play directly from it as well as stream from shared libraries. Depending on how old your MacBook is, however, you may need to use a separate cable for audio and the video quality may not be as good as with an ATV.

Migrating Exchange server from 2007 SP3 to 2013

Hi All,
We are planning to migrate our exchange server 2007 SP3 to 2013 , what are all the best options available?
Thanks,
Mani L
Mani L

Hi,
Here are some articles which can help you to migrate from Exchange 2007 to Exchange 2013 for your reference.
Upgrade from Exchange 2007 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
Checklist: Upgrade from Exchange 2007
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx
Install Exchange 2013 in an Existing Exchange 2007 Organization
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

Dear All,
I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
For example: in exchange 2010 PF:
In exchange 2013
\Public Folder\sales\A1_calendar
--->
\ Public Folder\sales\A2_calendar
---> ?
\Public Folder\sales\A3_calendar
---> ?
\Public Folder\sales\A4_calendar
---> ?
Thanks in advance.
Regards,
Willis Wong

Hi Willis,
This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Migrate from Exchange Server 2010 sp3 to 2013 sp1

I have one Exchange Server 2010 SP3 server (300 mailboxes) installed on Windows Server 2008 R2 SP1 with three major roles on it (CAS, MB and HT) - typical installation. Edge Transport server is not installed thus for controlling of mail flow
Symantec Messaging Gateway Virtual Appliance is used as Smart Host. UM server is not installed either. I set up test domain environment where I installed one domain controller (Windows Server 2008 R2 SP1) and one Exchange Server 2010 SP3 (Windows
Server 2008 R2 SP1) at first place and yesterday I did everything necessary to install Exchange Server 2013 SP1 on new test virtual server running Windows Server 2012 R2 which I successfully did.
Now in test domain I have two Exchange Servers (2010 SP3 and 2013 SP1). Is there any 100% reliable documentation with all actions that had to be taken in order to successfully migrate Exchange Server 2010 SP3 to 2013 SP1? I would want to know what
needs to be done not only for my scenario but also for other scenarios (DAG, CAS array, Edge, UM, multiple HT servers . . .) since I am interested in digging deep into Exchange Server 2013.

Hi BoxiKG,
In addition to the above mentioned, and this for your reference:
Upgrade from Exchange 2010 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Best regards,
Eric

Migration from Exchange server 2010 to Exchange server 2013

Hi All,
We have migrate Exchange Server 2010 to Exchange Server 2013. When I turned off my Exchange Server 2010, Outlook is not able to connect through Exchange 2013. It's prompting for user name and password again and again and nothing would happen
after provide user name and password. So, we are not able to uninstall exchange 2010 from old server.

Run these commands and post the update.
Get-WebservicesVirtualDirectory -Server E2K13SERVER |Fl internalURL,ExternalURL
Get-OWAVirtualDirectory -Server E2K13SERVER | Fl internalUrl,ExternalURL
Get-ClientAccessServer E2K13SERVER | Fl AutodiscoverServiceInternalUri
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Server 2013 architecture

Hi
We are planning to migrate Exchange server 2010 to 2013 with DR.
Could anybody please tell me the recommended design for this..
I am planning to put two CAS Server, two mbx server in production site and one CAS server , one MBX server in DR site.
Enabling DAC in DR site.
This design is ok or else i need to put all roles in two server in production and one in dr..
Please advise...

Either option would leave you with at least one available server per role in the main site, except that with two servers, you would have two servers holding the role not affected by the failure of a given server.
For example, you have CAS1, CAS2, MBX1, MBX2.
If MBX1 fails, you still have two CAS.
If CAS1 fails you still have two MBX.
What's generally more of a problem is quorum for the DAG cluster.
If you loose the main site, the database mailboxes cannot mount in the DR because they would not "have quorum".
This is adressed at the bottom of this article:
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.150).aspx
This also addresses the notion of "quorum":
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/exchange-2013-dag-dynamic-quorum-part1.html
You might address this (at a greater cost) with two DAG nodes in each site and with a FSW and alternate FSW.
Just a note: if you want all-around high availability, you would want to consider the CAS role as well (perhaps you have) which usually involves use of some form of load-balancing (or DNS round robin in a worse case scenario - not optimal).
Load-balancing between distant sites can be more of a challenge. If you have more questions, ask away.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Migrate exchange 2007 mailboxes to exchange 2013

Hi Guys,
im trying to move exchange 2007 mailboxes to 2013. to cut to the chase, is this possible because im getting different kinds of errors?
Please advise if this is possible and how to do it.
Thanks!

Hi,
Below link also will help you
Microsoft Exchange Server Deployment Assistant
http://technet.microsoft.com/en-us/office/dn756393.aspx
Before migrating exchange server, Make a plan
try to practcice on lab. " Production environment and practice lab is entire different"
I dont know your environment. Hope your Domain controller and Exchange environment is residing in same place. If it is different site, move FSMO roles to that site for installing purpose.
IT is really challenge and excitement .
Try to find the solution of client outlook connectivity,
I had this problem, after I install Cumulative update, this problem gone.
Login ECP console after install exchange server,
Certificate installation,
DNS pointing, port forward,
Apply auto discover.
I faced another issue as well during the installation. My ex admin upgraded exchange server 2003 to 2007. He may not uninstall exchange server 2003 properly. Exchange server
2003 record was in active directory. Exchange 2013 doesnt suport mixed version of exchange 2003 and 2013. I have to delete the Exchange server 2003 record under DNS and Adsiedit. After that only exchange server 2013 allow to continue to install.
Best of Luck " Nothing is impossible"
Regards,
Joby

Migrate Exchange 2010 to Exchange 2013, Need to defined win 7 users logon to Exchange 2010 & Win 8.1 users logon to Exchange 2013

Hi,
My organization have few win 7 and windows 8.1 clients. Now I want to migrate exchange server 2010 to 2013. And I don't want to remove exchange 2010 from the organization. Because I want to connect win 7 client through exchange 2010 and windows 8.1 user
connect to exchange 2013. Is there any way to define the win 7 users to connect to exchange 2010 and Windows 8.1 users to connect to exchange 2013?
Md. Ramin Hossain

The client connections are proxied to the mailbox servers that hold the mailbox.
You would need to have 2010 MBX servers with the mailboxes for the XP users, and 2013 MBX servers holding the mailboxes for the 7 users. And of course, the appropriate CAS servers.
Realistically, you need to migrate away from Windows XP. It is no longer supported.

Exchange server using interface IP after migrating from 8.2 to 9.1

hi,
i recently upgraded an ASA pair from 5510 (ASA OS 8.2) to 5512 (ASA OS 9.1). Many of the services are working fine including VPN after some tweaking and modifications in the new configuration, however the exchange server is not sending the traffic from its designated public IP which is mentioned in NAT statements. Exchange is using the public interface IP of the firewall for outbound communication. If i try to telnet from outside to the public IP addresses of the exchange server its giving proper response. kindly help me with this issue. i believe this is some NAT related issue.
OLD configuration (relevant part only)
access-list out_in extended permit tcp any host 213.42.201.35 eq www
access-list out_in extended permit tcp any host 213.42.201.35 eq https
access-list out_in extended permit icmp any host 213.42.201.35
access-list out_in extended permit tcp any host 213.42.201.35 eq smtp
static (DMZ,outside) tcp 213.42.201.35 www 172.16.2.200 www netmask 255.255.255.255
static (inside,outside) tcp 213.42.201.35 https 192.168.190.57 https netmask 255.255.255.255
static (DMZ,outside) 213.42.201.35 172.16.2.11 netmask 255.255.255.255
access-list out_in extended permit tcp any host 213.42.201.34 eq smtp
static (DMZ,outside) 213.42.201.34 172.16.2.21 netmask 255.255.255.255
New Configuraion
object network obj-172.16.2.21
host 172.16.2.21
description Created during name migration
object network obj-172.16.2.11
host 172.16.2.11
access-list out_in extended permit icmp any host 172.16.2.11
access-list out_in extended permit tcp any host 172.16.2.11 eq smtp
access-list out_in extended permit tcp any host 172.16.2.21 eq smtp
nat (inside,outside) static 213.42.201.35 service tcp https https
object network obj-192.168.0.0
nat (inside,outside) dynamic interface dns
object network obj-192.168.0.0-01
nat (inside,DMZ) dynamic 172.16.2.254 dns
object network obj_any
nat (inside,outside) dynamic obj-0.0.0.0
object network obj_any-01
nat (inside,DMZ) dynamic obj-0.0.0.0
object network obj-172.16.2.21
nat (DMZ,outside) static 213.42.201.34
object network obj-172.16.2.11
nat (DMZ,outside) static 213.42.201.35 service tcp smtp smtp
regards
Najeeb

Hi Najeeb,
If you are able to reach out to your SMTP via Public IP address , 172.16.2.11 will be using public IP address 213.42.201.35 for mail delivery (SMTP service alone) . Server 172.16.2.21 will be using Public IP address 213.42.201.34 for any traffic including SMTP , to double check this open your IE on your 172.16.2.21 google it for what is my IP address , you will see your public ip address 213.42.201.34 on your google results .
At any point time your both server will never use your outside interface for any external communication
The issue is exchange is sending the outgoing traffic via the outside interface of my firewall (213.42.201.46).
HTH
Sandy

Migrate from Server 2003 (no Exchange, single server) to SBS 2011

Are there any Technets or other Microsoft documentation on migrating from Server 2003 (no Exchange, single server) to SBS 2011? I understand it is possible, but I would like confirmation and some documentation before purchasing the appropriate hardware
and licenses.
Thanks,
Doug
Doug Orr

Hi Doug,
In general, the migration is the similar with migrating process from SBS 2003. In addition, also have main
difference.
“The main difference is that you don’t have to remove the source and that you have to follow the migration
instructions as the SBS migration wizard will not launch.”
You can get above description from following similar thread. Please refer to.
Migrate from Windows Server Standard 2003 (not SBS) to SBS 2011
http://social.technet.microsoft.com/Forums/en-US/68790e41-b833-4e81-8200-63852ab9e196/migrate-from-windows-server-standard-2003-not-sbs-to-sbs-2011?forum=smallbusinessserver
Meanwhile, please refer to the following article. It may be helpful.
Step By Step Guide To Migrating To SBS 2011
http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
However, as Robert suggests, would you please confirm specific version of SBS? It may help us to understand
clearly and provide correct information.
Hope this helps.
Best regards,
Justin Gu

Exchange server name not changing in mail profile after migration from 2010 to 2013

Following a migration from 2010 to 2013 we are finding that for a number of users the old exchange server address stays in the mail profile (control panel -> mail -> e-mail accounts) which causes Outlook not to load.
We are able to go into control panel -> mail -> e-mail accounts and change this manually to the new exchange 2013 server address but we have quite a number of users and don't really want to do it manually.
Shouldn't it be updating automatically and if so why is it?

Hi,
Yes, it should be changed by autodiscover. Does this issue occur to all the migrated users?
I have seen this kind of issues before when migrating from Exchange 2003/2007 to Exchange 2010. The most efficient way is to rebuild the Outlook profile.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Migrating Exchange 2013 public mailboxes to a new server

We have a client that is leaving their current Hosting company and wants to move to our hosting facility. We have recreated their DC,an Exchange Hub, and Exchange Store. We have exported and imported all of their recipient mailboxes and flipped the switch
and all mail flow is now going through our hosting facility. The problem lies in that I can not figure out how to move the public mailboxes out of the old exchange server and import it into the new server. Both are Exchange 2013 and running on windows server
2012. Any help would be greatly appreciated.

You're looking at a third-party product. MigrationWiz does public folders. There are other cloud-based migration solutions, but I don't know whether they support public folder migrations.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange Server 2013 migration and high avalability

Hello,
We are using Office 365 online and will be migrating onto an in-house Exchange Server 2013 on a new Windows Server box.
I have two questions:
1. What is the best way to migrate everything from the Office 365 to the in house server? Do I setup a hybrid environment and then move the mailboxes and then remove the hybrid environment?
2. What is the best way to setup high availability for the in-house Exchange server? I found out that in order to setup Exchange 2013 as high availability it needs to run on Windows server 2012 STD or Windows server 2008 Enterprise.
Please let me know and provide links to step by step instructions if possible.
Thank you, Karel
Thank you. Karel Grulich, MCSE, SBS

Hi Karel,
Thank you for your question.
In addition Ed’s suggestion, moving mailbox form Exchange online to Exchange on premise could be refer to the following link:
https://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
Exchange 2013 high availability could be referred by the following link:
https://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Migrate Exchange Server

Similar Messages

Maybe you are looking for