Exchange 2013 & 2010 coexist problem. Authentication Credentials Prompt in Outlook
Hello Forum
We have two Exchange servers coexisting together. A new 2013 and a old 2010.
Everything was setup with the help of the Exchange Deployment Assistant.
I have had alot of trouble with Outlook 2013 Prompting for credentials on Exchange 2013 Mailboxes. None of the 2010 Mailboxes expericence this popup.
I solved most of the popup issues with this by changing the ExternalClientAuthenticationMethod to ntlm.(from negotiate)
http://blog.gothamtg.com/2013/10/15/users-constantly-prompted-for-credentials-after-being-migrated-to-exchange-2013/
and installing this update for Outlook:
http://support2.microsoft.com/kb/2899504/en-us
Now 2013 Mailboxes Work without any anoying popups. Except when they try to open another users mailbox that is located on the old 2010 server or a shared 2010 calander.
The connection to Exchange 2010 is working if I input the users password, but should it not work without this popup too?
This connections name acording to Outlook is called: Exchange-Mail RPC/HTTP (remote [NTLM])
We use the same domain for external and internal autodiscover connections.
Test Exchange Connectivity Analyzer shows everything ok.
If i run
get-outlookanywhere | fl *external*
(2013 server)
ExternalHostname : webmail.domain.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
(2010 server)
ExternalHostname : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl : True
Only one thing I am wondering here is. If I change my old 2010 Auth Method to NTLM if that will break anything i OWA and so on.
What do you Guys have setup in your environments and can you point me towards any troubleshooting?
Thanks!
For us, the changes made in IIS are permanent, there quite possibly is a powershell way of doing it but I am still getting to grips with PS myself so I don't know.
I wont plagiarise others work but these two links here give a good explanation between Basic and NTLM. personally, I have always used basic because I always seem to get problems with NTLM, though one time it did work as expected but I forgot what I did to
get it working now.
https://social.technet.microsoft.com/Forums/exchange/en-US/92178beb-3310-4363-8848-d022a6e2a77f/basic-vs-ntlm-authentication-outlook-anywhere
http://www.sysadminlab.net/exchange/outlook-anywhere-basic-vs-ntlm-authentication-explained
Similar Messages
-
Missing ECP directory in Exchange 2013/2010
Hi Folks,
I have an exchange 2013 and 2010 server running in a domain.
I was trying to log into the Exchange Admin Centre on Exchange 2013. After typing the credentials the page just refreshed and set the prompt back in the password field.
Doing a Get-ECPVirtualDirectory results in the message "An IIS directory entry couldn't be created. The error message is Access is denied", Category Info: Not Installed (myserver\ecp (Default Web Site):ADObjectId). FSComputername:(name of exchange
2010 server).
I am unable to either create or remove the ECP directory (although it claims one exists). Opening the exchange management console on my 2010 server shows OWA is set up, but the ECP entry is blank.
If I try and login to OWA I get the login screen, but after entering credentials I just get HTTP 400 bad request.
In IIS on my 2013 server, there is an ecp directory with just a web.config and auth directory under the default website, there is also an ecp directory (containing contents) under the 'Exchange Back End' site.
Does anyone know how to go about re-creating the ECP directory etc.
Regards
AndyHi Andy
Ensure that Microsoft Exchange Security Groups and Exchange Trusted Subsystem group should be a member of the local admins and restart the server
Steps:
Launch IIS Manager Navigate to -> Web Sites -> Default Web Site Right Click on Default Web Site and choose Permissions Add Exchange Trusted Subsystem and grant Full Control Restart IIS Restart the server
If none of the above works then try the following
First remove the affected one
Get-ECPVirtualDirectory | Remove-ECpvirtualDirectory
Then create a new one by following below
http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
Remember to 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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP) -
Exchange 2013/2010 - Co-Existence, URLs.
Hey Team,
I am sure this is well documented and i for some reason cant seem to get good solid answer. But here is my questions. what are the correct URL settings for (OWA, ActiveSync, EWS) etc for Exchange 2013/2010 in a coexistence scenario?
1) All servers in the same ad site
2) mail. autodiscover, pointed to the 2013 server
3) 2013 server is internet connected.
Am i supposed to clear all the 2010 URLs?, Just the external ones? Use a separate namespace?
Thanks,
Robert
RobertThis is well documented in the below post, I would recommend you check it:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
In Exchange 2010/2013 coexistence scenario, CAS 2013 will proxy all connections to Exchange 2010.
How CAS2013 Picks a Target Legacy Exchange Server
It’s important to understand that when CAS2013 proxies to a legacy Exchange Client Access server, it constructs a URL based on the server FQDN, not a load balanced namespace or the InternalURL value.
When a CAS2013 starts up, it connects to Active Directory and enumerates a topology map to understand all the Client Access servers that exist within the environment. Every 50 seconds, CAS2013 will send a lightweight request to each
protocol end point to all the Client Access servers in the topology map; these requests have a user agent string of HttpProxy.ClientAccessServer2010Ping
Mohammad Saeed Abdelaziz | MCSE 2003 | MCTS: Lync, OCS, Exchange2007 | CCNP | UC Voice Specialist http://lyncrocks.wordpress.com/ -
Exchange 2013/2010 Co-existance Outlook Users Always Prompted for Password
Hello,
We are in the process of attempting to migrate to Exchange 2013, but during the migration time, we need to coexist with the two versions. Our outlook clients are a mix of Office 2007, 2010, and 2013. When a user is migrated from 2010 to 2013,
they start getting prompted for their password in Outlook every few minutes. They can click cancel and continue working, but they continue to get prompts for their password. If they click the update folder button in outlook, it updates fine, and
the password prompt goes away for awhile.
Most topics on this state that this is caused by a certificate issue. We have an internally deployed CA, with the Root certificate trusted by all clients. The exchange 2013 server has a certificate that was created by this CA.
I believe that this is caused by OAB (address book) still being hosted on the Exchange 2010 server (with a self signed cert), that is causing the connection to fail. Is there anyway to test this without breaking outlook connections for the users that
are on Exchange 2010? Or is there any other reason that this would occur?
Thanks for any assistance.Sorry for taking so long to reply, other items came up that rank higher then this migration.
I ran the Test-OutlookWebServices CMD and got this result:
[PS] C:\Windows\system32> Test-OutlookWebServices
Source ServiceEndpoint
Scenario Result Latency
(MS)
EXCHANGE13.company.local exchange10.company.local Autodiscover: Outlook Provider Failure 229
EXCHANGE13.company.local
Exchange Web Services Skipped 0
EXCHANGE13.company.local
Availability Service Skipped 0
EXCHANGE13.company.local
Offline Address Book Skipped 0
I
am currently thinking that this may be the error. Is there a way to
change the first failing result to the hostname of the
exchange13.company.local without breaking the current settings for the
exchange10.company.local autodiscover? -
User calendar sharing problem on Exchange 2013 & 2010 co-existence
Recently, I am trying to upgrade my site to Exchange 2013 from 2010. Most of the functions are work without problem except 2013 mailbox user try to access the sharing calendar on Exchange 2010 mailbox server.
e.g. User A is exchange 2010 mailbox user
user create a calendar 'testing' and sharing with user B
who is exchange 2013 mailbox user when user B try to add the calendar in OWA, user B get
'The action couldn't be completed.
An error occurred and your request couldn't be completed. If the problem continuesm contact your helpdesk with this HTTP Status code: 500.'
Actually, the error is 'The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.'
But there are no problem if user A sharing his own calendar. User B could add it without problem.user B can access the calendar from outlook ? if its still not working from outlook please try to repair outlook profile and check
Regards
John
Thanks for your reply. However, user B could not add the calendar in OWA 2013. I think, it doesn't related to outlook profile. -
Exchange 2010 to Exchange 2013 Public Folder Problem
Dear Experts,
I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
1) Parent Domain in Site A (abc.com)
2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
Anyone help will be highly appreciated.
Thanks & Regards,
ZBso you want users to access the PF in site B.
Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
run this for Exchanger 2013 DA
Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
Where Technology Meets Talent -
Exchange 2013 - Mail receive problem -Help!
Exchange 2013 SP1 -fresh install -test environment with one test mailbox setup in addition to the Administrator account. Using default Receive Connectors and it is set for Anonymous. Using OWA and Outlook 2010 for testing.
We can send/receive mail INTERNALLY in both Outlook & OWA between our test user and the Administrator user.
We can send mail externally from both accounts.
We are not receiving mail into the Inbox of either OWA or Outlook.
We are not seeing any authentication issues with Outlook -always shows connected to Exchange. But if we have same problem in OWA then we are just testing with it for now.
We ran the Microsoft Connectivity Analyzer for both Inbound and Outbound SMTP and it passed with no errors/warnings L
We did NSLOOKUP, from a Command prompt at the server wtith this result -not sure why it shows server as unknown?:Thank you for replying. Yes the mailbox is at Time Warner and I can use their webmail interface and see the messages I sent to the test user are there.
No, our domain name is companyname.com (if you need the actual name..I am not sure if I should send it to you?) and we use
[email protected] for email.
Our external A records and MX records are at Network solutions and that is posted here-- but decided to start another thread with more concise information as I learned of it:
http://social.technet.microsoft.com/Forums/office/en-US/0b18e928-0207-4ab9-bc12-c00a75088bdc/new-deployment-outlook-can-send-but-not-receiving-messages?forum=exchangesvrsecuremessaging
When I do NSLOOKUP of our domain I get just the two MX records at Time Warner. Not anything with our actual domain name for email in it. I just added the A records for mail.companyname.com and autodiscover at Network Solutions yesterday...but though those
were only for use externally for OWA, ActiveSync, etc
Note we do not use Split-DNS on our internal domain either. Our AD name is different than our public domain name - The AD is named with a subdomain: qs.companyname.com
Lastly, I did not create an MX record at network solutions for mail.domainname.com. Should I do that and set it to a higher priority? -
Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes
Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic? -
Exchange 2013/2010 coexistence DAG functionality?
Hi, so this is a bit of a silly question. But I need to make sure I understood the situation correctly.
I currently have an Exchange 2010 DAG with 2 servers and I am mid way through (In the Exchange Server Deployment Assistant) introducing my first Exchange 2013 server.
The plan is to make the new 2013 server the active DAG member one of the old 2010 servers the passive member for a short term until that 2010 server is rebuilt to 2013, but that's not going to work is it? Once I migrate a 2010 user to a 2013 database, that
user only exists in 2013, right?
Theres no way of adding a 2013 database into a 2010 DAG, so that if the 2013 server is down, the 2010 server will become active?
ThanksNo, there is not. You will build a new Exchange 2013 DAG and move mailboxes from Exchange 2010 to Exchange 2013 mailbox databases.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." -
Exchange 2013 - Quota notifications problem
Hello,
First of all I want to express mild disappointment with the way quota notification alerts are documented on Technet for Exchange 2013. The only reference I could find is that QuotaNotificationSchedule parameter of the Set-MailboxDatabase cmdlet no longer
does anything: "This parameter has been deprecated in Exchange 2013 and it no longer does anything.".
The only other reference I could find is this forum post:
http://social.technet.microsoft.com/Forums/exchange/en-US/f30bb2ca-91ab-4e69-a8b6-720e6a8a5b83/exchange-2013-quota-notification-message-not-sent-during-schedule?forum=exchangesvrgeneral
where it says: "Quota messages are generated once the user log in to mailbox in exchange 2013."
However, Microsoft Press published a book in 2013 "Inside Out: Microsoft Exchange Server 2013: Mailbox and High Availability" where QuotaNotificationSchedule parameter is being referenced as a working parameter which controls when Quota notification
are being sent.
My experience says that the forum post is correct.
Now onto the problem.
While our customer was still on Exchange 2010 they were the victims of this issue:
http://support.microsoft.com/kb/2480474/en-us which could easily be fixed with
CheckWarningQuota registry key.
Now we have migrated those mailboxes to Exchange 2013 and again, users are not receiving quota notification e-mails. Only a few users receive quota notifications e-mails and those are users that got their mailbox created on the new Exchange 2013 system.
Migrated users do not receive notifications. We have tried CheckWarningQuota on Exchange 2013 but it does nothing. Our theory is that mailbox flag introduced in Exchange 2010 SP1 is migrated with the mailboxes to Exchange 2013 and is the
reason why we are not receiving quota notifications again.
I appreciate thoughts and comments.
Regards,
DinkoCU8 addresses this issue, however, only for mailboxes not yet moved to 2013: https://support.microsoft.com/en-us/kb/303695
Mailboxes already moved will have to be manually fixed. The issue is they are missing their lcid (location ID). For whatever reason, the attribute does not make it across from 2010 to 2013. However, if you move the mailbox again to another 2013 database,
it fills in the lcid automatically. That is one workaround, but not necessarily a good one for people who have migrated a ton of their users already. So what do you do?
In the KB article, it shows you how to identify the users who are missing their LCID by doing the following in the exchange management shell:
#first load in the ManagedStoreDiagnosticFunctions, you will need this for the get-storequery cmdlet to work.
. .\'C:\Program Files\Microsoft\Exchange Server\V15\Scripts\ManagedStoreDiagnosticFunctions.ps1'
#then generate the list of all mailboxes with an LCID of 0.
$mbxs = get-mailbox –resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
$mbxsq = $mbxs | %{Get-StoreQuery -Database $_.database -query "select * from Mailbox where Mailboxguid = '$($_.ExchangeGuid)'"}
$mbxsq | ? {$_.lcid -eq 0} |fl displayname, mailboxguid, lcid
You can modify the script to dump the list to a text file if you need to.
Now, to address this, I simply populated the lcid for all my mailboxes. All of mine were en-US or lcid 1033, so it was easy to set them all at once. I just grabbed all Exchange 2013 mailboxes and applied the language (en-US) and DateFormat (MM/dd/yyyy) to
them (replace DOMAIN with your domain name) which in turn sets the lcid to 1033:
$mailboxes = get-mailbox -resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
($mailboxes).SamAccountName| %{set-MailboxRegionalConfiguration "DOMAIN\$_" -Language en-us -DateFormat MM/dd/yyyy} | FT -a
Incidentally, if you have already migrated all of your 2010 mailboxes, and you are on at least Exchange 2013 CU6, that script will resolve the issue whether you apply CU8 or not. CU8 fixes it for any other mailboxes that have not yet been migrated to 2013.
Hopefully this help you out.
Chris Allen
Microsoft Support Escalation Engineer -
Exchange 2013 - Shared Calendar problems
Since we put in Exchange 2013 in July 2013 we have had a problem with Shared Calendars. Even though a User has Owner Permission on another Calendar, New Appointment is Grayed Out and the User cannot add or amend and occasionally Outlook will hang.
We have tried Outlook 2010 and 2013 Clients as well as Cached Mode and Online Access. Exchange Server Standard 2013 CU2 was installed and this seemed to stop the problem for a while and now it has returned.
Permissions have been removed and reapplied both through the Exchange Powershell Interface and on the Mailbox. All other aspects of the system seem fine.
Any advice would be welcome.Hi,
Please check your application logs in your Exchange server. Confirm whether there are some error logs such as Event 9646.
It may because there are too many users connect to shared calendar at the same time that cause this issue. And there is a limit on the number of items that clients can open.
If so, we can change regedit
on the Exchange computer to resolve this issue. For more information, please click the following KB:
http://support.microsoft.com/kb/830836/en-us
Thanks,
Winnie
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Exchange 2013 mail flow problem
Hello!
We have problem, could not send mails via Exchange 2013 server.
Symptoms:
-no messages in message queue
-if sending mail to this domain, the message seems sent at Sender.
-if sending mail from this domain, the messages are in the mailboxes' DRAFT folder
Here are some SMTP logs:
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,10,192.168.3.2:26408,192.168.3.2:2525,<,250-STARTTLS,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,11,192.168.3.2:26408,192.168.3.2:2525,<,250-AUTH NTLM,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,12,192.168.3.2:26408,192.168.3.2:2525,<,250-8BITMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,13,192.168.3.2:26408,192.168.3.2:2525,<,250-BINARYMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,14,192.168.3.2:26408,192.168.3.2:2525,<,250 CHUNKING,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,15,192.168.3.2:26408,192.168.3.2:2525,*,,"EHLO options between current server and proxy target do not match : Xrdst, . Critical
non matching options : Xrdst, . Failing over."
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,16,192.168.3.2:26408,192.168.3.2:2525,>,QUIT,
Software Enviroment:
-Windows Server 2012 Server Standard
-Exchange Server 2013
-fully patched system (includes the brand new Exchange 2013 CU1), the error was realized before this update.
Regards.
molniHi
Can you run ipconfig/flushdns or create hosts file recorder?
Terence Yu
TechNet Community Support -
Exchange 2013 sp1 DAG problem on Wondows 2012 r2
Hi,
I have configured this on my servers. It seems to be working almost 100%.
When I look at server-databeses in ecp I see the DB is healthy both active and psssive.
When I run this (Get-DatabaseAvailabilityGroup) | ForEach {$_.Servers | ForEach {Test-ReplicationHealth -Server $_}}
I get DatabaseAvailabilty FAILED on both active and passife DB.
When I Switchover to the other sever I get no errors but in ca. 2 min it Switches back.
If I try to move mailbox from Exchange 2010 sp3 to Exchange 2013 sp3 I get
Data migrated: 1.327 GB (1,425,379,174 bytes)
Migration rate: 0 B (0 bytes)
Error: MigrationPermanentException: Error: Mailbox changes failed to replicate. Database 18475dc2-2111-4da6-854b-6583d42c9279 doesn't satisfy the constraint SecondCopy because the commit time 3/12/2014 12:17:49 PM isn't guaranteed by replication
time 1/1/0001 12:00:00 AM.
I admit that I had this configured before I installed SP3 :( Do I need to delete the DAG and create it again?
thanks.
ErróHello,
Please use Get-MailboxDatabaseCopyStatus cmdlet to view health and status information about one or more mailbox database copies.
Based on your environment, please set DataMoveReplicationConstraint to None to check the result.
Set-MailboxDatabase "mailbox database name" -DataMoveReplicationConstraint None
After you have done the move, please set DataMoveReplicationConstraint to SecondCopy again.
Set-MailboxDatabase "mailbox database name" -DataMoveReplicationConstraint SecondCopy
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support -
Exchange 2013 / 2010 coexistence with different public domains
Currently in my organization
1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
1x Exchange 2010 Standard w/SP3 - Mailbox
In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
miles away. We have no IT staff in any of our field locations.
We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
domain.local - Our internal Active Directory domain.
We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
severely underutilized.
Goals for the Exchange migration
My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
final topology is:
2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
1x VM with Exchange 2013 Standard w/SP1 - Client Access
1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
until Exchange 2013 SP3 is released.
Deployment Plan
Install Exchange 2013 on new VMs.
Create CAS Array object.
Configure Exchange 2013 to publish under the new namespace.
Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
Unknowns
My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
since we'll be using the new domain for each mailbox we move.
My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?Hi,
From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013.
About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
Checklist: Upgrade from Exchange 2010
Install Exchange 2013 in an Existing Exchange 2010 Organization
Upgrade from Exchange 2010 to Exchange 2013
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support -
Exchange 2013 / 2010 / 2007 - Public Folders
I have read that legacy public folders and 2013 public folders canot co-exist.
If I have legacy public folders A, B and C, does this mean...
that if I migrate folder A to 2013, i cannot maintain a replica on legacy systems, but folders B and C are still accessible
..or..
If I migrate folder A to 2013, I must migrate folders B and C also.
If I am need to import folder D, from an external Exchange 2013 installation, into my legacy public folder system, is it possible to migrate folder D out of the external 2130 environment into my legacy public folder environment? If so, is there any extra functionality
2013 PF has that the users will lose if the folders are down graded to legacy?
Thanks!
TomHi,
User mailboxes on Exchange 2013 servers can connect to legacy public folders, but legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 server.
Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously.
Before you migrate public folders, you need to migrate mailboxes to Exchange 2013 first.
Please refer to the following article.
http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
Besides, here is a related thread for your reference.
http://social.technet.microsoft.com/Forums/office/en-US/7603f02e-beb4-4c3d-8cb9-613ad806766b/public-folder-migration-from-multiple-exchange-2007-to-exchange-2013?forum=exchangesvrsharingcollab
Best regards,
Belinda Ma
TechNet Community Support
Maybe you are looking for
-
recently my iphone 4 shut down and wont come back on. when i plug it in to outlet or computer it shows the apple signal but still wont turn on. i need to restore to factory settings
-
Problem with table size (initial extent)
Hi, I have imported a table from my client's database, which shows the following size parameters as displayed from the user_segments table :- bytes : 33628160 blocks : 4105 extents : 1 initial_extent : 33611776 next_extent : 65536 The number of rows
-
Error when upgrading to v7.1 of IM
Installed patch 118787-11 to upgrade from IM 7.0 to IM 7.1. I configured IM without the httpbind service. I have it seperated on two different machines. The server on one machine and the multiplexer on the other. The multiplexer seems to be running f
-
Heres my problem. I have two giwa boxes, gwiaa and gwiab. Each are on seperate boxes and each are in their own domain. If I take Gwiaa down, gwiab will receive inbound email and pass them on, however, it will not send outbound email.Gwiaa is the prim
-
Hi all, I am new SAP-BI 7.0.I created one multiprovider with one info cube ,when ever i activate that it is giving error as multiprovider not yet locked.Please give your valuble solutions ASAP. Suneel