Exchange 2013 and exchange 2007 mixed mode questions

I made my first attempt at migrating from 2007 to 2013 but ran into some problems. My 2013 CAS and MB servers are successfully installed along with their prerequisites (AD entries, external and internal DNS is active or ready to be, FW rules etc..). I'm
at this point here in the Microsoft plan..
http://technet.microsoft.com/en-US/exdeploy2013/PrintChecklist?state=2284-W-CQCkAgIAQACACEEAAQAAAA~~
"Perform the switch over"
My questions are about behavior.
1. When I have everything setup correctly and DNS and the SCP's changed, the Webmail OWA site for all users will be the 2013 login interface, and after logging in will my 2007 users then see the 2007 OWA interface on my old CAS?, or will they access their
2007 MB using the 2013 interface?
2. There is a "backend imap4" service on my 2013 servers. We will still have some 2007 mapi connected MB clients. Do I need these services started to hand off 2007 mapi requests to the 2007 portion of the environment?

Hi,
Yes.
Based on my knowledge, we should do some configurations.
More details in the following articles:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
Please also add the new URLs into certificates.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Exchange 2013 and exchange 2000

Hy guys...
I have this problem...i have a dommain controller x.com and i installed Exchange 2013 on it. I have another dommain controler
y.com with Exchange 2000. Thex.com dommain sends and receives mails from other Exchange 2013 servers but when it comes to
y.com dommaind i am only able to send emails to
[email protected] I cannot send emails from y.com
(Exchange 2000) tox.com (Exchange 2013).
Bothx.com dommain controller and y.com dommain controller are in the same network and i fave connectivity between them.
What might be the problem?
Than u,
M.S

Hi,
Firstly, it’s not supported to install Exchange 2013 and Exchange 2000 in the same organization and it’s not recommended to install Exchange server on Domain Controller.
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.exchange2000or2003presentinorg(v=exchg.150).aspx
To understand more about the mail flow issue, I’d like to confirm your meaning that two DCs are in the same network.
If they are in the same forest, it’s by design that Exchange 2013 and Exchange 2000 cannot coexist.
For general mail flow troubleshooting , we can use telnet to check it.
For more information, you can refer to the following articles:
http://technet.microsoft.com/en-us/library/bb123686(v=exchg.150).aspx
http://msexchangeguru.com/2013/07/29/troubleshooting-mail-flow-issues/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 and Outlook 2007

Is there a new way to connect EX2013 to Outlook 2007 SP3?
MSB

Hi Baker,
According to the description, I notice that you want to migrate from Exchange 2010 to Exchange 2013 and want to know how to connect Exchange 2013 with Outlook Client 2007.
Following is an article about the migration, for your reference:
Upgrade from Exchange 2010 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Outlook client uses Autodiscover and Outlook Anywhere to connect to Exchange server, please make sure services’ URLs configured correctly.
If you want to communicate with external users, you need to apply a certificate issued from a Public CA.
After configuring all the points above, please run “Get-Mailbox –Identity allen | FL *GUID*” in EMS to get mailbox GUID of allen’. Input the GUID into server name filed.
More details on “Manual configuration guide for Outlook 2010 (Exchange 2013)” for your reference:
http://support.sherweb.com/Faqs/show/manual-configuration-guide-for-outlook-2010-exchange-2013
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Allen Wang

Exchange 2013 and Exchange 2010 coexistense

We have a and exchange 2010 organization with SP3 on most servers except for one 2010 CAS server that still requires SP1 for the purpose of legacy application compatibility. Can we introduce exchange 2013 in the org or will the setup detect
that there is an exchange 2010 server still with SP1 and fails to continue?

Hi,
For Exchange 2013 coexistence with Exchange 2010, the mininum version of Exchange server is Exchange 2010 SP3 on all Exchange 2010 servers in the organization. For more information about it, please refer to the Coexistence of Exchange 2013 and earlier versions
of Exchange server part in the article below:
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Personal suggestion, please upgrade your legacy application to the latest version which is supported with Exchange 2010 SP3 or higher Exchange version.
Regards,
Winnie Liang
TechNet Community Support

Autodiscover exchange 2013 and 2007

hello,
i am in the process of setting up autodiscover properly for a coexistence environment of exchange 2007 and 2013.
currently, exchange 2007 has the active CAS server role. let's call it server1.contoso.com. Exchange 2013 is installed with the CAS and Mailbox role. let's call that server server2.contoso.com
Assuming all certificates have been installed, i assume that server2.contoso.com has to point to the autodiscover of server1.contoso.com until i have fully moved all mailboxes over to 2013 CAS, correct?
the powershell command i used to set autodiscover on server2 is as follows,
Set-ClientAccessServer -AutodiscoverServiceInternalUri https://server2.contoso.com/Autodiscover/Autodiscover.xml
it then asks for identity and i enter "server2.contoso.com".
Currently, when i type "get-clientaccess server | fl server,*uri I get the follow results,
AutoDiscoverServiceInternalUri : https://server1.contoso.com/autodiscover/autodiscover.xml
AutoDiscoverServiceInternalUri : https://server2.contoso.com/autodiscover/autodiscover.xml
Should they both be "AutoDiscoverServiceInternalUri : https://server1.contoso.com/autodiscover/autodiscover.xml" since server1 is the active CAS server?
Again, once everything has been migrate i will then change the CAS server to server2.contoso.com
Thanks!!

Apologies if I have confused everyone here.
we need 2 urls for Owa and EWS in 2007 and 2013. My this blog should help
http://msexchangeguru.com/2013/12/31/e20132007-urlsauth/
Undying: Answers are in line.
1. What I understand from the post marked as Answer is there is no need for legacy namespace for Exchange2007/Exchange2013 co-existence, meaning after the installation of Exchange 2013 in the environment there is no need to modify the virtual dirs on exchange
2007 side. Both 2013 and 2007 will be using the mail.domain.com namespace for all the services and once the virtual directories have been configured on the Exchange 2013 CAS it will redirect the request to Exchange2007 CAS for the Exchange2007 mailboxes. And
since there's no need for legacy namespace, it should also mean that there would be no need for any additional publishing rule in the reverse proxy (ISA/TMG), just modifying the current one (mail.domain.com) to point to the Exchange 2013 CAS should do the
trick. Am I correct?
Just to summarize, all the redirection from Exchange 2013 to Exchange 2007 will be done without the need of legacy namespace and without modifying any URls on the Exchange 2007 side.
PN Answer:
You need 2 urls for OWA and EWS.
legacy.domain.com and mail.domain.com
Also need
autodiscover.domain.com
Basically you need to change these urls on 2007 side to legacy.domain.com
This means you need to get this url added into the cert.
On TMG side direct all the traffic to 2013 and it will redirect to 2007.
you would need a new public host record for the legacy url.
2. If all that is indeed correct then why the Technet article still make it sound like that the legacy host name is mandatory? http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
(Step 7)
PN Answer: Yes we need legacy url
Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

Cannot send mail from Exchange 2013 to Exchange 2007

I have an
Exchange 2007server with all roles in the same server (Version:
08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
(full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
few articles on the Internet.
Any suggestions?

These two sentences are in conflict : "I can also send
internal mail
from Exchange
2007 to
Exchange 2013. But
the problem is
that I am unable
to send from Exchange
2007 to
Exchange 2013. "
Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
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. Thank you! Damir

Introduction of New OAB Architecture in Exchange 2013 and Some General Troubleshooting methods

Exchange 2013 is different from previous versions of Exchange server on architecture, some of the old features have been changed. In this FAQ, I will demonstrate the changes on OAB and list a common issue for your reference.
[Agenda]
1. Differences between Exchange 2007/2010 OAB and Exchange 2013 OAB
a. Generation
b. Distribution
c. Download
2. Common issue and troubleshooting
3. More information
[Difference between Exchange 2007/2010 and Exchange 2013 on OAB]
As we know, OAB in Exchange 2007/2010 has 3 points, OAB files generated from MBX server, distributed to CAS server and downloaded to Outlook client. However in Exchange 2013, these 3 points have a little different from previous servers. For example, the OAB
Distribution process doesn’t depend on Microsoft Exchange File Distribution service anymore. Now let me show you the changes of OAB in Exchange 2013.
[OAB Generation]
====================
Exchange 2007/2010:
1. OAB generation server is the specific MBX server which has –server property.
2. If MBX01 is down, OAB generation will be affected.
3. Previous Server using Microsoft Exchange System Attendant service for OAB generation.
4. OAB generation is a scheduled process. By default, OAB files generated at 5:00AM every day.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
Exchange 2013:
1. OAB generation server is the MBX server that hosts a special type of arbitration mailbox, called organization mailbox. Thus, the same OAB files could be generated from multiple
MBX servers.
2. If one of the MBX server down, other MBX server still have the ability to generate the specific OAB files.
3. Exchange 2013 server using OABGeneratorAssistant for OAB Generation.
4. OAB generation is a throttled process. It depend on the Server workload.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
[OAB Distribution]
====================
Exchange 2007/2010:
Previous Servers use Microsoft Exchange File Distribution service to distribute OAB files from MBX server to CAS server. The distributed oab files stored in CAS server.
Exchange 2013:
The OAB files doesn’t distributed to CAS server. The OAB files only stored in MBX server.
[OAB Download]
====================
Exchange 2007/2010:
If Autodiscover works fine, Outlook should use OAB URL to get the OAB files and download it.
If Autodiscvoer doesn’t work, authenticated users can also get the OAB from the CAS server local disk.
Exchange 2013:
Microsoft Exchange File Distribution service has been removed from Exchange 2013 and the OAB files stored in MBX server. CAS server will proxy all OAB download requests to the appropriate MBX server.
Outlook also use Autodiscover to get the OAB URL and download it.
[Common issue and Troubleshooting]
Issue: Outlook doesn’t download OAB files automatically. When I try to manually download OAB, get this error: Task xxx reported error (0x80190194): The operation failed.
Troubleshooting:
1. First, please run following command to check the information of OAB Generation Server.
Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like “*OAB*”} | ft Name, Servername, Database
Example result as below:
2. Please make sure the authentication settings and URLs are set properly.
3. Try to verify whether the OAB files generated from MBX server successfully. Path as below:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
4. If all of the settings above set correctly, please try to check Autodiscover. Run “Test E-mail Autoconfiguration” to check whether there is anything abnormal on OAB. If has, please search the error code on MS official documents.
5. If this issue is related to local cache, please try to delete the OAB caches from local PC and re-download OAB for testing. Path as below:
C:\Users\Administrator.CU1(different)\AppData\Local\Microsoft\Outlook\Offline Address Books
[More information]
http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi Techy,
According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 and 2010 co-existance

We will have 2013 and 2010 exist together for a while...we plan to move away from using Unified Access Gateway for HTTP redirection to our Exchange services and implement Kemp
load balancers...two at our HQ site and two at our DR stie...
We plan to have a one arm configuration...from what I gathered...each load balancer will have a network connection and only one network connection and be on the same network as
our new Exchange 2013 servers. Can someone take a look at my config and give some input whether or not this will work and some suggestion on Ex13 urls, cert SAN names, etc.
HQKemp 2400 A
HQKemp 2400 B
DCKemp 2400 A        DCKemp 2400 B
172.16.1.104
172.16.1.105
172.25.1.104
172.25.1.10
Virtual IP   172.16.1.106
                         Virtual IP
172.25.1.104
From the video I’ve watched for Kemp install…we’ll create the following internal DNS records for the Exchange services that will be configured on balancers.
OWA/ECP
    mail.corp.local.com
              172.16.1.107
EWS               ews.corp.local.com
172.16.1.108
OAB               oab.corp.local.com
172.16.1.109
ActiveSync      mobile.corp.local.co
172.16.1.110
OA                 oa.corp.local.com
172.16.1.111
Autodiscover   autodiscover.corp.local.com 172.16.1.112
Question:
We will configure the Exchange services with these ip addresses linked to each service on all four load balancers?
Or will DR site load balancers have different IPs configured for same Exchange services?
Exchange services are split between our two sites…meaning Outlook Anywhere is configured for our CAS servers at our DR site and ActiveSync comes to HQ CAS servers as an example…so
I want all Exchange services to come through the newly installed load balancers at HQ and if they don’t respond…the Exchange services get redirected to the load balancers at our DR site.
Can you give some insight on the config of load balancers as to how we can do that?
I have a question about the cert we will have.
Our Microsoft rep says we should get a new wildcard cert…currently we have a UCC cert with the following SANs attached.
Will this new cert have to be installed on load balancers?
If so…can you suggest some ideas as to what new SANs I need if any of the new cert with Exchange 2010 and 2013 co-existing for a while.
Below are the SANs on our current UCC cert.
Outside resolvable SANs
Webmail.corp.local.com
205.223.19.25           portal.corp.local.com     205.223.27.78
Portal2.corp.local.com
205.223.19.25
Autodiscover.corp.local.com
205.223.19.25
Internal SANs
Hqcas1.corp.local.com
Hqcas2.corp.local.com
Dccas1.corp.local.com
Dccas2.corp.local.com
Owamail.corp.local.com
(this CAS Array server name that HQ CAS servers create)
What do you suggest we use for the external urls on Exchange 2013 for these services?
Our firewall guy says we’ll use same names,
but I’m not sure if we try to use same name if we’ll get an error?
Active Directory may say name already in use?
We plan to have firewall to just redirect requests for external urls to load balancers…sound correct?
Meaning load balancer won’t have an external NIC defined…which makes it a one arm config…correct?

Hi Techy,
According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
Regards,
Winnie Liang
TechNet Community Support

Create failover cluster to host Windows 2012 DC, Exchange 2013 and SQL as VMs

One of our clients has running Windows Essential 2012, SQL and exchange 2007 as VM on VMware for 4 years without major issue. However, the physical server is getting old and have some hardware issues recently. They have budgets to buy two Dell servers, EqualLogic
SAN, Windows server 2012 Datacenter and Exchange 2013. Is it possible for them to create failover cluster to host Windows 2012 DC, Exchange 2013 and SQL as VMs?
Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.howtonetworking.com

We will move all VMs from VMware to Hyper-V. Thank you.
Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on <a href="http://www.chicagotech.net">http://www.ChicagoTech.net </a>
How to Setup Windows, Network, VPN & Remote Access on <a href="http://www.howtonetworking.com">http://www.howtonetworking.com </a>

Exchange 2013 server stuck in maintenance mode.

Hello,
I have a single server setup for Exchange 2013 and recently had an issue with Maintenance mode during updates. I was in the process of getting the server upgraded to SP1 when it happened. I had tried to run the service pack when it returned an error
saying something was pending and it couldn't install. Because the server had several windows updates and 1 Exchange 2013 security update downloaded from wsus, I thought it was obviously this. So I cancelled out of the sp1 install and ran the updates.
Once the updates were finished and the server rebooted, mail wouldn't flow. Found out it was because it was in Maintenance mode.
I'm not sure if it was the SP1 install or the security update that placed the server in this mode, but it seemed like it was the security update(KB2880833.) From what I've found on the interwebs, Maintenance mode is meant for High Availability setups, which
mine is not and it has to be put into that mode mannually. I never put the server into this mode. Is this done automatically by running updates or Service packs? and if so, how can I turn prevent it from happening automatically? Is it necessary? I have
no reason to use it, as we only have one server. I've found plenty of info on how to turn it on or off, but nothing about any automatic settings.
THanks for any guidance.

Hi,
When a CU or SP is installed, the server is automatically put in maintenance and I don't think there is a way to stop that. It is written to the
ExchangeSetup.log and will look like this:
Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
If the CU or SP runs successfully, it will be taken out of maintenance mode automatically with the below commands but if a failure occurs, it can be done manually with:
Set-ServerComponentState SERVERNAME -Component Monitoring -Requester Functional -State Active
Set-ServerComponentState SERVERNAME -Component RecoveryActionsEnabled -Requester Functional -State Active
Set-ServerComponentState SERVERNAME -Component ServerWideOffline -Requester Functional -State Active
Martina Miskovic

Data sync between exchange 2003 and exchange 2013

Need assistance on a general direction.
There is a 2003 domain with exchange 2003 currently in use. On this domain there is also a contact management application that is heavily integrated and cannot be update at this time. I would like to bring up a new 2013 exchange server.
Is there a method that I could have user data synchronized between the 2013 exchange data and the 2003 exchange? In this manner users could use the 2013 exchange as primary and the Contact manage application could use the sync copy of exchange 2003. For
now I am only concerned about he the calendar however I am sure the other information will need to be sync as well.
Please let me know. Thank you.

Hi There,
Once you install Exchange 2013 it will use the same data your Exchange 2003 is using \ seeing because both of them use Active directory for Directory information.
Exchange 2013 will see all the users that are 2003 without you needing to sync \ move data.
If you need to users to be on Exchange 2013 and keep Exchange 2003 all you need to do is move the mailboxes to Exchange 2013.
Cheers,
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Migrating to Exchange 2013 from Exchange 2003, EV7, Office 2003 and XP

What is the best approach for migrating our 300 user Exchange 2003 organisation to Exchange 2013.? We use Enterprise vault v7.5 and the clients are Office 2003 on an XP desktop.
We are also planning to upgrade to Windows7 and Office 2013 this year so I am trying to understand the sequence. Should we just aim to upgrade to Exchange 2010 with Outlook 2010 instead?
Many thanks.

Hi,
You can't install Exchange 2013 until and unless you decommission your Exchange 2003. Coexistence of Exchange 2013 with Exchange 2003 is not supported. You first need to upgrade to Exchange 2010 SP3 and then move users to Exchange 2010 and decommission your
Exchange 2003 servers. Once you are done with the decommissioning of your Exchange 2003 server you will be able to install your first Exchange 2013 machine in your messaging infrastructure.
Kindly mark this as answer if it fulfill your requirements. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Certificate configuring for exchange 2013 and office 365 hybrid deployment

Please advise on what digital certificate requirements for hybrid deployment and to configure it.

Hi sphilip,
If you want to deploy AD FS with Single Sign-On(SSO), we need use certificate to establish secure trust between on-premises Exchange 2013 and Office online.
We can use and configure a trusted third-part CA within all on-premises Exchange 2013 Mailbox and Client Access servers to ensure secure mail transport, more details about
Office 365 Hybrid Configuration Certificate Planning, for your reference:
http://blogs.technet.com/b/neiljohn/archive/2011/08/25/office-365-hybrid-configuration-certificate-planning-adfs-exchange-web-services-owa-oa.aspx
Best Regards,
Allen Wang

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
First my organize has Exchange on 2 site like
site A (internet facing) : 2CAS 2 MB all are Services pack1
site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1
so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....
When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).
But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
some query command cannot return for any result that are server on siteB (just some query command)
Problem
EMS on CU5 return very slow result.
EMS on SP1 still ok.
Does anyone face this problem before for CU5??? Please help me figure this out. Thank you
reply from Social.technet

Hi,
Have you used the above cmdlets to check your Exchange server health?
"all other command that I ran on EMS didn't logged on event viewer.", my environment is the same with you. I use Exchange 2013, only errors will be displayed in MSExchange Management. Actually, it is not related to slow EMS response.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Introduce an "passive" Exchange 2013 in Exchange 2010 environment without user or administration impact.

Hi
We wish to introduce an Exchange 2013 server in our existing Exchange 2010 environment.
The Exchange 2013 server is only needed for migration purposes where we wish to leverage the new features of the migration-batch functionality.
It’s important that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, right now, since the customer wish to stay on 2010.
Can you guys come up with anything to be aware of?
Oblivious we disable the Autodiscover SCP for the Exchange 2013 server, so that the clients will not hit this server. Nor will we point any URLs to the Exchange 2013
I can see that a new “Default Offline Address Book (Exch2013)” is created and set as default when EX2013 is installed. We will change this back to the default EX2010.
The server will properly take part in the Shadow Redundancy feature, and is doesn’t seem to be possible to exclude the server or avoid, unless disabling Shadow Reduncancy.
I can only come up with these 3 things that will have a "direct" impact on the environment, but any input will be highly appreciated!
BR,
Martin

Hi,
I agree with Li Zhen’s suggestion. If you don’t migrate from Exchange 2010 to Exchange 2013, we can disable add services in Exchange 2013 and don’t use it any more.
If you want that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, please keep the published server to pointed to Exchange 2010. Then the original configuration in Exchange 2010
would not be changed to the new configuration in Exchange 2013.
If you want to use Exchange 2013, then we can point the published server to Exchange 2013 and configure the virtual directories in Exchange 2013. Though all mailboxes are still located in Exchange 2010, all external requests would be proxy or redirected
from CAS 2013 TO CAS 2010 automatically.
For more information about Client Connectivity in an Exchange 2013 Coexistence Environment, please refer to:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 and exchange 2007 mixed mode questions

Similar Messages

Maybe you are looking for