Is it possible to remove 2010 Hub Transport entirely in an Exchange 2013 environment?

I'm using Exchange 2010 Edge Transport in our organization that I've recently upgraded to Exchange 2013. I like Edge Transport - along with our spam filter it is an effective and simple way to send and receive external e-mail - and I don't want
to get rid of it. But it seems like it needs a 2010 Hub Transport server to interact with.
Right now the only other Exchange 2010 Server I have left running in the organization is the one Hub Transport server that interacts with the Edge Server. Is there a way to undeploy this server too and connect the Edge Server directly to one of the
2013 Mailbox Servers? Or will this need to stay as part of the organization as a pair with Edge Transport?
I noticed mail flow was running just fine while the Hub Transport server was turned off. So it seems like it's possible. But I want to be able to undeploy it safely without hurting mail flow. Are there any links or white papers that show
how best do do this?
----------- Ron E Biggs Chief Tech Officer Entertainment Studios

Before you remove your HUB servers, make sure you re-subscribe the Edge server using the below steps:
On Edge Server:
New-EdgeSubscription -FileName "C:\EdgeSubscription.xml"
copy the file to one of the mailbox servers, and run:
New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeSubscription.xml " -Encoding Byte -ReadCount 0)) -Site
"ADSITENAME"
once completed, most of the tasks to manage/test your Edge sync will be via PowerShell, please see the below link for more details:
http://technet.microsoft.com/en-us/library/aa996865(v=exchg.150).aspx
Mohammad Saeed | MCSE 2003 | MCTS: Lync, OCS, Exchange This posting is provided "AS IS" with no warranties, and confers no rights

Similar Messages

How to migrate Exchange HUB transport 2007 server with Exchange Hub transport 2010.

Hi,
How to migrate hub transport 2007 server with Exchange 2010 hub transport server.
Regards
Anil

Hi Anil
You do not do an in-place upgrade of Exchange - you build new Exchange 2010 Hub Transport Servers, you can utilize existing hardware by uninstalling and installing Exchange 2010 - but you must have Hub Transport Servers that match the Exchange version in
place for all Mailbox Servers that have the same Exchange version.
Essentially there must be Exchange 2007 Hub Transport servers in place whilst there are Exchange 2007 Mailbox servers.
Read "Upgrading from Exchange 2007 Transport -
http://technet.microsoft.com/en-us/library/dd346708%28v=exchg.141%29.aspx"
Exchange 2010 will synchronise certain configuration like Transport Rules and journaling when installing the first Exchange 2010 Hub Transport server, but from then on you must ensure synchronisation yourself.
Send Connectors and Recieve Connectors will need manual configuration.
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Exchange 2010 in a Exchange 2013 Environment

I am trying to install Exchange 2010 in an Exchange 2013 environment which was migrated from Exchange 2007 earlier.
Exchange 2010 sp1 Mailbox and Hub roles installed fine however I cannot install the CAS role. Saw some references to change the OAB to a non exchange 2013 version - however that is the only version we have = OAB 2013.
This is the error I get:-
Error:
The following error was generated when "$error.Clear();
get-OfflineAddressBook -DomainController $RoleDomainController | where { $_.IsDefault } | Enable-OabWebDistribution
" was run: "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).".
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).
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:02:15
Finalizing Setup
Cancelled
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

Hi,
Please temporary remove all the OAB objects then try re-install the CAS server again.
After installing CAS server, we can re-build the OAB on Exchange 2013.
More details in the following articles:
Remove-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/aa995963(v=exchg.150).aspx
New-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/bb123735(v=exchg.150).aspx
Hope it is helpful.
If the CAS server still cannot be installed, please post the details of setup log.
Thanks
Mavis

Exchange server 2010 - Hub Transport rule not working

Hello,
I'm trying to create a hub transport rule that blocks any incoming / outgoing email with attachments larger than 10MB with an exception of a few users.
I've followed this article https://www.simple-talk.com/sysadmin/exchange/increasing-email-size-limits-for-your-high-profile-users-in-exchange-2010/.
The send connector & receive connector is at 30MB right now and the distribution group has been made.
I added myself to the distribution group which allowed me to send a 20MB size email.
If I remove myself from the distribution group, exchange still allowed me to send the 20MB email size.
Any advise is much appreciated.
Thanks,
Daniel

Hi Daniel,
Thanks for your response.
The Hub Transport server is responsible for handling transport rules. The transport rules can't work without a Hub server.
If there are any problems with Exchange, welcome to our forum.
Best regards,
Amy
Amy Wang
TechNet Community Support

Error Installing Service Pack 3 for Exchange Server 2010 (Hub Transport)

I get the following error;
"[ERROR] Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
This is one of two Hub Transport only servers. The Client Access servers upgrade without a problem.
Thanks,
Randel

Hi,
Based on my research, to remove the error, here is a solution you can refer to:
1. Run the MsiExec.exe /X {4934d1ea-be46-48b1-8847-f1af20e892c1} to uninstall the Microsoft Full Text Indexing Engine for Exchange.
2. Manually start the World Wide Web Publishing Service and IIS Admin Service then run the setup again.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 Hub Transport

Hi Spiceheads, I thought that with Exchange 2010 mailboxes will always use the local hub transport on that server first but alas I was wrong. We need to migrate an exchange 2010 box to virtual hardware, I setup and configured a new server with the old one still live, as soon as I installed the HT role on the new server mail immediately started flowing out of it first even though every mailbox and DB was still on the old server, of course this ended up causing our mail to get flagged as spam as the spf records didn't match, thankfully this lasted all of 3 minutes while I uninstalled the role from the new server, My question is - is there a way to add the HT role but still have mail flow out of the old HT server vs the new one?
I want to add the role so I can configure all the options first, including some third party software we have...

Hi allAfter a rather heated conversation with our MSP I come to you for guidance.We've recently acquired another business and need to add two new sites plus a butt hosted server to our network. The current layout is as follows (forgive my terrible diagram):Top is our business, bottom is the one we've purchase, red indicates how the VPNs are structured. We have extensive on-premise infrastructure at the Main Office (top left) so we are planning to retire my butt hosting once our systems have been merged but in the meantime we need to be able to access their system and vice versa so I am hoping for the following:In summaryNew link from my butt hosting to the Main OfficeNew link from the alt-main office to Main officeNew link from the new "other site" to Main OfficeNow, our VPNs are controlled by our MSP, after a two week delay waiting...

Exchange 2010 hub-transport server

i have 2 exchange 2010 hubtransport servers.
ideally when i send email my email should be load-balanced but emails send using hubcas1 goes fine and hubcas2 kepts in queues
suppose if i send at a time 5 mail
3 emails go through hubcas1
2 emails stucks in queue in hubcas2

Hi,
As you said you have added both the hub transport servers in the source server option of the send connector.Same time you have mentioned you don't have the smart host to deliver the emails to the internet and also the server hubcas2 can able to resolve the
external domain namespaces .Then do the following .
step 1 :Then please enable the protocol logging on the send connector to see the why the connections from the server hubcas2 is rejected to send emails to internet.
Step 2: Then do the outbound email test from EXRCA tool by using the ip address or name which is mapped on the MX record which belongs to the server hubcas2.
Please feel free to reply me if you have any queries .
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
the following command:
Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
Many thanks.

Hi Dennis,
Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
Please check your connection authentication. We can run the following command to set your Outlook Anywhere for Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
In Outlook side, please ensure the following settings in Account Settings:
In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
Regards,
Winnie Liang
TechNet Community Support

Migrating from 2010 windows nlb cas array to exchange 2013 using netscaler for HLB

i currently have exchange 2010 sp3 setup as follows
2 cas/ht using windows nlb for array.internal.com as the nlb name
2 mailbox servers using 1 dag for replication between them.
I would like to stand up 2 new CAS 2013 sp1 servers(2012 r2) and use our netscaler hlb to load balance and do ssl offloading.
id like to use the hlb to load balance and ssl offload all possible traffic not just owa, i.e. activesync etc.
the netscaler is running version 10.5.
does anyone have any thoughts on how to perform such a migration?
id like to make this as seamless as possible for the user, so no owa name change or anything like that.
thx in advance for any help.

Exchange 2013 CAS cannot be managed effectively without an Exchange 2013 mailbox server since the CAS won't run the Exchange 2013 management tools without it. Your Exchange 2013 servers should simply have both roles. There are few cases where
splitting the roles has any business value.
If what you're planning to do is within the same forest and organization, then it's a "transition", not a "migration". What you are asking to do is easy. Build the Exchange 2013 servers, configure load balancing, test
access, and then switch the DNS records to point to them.
Personally, I would skip the SSL offloading. It's my opinion that it makes the solution more difficult to troubleshoot without providing any real benefit.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

We are in the process of migrating from 2010 to 2013. Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
alex serdyukov

Hi Alex,
As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
Cumulative Update 8 for Exchange Server 2013
Best regards,
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]
Niko Cheng
TechNet Community Support

Does Edge transport server for Exchange 2013 work with Exchange 2010?

Hello everyone,
I want to install Edge transport server for my Exchange servers,
Could you tell me if Edge transport server 2013 works with Exchange 2010?
Thank you in advance

Hello
tip:
https://technet.microsoft.com/en-us/library/jj898583%28v=exchg.150%29.aspx
2 If you want to create an EdgeSync
Subscription between an Exchange 2010 Hub Transport server and an
Exchange 2013 SP1 Edge Transport server, you need to install Exchange
2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport
server.
sorry my english

Exchange 2013 upgrade from 2010 and no mail flow and cannot move mailboxes

I am in the process of moving to Ex 2013 from 2010. I have installed Ex 2013 SP1 on a new server 2012 R2. All of my Ex 2010 servers are SP3 RU 5. Ex 2013 is running and I can connect through the EAC and see all other Exchange servers and connectors that
were already in existence. Several puzzling things are happening now that the servers are in coexistence:
1) As soon as Ex 2013 was installed on the network, many Outlook users are continuously being prompted to enter their domain credentials. They can cancel the prompt and Outlook still sends/receives email. No user mailboxes are on Ex 2013 yet.
Why is this happening?
2) I am following the Ex 2013 Deployment Assistant and I get to the step to move the Ex 2010 Arbitration mailbox to Ex 2013 and the move does not happen--it just says "syncing" and never completes. I tried moving a test mailbox from Ex 2010
to the 2013 database and I get the same result. I created the move request on the Ex2013 server and I see it as queued on the Ex2010 server, so I know they are "talking" to each other. However, when reviewing the status of the move I
see "MapiExceptionNoAccess: Unable to open message store".
3) There seems to be no mail flow on the same Ex2013 server or between the Ex 2010 and 2013 servers. I created two new test user mailboxes in Ex 2013. The Ex2013 mailboxes cannot send/receive to each other or to Ex 2010 users. This
seems strange, unless I am completely missing something in the Ex 2013 install?
I know this is a lot in one post, but following the Deployment assistant, I was hoping this would be something that others have faced. Thanks for any input here.

Does the below points already fit for you.
Exchange 2013 Supported with the following minimum versions of Exchange:
1) Exchange*** 2010 SP3 on all Exchange 2010 servers in the organization, including Edge Transport servers.
2) Exchange 2013 CU2 or later on all Exchange 2013 servers in the organization.
*** If you want to create an EdgeSync Subscription between an Exchange 2010 Hub Transport server and an Exchange 2013 SP1 Edge Transport
server, you need to install Exchange 2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport server.
Thanks Prem P Rana MCSA Messaging 2003 MCSE 2003 Server MCTS MCITP Exchange 2007, 2010 Gurgaon, India http://blogs.msexchange-experts.com

Edge Transport Server - Exchange 2013 coexistence Exchange 2007

Hi Exchange-Gurus,
We have one Exchange Org.
sub AD Domain1: A.domain.com (with Exchange 2007 SP3 R10)
sub AD Domain2: B.domain.com (with Exchange 2013 CU6); DMZ contains Exchange Transport Server - Exchange 2013
Is it possible to install within the DMZ of AD Domain1 a Edge Transport Server - Exchange 2013?
Thanks.
Guitarman

Hi Guitar,
Thank you for your question.
Is it possible to install within the DMZ of AD Domain1
an Edge Transport Server - Exchange 2013?
A: Yes, we could create an Exchange 2013 Edge server on the DMZ of AD domain1.
Notice: Before we create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, we need to install Exchange 2007 SP3
Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

OWA problem Exchange 2013 coexistence with 2010

Hi all,
I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
to access OWA with a mailbox that is still on 2010 it fails with the following error:
something went wrong
A problem occurred while you were trying to use your mailbox.
X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
X-OWA-Version: 15.0.913.21
X-FEServer: <name of 2013 server>
X-BEServer: <name of 2013 server>
Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
Any help is greatly appreciated!
Best regards
Daniel

Hi,
How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
Regards,
Winnie Liang
TechNet Community Support

Primary mailbox (on Exchange 2010) and Personal Archive (on Exchange 2013), possible?

Current environment is Exchange 2010 SP3 RU5 supporting 4,000 Users. Client estate is Outlook 2010 SP1 going on SP2.
We're pulling our Archiving solution away from 3rd party and back into Exchange. Implementing a new set of Exchange 2010 Servers (old DAG or in a new Archive DAG) would be easy. But is there Exchange 2013 stepping stone potential?
Can the Archive DAG / Archive mailboxes be on 2013? i.e. for any given User, leave their primary mailbox on Exchange 2010 and create new Archive mailbox on 2013.
I want to avoid implementing 2010 Archive Servers and then go 2013 Archive 6 months or a year later.
This article suggests 'no':
http://technet.microsoft.com/en-gb/library/dd979800(v=exchg.150).aspx
"Locating a user’s mailbox and archive on different versions of Exchange Server is not supported."
I've found little info but the odd statement here / there.
Is this the latest position? Is it that cut & dry? Anyone tried it? Why won't it work (or will it but it's not supported)?
Thanks!

<I had a response from MS>
Below is a summary of the case for your records:
Symptom:
=============
Is it possible to implement a 2013 environment to host the Archive mailboxes? i.e. for any given User, their primary mailbox is on Exchange 2010 and their Archive
mailbox is on 2013.
Resolution:
=============
It’s not supported to have a user’s primary mailbox reside on an older Exchange version than the user’s archive. If the user’s primary mailbox is still on Exchange
2010, you must move it to Exchange 2013 before or at the same time when you move the archive to Exchange 2013.
http://technet.microsoft.com/en-us/library/jj651146(v=exchg.150).aspx
as per the repro in our lab, having the archive mailbox in higher version of exchange would fail with the error above
<the scenario isn't completely relevant, looks like he's trying to put the Primary on 2013 and not the Archive, no matter, we've established there are problems, question is whether they are looking into this area / to patch, they go on...>
At this point in time we don’t have a conformation from the product team, if the above would change in the future exchange versions.
<MS did say on the call that they were not looking at fixing it, naturally this isn't a "never", as per previous statement - they can't commit 100% to the future, but they've provided me the answer - they are not currently looking at resolving/providing
this as a migration scenario, end.>

Is it possible to remove 2010 Hub Transport entirely in an Exchange 2013 environment?

Similar Messages

Maybe you are looking for