Exchange 2013 migration and Lync server

hi guys,
i wanna upgrade my exchange 2010 to 2013 in our company.
but i faced with a question
will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
plz help me 
thanks guys

Hi,
you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
Here is a guide for enabling IM in OWA:
http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
Just remember to point DNS to the New Exchange 2013 server and it should be fine.
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! Off2work

Similar Messages

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

  • Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

    Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
    I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
    Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
    Error look like - cannot find exchange server.
    I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
    Someone have the same problem with migrated mailbox? How to solve it?
    Truly, Valery Tyurin

    You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
    Moreover, you can try this utility (
    http://www.exchangemigrationtool.com/ ) to accomplish this task.

  • Step by Step Migration from Lync Server 2010 to Lync Server 2013

    Hi All,
    I just finished migration from Lync Server 2010 to Lync Server 2013 (for enterprise servers) in my lab environment. After that I started to write article series that contains five parts. You can see below first three parts and I think , I will upload
    rest of parts until this weekend.
    Part 1 - http://www.oiboran.com/?p=1073
    Part 2 - http://www.oiboran.com/?p=1109
    Part 3 - http://www.oiboran.com/?p=1140
    Hope to be useful,
    Regards
    Part 4 http://www.oiboran.com/?p=1171
    Part 5 http://www.oiboran.com/?p=1219 (added on 20.12.2012)
     

    It's working for me now, so maybe it's back up.
    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 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

    I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
    on our system".
    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
    I've followed this post as a guide but it hasn't resolved my issue.
    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
    My Exchange environment looks like this:
    Site 1:
    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13
    Site 2:
    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13
    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
    Any help is greatly appreciated. I'd love to get rid of Unity. 
    EDIT:
    I just found this event in the event logs:
    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
    but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    9.1.2 I think it is, we upgraded to avoid the known DNS bug
    I cant see how to PM you either
    The crux of it was outlined below with some tweaks
    http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
    as any other CAS based service - point to 2013, and it will handle the rest

  • Exchange 2013 migration, disable SSLOffloading on 2010 CAS servers

    We just going through the Exchange 2013 migration from Exchange 2010. I have one or two questions when following the Exchange deployment Assistant. We have HLB where the certificates and we enable SSLoffload on the CAS server. So we don't have public CA's
    on our CAS 2010 servers.
    So on the documentation it says to run this command, were it will disable SSLOffloading and change to Basic authentication. Will my running outlook 2010 clients start getting certificate errors and  will they work as normal ?
    Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 14*") -And ($_.ServerRole -Like "*ClientAccess*")} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod
    Basic -SSLOffloading $False -ExternalHostName $Exchange2013HostName -IISAuthenticationMethods NTLM, Basic

    We have OA enabled on all CAS 2010 servers with NTLM authentication and SSLoffloading box checked. We have also setup our CAS2013 and is running. My question above was that if I ran that command, Will I break anything since all my users
    are still on Exchange 2010 mailboxes.
    Then as I mentioned, that command will do nothing as OA is already enabled on CAS 10.  It would only make a change if CAS10 had OA disabled. 
    Where {$_.OutlookAnywhereEnabled -Eq $False}
    Where {$_.OutlookAnywhereEnabled -Eq $False}
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

    Dear all
    During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
    wa' on 'MONAMBX2'.".
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
    und on 'MonaDc1.mona.local'.".
    Any advice please !!

    I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive.  Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
    error messages saying the database does not exist.  It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting.  To get around it, I deleted the database and created a new one on the drive
    where we wanted it.
    I discovered this when I was configuring the Antispam settings.  I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server.  The shell on 2013 was making changes to 2007.
    I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens.  Or maybe my issues will be fixed if I just remove the Exchange 2007 server?  I'm not ready to do that yet because I can't configure the spam filtering
    on 2013 yet with its shell not being able to make the changes that we need.
    I don't know if your environment is in coexistence mode like mine.
    Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server.  Does this happen after the 2007 server is removed?

  • Can we use SSRS in sharepoint 2013 standard and sql server standard edition

    can we use SSRS in sharepoint 2013 standard and sql server standard edition
    MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

    Yes you can. You do lose some features:
    http://msdn.microsoft.com/en-us/library/cc645993.aspx#Reporting
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Server 2012 and Exchange 2013 Migration from SBS 2011

    Server UpgradeI'm migrating an SBS 2011 server to a new machine with Server 2012 R2 and a Hyper-V server running Exchange 2013. I've set up the new machine, all is running well in a test environment. I now want to migrate the old server to new. These are the steps I'm going to take and I wanted advice for any modifications or errors. 1. Demote DC on Server 2012 that I set up to test. 2. Join new Server 2012 to existing SBS 2011 domain. 3. Promote Server 2012 to DC. 4. Join the Hyper-V Server 2012 to the Server 2012 domain.5. Migrate Exchange 2010 on the SBS 2011 Server to Exchange 2013. 6. Transfer FSMO role from SBS 2011 Server to Server 2012 DC. I'll copy shared data files using robocopy.The only things I'm not sure about is the FSMO order, when to do that and the fact that I already have Exchange 2013 installed in the test...
    This topic first appeared in the Spiceworks Community

    I recently acquired a SuperMicro chassis that has a SAS2 expander backplane. It has SFF-8087 ports on it.http://www.supermicro.com/manuals/other/BPN-SAS2-846EL.pdfI made a post on another forum and someone mentioned that the card couldn't be used with that backplane since it's a SATA controller, however, the backplane is both SAS and SATA device compliant, it's only the RAID controller, as far as I know, that is a "SATA II" controller, and not a SAS controller.So, I couldn't find anything in the official documentation of this controller on whether or not it was able to control SAS devices. The card itself has a 3 SFF-8087 ports though, couldn't this theoretically still be used with a SFF-8087 to SFF-8087 cable(seen below)since the backplane is a SAS/SATA backplane?...

  • Exchange Server 2013 migration and high avalability

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

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

  • How to configure AD on windows 2012 server for Exchange 2013 internal and external email flow

    Dear Experts,
    I have to configure exchange 2013 on Windows server 2012 STD. Company has registered Static IP addresses and can get the MX record pointing to any of this Static IP.  
    The registered domain name is e.g.  contoso.com. 
    a. What should I use as domain name on AD? contoso.com or contoso.local
    b. Is it recommended to have two different servers  for AD and Exchange?
    c. What should be my connector settings for mail flow?
    d. how can I set 2 email servers in company for load balancing?

    Hi,
    a, I suggest use contoso.com as domain name. It is convenient to add urls into our certificate for internal and external mail flow.
    b, Recommended that installing AD
    and Exchange Server on two separate
    Servers. If Exchange Server downed unfortunately, it can prevent AD server from crushing at the same time.
    c, Found some articles for your reference:
    Configure Mail Flow and Client Access
    http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
    Configuring Outbound Mail Flow in Exchange Server 2013
    http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/
    d, Load Balancing
    http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • On-Site Conversation Translator and Lync Server 2013

    To Whom It May Concern,
    I'm looking into deploying Lync Server 2013 Standard and I was curious as to whether there is a way to install the Conversation Translator as a service on-site.  Meaning not using the service on the Internet.  Similar to IBM's Websphere Application
    Server where I can install a local instance on a closed network, have Sametime Connect point to that service, and translate the IM conversation.
    I remember talking to a few MS folks a couple years ago, and they mentioned that it was going to be available as an add-on (or component) of Lync Server.  Is this possible?
    Thanks,
    Brendan

    There is a Client side plugin, take a look at:
    http://channel9.msdn.com/posts/Lync-2013-Translate-a-conversation-from-one-language-to-another-in-real-time-part-one
    http://voipnorm.blogspot.ca/2012/11/lync-2013-enabling-conversation.html
    http://code.msdn.microsoft.com/office/Lync-2013-Translate-a-a849e513
    Please mark posts as answers/helpful if it answers your question.
    Blog
    Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

  • Exchange 2013 SP1 and SCOM 2012 R2

    Hi there, 
    Hopefully someone can assist me with this issue, if it is one... 
    I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
    76 users in total, roughly 80GB of Public Folders.
    I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected. 
    Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues. 
    Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well. 
    Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010. 
    A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect. 
    Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy. 
    Attempted to reran the probe for EWS and got the error below:
    Is there perhaps anyone that can assist me with these errors?
    Cheers

    FYI... IIS ARR is not supported for Exchange Server.
    Check in event log if you are getting anything related to the issue.
    About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
    Are those mailboxes still moving or in move request?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 Migration in a complicated network environment

    Hello everyone,
    I am conducting an Exchange migration from 2007 to 2013. The client have 4 geographical site and each of those site have an Exchange CAS server on it. The sites
    have also DCs on each of them. 
    There's two types of connection between sites one is MPLS that's 50MBPs and the other is p2p that's 2mbps. Client wants to have only 2 Exchange 2013 Server with
    all the roles collocated on them and DAG between them.
    I already have installed and configured DAG on the servers. One server is located in the Central data center and the other is located on a second geographical
    site that also have a disaster recovery data center.
    Client wants to configure the MAPI network on Exchange 2013 to use the P2P 2mbps connection and use the MPLS 50mbps connection for the replication NIC. 
    The problem is that both networks MPLS and P2P have the same IP subnet, same gateway e.g. (10.1.1.0/16) but a range of those IPs are configured on the router to
    use the MPLS connectivity.
    I have tried to add static route to the replication network to use the gateway but when trying to add a copy of a centralized database to the DAG. the DAG copies
    the connection over the P2P line. 
    Is it possible to configure this with the same subnet or do I need to have the mpls connection on a totally different network and subnet? 
    I would appreciate all your suggestions and I  am very sorry for my terrible explanation because I am my self confused about their network topology. 
    I will prepare a visio diagram of the network, IPs and everything to clear everything out.
    Mohammed JH

    I have solved the issue, it was very simple but due to lack of knowledge about networking it got complicated. the way I have configured the replication networks between both sites was that each replication NIC on each site should have a different subnet
    that configured on the MPLS network with the high speed and bandwidth. they must be different on each site. 
    For each replication NIC a persistent static route should be configured on Exchange server to tell the NIC where to direct traffic exactly. 
    After configuring the subnets on the replication NIC, I added the static routes and the replication started to work flawlessly. 
    This is the static route command that I run on the first machine on the first site, it tells the Replication NIC to direct traffic to the subnet network on the second site through the gateway 10.1.1.1 
    route -p add 10.5.1.0 MASK 255.255.0.0 10.1.1.1 
    On Exchange on the second site, I had to run the same command as well
    route -p add 10.1.1.0 MASK 255.255.0.0 10.5.1.1 
    thanks everyone for the help.
    Mohammed JH

  • Double prompts for Exchange 2013 migrated users: "The microsoft exchange administrator has made a change that requires you to restart outlook"

    I have Exchange 2010 SP3 in my environment and am migrating to Exchange 2013. Whenever a mailbox is migrated, the Outlook 2013 client will prompt the user with a "the exchange administrator has made a change that requires you to restart
    Outlook". When the user does so, he or she is prompted again. After he or she closes and reopens Outlook for the second time, the issue is gone permanently.
    I've seen a number of other posts about repeated prompts like this but I haven't yet found one or someone gets exactly 2 prompts for each client and no more.
    A couple of pieces of information that may be relevant:
    1. On exchange 2013, the authentication method for the internal host name is NTLM
    2. I have not yet migrated public folders from Exchange 2010. I plan to do that after the mailbox migration is complete.
    Thanks in advance for your help.

    Hi,
    From your description, after mailboxes are moved from Exchange 2010 to Exchange 2013, users receive the following prompt when opening Outlook.
    The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook.
    In order to solve this issue, you need to apply the Outlook update that is described in KB 2863911.
    For your reference:
    Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
    https://support.microsoft.com/kb/2934750?wa=wsignin1.0
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

Maybe you are looking for