Exchange 2013 setup

Greetings
Currently i am using Exchange 2007 setup (xyz.com) and it is not published to the internet i.e. only the Domain joined users have access to it and mx records are not hosted for xyz.com
And have hosted solution (abc.com)
Now, I am planning to upgrade the Exchange 2007 to Exchange 2013 infra. But here my requirement is to use abc.com as the email address domain.
My plan is to migrate and add abc.com in accepted domain. Please suggest if this can be achieved by doing so and if yes, what other changes i need to plan as i want to have the same email address domain (abc.com) having the virtual directories by the same
name (mail.abc.com)
Please provide yours inputs.
Thanks
K2

Hi,
Thank you for your question.
By my understanding, you want to use Exchange 2013 with domain abc.com to replace domain xyz, right? If I misunderstand, please be free to let me know.
If that, we could refer to the following links to migrate Exchange 2007 to Exchange 2013 by crossing domains:
https://social.technet.microsoft.com/Forums/exchange/en-US/35828bef-3eaa-4540-b2ef-0dc1da0d77ca/cross-forest-migration-from-exchange-2007-to-exchange-2013?forum=exchangesvrgeneral
https://social.technet.microsoft.com/Forums/office/en-US/ccfaf77e-ae0f-47ac-94c4-c122df3efdf0/exchange-2007-to-2013-migrationcoexistance?forum=exchangesvrgeneral
But we suggest you install Exchange 2010 in abc.com domain, then we perform cross domain migration from Exchange 2007 to Exchange 2010, then migrate to Exchange 2013.
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

Similar Messages

Error reported after Exchange 2013 Setup (initialize-ExchangeUniversalGroups)

My Exchange 2013 setup reported the error below. Just wondering if someone has experienced this and how easy it was to fix.
Error:
The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:81ee6b49-29e5-41ff-93d4-30c547de15b1,CN=Deleted Objects,DC=ad,DC=mydomain,DC=co
on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ad,DC=mydomain,DC=co points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateRoleGroup(ADOrganizationalUnit usgContainer, RoleGroupDefinition roleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateAndValidateRoleGroups(ADOrganizationalUnit usgContainer, RoleGroupCollection roleGroups)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Roger

Thanks for replying.
My domain is actually routable (I just renamed it thinking that perhaps its more secure to withhold the info).
I had previously installed Es2013 and had to delete the VM. So this is a re-install on the Active Directory. I'm wondering if there isn't something in the "deleted folder" that is causing hassles.
Roger

Which exchange 2013 setup file should I use ?

I am seeing exchange 2013 RTM setup file for download from microsoft, as well as exchange 2013 CU3 setup file. This is my first exchange 2013 box. which file should I use to install exchange ?
Anand_N

Hi,
For new installs you should usethe most current build, CU3: http://www.microsoft.com/en-us/download/details.aspx?id=41175
Cumulative Update builds are full Exchange server installers so there is no need to install RTM version and then apply CU.
Robert Mandziarz | IT Administrator:
CodeTwo
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer
faster.

New exchange 2013 setup

my existing 2010 environment:
EXCH1 - datacenter 1
EXCH2 - datacenter 2
DAG, both Internet Facing.
Today I installed 3 Exchange 2013 CAS/Mail servers.
EXCH3 - datacenter 1
EXCH4 - datacenter 2
EXCH5 - DR site
I haven't setup mailboxes or anything yet, just external and internal URL's, a wildcard cert and internally OWA successfully proxy's via 2013 then redirect back to 2010 OWA as it should. All 3 2013 servers setup identical... :-)
However, and here is the problem - when EXCH5 is turned on users get prompted for the EXCH5 server cert, when I turn EXCH5 off they do not get prompted.
Any ideas where I should look?
info update -------------------------------------------
while the cert prompt is for the exch5 server cert when I view the cert its actually the correct wildcard public cert I'm using and want.
I have verified that all the virtual directories (via EAC) have the correct internal and external URL's and that the cert is bound to the SMTP and IIS services. One other clue, when I try to launch ecp from exch5 it redirects and logs me into OWA.
Not doing this on any other exch server.
open to suggestions :-)

Hi,
According to your description, it’s wildcard certificate in your environment. And I recommend you check the Outlook provider configuration: get-outlookprovider |fl identity, CertPrincipalName
Additionally, I’d like to confirm the name in the security alert.
If you have any question, please feel free to let me know.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

EXCHANGE 2013 - setup.exe schema prep error

Trying to install exchange 2013 sp1 (downloaded from here:
http://www.microsoft.com/en-us/download/details.aspx?id=41994).
on 2012 r2 server.
After I run (with domain admins affcourse): Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms
I recieve an error that user is not a member of schema admins and enterprise admins but I have double checked that account is in those groups. So, what am I missing there?
bostjanc

Hi Joe,
since we can make sure the user account is a member of Domain Admins, Schema Admins and Enterprise Admins groups, please also add the user to be a member of Organization Management group, don’t
just add the Domain admin to the Organization Management group, please directly add the account to the member of Organization Management group.
Then check if the account inherit permission form its parent level. To do this, please refer to the following steps:
Open ADUC, select “View->Advanced Features”;
Navigate to the user account you used, check its
Properties;
On the
Security tab, click Advanced, please make sure the inherited permission is enabled in the lower left corner. If not, please click “Enable Inheritance” to enable it.
Then use this account to login the server;
Right click “Command Prompt” and choose “Run as administrator”, then navigate to the setup file location, try to prepare schema by command:
Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms
6. If issue persists, please try Mavis’s suggestion to create a new user account, use above steps add the sufficient permission, then check the issue again.
Meanwhile, what do you mean by “single label domain”? Do we have a single domain and prepared DC/GC, or have parent/child domain configuration.
Regards, Eric Zou

Exchange 2013 SP1 Not Receiving e-mail

Hello,
Mail flow between Exchange 2010 sp3 & Exchange 2013 SP1 (update Cu5) not working.
Exchange 2013 setup is Exchange 2013 sp1 DVD
Exchange 2010 when sending mail to external it's ok.
Exchange 2010 when sending mail to exchange 2010 users it's ok.
Exchange 2013 when sending mail to External it's ok.
Exchange 2013 when sending mail to exchange 2010 users it's ok.
or
Exchange 2010 when sending mail to exchange 2013 not working
Exchange 2013 when sending mail to Exchange 2013 not working
From internet --> SMTP GW (exh edge) --> Exchange 2010 it's ok
From Internet --> SMTP GW (exh edge) --> Exchange 2013 not working.
organization;
1 AD site and 1 PDC (2012 R2) + 3 DC (1x 2008 R2 + 2 x 2003 Server) (Windows Server 2003 domain fl)
With Exchange 2010 exchange 2013 on the same subnet. Exchange 2010 physical machine, Exchange 2013 physical machine ( eth Microsoft Team Server 2012 R2 )
All server is region setting Turkey
Exchange 2010 error
451 4.7.0 Temporary server error. Please try again later. PRX4
Exchange 2013 error
451 4.4.0 primary target ip address responded with 501 5.5.4 Invalid arguments. attempted failover to alternative host, but that did not succeed. either there are no alternate host, or delivery failed to all alternate hosts. Th
thanks

Hi,
From your description, the Exchange 2013 server can't receive emails internally and externally. I recommend you follow the steps below for troubleshooting:
1. Please restart the Microsoft Exchange Frontend Transport service on CAS and the Microsoft Exchange Transport service on Mailbox and check the result.
2. Please make sure that the authentication on default receive connector is right. Here is the configuration in my environment for your reference:
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013 ECP and DAG issue

Good Day,
We have Exchange 2013 setup in Coexistence with Exchange 2007. Everything is working well except for two small issues I have noticed.
Current Setup of 2013:
SiteA:
2x CAS Servers on Windows 2012 R2 configured with windows NLB (Internet Facing).
2x MBX servers Configured in a DAG also running on Windows 2012 R2.
SiteB:
2x CAS Server on Windows 2012 R2.
2x MBX servers Configured in a DAG also running on Windows 2012 R2.
Issues I am having:
Issue 1:
When working on the ECP:
I can do all tasks on servers in the same site but get some errors when trying to do tasks on servers in the other site.
When trying to Activate a DB copy on the DAG at SiteB I get "The Microsoft Exchange Replication service does not appear to be running on Server name"
And just trying to go to the properties of a server at SiteB "An error occurred while accessing the registry on the server servername"
This happens vice versa.
I can access all servers on the same site but not between sites with some tasks.
I have made sure firewall is disabled and remote registry is indeed running but no luck.
From a network perspective all ports are open between the sites.
Issue 2:
When I reboot a DAG member with the active mailbox databases for testing outlook connectivity I get two issues.
Then I cannot access ECP at all until the server is up again.
Outlook keeps staying on trying to connect until it is reopened.
Any Ideas?
I will gladly give more information if needed.
Thank You
Riaan Rourke
Senior System Engineer

Since I don't see this with Hyper-V I'll assume this is on ESX. Please let me know it that's not correct.
In terms of virtualization best practices - whose list was that :)
There are multiple configuration things that you *MUST* do when using WLBS on ESX. It will depend upon multiple things in the environment. I'd start with this
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1556
Fix that, and chances are the other item will be also remediated.
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.

Exchange 2013 shell mailbox move requests showing up on 2010 hub server

We're in the process of migrating from exchange 2010 to 2013. All servers are patched and up to date. We have two 2010 CASs (one for external OWA use only) and a mailbox cluster. Our exchange 2013 setup is almost a mirror with the exceptions of how the exchange
server roles have changed.
Any new-moverequest commands entered from the either of our exchange 2013 CAS servers fail to show up in the EAC/recipients/migration page.
If the local move request is done in the EAC the batch(es) show up just fine.
The more perplexing part is: while I was going through a 2010 hub (looking for a different issue) I noticed ALL the batches/mailbox moves that weren't showing up in the 2013 EAC were listed in the 2010 move request section.
I can't get any info on the moves in the 2010 console (because they're 2013 jobs) but i can get statistics and such from a 2013 shell.
any ideas?

Are you running ex2013SP1 CU6? Can you try to update n check?
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 Mailbox Role Installation Error

Hi All,
I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
. HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
   at System.DirectoryServices.DirectoryEntry
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.RefreshCache()
   at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
   at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Any views on this is appreciated.
Regards
Boniface
Senior Systems Administrator

Hi,
After uninstalling the IIS, please run the following command to install prerequisites.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
In addition, please disable any third-part software for troublwshooting.
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]
Lynn-Li
TechNet Community Support

Exchange 2013 - outlook in LAN environment very slow upload but fast download - not using 'use cached exchange mode'

Hi,
I have Exchange 2013 setup in a new environment (no migration) and it is working great except I just realized there is a big problem.
I notice the following
Problem 1:
Outlook 2010 with sp2 with cached exchange mode on: when I import the pst into outlook, it imports fine but the sync is extremely slow. It uploads to the Exchange 2013 mail server at 20-70KB/sec (bytes) via LAN.
Problem 2:
Outlook 2010 with sp2 with cached exchange mode off: when I import the pst into outlook, it imports extremely slow. It uploads to the Exchange 2013 mail server at 20-70KB/sec (bytes) via LAN.
More info:
-user1 has 1GB of mail and when setting up the user on a new pc with outlook with cached exchange mode on, it downloads the mail very fast. It downloads at 40-80 Mbps/sec (bits).
-I have Exchange 2013 with CU3 with win2k12 non r2.
Why is the download so fast from Exchange 2013 but the upload to Exchange 2013 is extremely slow? How do I fix this?
Thanks

I did some more testing.
I setup a test environment with:
-Exchange 2013 SP1 on win2k12 r2
-Outlook 2010 SP2 on windows 7 sp1
-Outlook 2010 SP2 on windows 8.1
-Outlook 2013 SP1 on windows 8.1
Both windows 7 and windows 8.1 have the very slow upload issue to Exchange 2013. Windows 7 upload to Exchange 2013 is around 20-70KB/sec (bytes) via LAN. Windows 8.1 upload is a bit more responsive at around 500-600KB/sec (bytes) via LAN.
I changed the TcpAckFrequency to 1 for windows 7 and 8.1 and the problem went away. The upload on both Windows 7 and 8.1 was going at megabytes after the change.
I hope Microsoft fixes this soon.
PowerShell script to have this automated via GPO:
http://community.spiceworks.com/topic/571571-outlook-slow-after-migrating-to-exchange-2013
PowerShell Script:
$strGUIDS=[array](Get-WmiObject win32_networkadapter -filter "netconnectionstatus = 2" | select -expand GUID)
foreach ($strGUID in $strGUIDS) {New-ItemProperty -path HKLM:\System\CurrentControlSet\services\Tcpip\Parameters\Interfaces\$strGUID -propertytype DWORD -name TcpAckFrequency -value 1}

Installing Exchange 2013 CU7 fails - multiple Receive connectors

Coming from CU4 (aka SP1) and running this upgrade (to comply with hybrid requirements!), setup errors out on the transport role, that I have 2 receive connectors bound to the same IP address, and stops there.
The problem is that Exchange won't come back up for me to fix or delete the additional Recv connector.
Now what?
[12/17/2014 00:28:07.0489] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0489] [2] User specified parameters: -Identity:'MAIL\Default Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0490] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0494] [2] Searching objects "MAIL\Default Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0503] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0504] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0544] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0572] [2] Processing object "MAIL\Default Frontend MAIL".
[12/17/2014 00:28:07.0588] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0607] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0611] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0614] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0615] [2] User specified parameters: -Identity:'MAIL\Outbound Proxy Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0615] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0619] [2] Searching objects "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0630] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0631] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0669] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0696] [2] Processing object "MAIL\Outbound Proxy Frontend MAIL".
[12/17/2014 00:28:07.0711] [2] No properties changed for the object "MAIL\Outbound Proxy Frontend MAIL".
[12/17/2014 00:28:07.0711] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Outbound Proxy Frontend MAIL' have been modified.
[12/17/2014 00:28:07.0712] [2] Saving object "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
[12/17/2014 00:28:07.0712] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0714] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0717] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0718] [2] User specified parameters: -Identity:'MAIL\Client Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0718] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0723] [2] Searching objects "MAIL\Client Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0732] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0733] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0778] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0806] [2] Processing object "MAIL\Client Frontend MAIL".
[12/17/2014 00:28:07.0820] [2] No properties changed for the object "MAIL\Client Frontend MAIL".
[12/17/2014 00:28:07.0821] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Client Frontend MAIL' have been modified.
[12/17/2014 00:28:07.0821] [2] Saving object "MAIL\Client Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
[12/17/2014 00:28:07.0822] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0824] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0827] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0828] [2] User specified parameters: -Identity:'MAIL\Scanner email' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0828] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0832] [2] Searching objects "MAIL\Scanner email" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0840] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0841] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0884] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0912] [2] Processing object "MAIL\Scanner email".
[12/17/2014 00:28:07.0925] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0927] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0931] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0933] [1] The following 2 error(s) occurred during task execution:
[12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[12/17/2014 00:28:07.0965] [1] [ERROR] The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[12/17/2014 00:28:07.0965] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[12/17/2014 00:28:07.0966] [1] [ERROR] The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[12/17/2014 00:28:07.0966] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0967] [1] [ERROR-REFERENCE] Id=TransportCommonComponent___79d82f60693f413588aa8c3a58e90b41 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/17/2014 00:28:07.0980] [1] Setup is stopping now because of one or more critical errors.
[12/17/2014 00:28:07.0980] [1] Finished executing component tasks.
[12/17/2014 00:28:08.0061] [1] Ending processing Install-BridgeheadRole
[12/17/2014 00:28:40.0012] [0] CurrentResult setupbase.maincore:396: 0
[12/17/2014 00:28:40.0013] [0] End of Setup
[12/17/2014 00:28:40.0013] [0] **********************************************

Someone already found a fix for this here:
https://exchangeshare.wordpress.com/2014/07/14/exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges/#comment-1219
Just in case this link won't work some day, here was the fix:
Open ADSI edit on your Domain Controller
Go to Configuration, and drill down Services, Microsoft Exchange, First Organization, Administrative Groups, Exchange Administrative Groups, Servers, <Your Server Name>, Protocols, SMTP Receive Connectors
Find the offending connector and delete it.
Setup will resume as normal, and recreate the connector after setup completes.

Exchange 2013 - mail hops (Microsoft SMTP Server (TLS))

Hi,
I'm comparing the hops between exchange2013 and exchange2010. I notice Exchange 2013 has an extra hop when sending out emails. Please note that exchange2013 and exchange2010 are not part of the same Active Directory. They are completely separate companies.
The reason why I'm asking about the extra hop is I notice ex2013 first email takes about 1 min to get delivered externally and subsequent email sends are instant. If I haven't emailed for a while (eg. 10mins), the first email takes about 1min to get delivered
again externally and subsequent emails are instant. I don't notice this delay with Exchange 2010.
Exchange 2013 why is there an extra hop (hop #2, Microsoft SMTP Server (TLS))? Could the TLS be the reason of the delay because it is trying to talk to telus smtp via TLS but telus doesn't use TLS and exchange2013 falls back to smtp without TLS for email
send?:
Hop
Delay
from
by
with
time (UTC)
1
ex2013svr.corp.contoso1.com
ex2013svr.corp.contoso1.com
mapi
1/17/2014 5:22:07 PM
2
0 seconds
ex2013svr.corp.contoso1.com
ex2013svr.corp.contoso1.com
Microsoft SMTP Server (TLS)
1/17/2014 5:22:07 PM
3
39 seconds
ex2013svr.corp.contoso1.com 206.x.x.x
cmta1.telus.net
TELUS
1/17/2014 5:22:46 PM
4
1 Second
cmta1.telus.net 209.171.16.74
BAY0-MC2-F44.Bay0.hotmail.com
Microsoft SMTPSVC(6.0.3790.4900)
1/17/2014 5:22:47 PM
Exchange 2010 doesn't have the 'Microsoft SMTP Server (TLS)' hop:
Hop
Delay
from
by
with
time (UTC)
1
ex2010svr.corp.contoso2.com
ex2010svr.corp.contoso2.com
mapi
1/17/2014 5:20:48 PM
2
0 seconds
ex2010svr.corp.contoso2.com 98.x.x.x
skaro.stargate.ca
ESMTP
1/17/2014 5:20:48 PM
3
1 Second
skaro.stargate.ca 98.143.80.200
SNT0-MC2-F53.Snt0.hotmail.com
Microsoft SMTPSVC(6.0.3790.4900)
1/17/2014 5:20:49 PM

Are you using Self Signed Cert? If yes!!!
In Exchange 2013, Setup creates a self-signed certificate. By default, TLS is enabled. This enables any sending system to encrypt the inbound SMTP session to Exchange. By default, Exchange 2013 also attempts TLS for all remote connections.
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 Schema/AD/Domain Prep/Install & Outlook 2003

Hi
I am in the process of preparing for a migration from Exchange 2010 to Exchange 2013.
75% of our users are on Outlook 2007 Sp3 / 2010
25% of our users are on Outlook 2003.
I understand that Outlook 2003 is not supported for mailboxes on 2013.
However, can I perform the schema/AD/Domain prep and Exchange 2013 install without disrupting Outlook 2003 users?
I can then work on migrating them at a later point.
Many Thanks
Steven

Hi Steven
You can safely run all the schema extensions in preparation to Exchange 2013 setup in your environment.
But when you install the first Exchange 2013 server with the CAS role things will change fast, because you are then in a mixed coexistence scenario, where Exchange 2013 will start running the
show.
The reason why Exchange 2013 does not support Outlook 2003 is documented here:
technet.microsoft.com/en-us/library/jj619283(v=exchg.150).aspx
Outlook 2003 is not supported
To connect Microsoft Outlook to Exchange 2013, the use of the Autodiscover service is required. However, Microsoft Outlook 2003 doesn’t support the use of the Autodiscover
service.
As workaround you can always have you Outlook 2003 connect over IMAP until you get Outlook upgraded.
Even so I would really recommend starting by upgrading your clients and only then consider adding the new Exchange 2013 servers to your infrastructure.
You can confirm the Exchange Server Supportability Matrix here:
technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
A very nice entry on the Exchange team blog about exchange 2013 mixed coexistence and client connectivity:
blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
And here are a couple of articles that might help you prevent some minor bumps on your project:
technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx
msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/
Hope all of this helps you make the best decision for your environment.
Best regards.

Calendar sharing and editing between 2 exchange 2013 organisations

Not sure then.. wait for other spiceheads to reply...

Hi Guys
I recently had a client that was forced to split into 2 separate organisations each with their own exchange 2013 setup. However they will be sharing vehicles and conference rooms etc and previously they had calendars setup to manage this. I want to be able to have a calendar setup that both exchange organisations can access and edit.
I setup federated trust between the exchange servers however all I can do is view information and no one can actually make any changes etc.
Anyone know how this can be done easily?
Thanks
This topic first appeared in the Spiceworks Community

SSL for Exchange 2013 with ARR

Hi,
Need advice on the number of SSL i would need to purchase.
I know that I require to have a SSL with example: mail.domain.com & autodiscover.domain.com
How about the ARR server that I will be setting up. Refer to http://social.technet.microsoft.com/Forums/exchange/en-US/fe8d1aae-a3c9-432a-a139-7b770cb07576/new-exchange-2013-setup-vmware?forum=exchangesvrdeploy
do i need to have a SSL cert for the ARR server?
Thanks in advance!

Hi,
Just like all above saying, we do not need to generate a new certificate for IIS ARR server. We can configure
all protocols (OWA, ECP, EWS etc) published with the mail.domain.com
namespace.
When install IIS, we can export the Exchange certificate (from a CAS) and import the certificate to the local machine certificate store on the IIS Reverse Proxy, together with any required root or intermediate certificates. For more information
about it, here is a detailed article we can refer to:
Reverse Proxy for Exchange Server 2013 using IIS ARR
http://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 setup

Similar Messages

Maybe you are looking for