With the recent releases of Exchange Server 2013 RTM CU1, Exchange 2013 sizing guidance, Exchange 2013 Server Role Requirements Calculator, and the updated Exchange 2013 Deployment Asistant, on-p...
Updated Mar 24, 2020
Version 3.0
Blog Post
11 MIN READ
Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
@Martijn, going with all OA in Exchange 2010 is perfectly fine. There will be an increase of connection counts due to HTTP being a unidirectional protocol unlike RPC and you may have to tweak the CAS a bit (or add more of them) depending on how many active connections your environment has. (See; http://support.microsoft.com/kb/2832198/en-us?sd=rss&spid=13965)
@Steve, you will only need your HTTP SPNs in an Exchange 2013 environment. However, if your public folders are still on legacy Exchange versions I would not yet recommend going to Kerberos. Legacy Exchange versions do not support "negotiate" for authentication type, which is required for Kerb auth to work in 2013, and your PF connections will fail. You can utilize Basic or NTLM enabled until your PFs are on 2013, and then you can switch to Negotiate. The same kind of script of kerb is in the .V15Scripts directory. You may notice a warning when running the script that it says it wasn't tested with 620.29 (The RTM CU1 release), but it works fine.