Exchange Server 2013 on Srvr2012r2 fails on preinstall

During the preinstall of the Exchange server 2013 on virtual Server 2012r2 the installation fails at the second step of the preinstall. I tried the wizard and it also fails station the user does not have the correct rights.
This was probably caused by myself.  When I first installed the Exchange I did not install the client and mailbox items.  When I found out this was an error I uninstalled it and tried to reinstall.
Bonnie Whalon

hi Bwhalon.. your both the commands are incorrect..
1. it misses a parameter required somwhere
2. the role service which you have asked to install is incorrect..may be mistyped
ok now you can use below two way ...
1. Command...
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
take from http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx
after this you can start the install
2. Graphical install : check below links .. this is step by step procedure
http://www.techieshelp.com/exchange-2013-step-by-step-configuration/                                
Let me know if this helps...
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Similar Messages

  • Exchange Server 2013 CU7 Upgrade Failed

    I am trying to upgrade Exchange Server 2013 SP1 to CU7 but after complete 46% of Mailbox Role Transport Service the Upgrade Failed and automatically rebooted the server. After restart its showing memory dump. How can we solved it.

    Hi livesayed,
    According to your description, we cannot get the key of this question.
    Would you please help to collect related event log or setup log? It’s more helpful for further troubleshooting.
    Besides, I find an similar thread about Exchange 2013 CU2 upgrade to CU3 Failed at Front End Transport Service, for your reference:
    https://social.technet.microsoft.com/Forums/office/en-US/32e06b5b-76bb-45d0-bf99-0b83c3182199/exchange-2013-cu2-upgrade-to-cu3-failed-at-front-end-transport-service?forum=exchangesvrdeploy
    Best Regards,
    Allen Wang

  • 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

  • Exchange Server 2013: Installation fails

    Migrating SBS 2008 to Windows Server 2012 R2 (no virtualization) and Exchange Server 2013 SP1
    (1) ADprep on SBS 2008 went fine
    (2) Installed necessary feature for Exchange (website “Part 1: Step-by-Step Exchange 2007 to 2013 Migration”)
    A) the first time I installed Exchange 2013, the setup succeeded, however there were several ecp/WinRM errors.
    B) restored Windows Server 2012 R2 to the state (2). Removed from AD (ADSI Edit)
    … CN=Services; CN=Exchange; CN=First Organization; CN=Exchange Administrator Group; CN=Servers 
    delete new Win 2012 server
    Run Exchange setup again:
    The following error was generated when "$error.Clear();
    if ($RoleStartTransportService)
    start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40
            " was run: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".
    Checked:
    - IPv6 is enabled, but was setup correctly after installing ADDS role)
    - Administrators (Group) is a member of the Exch. Trusted Subsystem
    Probably there is an AD problem, after the restoration (B) (bare metal) of the Win 2012 server.
    Please help!
    Fulco

    Hi
    the error states that the MSExchangeTransport service failed to start. Can you manually try starting the service and then run the setup again?
    Hope this helps. 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.

  • Exchange Server 2013 SP1 Standard: Installation failing can't progress

    I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
    do they think they're running?).
    The error message:
    Error:
    The following error was generated when "$error.Clear();
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    " was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
    Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
    Error:
    The following error was generated when "$error.Clear();
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    " was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
    Parameter name: VirtualDirectoryName".
    And I have to remove this config using ADSI Edit, which just returns me to the first error.

    1. Prodution
    2. Just 1 DC for 1 site.
    3. Setup.EXE
    4. Matches SP1 version numbers
    5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
    6. Here is the log files:
    [03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
    [03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
    [03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
    [03/23/2015 22:06:52.0941] [1] Executing:
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    [03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
    [03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
    [03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
    [03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
    [03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
    [03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
    [03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
    [03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
    [03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
    [03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    [03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    [03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
    [03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
    [03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
    at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    [03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    " was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
    [03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    [03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
    [03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
    [03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
    It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

  • Issues trying to recover failed Exchange Server 2013 in a DAG

    Having several issues attempting to recover a failed Exchange Server 2013. To start out, the failed server was mounted on a virtual server using hyper-v. The virtual server failed due to some hard drive partition issues and would no longer boot. As there
    really was no purpose to having Exchange on a Virtual Server I decided to rename the host to the same name as the virtual server. I reset the name in AD and proceeded to rename the server. Then made sure all the necessary things were installed and proceeded
    to do a recovery installation. I neglected to properly delete the old databases belonging to that server. I simply deleted the files off the hard drive instead of doing it properly. I should mention this is a two node plus witness server installation.Now,
    it seems I cannot delete the former server in either ECP or command line. I have attempted to clean up the mess with the old databases but there is one that was mounted only on the failed server that I cannot remove. It seems until I can remove that, I cannot
    remove the failed server from the DAG and do a recovery install. The steps shown in the tech net articles to remove a failed database have also failed. At this point I am wondering if I should just give up on the server name and do an install on a new server
    name or if someone can give me some information on how to clean up the mess, that would be better I am sure. Here is a list of the things I have tried.
    https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and in this article, the item mentioned is not in ADSIedit.
    http://exchangeserverpro.com/unable-remove-failed-server-dag-exchange-server-2010/
    http://exchangeserverpro.com/exchange-2013-how-to-remove-dag-member/ This
    article describes one of the problems I am having but the solution is not there.
    Thanks to any and all who can offer advice.
    Ronald C. Pope

    Thank you for your answer. Running that command results in the following:
    [PS] C:\Windows\system32>Remove-MailboxDatabase "Mailbox Database 0939719168"
    This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
    arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database"Mailbox Database 0939719168". To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
    archive mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Archive. To get a list of all
    public folder mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -PublicFolder. To get a
    list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Arbitration.
    To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
    <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
    <Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
    Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
    the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
    Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
    Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
    -Database "Mailbox Database 0939719168".
        + CategoryInfo          : InvalidOperation: (Mailbox Database 0939719168:DatabaseIdParameter) [Remove-MailboxDatab
       ase], AssociatedUserMailboxExistException
        + FullyQualifiedErrorId : [Server=EX01,RequestId=69b60793-fc4f-4dac-beb9-8c9afe381a36,TimeStamp=1/26/2015 6:28:34
       PM] 2BA41E0C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase
        + PSComputerName        : ex01.<domain>com
    I was able to disable the one mailbox that was listed for the database. I got the following error when attempting the command Get-Mailbox -Database"Mailbox Database 0939719168"
    [PS] C:\Windows\system32>Get-MailboxPlan Database "Mailbox Database 0939719168"
    Get-MailboxPlan : The term 'Get-MailboxPlan' is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At line:1 char:1
    + Get-MailboxPlan Database "Mailbox Database 0939719168"
    + ~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Get-MailboxPlan:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    the public folder and archive switch simply return a command prompt leading me to believe that there are no public or archive boxes on that database.
    Ron

  • Exchange Server 2013: no send/receive after failed CU1- CU2 and machine restore

    Hi!
    For several reasons, I decided to fully restore my Exchange Server 2013 machine today.
    The machine is virtualized on Hyper-V.
    I rebooted the server and recovered from backup and Exchange seems to be working fine. However, I cannot receive or send mail. If I try to send a message it goes to the "drafts" folder. OWA and EMC is working. I can not send mail between interna mailboxes
    either. Outlook says disconnected.
    When running the Exhchange Connectivity Analyzer, I get the following:
    - Receive: Connection was successful but no banner was received.
    - Send: Successfull. However when trying to send mail to external mailbox it does not reach that mailbox.
    Mailflow was working perfectly at the time of the backup.
    Help is much appreciated!
    UPDATE 1: When telnet on local server i get SMTP banner. But not on other computers in same subnet.

    OK. After fiddeling around in ADSIedit and trying to rebuild my Exchange environment I ended ut breaking it completely.
    I then restored both my DC (Exchange schema CU2) and my EX (Exchange schema CU1). Scema Versions where the inconsistent as stated.
    Then I uninstalled the KB2874216 successfully. After that i tried to Upgrade Exchange to CU2. The Upgrade failed at Mailbox Role: Mailbox Service With error Message:
    The following error was generated when "$error.Clear();
              if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
                if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
                  $sysMbx = $null;
                  $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
                  $dispname = "Microsoft Exchange";
                  $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0)
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if ($dbs.Length -ne 0)
                      $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                      if ($arbUsers.Length -ne 0)
                        $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
                  else
                    if ($mbxs[0].DisplayName -ne $dispname )
                       set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
                    $sysMbx = $mbxs[0];
                  # Set the Organization Capabilities needed for this mailbox
                  if ($sysMbx -ne $null)
                      Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                      set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;
                      # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
                      # This can be remove after BUG(O15#2555914) is fixed.
                      if ($sysMbx.RetentionPolicy -eq $null )
                         $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
                         set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
                  else
                    Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
                else
                  write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox. Property Name: Database".
    Seems the problem was corrupted arbitrary system mailboxes from previous Exchange 2010 to Exchange 2013 migration.
    The solution for me was to restore the corrupted arbitrary mailboxes using this
    LINK. It is for 2010 but Works on 2013.
    I am now currently on Exchange CU2 on both my EX server and on my DC. Now I have to check mail flow and will report back.

  • Exchange Server 2013 failing Readiness Checks

    Here are the list of errors it reports
    Error:
    Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
    My user is in the Enterprise Admins group.    
    Error:
    The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx
    My user is in the Enterprise Admins group and it is also in the Organization Management Role
    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
    I am
    Error:
    Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have been created but have not yet replicated to the local domain.  Wait for replication to complete and then run setup again.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    While this is showing up, I do have the Exchange objects availabe on all of my DCs in all of the sites.
    Error:
    The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
    Its currently at 2008 Which is the highest I can make it in my organization at this time.
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
    I'm able to communicate with all the DCs from the machine I'm attempting to install exchange on.
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Has anyone encounterd this?  
    I've run Setup /PrepareSchema and Setup /PrepareAD on the DC in the site Exchange specified.
    I have installed all of the Prereqs
    Here's an example of my set up
    One Forest
    AwesomeCompany.net -
    There's Two sites
    Atlanta-HeadQuarters
    Atlanta-DataCenter
    and Two Sub Domains
    HeadQuarters
    DataCenter
    Exchange Machine is in Atlanta-DataCenter Site and attached to DataCenter domain.
    Exchange requested the /PrepareAD and /PrepareSchema be run on a Domain Controller in the root domain that is in site Atlanta-HeadQuarters.
    Any guidance would be appreciated.

    Hello,
    Just for double confirm, please run “WhoAmI” in CMDlet and see if you are using a local admin account.
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange Server 2013 SP1 - Readiness Check Failing - Detected Non-existent Exchange 2007 Servers

    For development purposes, I needed to install Exchange Server 2013 in our environment.  Our current environment includes a couple Domain Controllers, a Sharepoint Server, and a SQL Server.  So, it's got a very simple topology.  The one thing
    our environment does NOT have are current Exchange servers.
    During the "Prerequisite Analysis" phase of the install it complained that two servers, that I can find nowhere in our active directory domain, are running Exchange 2007.  Obviously, this presents some unique problems.  Perhaps as a test
    many years ago, someone installed Exchange 2007 to "play" with, but we've never run Exchange for any length of time.  
    So, this is quite the conundrum, given the above does anyone have any suggestions as to a potential solution?  Ideally, I'd like to be able to "lift the covers" and cleanup the references to the non-existent servers somehow, but ANY suggestions
    for fixes are MUCH appreciated.
    Cheers,
    Nate

    Here is the thing I would do (Only if I am not going to have any exchange 2007 ever in the environment).
    On any of windows server 2008 download
    Exchange 2010 SP3
    Extract the file and run the below command:
    Setup.com /ps
    This will make Exchange 2013 install. Also Deleting Exchange Administrator Group wouldn't help as Setup will look for the information about schema into AD.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange Server 2013: Failed to connect. Winsock error code: 10060, Win32 error code: 10060.

    Dear All,
    I have exchange server 2013 running with windows server 2012.
    My email server have been send and receive email with internal and external as normal.
    Today, i got the problem the email cannot send out to external and get the error below:
    Please comment.
    BR,
    Khemarin
    [email protected]

    Hi Khemarin,
    If it is Smarthost, are you able to telnet your smarthost using 25 port number?
    Also please check your Send Connector setting.
    http://technet.microsoft.com/en-us/library/aa998662(v=exchg.150).aspx
    Thanks
    Mavis
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

    Hi Team,
    Need urgent help in resolution of following error:
    Environment Details: VMware ESXi 5.5 (vMotion)
    Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
    Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
    OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
    Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
    Prerequisites: Installed
    Error: Installation gives Error at Step 10 during installation of Mailbox Service
    Error Details Below:
    Error:
    The following error was generated when "$error.Clear();
    if ([Environment]::OSVersion.Version.Major -ge 6)
    $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
    $reg= join-path (join-path $env:SystemRoot system32) reg.exe;
    $servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
    if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
    if ((get-service wsbexchange).Status -eq "Running")
    Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
    Exchange /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
    Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
    " was run: "Process execution failed with exit code 1.".

    Resolved ! :)
    Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
    As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
    Thanks to all.

  • Exchange Server 2013 Update from to CU3 to CU8 stuck, Exchange completely down

    Hello,
    We tried to update a Exchange 2013 server to CU8 because we needed support from Microsoft (certificate revoked, so OWA not working anymore) and they could only help us after updating to CU8 first. The problem is that the update got stuck and now Exchange
    is not working at all anymore. Since it is a production enviroment and there is mail in all outboxes we do not want to turn back to a snapshot but solve the problem and continue the update. Any help is welcome because all mail is down now :-(
    The error we received at the Exchange Server is:
    C:\Users\administrator.DOMAINNAME\Downloads\Exchange-cu8>setup.exe /m:upgrade /In
    stallWindowsComponents /IAcceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for
    installation.
    Languages
    Mailbox role: Transport service
    Client Access role: Front End Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Management tools
    Client Access role: Client Access Front End service
    Performing Microsoft Exchange Server Prerequisite Check
        Configuring Prerequisites                                 COMPLETED
        Prerequisite Analysis                                     COMPLETED
    Configuring Microsoft Exchange Server
        Preparing Setup                                          
    COMPLETED
        Stopping Services                                         COMPLETED
        Language Files                                            COMPLETED
        Removing Exchange Files                                   COMPLETED
        Preparing Files                                          
    COMPLETED
        Copying Exchange Files                                    COMPLETED
        Language Files                                            COMPLETED
        Restoring Services                                        COMPLETED
        Language Configuration                                    COMPLETED
        Mailbox role: Transport service                           FAILED
         The following error was generated when "$error.Clear();
              $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
              foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
    t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
            " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
    veConnectorRoleConflictException: The values that you specified for the Bindings
     and RemoteIPRanges parameters conflict with the settings on Receive connector "
    SERVER-EXCHANGE\Externe POP3 mailboxen". Receive connectors assigned to differen
    t Transport roles on a single server must listen on unique local IP address & po
    rt bindings.
       bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
    n, ErrorCategory errorCategory, Object target, String helpUrl)
       bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
    n, ErrorCategory category, Object target)
       bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
    r.InternalValidate()
       bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
    ncName, Action func, Boolean terminatePipelineIfFailed)".
         The following error was generated when "$error.Clear();
              $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
              foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
    t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
            " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
    veConnectorRoleConflictException: The values that you specified for the Bindings
     and RemoteIPRanges parameters conflict with the settings on Receive connector "
    SERVER-EXCHANGE\Default Frontend SERVER-EXCHANGE". Receive connectors assigned t
    o different Transport roles on a single server must listen on unique local IP ad
    dress & port bindings.
       bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
    n, ErrorCategory errorCategory, Object target, String helpUrl)
       bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
    n, ErrorCategory category, Object target)
       bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
    r.InternalValidate()
       bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
    ncName, Action func, Boolean terminatePipelineIfFailed)".
    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

    Hello Gadget,
    Please find the solution as follows
    This error is concern about WMSVC certificate which was deleted, we could refer to the following steps:
    1- Go to IIS Manager and select server certificate,
    2- Select “Create Self-Signed Certificate”,
    3- For Server 2012 in the Friendly Name Field type: WMSVC and select the personal (certificate Store),
    4- Now go to ” Management Service”,
    5- From SSL Certificate choose the newly create “WMSVC” Self-Signed Certificate,
    6- Apply,
    7- Now  start service of “Web Management service”.
    https://social.technet.microsoft.com/Forums/office/en-US/eac00dc2-6e43-45ae-939c-aad82a144908/cu8-install-fails?forum=exchangesvrgeneral
    Exchange Queries

  • Exchange Server 2013 // MFCMAPI could connect with errors

    While connecting with Exchange Server 2013 I have started facing problem with my application.
    My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.
    And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional
    details needed.
    ___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
        props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;
        prop_count++;
        props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;
        props[prop_count].Value.lpszA   = <[email protected]>;
        prop_count++;
        // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED
        props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;
        props[prop_count].Value.b        = FALSE;
        prop_count++;
        props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;
        props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS
    | CONFIG_SHOW_CONNECT_UI */;
        prop_count++;
        props[prop_count].ulPropTag     = PR_DISPLAY_NAME;
        props[prop_count].Value.lpszA   = <Mailbox Profile Name>;
        prop_count++;
        //Above setting used to be sufficient to connect using RPC
        //Below parameters added to connect via HTTPS
        LPSTR pwszUser = "domain\\username"; //also tried
    [email protected] AND username
        LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData
        props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;
        props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;
        props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM,
    RPC_C_HTTP_AUTHN_SCHEME_BASIC
        prop_count++;
        props[prop_count].ulPropTag =  PR_PROFILE_RPC_PROXY_SERVER_FLAGS;
        props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;
        props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;
        props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;               
    // RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;
        props[prop_count].Value.lpszA = pwszUser;
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;
        props[prop_count].Value.bin.lpb = dataBlobOut.pbData;
        props[prop_count].Value.bin.cb = dataBlobOut.cbData;
        prop_count++;
        DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"),
    this ) );
        hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props
        I still get MAPI_E_NETWORK not found
    Are there any configuration changes need to be done on Exchange Server?
    Is there any mistake in above parameters?
    Kindly suggest.

    You can refer Dave's blog post @
    http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
    DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

  • 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

  • Exchange Server 2013 Installation error

    Hi Support,
    I have try to install exchange server 2013 on server 2012. after configure active directory when try to install exchange server command Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>CD\
    C:\>E:
    E:\>cd pradeep\Ex Setup 2013
    E:\pradeep\EX Setup 2013>Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseT
    erms
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for
    installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                     FAILED
         A reboot from a previous installation is pending. Please restart the system
     and then rerun Setup.
         For more information, visit: http://technet.microsoft.com/library(EXCHG.150
    )/ms.exch.setupreadiness.RebootPending.aspx
    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    E:\pradeep\EX Setup 2013>

    Hi ,
    Please have a look in to the error message 
      "A reboot from a previous installation is pending. Please restart the system
     and then rerun Setup."
    Reboot the server and try again .
    Please reply me if you have any queries .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

Maybe you are looking for