Lync 2010 with Exchange 2013 UM

Hi,
I am currently in the early stages of a large migration from Exchange 2010 to Exchange 2013. We have moved some test user mailboxes over to Exchange 2013 however have stumbled at the UM integration.
We have 2 x CAS and 3 x Mailbox servers with Lync 2010.
When a user diverts his/her calls to VM, the calls just cuts off and we get "Unable to establish a connection. No connection could be made because the target machine actively refused it 1.1.1.2:5061.
We get this message for all 3 Mailbox servers that it attempts to route the call too. Mailboxes servers listen on 5063 for TLS in Exchange 2013 and these cannot be changed. So what is going wrong with my setup?
Only the CAS are members of the DialPlan (we have tried putting the mailboxes servers in the dial plan with no avail).
Shouldn't the CAS servers redirect Lync to the Mailbox servers on 5063 instead of 5061? Why is Lync trying to connect on 5061 (I know why, but how do I stop it!)
Many Thanks,
Eddie

In my case it were Active Directory attributes of object
CN=MCA1,CN=Servers,CN=Exchange AdmGr...DC=local,DC=com
The attributes
msExchUM* weren't configured at all, despite being set by GUI and PShell. I had to set them manually through ADSIedit.msc and UM began to work after restarting Lync Server.
I need to investigate further why they aren't set.

Similar Messages

Lync 2010 with Exchange 2010-2013 Migration?

We are installing Lync 2010 for the purpose of internal LAN and Internet/Federated instant messaging, video chat and desktop sharing.
There is no telephone integration and there is no Unified Messaging used in Exchange 2010.
Within a few months after rolling out Lync 2010, Exchange 2010 is going to be migrated to Exchange 2013. Outlook will remain at Office 2010 and Lync client will be 2010. We will continue to not use Exchange Unified Messaging after Exchange is
upgraded to 2013.
Are there any steps required to keep Lync 2010 working normally after the Exchange environment is upgraded from 2010 to 2013 in this scenario?

Hi
During the migration and post migration to EWS URL for the user i reachable by the Lync 2010 Client
And the outlook client is able to establish a Mapi session with the mailbox all should be fine
as best practice please have the Lync 2010 and outlook 2010 client update to the latest CU update
There is known issue when migrating from Exchange 2007 to 2013 good to know information
http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/
Please remember, if you see a post that helped you please click ;Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

Can't add multi exchange account on outlook 2010 with exchange 2013 Sp1

I did install exchange 2013 with DAG group successful, the exchange work fine now
Outlook can connect to exchange automatically and working fine
The problem appear when i need create the second exchange account by go to control panel/Mail add new profile and add new exchange profile
How can i solve the problem ?

This Problem in exchange generally appear when users mistakenly create the wrong account type or Outlook upgrades an older account profile.In these situations you need to remove that wrong account and create a New account .
When you have the wrong type of account configured in Outlook you can easily remove the account and create the correct type of account.
1 Go to Control Panel, search for the Mail. If you are using 64-bit Windows and 32-bit Outlook, it will be named as “Mail (32-bit)”
2 Double click on Mail (or Mail (32-bit)).
3 Click Email account button
4. Select the wrong account and click Remove. (If you only have one account listed in your profile,But you may need to create a New account first, set it as default then remove the wrong account.)
5. Click New, select Email Account for POP3 or IMAP accounts, or select other then the correct account type.
6. Fill in your preferred display name, email address and password on the Add New Account dialog.
Outlook will look for published account configuration for the domain and setup the account automatically.
In this event if your email provider does not publish autodiscover information, you’ll need to set up the account yourself. Check your mail providers support site for the proper configuration and then check the box to Manually configure the account at the bottom
of the Add New Account dialog.

Delete Button Disabled in Outlook 2010 with Exchange 2013

I recently switched from a 3rd party mail software to Microsoft Exchange. I have had some users ask me why the Delete button is disabled. I didn't enable any special policy to cause this, and the Delete key on the keyboard will delete messages.
The disabled Delete button I am referring to is in the Home ribbon and the right-click menu for selected e-mail(s). Is this standard behavior for Exchange, and can it be changed?

It so happens that I have an XP VM with Outlook 2007. That having been said, as previously mentioned, before testing, I (thought I) could confirm the same consistent behavior in the following configurations:
WinXP + Outlook 2003
Win7 + Outlook 2010
Each of these systems was using a different user account, and I have tried folderview repairs in EMC to no avail.
Strangely, WinXP + Outlook 2007 does not appear to exhibit the behavior. In this test case, the profile and OST were just created, but switching to folderview or moving the reading pane to the bottom did not affect the behavior.
Given that information, I proceeded to re-verify, and I hadn't checked winXP + Outlook 2003 because the computer in question had been upgraded to Outlook 2010. However, I verified the issue does still exist there. Next, I proceeded to check another
computer that I thought would be WinXP + Outlook 2003, but it had also been upgraded to Outlook 2010. This computer did not have the issue, and this leads me to a new theory about the cause (but no closer to resolution). For the record, of the
three computers (two exhibiting the issue, one not), only one has the Adobe plugin mentioned in my last post in response to Diane Poremsky, so the issue doesn't appear to be related to that.
That said, my theory follows: This is somehow related to IMAP in Outlook 2010. The computers that exhibit the issue were all previously running IMAP in Outlook 2010, and the IMAP PST filse were imported using the MailboxImportRequest feature.
I suspect this is related because of other issues that happen for these accounts. For instance, all new e-mail was only visible in OWA and not Outlook on all folders on these accounts, and I have had to have the users reset filters in the view settings
for each folder individually. I don't remember exactly which filter was somehow imported, but it definitely had to do with IMAP. This may be another red herring, but the behavior is consistent with it. I should also note that this behavior
did NOT exist when they were connected via IMAP to the old (non MS) server. I should also note that the filter behavior is somehow stored on the server (and therefore I imagine the delete button behavior could be as well), because creating a new Windows
Profile (and as such, a new Outlook profile and OST file) on a new computer did not make the IMAP filters go away.

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.Nithyanandham

Hi 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

Lync 2010 and Outlook 2013 - not talking!

I have problemns with Lync 2010 with Outlook 2013 under Windows 8.
Conversation History is not being saved.
All the patches are installed.
When I click on "show more in Outlook" it complains the accounts are not the same. I have two exchange accounts configured within the one Outlook profile. I never had this issue under Outlook 2010.
ERROR:
The email address used in your default Outlook profile is different from the sign-in address used in Lync 2010.
Change your default Outlook profile to match the sign-in address you are using in Lync, and then sign out and sign back in to Lync.
My default account is the same as my Lync sign-in name.
I have tried everything.

Mate,
There is no issue on conversation history save option, when I use Outlook 2010.
The issue only to Outlook 2013 with Lync 2010? Two observations;
=> Save IM in outlook ( greyed out ) - Lync 2010 client
=> When I check Lync config information - MAPI is not installed - Lync 2010 client
Could you advice.

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! :)

Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

Hi guys (and girls)!
Hear me up. The idea is like this:
A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
bostjanc

Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
already answered by PS CL above
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
Just install the Edge Transport Server and make sure you install ADLDS services.
as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
Where Technology Meets Talent

Lync Server Integration with Exchange 2013

Hello,
I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled.
So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
Thanks and Regards,
Nash Burns

Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

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 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.Nithyanandham

Hi ,
Please someone shed light on this case.
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Lync 2010 upgrade to 2013, 2 domains

Hello,
I have following scenario:
We are having two domains, old domain ( domain1.local ) is running Exchange 2010 + Lync 2010 with single FE & Edge and new domain ( domain2.ads ), where we are currently deploying Exchange 2013 + Lync 2013. Two-way trust exists between domains.
Useraccount & computers are joined to new domain. Users have linked mailboxes to old domain, and they are using lync with old domains credentials. E-mail address that is used is in form [email protected], and the same domain is being used on new exchange
& lync aswell.
Currently I have installed Front End, Edge & ARR as reverse proxy, and configured networks for them.
I also created a topology, However, I have not published topology yet, as I am not entirely sure what possibly could happen if I would do that.
There are some DNS-records missing on internal DNS, as i cannot figure, how I could add the SRV records without breaking the old enviroment, as users are using new domains DNS.
So Question goes,
If I publish the topology, is it possible that the old lync enviroment could malfuction, and if yes, is it possible to revert the changes ? I tried to download old topology, but it cannot be found ( probably due missing dns-entries ).
Second question is that is it possible to migrate user contactlists etc to new enviroment, as the useraccount is going to change?
Thanks In advance

Hi,
If the two domains in the same forest, only one Lync Server environment should be deployed. You can deploy the Lync Server 2013 as another Lync Pool which hosted in the Domain 2.
You can refer to the link below:
https://technet.microsoft.com/en-us/library/jj205144%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Outlook 2013 can't communicate with Exchange 2013

we're just finishing migration to Exchange 2013 and found some Outlook 2013 clients (migrated from Exchange 2010) can't communicate with Exchange 2013. even if i recreate the Outlook profile.
what worked is to reinstall Office 2013. just want to get ideas why a reinstall fixed the problem.
same outlook proxy is there in the account settings.

Hi,
What was the symptom that Outlook couldn't communicate with Exchange 2013? Could you please detail this a bit?
If the Account Settings are completely same before and after the reinstallation, we can say the cause is not on the Exchange side. While I can't guarantee the root cause based
on the provided information. A reinstallation fixes the corrupted or missing components/files in Office, but it's hard to say what has been fixed during the reinstallation.
If you still have some Office 2013 clients that have not been reinstalled, try to run Microsoft Office Configuration Analyzer Tool to quickly identify problematic configurations in Outlook:
https://www.microsoft.com/en-us/download/details.aspx?id=36852
Regards,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here.

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,
ZB

so 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

Lync 2010 with Exchange 2013 UM

Similar Messages

Maybe you are looking for