Exchange 2010 coexist with exchange 2013
Hi All ,
Planning to have a coexistence scenario in my environment which is mentioned below
Exchange 2010 - ambiguous url in place - OA enabled
For mapi/rpc traffic - mail.domain.in - exchange 2010
For https traffic - mail.domain.in - exchange 2010
mail.domain.in will get resolved in to cas array in exchange 2010 .
After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
Note :
On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
exchange server via exchange 2013 server.
question : I would like to know above mentioned scenario is possible or not ?
On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
All of you tell me your valuable suggestions.
Regards
S.Nithyanandham
Hi,
Going Straight to the point... and answering your question...
The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
As per Exchange Team...
In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
their DNS cache expires after the shared FQDN is moved to CAS 2013.
As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
fix existing Outlook clients with the old value in the server field.
So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
Outlook 2013: 15.0.4420.1017 (RTM or later)
I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx>
Hope it can help you!
Cheers,
Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)
Similar Messages
-
Exchange 2010 install with Exchange 2013 present
Good day,
I have an Exchange 2010 SP3 instance, I then added a Exchange 2013 installation, the 2010 Exchange needs to be rebuilt due to space issues on the current host and moving the 2010 Exchange will require too much downtime.
The issues that I am running into is when installing the new instance of 2010 on the new host with the Exchange 2010 x64 SP1 ISO, I am met with the following error:
[08/22/2014 07:09:03.0912] [1] 0. ErrorRecord: The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
[08/22/2014 07:09:03.0912] [1] 0. ErrorRecord: Microsoft.Exchange.Data.InvalidObjectOperationException: The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
After some reading I understand that Exchange 2010 must include SP3 to co-exist with Exchange 2013, all the roles have installed without any issues except the client access role, I get the above mentioned error, thus I cant upgrade to SP3.
I came across a solution where the OAB needs to be removed and then re-created, but unfortunately this will cause too much issues as the OAB is always in use.
So I am stranded where I need 2010 SP3 to install the server, but as far as I know there is no 2010 ISO with SP3 available.
Any advice would be appreciated.
Regards,
Hendrik"So I am stranded where I need 2010 SP3 to install the server, but as far as I know there is no 2010 ISO with SP3 available."
I'm not sure I understand this? If you download Exchange 2010...
http://www.microsoft.com/en-us/download/details.aspx?id=36768
That *is* the SP3 version.
Otherwise, if you install Exchange 2013 (with no other Exchange 2010 servers present), you definitely cannot add 2010 servers after the fact.
http://forums.petri.com/showthread.php?t=64056
But if you started with 2010, then add 2013... I think you can add or replace 2010 servers provided they are at SP3.
What if you had lots of Exchange servers (a hosting company for example) and had to replace a server member of a DAG? Let's assume some mailboxes have been migrated to DAGs on E2K13 and some are still on E2K10.
Note: within a particular DAG you cannot have differents versions of Exchange but you could have some DAGs with E2K10 and others using E2K13.
It would seem that you would have to be able to install a new/replacement E2K10 server in this case? You could not replace it with a E2K13 server.
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. -
Exchange 2010 MBX with a Exchange 2003 Frontend server. Coexist?
We currently have a exchange 2003 environment with 5 mailbox server and 1 front end server. We would like to introduce a 2010 Exchange MBX server. Is that possible? Do we just install the MBX role with CAS/HT?
Thnaks,Hi
You need to have MBX,CAS and HUB all the three in Exchange 2010 else they wont be functioning without any one of them.
You can introduce Exchange 2010 server in Exchange 2003 server environment
Ensure you have at-least Exchange server 2003 SP2 else the it wont allow you to install Exchange 2010
You can only deploy Exchange 2010 in an Exchange 2003 organization that operates in native mode
Below article for your reference
http://technet.microsoft.com/en-us/library/aa998604(v=exchg.141).aspx
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.
Regards,
Sathish -
Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration
Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1722
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 323
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
Lid: 62184
Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1237
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 313
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
Lid: 62184
Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 311
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
Lid: 62184
Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
Lid: 53361 StoreEc: 0x977
Lid: 51859
Lid: 33649 StoreEc: 0x977
Lid: 43315
Lid: 58225 StoreEc: 0x977
Lid: 39912 StoreEc: 0x977
Lid: 54129 StoreEc: 0x977
Lid: 50519
Lid: 59735 StoreEc: 0x977
Lid: 59199
Lid: 27356 StoreEc: 0x977
Lid: 65279
Lid: 52465 StoreEc: 0x977
Lid: 60065
Lid: 33777 StoreEc: 0x977
Lid: 59805
Lid: 52487 StoreEc: 0x977
Lid: 19778
Lid: 27970 StoreEc: 0x977
Lid: 17730
Lid: 25922 StoreEc: 0x977
+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment
hi,
I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot.
I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?
ThanksHi Muhammad
Can you please give few more information about your environment so that people around here can help you out
I have existing Exchange Server 2010 Hybrid Deployment - Do you have Exchange 2010 and Office 365 in a
hybrid setup now ?
Are you trying to upgrade your on premise Exchange 2010 servers to Exchange 2013 ?
Or Are you trying to migrate your on premise Exchange 2010 to a different forest to Exchange 2013 ?
You can try the below suggestions-
I would better suggest you to follow Microsoft Exchange Server Deployment Assistant - http://technet.microsoft.com/en-us/office/dn756393.aspx
Also i would recommend you to check the prerequisites for hybrid deployment with office 365
http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Cheers !!!
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 2010 in a Exchange 2013 Environment
I am trying to install Exchange 2010 in an Exchange 2013 environment which was migrated from Exchange 2007 earlier.
Exchange 2010 sp1 Mailbox and Hub roles installed fine however I cannot install the CAS role. Saw some references to change the OAB to a non exchange 2013 version - however that is the only version we have = OAB 2013.
This is the error I get:-
Error:
The following error was generated when "$error.Clear();
get-OfflineAddressBook -DomainController $RoleDomainController | where { $_.IsDefault } | Enable-OabWebDistribution
" was run: "The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).".
The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:02:15
Finalizing Setup
Cancelled
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"Hi,
Please temporary remove all the OAB objects then try re-install the CAS server again.
After installing CAS server, we can re-build the OAB on Exchange 2013.
More details in the following articles:
Remove-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/aa995963(v=exchg.150).aspx
New-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/bb123735(v=exchg.150).aspx
Hope it is helpful.
If the CAS server still cannot be installed, please post the details of setup log.
Thanks
Mavis -
Exchange 2010 dag with only 2 servers
I have my exchange 2010 running on win server 2012 R2 and I have installed another exchange 2010 server with the same FQDN and I want to configure DAG with only these 2 servers. Can I implement DAG with only 2 servers?Can the mailbox,client access and hub
transport roles still work with only 2 servers? If Mailbox and Hub transport could work it will be fine for me as CAS switchover can always be done manually.My main concern is securing data. Any article on how to implement that would be highly appreciated.
ThanksHi,
Yes, we can create a DAG with 2Servers and Each server can have upto 100 database depends upon Standard or Enterprise.
Here is a great link that explains about DAG
Exchange 2010 DAG Installation
Mark as Answer/Helpful Post if it helps
Regards.
Naren Neelam, Messaging Consultant, ITBigBang (P) Ltd Www.ITBigBang.Com | Hire Us for Messaging Consulting -
Exchange 2010 Integration with Salesforce
Hello,
We are planning to integrate our Exchange 2010 environment with Salesforce. This is to sync the contacts and events for Salesforce users. They need us open the ports between Exchange 2010 servers and Salesforce servers. Is it fine if the ports are
opened between CAS array and salesforce servers ? or do we need to open the ports between all the exchange servers or salesforce servers? Please advise.
Thanks,Hi,
Great information from both Derbyshire and Martin. Also find additional information for your reference:
Exchange Network Port Reference
http://technet.microsoft.com/en-us/library/bb331973(v=exchg.141).aspx
Thanks
Mavis Huang
TechNet Community Support -
Hello,
Please advice, i have an Exchange 2010 server with 2 DAG servers - DAG1 and DAG2 - backup with 2 DPM servers, one for DAG1 and one for DAG2 is it possible ?Hi,
I confirmed with Exchange support team that DAGs could be backed up separately.
Meanwhile backup database is important if you need to recover both Exchange server settings and database. See:
Recover a database availability group member server
http://technet.microsoft.com/en-us/library/dd638206.aspx
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Exchange 2010 deployment in Exchange 2003 Environment
Hello,
I have recently installed Exchange 2010 in an Exchange 2003 environment. I need some help migrating all my settings over to Exchange 2010
-- mailboxes, recipient policies, offline address book, free/busy, etc.
I have looked at these following TechNet sheets for assistance, but getting a bit confused:
http://technet.microsoft.com/en-us/library/aa996719.aspx (Exchange 2013 System
Requirements)http://technet.microsoft.com/en-us/library/ee332348.aspx (Upgrade
from Exchange 2003 Client Access)http://technet.microsoft.com/en-us/library/aa998186.aspx
(Exchange 2003 - Planning Roadmap for Upgrade and Coexistence)http://technet.microsoft.com/en-us/library/ee681662.aspx (Install
Exchange 2010 in a Mixed Exchange 2003 and Exchange 2007 Organization)
I have two domain controllers. Exchange 2010 is not installed on a DC, but Exchange 2003 is on one of them. I want to eventually decommission
the Exchange 2003 environment and implement and Edge Server in its place. Exchange 2010 is installed on a Virtual Machine. It's running SP3, the latest service pack. Exchange 2003 is on a physical machine and it's running SP2.
Please help me simplify what exactly I need to do to migrate 2003 configurations over to 2010.
Thank you for you much appreciated assistance.Hi
I would install a new DC and seize the MSO roles to the highest server. Remember you can install server 2012 but not R2 yet.
You can setup your connectors on exchange 2010 to send/receive mail to the internet. make sure your ISP allows the new server.
You can also setup a routing group connector so that mail flows from EX2003 to EX2010 and vice versa during your transition period.
Remember to replicate your public folders to the new server and if you have a lot of data be patient. Once you happy with everthing then decomission the old DC.
Hello,
All FSMO roles are transferred (not seized) on my Windows 2008 R2 Standard Domain Controller. I transferred all the roles off my Windows 2003 Domain Controller. The W2K3 DC is also my Exchange Server 2003 SP2. I specifically did not want to
install Exchange 2010 on a DC. It's on its own member server.
Should I make the Exchange 2003 Server a Front-End Server when I create a routing group for mail flow to Exchange 2010? I want to eventually implement an Edge. Also, can I have mail flow from the Internet directly to the Hub and bypass the Exchange
2003 mail flow? -
Cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2
Hi,
We are planning cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2.
Requesting you to please help us out for below scenario.
Source Exchange 2010 SP2:- abc.com
2AD, 2CAS & 2 MBX servers
Database:- 4
Total Users :- 3500
Accepted Domains :- 8
Total Data:- 5TB +
Target Exchange 2010 SP2:- xyz.com
Resource allocated same as above.
Now we have to migrate users along with data to target forest xyz.com keeping both setup live, as moving 5TB + data will be a ongoing process and the same will take some time.
With the guidelines mentioned in
http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-14203 we are able to migrate test users along with data, but after migration the migrated user is not able to connect through MS Outlook even not able to login into
OWA. It gives error “The Outlook Web App address
https://mail.abc.com/owa is out of date.”
Kindly let us know how to solve this issue.
Kindly let me know if you want any more information from our end.
Thanks in advance.
Thanks and Regards, Shashank KudiHi Shashank,
Do you have certificates properly installed and configured in the target Exchange?
If not, Please configure certificate and import the certificate to the trusted root CA if you are using internal CA cert.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Integration b/w Exchange 2010 SP2 and Exchange 9.1.1.7 connector
Has any succesfully integrated exchange 2010 sp2 with 9.1.1.7 conncetor ..
Sp2 is not in the certifcation list in the connector documentation .. just want to check if any one has done this before ..
ThanksHi Sembee,
We did this already.
We got it working now after doing above but with the shell.
First we confirmed if the mailbox is disabled with the following command: Get-MailboxStatistics -Database MBD01 | Where { $_.DisconnectReason -eq "Disabled" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason
It did show as disabled but when we try to enable it we got the following: This task does not support recipients of this type.
So we disabled the mailbox in the shell, enable it again and it was fine.
Get-MailboxStatistics -Database MBD01 | Where { $_.DisconnectReason -eq "Disabled" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason helped us, cause in the EMC exchange showed the user as enabled.
Thanks -
Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013
Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.NithyanandhamHi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham -
Remove Exchange 2010 DC from single server environment coexisting with Exchange 2013
My new Exchange server (2013) has completed all the migration steps including public folders. Mail is working well. I do not use the old DC running Exchange 2010 for any local domain logins or computer control, it is strictly for OWA as is my new Exchange
2013. I went through the uninstall of Exchange 2010 with out error but cancelled it after it said it was ready to uninstall. When I shut down Exchange 2010 server mail no longer is available. What am I missing? I am using same Public IP and different
private (192.168.1.4 new EXchange 2013, 192.168.1.7 for Exchange 2010) I changed these settings in my asa Firewall and that is working with new settings as well. Send and Receive connectors are on new while old one have been deleted. Do my MX records
need to be updated to reflect new server (ex2) as opposed to old server name (ex)?
You can come to Maui for a "Site Inspection" lol!
System AdminHi
You need to make sure all your DNS settings are correct with the new server IP as well as autodiscover. Remove any routing connectors between exchange 2010 and 2013.
Not best practice to run exchange on a DC but if you comfortable you have migrated all system mailboxes, user mailboxes and that the settings on your new server match the old one then proceed with the uninstall.
Your ISP will obviously route mail to your firewall as you are doing the NAT from there. -
Exchange 2010 ambiguous URL'S issue while coexist with exchange 2013
Hi ,
Please correct me if i am wrong and also all of you tell me your valuable suggestions.
Like as said in the below article we are having an exchange 2010 ambiguous url's in place.
Referred
article :
http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
As said in this article, if we have exchange 2010 ambiguous url's in place we will face issues during exchange 2013 coexistence.I agree with that point .
Question : On such case why don't we use a separate namespace for internal and external outlook anywhere settings in exchange 2013 which is different from cas array name and also there is no need to disturb the existing exchange 2010
environment by changing the rpc client access attribute in exchange 2010 databases or by forcing the exchange 2010 internal outlook clients to connect via OA. Please clarify my doubt and say whether the mentioned scenario is possible or not ?
Note : Same time please consider the new namespace which is going to be utilized on exchange 2013 outlook anywhere settings is available on SAN certificate.
Regards
S.NithyanandhamHi ,
Please someone shed light on this case.
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham
Maybe you are looking for
-
It happened after i did a load of updates. Icons are now missing - not a huge problem because they still download (just nice to get a glimpse of what i'm buying - there's no screenshots any more either). Updates page doesn't look like it's loaded pr
-
Hi All, I have already made the stripping for 3 disks in home slice. This function are destructive process in disks slice. So all data are destroyed in home. However, the metatool can't allow the stripping in root, swap and usr directories because th
-
How do I create a keyboard short cut, how do I create a keyboard short cut
How do I create a keyboard short cut. I use excel and want to add the + on the numerical keyboard as an instruction to add all highlighted boxes and drop the answer into the next available box either horizontally or vertically.
-
MacBook Pro Overheating with WoW Patch 4.2
Hi all, I've started having a problem with my MacBook Pro. The only heavy things I do with it are pretty much World of Warcraft and Starcraft II. Prior to WoW's most recent patch my computer would get from around 180F-190F (82C-87C) when raiding, oth
-
Using Excel template in ALV Report
Dear Gurus, I am having problem with excel template as layout used in ALV report (as i am new to this topic). I uploaded the excel sheet through report BCALV_BDS_UPLOAD. And i am calling the excel template with change layout option but it is not upda