New Deployment of Exchange Server 2013.

Hello All,
Good Day !!
We are planning to install Exchange 2013  Mailbox and Client Access on single server ( Windows Server 2012 Standard).
Currently Active Directory roles runs on windows server 2008R2 Sp1.
Its a new deployment for exchange as currently we are using Godaddy email server ( Can we migrate all our emails from Go daddy to our exchange Server).
Also confirm  current active directory will support the installation and deployment of Exchange Server 2013.
How much HDD, RAM and  CPU cores are required to support exchange Server Mailbox and Client Access roles( Users are 30 ).
How many Static IP's and SSl certificates are required for exchange.
Atlast as i said its new deployment please suggest if anything else is missing from my end. 

Hello,
I recommend using professional cheat-sheet articles for Exchange 2013 sizing:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part1.html
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part2.html
The server's requirements depend on many factors ie. number of emails received/sent, mailboxes sizes etc.
In addition your AD environment's level supports Exchange 2013 deployment. You will need only prepare your schema and forest for Exchange installation. You will need also at least one public IP address and SSL certificate for that server.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
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.

Similar Messages

  • Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

    Hi people,
    What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
    Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
    Thanks

    Hey AlbertWT,
    Can you clarify exactly what you mean when you say "server patching?"  Do you mean patching at the ESXi host level or something within the guest?
    As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer.  Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role.  NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
    If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
    Matt
    http://www.thelowercasew.com

  • New installation of Exchange Server 2013

    After installing Exchange 2013 on a Server running Microsoft Server 2012 I am unable to bring up the (EAC) Exchange Administration Center. I am entering the addresshttp : // <servername> / ecp as listed in my instructions and i am getting
    ERROR 404 from the IIS8 Server.
    404 - File or directory not found.
    The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

    Hello,
    If you to go check on Exchange CAS server, can you access it?
    Did you get any error when you install the CAS server?
    Thanks,
    Evan
    Evan Liu
    TechNet Community Support

  • Exchange Server 2013 deployment on VMware Fault Tolerance

    Hi People,
    Instead of using the DAG feature on the Exchange Server 2013, so what is the caveats in deploying the Exchange Server 2013 stand alone and then implementing the Vmware FT or at least HA to give the availability at the Hypervisor level ?

    Hey AlbertWT,
    With Exchange 2010, try not to think of entire servers as being active or passive.  Instead, think of database copies as being active or passive.  Your Mailbox role virtual machine can contain both active and passive copies of databases within your DAG.
    Think of a scenario where you have three virtual machines running the Exchange 2010 Mailbox role and you have a total of three databases.  You would have an active copy of each database and then presumably two passive copies as well.  That there is only one active database on a Mailbox server at a time, and if that server fails there are two other copies that can come online automatically.
    In the case of vSphere HA, if you lose a host that's running a Mailbox server, that active database would automatically be brought up on one of the two surviving Mailbox servers. vSphere HA would then automatically restart that failed virtual machine on another host and you'd quickly be back to having three Exchange Mailbox servers online.
    Does that help clarify things for you?
    Matt
    http://www.thelowercasew.com

  • Exchange Server 2013 SP1 - Internal Email Flow slowness

    Hi Fellows,
    I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
    I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
    When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
    Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
    Header analysis shows the message exchange between mailbox servers is taking time. any clue?
    Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
    Network communication, Storage performance, Server performance are all as good as we love to.
    Thanks.
    J.A

    Hello,
    When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
    Cara Chen
    TechNet Community Support

  • Exchange Server 2013 Logs Out of Control

    I have a fairly new install of Exchange Server 2013 running in full production. Everything has been great except for the high level of log files that are generated on a daily basis. I am able to truncate the Transaction logs everyday with a Server Backup,
    but that still does not help me with the other constantly growing log files in C:\Program Files\Microsoft\Exchange Server\V15\Logging. Is there any way to set these to automatically purge after a set amount of days? I have found resources that discuss setting
    up a powershell script that will delete everything after a set amount of days, but I want to know if anything in Exchange 2013 will allow me to do this. I am getting tired of expanding my VM disk. Any help would be greatly appreciated. 

    Unfortunately Exchange 2013 creates alot of log files that it does not clean up on it's own.  While there isn't a way to tell Exchange to clean up the files after X number of days, there is a very helpful script someone else has already written that does
    the work for you. He has 2 versions, 1 that you have to put on each individual server (I like that one in case I lose the server I put the script on) or 1 that you can run on 1 server that takes care of all of your Exchange Servers.
    http://www.c7solutions.com/2013/04/removing-old-exchange-2013-log-files-html
    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

  • I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    Hi,
    From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
    Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
    http://support2.microsoft.com/kb/2997209
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • New Exchange Server 2013 in a Exchange 2007 Org, can't get cu's to install

    Hi,
    We have an Exchange Server 2007 in our organization. I installed an Exchange Server 2013 but could not get the CU3 to install, would throw exceptions. I tried CU2 and it got a lot further but failed to start a service near the end. Don't ask for specifics
    as I got frustrated and blew this machine away and installed a fresh VM. I read that you can install the CU's as if they are a fresh installation. I tried this but it fails saying "the Exchange server is in an inconsistant stet....recover". There
    IS no Exchange server yet!!
    What am I doing wrong? I used the command line for CU3, like: setup /mode:install /roles:ca,mb,mt /IAccept blah blah blah. I didn't set powershell execution policy, not sure if that was it. Are there switches I am missing? I want to see if I can install
    the Exchange CU3 right from the get-go.
    HeLp!

    Hi,
    According to the error message, this issue may occur if the previous Exchange installation or un-install failed to complete. This situation leaves the Exchange server
    object in Active Directory and prevents a new installation.
    We can try:
    1. Install ADSI Edit.
    2. Launch ADSI Edit. To do this, click Start, click Run, type adsiedit.msc in the text box, and then click OK.
    3. Locate the Exchange server object by going to the following location: CN=Configuration, DC= Domain Name, DC=com, CN=Services, CN=Microsoft Exchange, CN=<Organization
    Name>, CN=Administrative Groups, CN= <Exchange Administrative Group>, CN=Servers, CN=<Server Name>.
    4. Delete the server object.
    5. Remove the Exchange server's machine account from Security groups Exchange Servers and Exchange Install Domain Servers.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Best practice on mailbox database size & we need how many server for deployment exchange server 2013

    Dear all,
    We have  an server that runs Microsoft exchange server 2007 with the following specification:
    4 servers: Hub&CAS1 & Hub&CAS2 & Mailbox1 & Mailbox2 
    Operating System : Microsoft Windows Server 2003 R2 Enterprise x64
    6 mailbox databases
    1500 Mailboxes
    We need to upgrade our exchange server from 2007 to 2013 to fulfill the following requirment:
    I want to upgrade the exchange server 2007 to exchange server 2013 and implement the following details:
    1500 mailboxes
    10GB or 15GB mailbox quota for each user
    How many
    servers and databases  are
    required for this migration<ins cite="mailto:Mohammad%20Ashouri" datetime="2014-05-18T22:41"></ins>?
    Number of the servers:
    Number of the databases:
    Size of each database:
    Many thanks.

    You will also need to check server role requirement in exchange 2013. Please go through this link to calculate the server role requirement : http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
    2TB is recommended maximum database size for Exchange 2013 databases.
    Here is the complete checklist to upgrade from exchange 2007 to 2013 : http://technet.microsoft.com/en-us/library/ff805032%28v=exchg.150%29.aspx
    Meanwhile, to reduce the risks and time consumed during the completion of migration process, you can have a look at this proficient application(http://www.exchangemigrationtool.com/) that would also be
    a good approach for 1500 users. It will help you to ensure the data security during the migration between exchange 2007 and 2013.

  • Deploying Windows Server 2012 and Exchange Server 2013

    Hi All,
    Our Clinet is planning to implement Exchange Server 2013 as an email solution. There is no Active Directory Domain exists in the environment. So, we have planned to configure a Windows Server 2012 R2 Standard as a Domain Controller and Exchange
    Server 2013 Standard would be installed on another Windows Server 2012 R2 Standard.
    The setup would be for 250 users. Please guide me about the Cost of OS + Exchnage and CAL for 250 Users.
    Warm Regards,
    Prosenjit Sen
    Thanks & Regards, Prosenjit Sen.

    Another option would be to consider signing up for Office 365 instead of setting up the hardware and software for such a small number of users.  It will take a long time for the cost of the hardware, maintenance, and support to be less costly than Office
    365, if it would ever be less expensive.  There is a lot of maintenance required for Exchange, so unless your client already has someone experienced in configuring and maintaining Exchange, there is a lot of expense in bringing someone up to speed to
    perform those functions capably.
    Just a suggestion.  I do not work for Microsoft and I have no financial incentive to propose an Office 365 environment.  I just know that if I were running my own business, I would have to be convinced that my business required its own internal
    mail system when there are so many fully functional and capable mail systems available via subscription.
    . : | : . : | : . tim

  • Exchange Server 2013 and Remote Access VPN on a single server running Windows Server 2012?

    Just by way of background, I have been installing and administering network servers, e-mail systems, VPN servers, and the like for many years.  However, my involvement with Exchange and Windows Server has been mostly on the forensics and data recovery
    level, or as a (sophisticated) user.  I have never tried to deploy either from scratch before.  My deployment experiences have been mostly with Linux in recent years, and with small private or personal "servers" running such cutting edge
    software as Windows XP back when it was new.  And even NetWare once.
    When a client asked me if I could set up a server for his business, running Exchange Server (since they really want Outlook with all of its bells and whistles to work, particularly calendars) and providing VPN access for a shared file store, I figured it
    could not be too difficult given that its a small business, with only a few users, and nothing sophisticated in the way of requirements.  For reasons that don't bear explaining here, he was not willing to use a vendor hosting Exchange services or cloud
    storage.  There is no internal network behind the server; it is intended to be a stand-alone server, hanging off a static IP address on the Internet, providing the entirely mobile work-force of about 10 people with Exchange-hosted e-mail for their computers
    and phones, a secure file store, and not much else.  If Exchange didn't need it, I would not need to install Active Directory, for example.  We have no direct need for its services.
    So I did the research and it appears, more by implication than outright assertion, that I should be able to run Windows Server 2012 with Exchange Server 2013 on a server that also hosts Remote Access (VPN only) and does nothing else.  And it appears
    I ought to be able to do it without virtualizing any of it.  However, I have spent the last three or four days fighting one mysterious issue after another.  I had Remote Access VPN working and fairly stable very quickly (although it takes a very
    long time to become available after the server boots), and it has mostly remained reliable throughout although at times while installing Exchange it seems to have dropped out on me.  But I've always been able to get it back after scrounging through the
    logs to find out what is bothering it.  I have occasionally, for a few minutes at a time, had Exchange Server willing to do everything it should do (although not always everything at the same time).  At one point I even received a number of e-mails
    on my BlackBerry that had been sent to my test account on the Exchange Server, and was able to send an e-mail from my BlackBerry to an outside account.
    But then Exchange Server just stopped.  There are messages stuck in the queues, among other issues, but the Exchange Administration Center refuses now to display anything (after I enter my Administrator password, I just get a blank screen, whether on
    the server or remotely).
    So, I am trying to avoid bothering all of you any more than I have to, but let me just begin with the basic question posed in the title: Can I run Exchange Server (and therefore Active Directory and all of its components) and Remote Access (VPN only) on
    a single Windows Server 2012 server?  And if so, do I have to run virtual machines (which will require adding more memory to the server, since I did not plan for it when I purchased it)?  If it can be done, can anyone provide any pointers on what
    the pitfalls are that may be causing my problems?  I am happy to provide whatever additional information anyone might like to help figure it out.
    Thanks!

    An old thread but I ran into this issue and thought I share my solution since I ran into the same issue. Configuring VPN removes the HTTPS 443 binding on the Default Site in IIS for some strange reason; just go and editing the bindings, add HTTPS and things
    should be back to normal.

  • 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

  • Upgrade Exchange server 2013 to CU7 error

    Dear Microsoft Team
    I have Exchange server 2013 SP1 and upgrade it to CU5 it is working normal
    But wen I try to Upgrade it to CU7 I got this error massage
    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.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.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)".
    Best Regards
    Rawa Zangana

    Hi Rawa Zangana,
    According to the error message, it seems that the Global Catalog not reachable from DC.
    Please perform following steps.
    1. Port 3268 listened on DC.
    2. Enable Global Catalog role on all DCs.
    3. Restart Exchange Server 2013 CU5.
    4. Check whether Event 2080 found on all DCs, Event 2080 means that AD connectivity works fine.
    5. Repeat CU7 installation.
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Error occurred at the 7 of 15 step of Microsoft Exchange Server 2013

    Hi all to every techies ....
    I'm a new to exchange server 2013 , I tried to install exchange server 2013 on windows server 2012 but couldn't get the success , It stops either 7 or 8 step of 15 , I tried to google it out but can not getting any progress , I tried to remove it , I deleted
    by using ADSI Edit then I removed from the IIS then I delete the Microsoft folder from the Installed directory , and also I removed it from the registry editor as well , Thing thing is pulling my hair out my scalp , Any related help highly appreciated , 
    The registry key (pickup / transport) doesn't exist in specified registry location , (i.e HKEYLM_SOFTWARE_MICROSOFT_EXCHANGESERVER 
    Thank you all
    Neil Patric 

    Hi,
    To understand more about the issue, I’d like to confirm the detail error when the installation failed.
    As far as I know, deployment of an Exchange Server 2013 server goes through three main stages.
    1. Preparing Active Directory (if you are installing Exchange Server 2013 for the first time)
    2. Installing the Exchange Server 2013 pre-requisites on the server
    3. Running Exchange Server 2013 setup
    For more information, you can refer to the following article:
    http://exchangeserverpro.com/how-to-install-exchange-server-2013/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Angela Shi
    TechNet Community Support

  • 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

Maybe you are looking for

  • How to restrict the users not to change receiving batch no. in 305 mov.type

    Dear MM Guru, We are using mov.type 303 & 305 for transferring the materials from one plant to another plant. t.code is MB1B (Non split valued item) While receive the goods through 305 mov.type the user having the chance to change the receiving batch

  • Webcam on skype.

    Hello. Every time i try to turn my camera on - skype call fails. I can talk free while it's off. But as soon as i turn it on, some weird Internet connection problems appear. No matte what i do, nothing changes. I tried to reinstall skype, i tested my

  • Blue folder icon with question mark at start-up

    Hi all! I've read the previous threads and posts and didn't really find any other user who has this problem.. I'm new here and yes I'm freaking out. I can't even check my mac specs. so at this point I'm not sure if it's a MAC OS X (10.5.7) I just sel

  • QuickTime stops immediately after opening on MacBook pro Mountain Lion

    All updates have been done, I did not install anything nieuw.Can anybody help?

  • HDMI Settings with AppleTV 2.0

    I just noticed that you can switch the HDMI output between 4 settings, (Auto, RGB High, RGB Low, Yc...((component basically))). Does anyone know which of these settings is the best to use? I'm using the ATV with a 720p LCD and didn't know if any of t