Exchange server 2013 services need to restart automatically at certain period of time how do i schedule

Hi All,
Need to restart exchange server 2013 services automatically at a certain period of time is there a script to schedule to automate can you please help me step by step process.
Thanks & Regards, Santosh Chowdary Vasireddy System Administrator Prolifcs DHFLVC Silicon Towers, 5th Floor, Survey #14, Kondapur, Hyderabad – 500 032. Work +91 40 3999 1999 Ex.1656 l Cell +91 9849277255 l [email protected] A Global
Provider of IBM, Microsoft and Testing Solutions Award Winner for Technical Excellence, BPM, SOA, Portal and Governance

You can create a PS1 file and run it in a scheduled task.
The PS1 files will need to have this.
Restart-Service MSExchangeTransport
Restart-Service MSexchangeIS
etc...
How to add a Scheduled task is given in this link.
http://www.mikepfeiffer.net/2010/02/creating-scheduled-tasks-for-exchange-2010-powershell-scripts/

Similar Messages

  • Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

    Hi,
    After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
    same. Outlook was working fine before the upgrade.
    Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
    Already applied the transport fix.
    Thanks in advance!

    Hi,
    According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
    To narrow down the issue, I’d like to recommend the following troubleshooting:
    1. Check if the issue happens on all Outlook users
    2. Check the Outlook Anywhere connectivity by using ExRCA:
    https://testconnectivity.microsoft.com/
    Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
    If you have any question , please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Manages Exchange server health Service is NOT starting after installing EDGE role using Exchange2013 SP1+CU5 setup

    I used Exchange 2013 SP1+CU5 to install Edge role on Windows server 2012 R2 workgroup machine
    then after installation the service "Exchange server health Service" was not starting automatically or manually with the following error "Error 1075: The dependency service does not exist or has been marked for deletion"
    and in the Event Viewer I have this error:
    Event Id: 7003
    The Microsoft Exchange Health Manager service depends on the following service: MSExchangeADTopology. This service might not be installed.
    please advice

    The Exchange 2013 Edge Role has a reduced set of services compare to a CAS or MBX server role:
    Active Directory Web Services
    Microsoft Exchange ADAM
    Microsoft Exchange Anti-spam Update
    Microsoft Exchange Diagnostics
    Microsoft Exchange Credential Service
    Microsoft Exchange Health Manager
    Microsoft Exchange Service Host
    Microsoft Exchange Transport
    Microsoft Exchange Transport Log Search
    The above one was from Exchange 2013 Sp1. Not sure whether Microsoft Exchange Health Manager service has been replaced from CU5.
    Just restart the edge server once again and ensure that you are able to see this service again in services console.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Installation of exchange server 2013

    Hi,
    can we install ADDS, DNS, and Exchange server 2013 on a single server, and the OS is windows server 2012 r2 Standard Edition.
    If it is possible then, is there any dis-advantages that my disturb Exchanger Server 2013 Services.
    Thanks & regards,
    Anil.  

    Its not recommended for wide variety of reasons in Production environment... Good to go if you want to just test something and not worried about things...
    Configuring Exchange 2013 for Active Directory split permissions isn’t supported.
    The Exchange Trusted Subsystem universal security group (USG) is added to the Domain Admins group when Exchange is installed on a domain controller. When this occurs, all Exchange servers in the domain are granted domain administrator rights in that domain.
    Exchange Server and Active Directory are both resource-intensive applications. There are performance implications to be considered when both are running on the same computer.
    You must make sure that the domain controller Exchange 2013 is installed on is a global catalog server.
    Exchange services may not start correctly when the domain controller is also a global catalog server.
    System shutdown will take considerably longer if Exchange services aren’t stopped before shutting down or restarting the server.
    Demoting a domain controller to a member server isn’t supported.
    Running Exchange 2013 on a clustered node that is also an Active Directory domain controller isn’t supported.
    Refer:
    Installing Exchange on a domain controller is not recommended
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Exchange Server 2013 installer will not start or complete

    Hello,
    I am trying to MS Exchange Server onto a Windows Server 2012R2 with Active Directory network. I had started an installation process and it shot out a list of pre-requisites that server need before it can attempt to install. I fulfilled every pre-requisite.
    Rebooted the server. Now whenever I attempt another installation process again. It starts, gathers information, and quits with event log:
    Windows Installer installed the product. Product Name: Microsoft Exchange Server. Product Version: 15.0.516.32. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.
    MS Exchange Server is not listed in Programs and Features to even remove, is it a faulty Microsoft Installer? I have already rebooted numerous times to no avail.
    EDIT: Here's a copy of the MSI log, I couldn't find anything to indicate what's going wrong myself, http://pastebin.com/LwCAimuF

    Hi,
    I've downloaded (as per instructions above):
    Microsoft Exchange Server 2013 Service Pack 1 (SP1)
    http://www.microsoft.com/en-us/download/details.aspx?id=41994
    Again, the installer repeats the same behavior as before, right now I am running a repair tool on .Net repair tool.
    New log http://pastebin.com/SDynMaDe
    Edit: Looks like there's long list of issues trying to fulfill Exchange Pre Requisite.
    Windows Management Framework 4.0
    http://www.microsoft.com/en-us/download/details.aspx?id=40855
    "The certificate for the signer of the message is invalid or not found"
    It would probably be best to re-install Windows Server again

  • Exchange server 2013 Installation issue

    Dear Experts,
    Thanks in advance...
    I am not able to Install Exchange server 2013. I have tried my best to Install but not success. Please find my system configuration.
    Dell Laptop Intel I5 1.7 GHZ
    RAM -8GB
    Vmware workstation 9.
    Steps I followed
    Created a VM inside Vmware and Installed windows 2012 Std. Edition
    Memory assigned to VM is 1 GB
    All prerequisites completed and tried to Install Exchange server 2013 SP1
    During installation it asked me to select the  role to Install and I selected Mailbox server role and CAS
    Exchange setup process started at 3 P.M till 9 P.M setup was not finished finally setup process halt and I got the error  setup could not completed .
    Please find the logs for your reference.............
    04/13/2015 08:41:02.0303] [0] **********************************************
    [04/13/2015 08:41:02.0303] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
    [04/13/2015 08:41:02.0303] [0] **********************************************
    [04/13/2015 08:41:02.0303] [0] Local time zone: (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi.
    [04/13/2015 08:41:02.0303] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
    [04/13/2015 08:41:02.0328] [0] Setup version: 15.0.847.32.
    [04/13/2015 08:41:02.0328] [0] Logged on user: WIN-4D2C2JMF5R1\Administrator.
    [04/13/2015 08:41:02.0336] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
    [04/13/2015 08:41:02.0368] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
    [04/13/2015 08:41:02.0600] [0] Command Line Parameter Name='sourcedir', Value='C:\Softwares\Exch-13'.
    [04/13/2015 08:41:02.0615] [0] Command Line Parameter Name='mode', Value='Install'.
    [04/13/2015 08:41:02.0632] [0] RuntimeAssembly was started with the following command: '/sourcedir:C:\Softwares\Exch-13 /mode:Install'.
    [04/13/2015 08:41:02.0632] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
    [04/13/2015 08:41:05.0504] [0] Finished loading screen CheckForUpdatesPage.
    [04/13/2015 08:41:13.0567] [0] Starting file's copying...
    [04/13/2015 08:41:13.0599] [0] Setup copy files from 'C:\Softwares\Exch-13\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
    [04/13/2015 08:41:13.0794] [0] Finished loading screen CopyFilesPage.
    [04/13/2015 08:41:15.0033] [0] Disk space required: 1826493368 bytes.
    [04/13/2015 08:41:15.0033] [0] Disk space available: 46620041216 bytes.
    [04/13/2015 08:42:55.0484] [0] Finished loading screen InitializingSetupPage.
    [04/13/2015 08:42:55.0484] [0] File's copying finished.
    [04/13/2015 08:43:13.0922] [0] Setup is choosing the domain controller to use
    [04/13/2015 08:43:28.0885] [0] Setup is choosing a local domain controller...
    [04/13/2015 08:43:32.0221] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server 
    is not available. Error message: Active directory response: The LDAP server is unavailable. 
    See the Exchange setup log for more information on this error.
    [04/13/2015 08:43:32.0335] [0] [ERROR] Active Directory server 
    is not available. Error message: Active directory response: The LDAP server is unavailable.
    [04/13/2015 08:43:32.0366] [0] [ERROR] The LDAP server is unavailable.
    [04/13/2015 08:43:32.0366] [0] Setup will use the domain controller ''.
    [04/13/2015 08:43:32.0366] [0] Setup will use the global catalog ''.
    [04/13/2015 08:43:32.0596] [0] No Exchange configuration container was found for the organization. Message: 'Active Directory server 
    is not available. Error message: Active directory response: The LDAP server is unavailable.'.
    [04/13/2015 08:43:32.0707] [0] The following roles have been unpacked:
    [04/13/2015 08:43:32.0721] [0] The following datacenter roles are unpacked:
    [04/13/2015 08:43:32.0739] [0] The following roles are installed:
    [04/13/2015 08:43:32.0739] [0] The local server does not have any Exchange files installed.
    [04/13/2015 08:43:32.0834] [0] Server Name=WIN-4D2C2JMF5R1
    [04/13/2015 08:43:33.0032] [0] Setup will use the path 'C:\Softwares\Exch-13' for installing Exchange.
    [04/13/2015 08:43:33.0084] [0] The installation mode is set to: 'Install'.
    [04/13/2015 08:43:51.0460] [0] Exchange organization name is required for this mode.
    [04/13/2015 08:43:51.0460] [0] Active Directory Initialization status : 'False'.
    [04/13/2015 08:43:51.0472] [0] Schema Update Required Status : 'False'.
    [04/13/2015 08:43:51.0472] [0] Organization Configuration Update Required Status : 'False'.
    [04/13/2015 08:43:51.0472] [0] Domain Configuration Update Required Status : 'False'.
    [04/13/2015 08:43:51.0536] [0] Applying default role selection state
    [04/13/2015 08:43:51.0565] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:43:51.0565] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:43:51.0565] [0] InstallModeDataHandler has 0 DataHandlers
    [04/13/2015 08:43:51.0565] [0] RootDataHandler has 1 DataHandlers
    [04/13/2015 08:43:52.0848] [0] CurrentResult launcherbase.maincore:90: 0
    [04/13/2015 08:43:53.0067] [0] Finished loading screen WelcomePage.
    [04/13/2015 08:44:06.0654] [0] Finished loading screen EULAPage.
    [04/13/2015 08:44:10.0679] [0] Finished loading screen RecommendedSettingsPage.
    [04/13/2015 08:44:13.0814] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:13.0814] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:13.0814] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:13.0844] [0] InstallModeDataHandler has 8 DataHandlers
    [04/13/2015 08:44:14.0048] [0] Finished loading screen RoleSelectionPage.
    [04/13/2015 08:44:18.0619] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0619] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0619] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 9 DataHandlers
    [04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 10 DataHandlers
    [04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 11 DataHandlers
    [04/13/2015 08:44:18.0648] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0648] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0648] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0648] [0] InstallModeDataHandler has 12 DataHandlers
    [04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:22.0644] [0] InstallModeDataHandler has 13 DataHandlers
    [04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:22.0656] [0] InstallModeDataHandler has 14 DataHandlers
    [04/13/2015 08:46:00.0423] [0] Finished loading screen InstallationSpaceAndLocationPage.
    [04/13/2015 08:46:28.0427] [0] Finished loading screen ExchangeOrganizationPage.
    [04/13/2015 08:46:30.0221] [0] Finished loading screen
    Regards
    Biswajeet

    Hi,
    Please find the DC Health check report.
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    C:\Users\Administrator>dcdiag
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = EX-13
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\EX-13
          Starting test: Connectivity
             ......................... EX-13 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\EX-13
          Starting test: Advertising
             ......................... EX-13 passed test Advertising
          Starting test: FrsEvent
             ......................... EX-13 passed test FrsEvent
          Starting test: DFSREvent
             ......................... EX-13 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... EX-13 passed test SysVolCheck
          Starting test: KccEvent
             ......................... EX-13 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... EX-13 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... EX-13 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... EX-13 passed test NCSecDesc
          Starting test: NetLogons
             ......................... EX-13 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... EX-13 passed test ObjectsReplicated
          Starting test: Replications
             ......................... EX-13 passed test Replications
          Starting test: RidManager
             ......................... EX-13 passed test RidManager
          Starting test: Services
             ......................... EX-13 passed test Services
          Starting test: SystemLog
             An error event occurred.  EventID: 0x0000272C
                Time Generated: 04/14/2015   18:01:37
                Event String:
                DCOM was unable to communicate with the computer fec0:0:0:ffff::1 us
    ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
    m32\dcdiag.exe).
             An error event occurred.  EventID: 0x0000272C
                Time Generated: 04/14/2015   18:01:49
                Event String:
                DCOM was unable to communicate with the computer fec0:0:0:ffff::2 us
    ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
    m32\dcdiag.exe).
             An error event occurred.  EventID: 0x0000272C
                Time Generated: 04/14/2015   18:02:02
                Event String:
                DCOM was unable to communicate with the computer fec0:0:0:ffff::3 us
    ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
    m32\dcdiag.exe).
             ......................... EX-13 failed test SystemLog
          Starting test: VerifyReferences
             ......................... EX-13 passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : NETMAGIC
          Starting test: CheckSDRefDom
             ......................... NETMAGIC passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... NETMAGIC passed test CrossRefValidation
       Running enterprise tests on : NETMAGIC.IN
          Starting test: LocatorCheck
             ......................... NETMAGIC.IN passed test LocatorCheck
          Starting test: Intersite
             ......................... NETMAGIC.IN passed test Intersite
    Regards
    Biswajeet

  • 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

  • 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

  • Exchange Server 2013 server restarts automatically (The bugcheck was: 0x000000ef (0xffffe00000ee8080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

    Hi,
    We have Exchange server 2013 restarting issue.(15.0.847.32)
    Found The bugcheck was: 0x000000ef (0xffffe00000ee8080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000) Event in the logs.
    We have performed below steps but still same issue.
    1. We have removed
    Global Override for
    ServiceHealthMSExchangeReplForceReboot responder (Reason for this as its not getting disabled)
    2. Created Local Override and set the value to "0" (Disabled)
    Server still restarting.

    Hi,
    I have followed above already the problem remain same.
    I have disabled Microsoft Exchange Health
    Manager Service to monitor till now issue not reported.
    Is this best practice to disable the service in these kinds of issues or is there any other way?
    Its a workaround that many have used yes.
    However, having said that, its not something you want to leave in place.
    I would suggest upgrading to at least CU6 or CU7 and if that does not resolve the issue, opening a support case with Microsoft.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • 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

  • Exchange Server 2013- Information Store Service not starting

    Hi Everyone,
    We are having an issue with one of our Exchange Servers that is running Exchange Mailbox server role.
    Server : Exchange 2013 CU3 , Windows Server 2012 R2
    We noticed on Friday that its "Information Store Service" has stopped working and we try to manually run it (Services->Microsoft
    Exchange Information Store Service -> Start) 
    Service didn't start and gave : Error 0x80004005 Unspecified Error
    Trying to start the service using the command line using:  net start MSexchangeIS gave us a different error:
    System Error 16389 has Occurred
    The system can not find message text for message number 0x4005 in the message file for BASE
    Event viewer has  (Event ID : 7031):
    The Microsoft Exchange Information Store service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.
    Since we have got this error we have tried some fixes such as  Checking Time synchronisation  and IPv6 issues. But nothing
    seems to have caused this. We have rebuild the windows server from scratch and used the recover server switch to  rebuild the Exchange server. Still the same issue.
    Any help would be greatly appreciated.

    Hi Tiraj,
    Any update? Does the issue still occur after install Exchange server on Windows Server 2012?
    I wonder if the issue occurs suddenly or did you configured something on database.
    In addition, overload on server could also cause the issue.
    Regards,
    Rebecca Tu
    TechNet Community Support

  • Exchange Server 2013 POP3 Service on CAS cannot after Upgrade to SP1

    Exchange Server 2013 POP3 Service on CAS cannot after Upgrade to SP1
    When I manual start MSExchangepop3 Service on CAS It show "The Microsoft Exchange POP3 Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
    In event log show POP3 EventID 1018 , 1019 , 1036
    It said like this blinding already use (0.0.0.0)
    The point is "IF I SET BINDING FOR 995 , MSEXCHANGE POP3 Service will automatic stop"
    Does anyone face this issue please?
    Thank you

    You could check what (if anything) else is running on that port.
    From a command prompt, type netstat -ano | find 995
    This will give you the Process Identifier (PID) for the process that is running on port 995. Then you can open Task Manager, add PID as an additional column, and find out what that process is.
    Hope that helps.

  • Exchange Server 2013 Management Pack in SCOM 2012, can not update healthset status automatically

    Hi, all
    I have Exchange Server 2013 and SCOM 2012 installed. I have imported Exchange Server 2013 Management Pack to SCOM 2012. Now I have a question that when there is a service not healthy, I can find the red alert in my alert view with the Exchange 2013 server,
    but after the service is healthy automatically, the red alert is still there. I can only make it become green healthy status after reseting the healthset status in the healthset explorer.
    Does anyone know how to make the server become green healthy status automatically after the monitor is healthy?
    Thank you.
    Nile

    Hi,
    How many Exchange Servers do you have? Does this issue only occur on one Exchange Server?
    Please check the application log on the problematic Exchange server and see whether there are any related event error.
    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.

  • I need to buy Microsoft Exchange Server 2013 License.

    I need to buy exchange 2013 license but problem is that I have total 175 users in my organization and then exchange standard license support upto 5 mailboxes and exchange enterprise support upto 100 mailboxes. My boss want to have each user have separate
    mailbox.. 
    So i am looking a solution for 175 users with 175 mailboxes. If anyone can help me and guide me which exchange server is best and how can i manage 175 separate mailboxes ????
    note: in future i also want to have symantec exec backup solution (mailboxes archiving) for that exchange server which i deploy in my organization.  
    need fastest response. 
    thanks in advance

    Hi FAISAL,
    Regardless of which version of the Exchange 2013 will not limit the number of mailboxes, however,different versions of the
    restrictions embodied in the number of databases.
    More details please refer to the following article:
    Exchange 2013: editions and versions
    Microsoft Exchange Server 2013 is available in two server editions: Standard Edition and Enterprise Edition. Enterprise Edition can scale to 50 mounted databases per server in the Release to Manufacturing (RTM) and Cumulative Update 1 (CU1) versions, and
    100 mounted databases per server in Cumulative Update 2 (CU2) and later versions; Standard Edition is limited to 5 mounted databases per server.
    Best regards,
    Niko Cheng
    TechNet Community Support

Maybe you are looking for