Exchange server 2013 & 2010 calender federation

Hi ,
I need your wise advice on this.
goal-calendar sharing in between tow different public domain a.com and b c.om .
a.com running exchange 2010
b.com running exchange 2013 in hosted environment where other company mail server running on this .
I have tried lot but no luck
acompleshed- update txt recrod for both domain at public register site
If we do get-federated domain proof for
b.com it comes with txt record while running same command on
a.com error unable to retrieve proof from external domain
Don't forget to mark helpful or answer
connect me :-
http://in.linkedin.com/in/satya11
http://facebook.com/satya.1000

Hi,
Based on my experience, here are some troubleshooting:
1. Check if all your Exchange 2013 services are working properly.
2. Check if the login account is a member of Exchange management group. You can try another admin account.
3. Check your event log and find if there is any error.
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

  • Exchange Server 2013 setup / coexistance Exchange 2010

    So started setting up Exchange 2013 and ran into a random issue regarding the OAB. Resolved by deleting/recreating the OAB in Exchange 2010.
    My issue now is setup will not complete, just tells me an "Incomplete Installation Detected" starts to resume the installation.   Upon "next" I receive just a hanging screen of "Setup Progress" which goes no where.   
    [06/12/2014 20:05:19.0860] [0] **********************************************
    [06/12/2014 20:05:19.0876] [0] Starting Microsoft Exchange Server 2013 Setup
    [06/12/2014 20:05:19.0876] [0] **********************************************
    [06/12/2014 20:05:19.0876] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
    [06/12/2014 20:05:19.0876] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
    [06/12/2014 20:05:19.0876] [0] Setup version: 15.0.516.32.
    [06/12/2014 20:05:19.0876] [0] Logged on user: DOMAIN\Admin.
    [06/12/2014 20:05:19.0954] [0] Command Line Parameter Name='sourcedir', Value='F:\'.
    [06/12/2014 20:05:19.0954] [0] Command Line Parameter Name='mode', Value='Install'.
    [06/12/2014 20:05:19.0969] [0] RuntimeAssembly was started with the following command: '/sourcedir:F: /mode:Install'.
    [06/12/2014 20:05:20.0344] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole AdminToolsRole
    [06/12/2014 20:05:21.0391] [0] Setup is choosing the domain controller to use
    [06/12/2014 20:05:21.0595] [0] The MSExchangeADTopology has a persisted domain controller: DOMAIN CONTROLLER
    [06/12/2014 20:05:22.0485] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use DOMAIN CONTROLLER
    [06/12/2014 20:05:22.0485] [0] Setup is choosing a global catalog...
    [06/12/2014 20:05:22.0516] [0] Setup has chosen the global catalog server DOMAIN CONTROLLER.
    [06/12/2014 20:05:22.0516] [0] Setup will use the domain controller 'DOMAIN CONTROLLER'.
    [06/12/2014 20:05:22.0516] [0] Setup will use the global catalog 'DOMAIN CONTROLLER'.
    [06/12/2014 20:05:22.0516] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
    [06/12/2014 20:05:22.0532] [0] Exchange organization container for the organization is 'CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
    [06/12/2014 20:05:22.0579] [0] Setup will search for an Exchange Server object for the local machine with name 'LOCALHOST'.
    [06/12/2014 20:05:22.0751] [0] Exchange Server object found : 'CN=LOCALHOST,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
    [06/12/2014 20:05:22.0751] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
    [06/12/2014 20:05:22.0751] [0] The following datacenter roles are unpacked:
    [06/12/2014 20:05:22.0751] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole AdminToolsRole
    [06/12/2014 20:05:22.0766] [0] The local server has some Exchange files installed.
    [06/12/2014 20:05:22.0798] [0] Server Name=LOCALHOST
    [06/12/2014 20:05:22.0829] [0] Setup will use the path 'F:\' for installing Exchange.
    [06/12/2014 20:05:22.0829] [0] Setup will discover the installed roles from server object 'CN=LOCALHOST,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
    [06/12/2014 20:05:22.0829] [0] 'BridgeheadRole' is installed on the server object.
    [06/12/2014 20:05:22.0829] [0] 'ClientAccessRole' is installed on the server object.
    [06/12/2014 20:05:22.0829] [0] 'MailboxRole' is installed on the server object.
    [06/12/2014 20:05:22.0829] [0] 'UnifiedMessagingRole' is installed on the server object.
    [06/12/2014 20:05:22.0845] [0] The installation mode is set to: 'Install'.
    [06/12/2014 20:05:44.0768] [0] An Exchange organization with name 'DOMAIN' was found in this forest.
    [06/12/2014 20:05:44.0768] [0] Active Directory Initialization status : 'True'.
    [06/12/2014 20:05:44.0768] [0] Schema Update Required Status : 'False'.
    [06/12/2014 20:05:44.0768] [0] Organization Configuration Update Required Status : 'False'.
    [06/12/2014 20:05:44.0768] [0] Domain Configuration Update Required Status : 'False'.
    [06/12/2014 20:05:44.0768] [0] The locally installed version is 15.0.516.32.
    [06/12/2014 20:05:44.0768] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
    [06/12/2014 20:05:44.0830] [0] Applying default role selection state
    [06/12/2014 20:05:44.0877] [0] Setup is determining what organization-level operations to perform.
    [06/12/2014 20:05:44.0877] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN-NAME.
    [06/12/2014 20:05:44.0877] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [06/12/2014 20:05:44.0893] [0] InstallModeDataHandler has 0 DataHandlers
    [06/12/2014 20:05:44.0893] [0] RootDataHandler has 1 DataHandlers
    [06/12/2014 20:05:45.0737] [0] Finished loading screen IncompleteInstallationDetectedPage.
    [06/12/2014 20:05:48.0518] [0] Setup is determining what organization-level operations to perform.
    [06/12/2014 20:05:48.0518] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN-NAME.
    [06/12/2014 20:05:48.0518] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [06/12/2014 20:05:48.0518] [0] InstallModeDataHandler has 0 DataHandlers
    [06/12/2014 20:05:48.0518] [0] RootDataHandler has 1 DataHandlers
    [06/12/2014 20:05:48.0737] [0] Finished loading screen SetupProgressPage.

    Hi,
    Let's try the following resolutions:
    1. Check if the discovery SearchMailbox is present on Exchange 2010 when you run the Exchange 2013 Install.
    2. Reinstall your Exchange 2013 server:
    Open ADSIEDIT, CN=Configuration, DC=your domain ->CN=Services ->CN=Microsoft Exchange ->CN=First Organization ->CN=Administrative Groups ->Cn=Exchange Administrative Group ->CN=Servers ->CN=Server name
    After remove the exchange server, please reinstall your exchange server to test the result.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Outlook 2010 Exchange Server 2010 to Exchange Server 2013 Features

    Hi All
    We have recently upgraded from Exchange Server 2003 to Exchange Server 2010. We are using the Outlook 2010 (32 bit) email client. When mailboxes were moved on to the new server various features inside the system were activated. For email Internal Out of
    Office Messages, External Out of Office Messages, notifications in the email recipient bar when creating emails if the user was out of office.
    What new features would be available with Outlook 2010 (32 bit) and Exchange 2013. And are they dependent on the Office Service Pack?
    Kind Regards
    Please note that I have previously posted this in another forum but was advised to post here in this forum.

    Hi,
    I find your post on Office forum:
    http://social.technet.microsoft.com/Forums/en-US/fc538968-212c-411c-8ce8-0ef1d7acfcca/outlook-2010-exchange-server-2010-to-exchange-server-2013-features?forum=outlook
    The Steve's answer is comprehensive, great links on Exchange 2013 new features and removed features.
    About "And are they dependent on the Office Service Pack?", I will give the answer.
    Based on my knowledge, when new SP releases, it include enhancements in security and compliance, architecture and administration, and user experiences.
    For example, Exchange 2013 SP1, it connects to Outlook 2013 SP1 via MAPI over HTTP.
    If you want to know more about the Exchange new features, please see Exchange Team Blog.
    Find blog about SP1 for your reference:
    http://blogs.technet.com/b/exchange/archive/2014/02/25/exchange-server-2013-service-pack-1-available.aspx
    Thanks
    Mavis
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • If the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

    if the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

    thanks for your reply!
      what's protection software can use for exchange server 2013?
    Hi,
    Most (if not all) of the bigger vendors has a product that supports Exchange 2013, so look them up.
    Exchange 2013 has some Anti-Spam and Anti-Malware Protection functionality that you can read about here:
    http://technet.microsoft.com/en-us/library/jj150481(v=exchg.150).aspx
    Martina Miskovic

  • Exchange Server 2013 to 2010 mailbox proxy is not working

    I have exchange server 2013 and exchange server 2010 in co-exist. I have 3 cas server and 3 mbx server 2013 on windows server 2012 standard, 2 hub/cas server and 2 mbx server 2010 on windows server 2008 r2. when I try to access owa of exchange server 2010
    mailbox using exchange 2013 url, I am getting the error as "something went wrong. sorry, we can't get that information right now, please try again later. If the problem continues please contact your helpdesk"
    Vishal C. Kalal | MCITP: Exchange 2010-2007 | Windows Server 2008

    Hi,
    To narrow down the cause, I recommend the following troubleshooting:
    Check if the issue happens on all users.
    Try to directly login OWA 2010  and check if it works well.
    Check the IIS log on CAS 2013 server and find the error related to OWA.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange Server 2013 OAB Web Distribution Configuration in Exchange 2010 & 2013 Coexistence.

    Hi,
    We have OAB Issue for Exchange 2010 Users in our Organization.
    We have Exchange 2010 and Exchange 2013 Coexistence.While Checking in Exchange Server 2010 Server OAB properties in Org Configuration--> Mailbox-->OAB Properties -->Distribution we are not seeing any CAS servers and Its Grayed Out.
    Please let us know How to add Exchange 2010 CAS in Exchange 2013 Web distribution.

    They made alot changes with the OAB in Exchange 2013, and it doesn't really function in the same manner as it did in 2010.  It might be best to take a look at the following blog posts from the Exchange Team, they should give you a better understanding
    on how it works and how to manage it going forward.
    http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
    http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • Mail Delivery betweek Exchange Server 2013 co-existance with Exchange server 2010

    Hello Guys
    I have a mailflow issue, hoping someone can help with detail description, below is the setup
    Exchange server 2010 SP3 with all roles in one server
    Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010
    to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole
    server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the
    queue ..
    Can someone please provide detailed solution what needs to be configured?
    MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

    Hi,
    1.please check the mailbox send and receive quota for exchange 2013 migrated mailbox.
    2.Please check the email attributes of the exchange 2013 migrated mailbox because it seems to be a problem with that particular mailbox.
    3.Then do the message tracking and that would be the only way to find the where the send messages has gone.
    4.Please check and confirm you have an enough space on the disk where exchange queue database is residing.
    I think I need to create a receive connector in the 2013 to receive from 2010 ?
    No need ,by design  exchange 2013 cas server default frontend receive connector will be having an
    entire ipv4 and ipv6 segment and anonymous connection is checked by default.
    I think I also need to create a send and receive connector for 2013 users to each other?
    No need , an intra organisation send connector and the default receive connectors in exchange will be used
    for internal mail flow between the exchange 2013 users.
    Please reply me if you have any queries .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange Server 2013 Database not showing in ECP after removal of Exchange Server 2010

    I recently complete the migration of my Exchange 2010 server to Exchange 2013. I then proceeded to uninstall the 2010 server using setup.com /m:uninstall. At the end of the process I received an error that it did not complete the uninstall.
    I checked the server and Exchanged 2010 was removed. When I checked ECP on 2013 it still showed the old 2010 server listed. I used ADSI edit and manually removed the old sever.
    Now when I log into 2013 ECP I only see the one serve but when I go into databases, none are listed. I check under the server itself and it shows the database that it is using but it is not listed under the database tab.
    If I do a search under the database tab I can find it and adds it to the list. I can then open and view details.
    My issue is, after I log out and then back in, I have to run the search to find the database again. In ideas on how to have it show up in the list like it did  before I removed the 2010 Exchange server?
    Thank you,

    Hi,
    From your description, I recommend you verify the following things for troubleshooting:
    1. Please make sure that AD replication is completely by checking the user object's homeMDB attribute. This value should contain the DN value of the Exchange Server 2013 mailbox database.
    2. Wait 30 minutes for the cache on the Exchange Server 2013 Client Access Server to clear or restart the MSExchangeOWAAppPool on the Exchange Server 2013 Client Access Server.
    For more information, here is a kb for your reference.
    Exchange 2013 Redirects to Exchange 2010 for OWA and ECP
    http://support.microsoft.com/kb/2931385
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Recover mailbox from Exchange server 2010 information store to exchange server 2013

    I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
    I would like to recover a couple of mailboxes to an exchange server 2013.
    Can anyone give me a detailed walk through of how I can accomplish this?
    Thank in advance

    Well if your AD is messed up that leaves you in a jam for sure because;
    1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
    2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
    3. Here is a good article on how to accomplish
    http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
    4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
    That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB.   We make a product that can do this (DigiScope), however if you don't
    have any budget to handle its a non-issue.
    The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
    BTW if you AD is messed up, where are you putting this new 2013 server?
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • How to : Configure Project Server 2010 to work with Exchange Server 2013

    Hi everybody. I have a problem. I did integration success project server 2010 with exchange server 2010. But now my customer use exchange server 2013. So my question is "Have a way to integration project server 2010 with exchange server 2013 ?"

    I haven't seen any document with Project 2010 and Exchange 2013. You could still try the old document with Project 2010 and Exchange 2010.
    http://technet.microsoft.com/en-us/library/ff468700(v=office.14).aspx
    It might just work.
    Thanks Gaurav Wason MCITP, PMP

  • Migration from Exchange server 2010 to Exchange server 2013

    Hi All,
    We have migrate Exchange Server 2010 to Exchange Server 2013. When I turned off my Exchange Server 2010, Outlook is not able to connect through Exchange 2013. It's prompting for user name and password again and again and nothing would happen
    after provide user name and password. So, we are not able to uninstall exchange 2010 from old server.

    Run these commands and post the update.
    Get-WebservicesVirtualDirectory -Server E2K13SERVER |Fl internalURL,ExternalURL
    Get-OWAVirtualDirectory -Server E2K13SERVER | Fl internalUrl,ExternalURL
    Get-ClientAccessServer E2K13SERVER | Fl AutodiscoverServiceInternalUri
    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.

  • Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

    Dear All,
    I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
    For example: in exchange 2010 PF:   
    In exchange 2013
               \Public Folder\sales\A1_calendar
              --->
               \ Public Folder\sales\A2_calendar 
    ---> ?
                \Public Folder\sales\A3_calendar 
    --->  ?
                \Public Folder\sales\A4_calendar 
    ---> ?
    Thanks in advance.
    Regards,
    Willis Wong

    Hi Willis,
    This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Steve Fan
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    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]

  • Exchange Server 2013 Client Mail are Return.Error is [0x80040305-0x0004de-0x00054a]

    Hi,
    We are using Exchange Server 2013.we have Outlook 2007 SP3 and 2010 SP2 client .Some clients inform mails are return.
    Return massage
    "This message could not be sent. Try sending the message again later, or contact your network administrator. Your server administrator has limited the number of items you can open simultaneously.
    Try closing messages you have opened or removing attachments and images from unsent messages you are composing. Error is [0x80040305-0x0004de-0x00054a]"
    Thanks,
    Gayan

    1) Disable TCPChimney and RSS on CAS and Mailbox Servers by running below commands
    netsh int tcp set global chimney=disabled
    netsh int tcp set global rss=disabled
    2) Disable unwanted Add-Ins in outlook that may open many sessions
    3) If above steps doesnt resolve, you can delete existing outlook profile and create new Outlook online profile

  • How can I clone a completed Exchange Server 2013 in a Lab Enviroment?

    I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken
    (1)Clone the Exchange1 and turn it off
    (2) Brought the Clone Exchange2, renamed it, change the IP configurations,
    (3) Re-ran the ADprep/Doamin prep
    (4) Checked the ASDIedit to verify the Schema/configuration in AD
    (5) Restarted I and was able to logon to the Exchange2
    (6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database
    What I did to fix this:
    (7) Rejoin the Exchange1 to the domain - and was able to logon
    (8) Unable to access ECP or OWA of any of the two servers.
    (9) Errors received - Fix the configuration file of the application
    My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?
     

    Unless you are cloning an entire environment, and then bringing it up in a seperate isolated environment, it is not supported to simply clone an Exchange Server, and then bring it online in an existing environment and rename it to save on setup and configuration
    time.
    You can script the setup and configuration of Exchange through Powershell, either with scripts or with another product controlling it - something like
    System Center Orchastrator.
    From the script side of things there are many available on peoples blogs. Check
    here.
    Edit: and to be clear, there is no need to re-run any prep tasks against Active Directory when installing a new Exchange Server, unless you are installing into a new domain as part of your Forest.
    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

  • Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

    What am I trying to do?
    I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
    error logs at the bottom of the page but the basics are in order it will throw which loop around are:
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
    What am I running?
    2 X DC on domain and forest functional level 2008R2 both writable
    1 X fresh install of Windows 2012 R2 which is domain joined
    What have I tried?
    Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
    Rebooted every server
    Run setup as Administrator
    My account is part of the domain Enterprise Admin group
    Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
    Computer Configuration Windows Settings
    Security Settings + Local Policies
    User Rights Assignment Mange auditing and security log
    Turned off firewall on DC and Exchange Server even stopped the service
    Turned off all AV on the DC and Exchange Server
    Checked I could telnet to global catalog servers on port 3268 which I can
    Checked the global catalog records existed in DNS which they all do
    Done the obvious ping tests all round which confirms connectivity
    Schema has been prepared using appropriate commands before running the setup exe
    setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
    Making sure the following path has full permissions:
    EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    Restarted Microsoft Exchange Active Directory Topology service
    DcDiag all looks good
    What have I noticed that is suspicious?
    Microsoft Exchange Transport service will not start even though both of its dependences services have started:
    Microsoft Filtering Management Service
    Microsoft Exchange Active Directory Topology Service
    It will eventually error with
    “Windows could not start the Microsoft Exchange Transport Service on local computer
    Error 1053: This Service did not respond to the start of control request in a timely fashion”
    This error is from the GUI wizard itself:
    Error:
    The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
    " was run: "System.Exception: Unable to set shared config DC.
    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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Exchange logs which have been written:
    **The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
    [01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
    '{ mydomain.com}'
    [01/20/2015 17:13:20.0084] [2] User specified parameters: 
    -DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
    No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
       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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "System.Exception: Unable to set shared config DC.
       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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
    [01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
    [01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
    Windows Event Viewer:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
    in either the local site 'Default-First-Site' or the following sites:

    Hi apl228,
    1. Please make sure the IPv6 is enabled.
    2. Please make sure the account that install Exchange server has Administrator permission.
    3. Please make sure DNS has been configured correctly.
    Thanks
    Mavis Huang
    TechNet Community Support

Maybe you are looking for