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.

Similar Messages

  • Anyone done SBS 2008 to Exchange 2013 migration - disable IPv6 on SBS?

    IPv6 enabled on ours without any problems. THanks for the links Anil, had not heard of those problems before

    Well, considering over the scenario you have mentioned, I would like to refer you on this informative article that covers few parts of causes when disabling IPV6 on Exchange 2013 Server installation : http://mike-graham.co.uk/blog/2013/08/12/disabling-ipv6-on-exchange-2013-servers-causes-problems/Here is a well documented technet resource that also provides step-wise instructions when proceeding to migrate from Exchange 2007 to 2013 by checking all the required prerequisites : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migra...Moreover, while need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on LepideMigrator for Exchange tool that provides a hassle-free environment to get this job done without having downtime or any further interruption.

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

  • Exchange 2013 / 2013 Coexistence - OWA rendering on 2010 CAS for 2013 Mailbox

    So I'm running Exchange 2013 CU2v2 alongside Exchange 2010 SP3 (both on top of 2008 R2 SP1) and I'm having a bit of a weird thing happen when migrating test users from Exchange 2010 to 2013. 
    After migrating a user from a database on the 2010 server to a database on the 2013 server, when you access OWA (through a url pointing at the 2013 server), it still appears to render on the 2010 CAS (and functions normally). If you click ? > About it
    shows properly that the mailbox server is the 2013 server, but the host address and client access server are still the old 2010 server. It seems that after a few hours it fixes itself. ECP, however, renders properly on the 2013 server immediately after migration.
    The migration completes successfully with no errors, and outlook connects fine after migration, hitting the 2013 CAS.
    I thought maybe this had to do with the Exchange Information Systems Cache, as in 2010 this was occasionally an issue:
    http://www.terminal.com/blog/bid/70313/Moving-Mailboxes-During-an-Exchange-Migration
    but the mailbox will still render on the 2010 CAS even after restarting the ExchangeIS service.
    I should also note that this behavior DID NOT occur with Exchange 2013 CU1 alongside 2010, and only started happening after upgrading to CU2v2.
    Does anyone have any thoughts as to why this is happening and what I can do to make it transition quickly to render OWA against the new mailbox? Thanks!

    Exact same symptoms here;
    Single site, 1 Exchange 2013 CU3 on 2012 Server, 1 Exchange 2010 SP3 as source for migration;
    Exchange 2013 configured as external access 'cas' owa etc. and proxy to 2010.
    Accessing an 2010 mailbox thu 2013 works correctly (OWA, ECP, ActiveSync, Outlook Anywhere etc.)
    Created new mailbox on 2010, migrated to 2013 and this mailbox is accessed/proxied thru OWA 2010. Strangely this mailbox is hosted on the proxying 2013 server now but still gets proxied. ECP for this user does instantly connect to the correct 2013 server.
    The 2010 OWA connecting to 2013 mailbox server: help | about:
    Host address: https://ex2010.corp.local/owa
    Version: 14.3.174.1
    Proxy host address: https://ex2013/owa
    Proxy version: 15.0.775.0
    Proxy server name: ex2013
    S/MIME control: not installed
    Exchange Client Access server name: ex2010.corp.local
    Exchange Client Access server .NET Framework version: 2.0.50727.5472
    Client Access server version: 14.3.123.0
    Client Access server platform: 64bit
    Mailbox server name: ex2013.corp.local
    Mailbox server Microsoft Exchange version: 15.0.775.0
    Other Microsoft Exchange server roles currently installed on the Client Access server: Mailbox, Hub Transport
    Authentication type associated with this Outlook Web App session: Basic
    Authentication type for Exchange Client Access server to Client Access server proxy session: Negotiate
    Public logon: Yes
    So to me is that the 2013 server is still proxying to 2010 and the 2010 CAS is accessing the mailbox on 2013 ;).
    This even when the mailbox is moved on the 2013 server itself!!
    How strange is this?!
    Regards,
    Arian van der Pijl
    Hello!

  • Public Folder Exchange 2010 to Exchange 2013 Migration

    hi guys
    i have Exchagne 2010 SP3 and Exchange 2013 CU2 , i have moved all my mailboxes to Exchange2013 , before that i created Exchnage2013 Address Book ( web base ) for OAB . i have Public folder Database( used for Default Address book ) -Free/Busy on exchnage
    2010 . now i don't need PF at all on Exchange 2013, So can i just Delete Public Folders from Exchange 2010 without Moving Public Folder ( free/Busyy , etcc... ) to Exchange 2013.  from exchange 2007 to exchange , we did create Public folder
    on Exchnage 2010 , Add replica , waited for sync, moved OAB generated Server as Exchnage 2010.
    as i see from deploymetn guild, there are few steps need to be done to move PF to excahnge 2013, but since i don't need PF, can i just delete it.  
    Indunil

    Hi
    I m migrating public folder 2010 to 2013
    When i do :
    Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | Format-List
    I have a lot of line like this
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-18-33-94-00-00 ». Ce dossier peut être
      lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
      23/05/2014 19:18:02 [serveur] Avertissement : échec de recherche ou de liaison de l'objet destinataire « 96-7D-85-6C-DC-A6-83-42-AC-77-A4-5E-BD-CD-52-9B » dans
      Active Directory pour le dossier public à extension messagerie « Public Root/IPM_SUBTREE/Secrétariat RC/PAYS/VENEZUELA/2006/SINCOR » avec l'ID d'entrée «
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-13-4D-8A-00-00 ». Ce dossier peut être
      lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
     it scared me, what does it means ? Do i do something wrong?
    I have let it work
    And when i check status i have this :
    Statut: Failed
    Détails status : Failed other
    Syncstages : Copying message
    Estimed transfert size : 0
    Pourcentcomplete : 95
    What do i do? Can You help me? I m a little scared right now
    Thanks

  • Exchange 2013 Migration from 2010 Test (Shared split DNS)

    Hi
    Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13
    and EXC10 ip adresses (Round Robin).
    I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
    get:
    A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
    Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?

    You should never use the server name in any of the URLs.  You should use either a CNAME or a load-balanced VIP with a generic name like mail.company.com or webmail.company.com.  Then you just point this name to the new server.  If
    you're currently using a server name, it's about time to change that first before trying to switch to Exchange 2013.
    Curently im using a generic name, mail.test.com. But that's just a normal A record on the internal DNS. So i cannot use that on both?

  • Journaling mailbox - Exchange 2013 Migrations from 2010

    hi guys
    i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
    and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
    move old one at the end .
    my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ?? 
    thank you
    Indunil

    Hi,
    Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
    And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
    So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • 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

  • 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?...

  • 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

  • Exchange 2013 migration between AD sites

    Hello,
    I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different  AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
    I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
    I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
    Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
    http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
    Any advice on performing this migration without issues?
    Thanks

    Hello,
    I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different  AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
    I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
    I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
    Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
    http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
    Any advice on performing this migration without issues?
    Thanks
    Mailbox Moves are pretty seamless, so not a concern.
    As far as the CAS namespaces. How are you handling that ? Load balancing between the CAS? Round Robin DNS? Or are you going to cut everything over at once and change DNS to point to the new server? Are both CAS accessible from the internet?
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 migration warning, cmdlet canceled

    I have an Exchange 2013 SP1 on 2012 R2 and I get this warning migrating a users mailbox from 2010
    Cmdlet cancelled. Cmdlet New-MoveRequest, parameters {TargetDatabase=XXXX, WhatIf=True, Identity=xxxxx BadItemLimit=3, BatchName=MigrationService:XXXX, CompletedRequestAgeLimit=7.00:00:00}.
    I removed user info.
    Looking here I see some similar postings but nothing in the way of an answer. It completes fine, no issues, but these warnings indicate something is off.
    Any answer for this?

    Hi,
    Based on my research, the warning may be caused by the disk storage performance on one of your Exchange servers. And here are some similar threads you can refer to:
    http://social.technet.microsoft.com/Forums/en-US/00a48c77-3ddf-4d3b-b870-425a8a6e288e/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin
    http://social.technet.microsoft.com/Forums/en-US/d93249da-22d9-496a-a5c0-529077ea33be/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin
    Thanks,
    Angela Shi
    TechNet Community Support

  • 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

  • Exchange 2013 migrations logs deleted!

    Hi,
    I migrated mailboxes from 2010 to 2013 one domain straight forward process that went successfully. The migration reports were deleted from the 2013 ECP. Any idea how to get logs or information on "when" mailboxes were moved to the 2013 servers?
    Thank you
    Ibby667

    Hi,
    I migrated mailboxes from 2010 to 2013 one domain straight forward process that went successfully. The migration reports were deleted from the 2013 ECP. Any idea how to get logs or information on "when" mailboxes were moved to the 2013 servers?
    Thank you
    Ibby667
    You can get that information using Get-Mailboxstatistics.
    Example:
    Get-Mailbox | Get-MailboxStatistics -IncludeMoveReport | FL Displayname,MoveHistory
    UPDATE: Exchange 2013 stores by default information about the latest
    5 moves in the mailbox, so that is why you can get the information even if the migrationbatch or moverequest has been deleted (MaxMoveHistoryLength="5" in  *\bin\MsExchangeMailboxReplication.exe.config)
    Martina Miskovic
    all suggestions in here will work, however i like & believe it is best to pull the moverequeststatistics vs the mailbox statistics. 
    as listed in my reply, this will help to user determine numerous things about the move that the mailboxstatistics will not show
    I agree, but if the moverequests has been deleted (default setting: 30 days) and you want to know when a mailbox was moved, then you can with Get-Mailboxstatistics.
    Martina Miskovic

  • Applying CU4 for Exchange 2013 SP1 in a mixed 2010 / 2013 Environment

    We're planning to apply Exchange 2013 SP1 CU in our mixed 2010 / 2013 environment. We'd also like to apply Exchange 2010 SP3 Rollup 5 as well. Are there any gotchas or best practices on what update to apply first?
    Orange County District Attorney

    We are planning to update our 2013 from CU5 to CU8
    and 2010 SP3 to Rollup 9
    I cant find any official documentation from MS concerning the upgrade path. Example. 
    Exchange 2013 first, then 2010. Like the above post outline. 
    I see 2010 being upgraded first thus bring version numbers closer together, reducing incompatibilities. 
    Do you still feel this is the appropriate install procedure? 
    Have you done this? 
    Djoe

Maybe you are looking for