Exchange 2013 SP1 setup fails at prerequisite Analysis

I installed a completely new server network with Hyper-v 2012R2
I installed two virtual 2012R2 servers: DC01 as the Domain Controller of "testdomain.local" and EX01 as the Exchange server.
EX01 is joined the domain "testdomain" from DC01
I log in on EX01 with an in AD created testdomain\exadmin account who is member of domain admins, enterprise admins, schema admins, administrators and group policy creator owners.
I have run the 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, Telnet-Client, RSAT-ADDS
on EX01
I have installed the Microsoft Unified Communications Managed API 4.0
Then I run the Exchange 2013 SP1 setup and the prerequisite check gives the following errors:
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
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
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
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
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
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
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
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.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
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 can connect with the Active Directory Sites and Domains and other applets to the AD. So Why these errors???
HELP!
Regards, Manu
Manu van Winkel

Hi, thanks for the answer.
I restarted the server and did the "run as administrator": same result.
The first errormessage in the exchangesetup.log is:
[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.
When I run dcdiag /s:DC01 from EX01 it passes all tests except:
DFSREvent "The RPC server is unavailable"
KccEvent "The RPC server is unavailable."
SystemLog  "The RPC server is unavailable."
Could these be of any influence?
Running dcdiag on DC01 passes all tests.
The only thing I changed after setting up DC01, was changing the fixed IP-adres from 192.168.25.3 to 192.168.25.2, but I ran ipconfig /flushdns and ipconfig /registerdns and dcdiag /fix afterwards.
The only roles installed on DC01 are AD DS (I tried installing exchange before and after adding the AD DS role), AD, DNS, DHCP and Fileservices
I don't know where to look anymore....
Manu van Winkel

Similar Messages

  • Exchange 2013 SP1 Setup fails

    I am getting very frustrated. It really shouldn't take over a week to install Exchange.
    I have two domain controllers, Windows 2003 and Windows 2008 R2. The 2008 is now all Operations Masters for all roles.
    I have a clean install of W2K8 R2 SP1 installed under Hyper-V on a separate physical W2K8 server. Before starting the install I used ADSIEdit to ensure there was nothing left in the AD of prior Exchange install attempts. This is the first and only installation
    of Exchange.
    I am running the install as the Domain\Administrator and naturally that account is a member of all the appropriate security groups. RSAT are installed on the Exchange server and using them to access Users and Computers clearly shows this. The install fails
    with the errors below, all of which appear to be incorrect.
    *** BEGIN ERROR ***
    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
    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
    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
    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
    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
    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
    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
    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
    Error:
    Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.  See the Exchange setup log for more information on this error.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    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
    Error:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://go.microsoft.com/fwlink/?LinkId=262357). Please install the update, and then restart Setup.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7WindowsIdentityFoundationUpdateNotInstalled.aspx
    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
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    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
    *** END ERROR
    Why can't Exchange installation see the AD when everything else can?

    It appears that these error messages are pure fiction. I went back to ADSI Edit and removed some MS Exchange container and then reran setup /prepareschema again followed by setup /preparead and finally setup /mosde:install /role:clientaccess,mailbox and
    it churned away for a long time, apparently working.
    It appears than when it says you aren't a member of Schema Admins and that it can't access Active Directory, what it really means is it could find the AD just fine, but didn't like what it saw.
    My guess would be very sloppy programming in which the low level error doesn't bubble up and so when something fails it just assumed you didn't have permissions.
    It's not quite finished yet, but I am beginning to believe it will finish. So that's almost 6 days of non stop effort to install Exchange. It's hard top believe they are allowed to charge for this stuff.

  • Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

    Here is the scenario:
    Legacy Host: Windows 2008 R2
    Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
    After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster).  (copy VM files to new 2012 R2host) Everything works fine.
    Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
    of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
    to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
    I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
    Services upgrade.
    Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
    upgrade.
    Thanks
    Gerhard Waterkamp ACSLA Inc.

    Hi,
    Could you try use the following method to fix this issue first?
    1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
     1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
     Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
     http://support.microsoft.com/kb/947821/en-us
    2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
    %SYSTEMROOT%\Logs\CBS\
    3. Please paste the checksur.log here for analysis.
    If there is no error found, please try the following step.
    ==================================
    2. Use Fix it tool to reset the Windows Update components.
     1. Open the following link.
     http://support.microsoft.com/kb/971058/en-nz
     2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
     3. Click “Run Now” to reset the Windows Update components.
    Note: We can reset the Windows Updates manually by following the steps in the KB above.
    3. Use the System File Checker tool to repair missing or corrupted system files
     1. Open the command promote with Administrators.
     2. At the command prompt, type the following command, and then press ENTER:
         sfc /scannow
    Any errors are found in the steps above, please let me know.
    Hope this helpful.
    Best Regards,
    Jason Zeng
    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 2013 SP1 - healthsets failing

    Hi,
    I have recently installed two Exchange 2013 SP1 servers in different environments and are experiencing issues on both. Issues that I haven't seen on Exchange 2013 without SP1.
    I have 6 healthsets which are unhealthy. 
    Autodiscover...
    ActiveSync.P...
    EWS.Proxy
    OAB.Proxy
    Outlook.Proxy
    OutlookMapiH...
    I found this article: 
    http://technet.microsoft.com/en-us/library/ms.exch.scom.ecp.proxy(v=exchg.150).aspx
    Which describes, that try to restart the app pool, then an iisreset - and lastly reboot the server. Tried all and none of them helped.
    But then I found this error in the Exchang event log:
    RecycleApplicationPool-MSExchangePowerShellAppPool-RpsDeepTestPSProxyRestart: Throttling rejected the operation
    Which fails almost every minute.
    And I guess that this could be the issue. But I can't figure out which throttling that is causing this.
    Any one else with this issue on Exchange 2013 SP1?
    Thanks in advance.
    /Kim

    Hi,
    I have seen a lot of similar issues with health manager service. For IIS services, we can safely ignore these warnings. Personal experience, we just need to monitor whether there are related
    error reports in event log.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Exchange 2013 cu3 setup fails with 'problem... validating the state of Active Directory... supplied credential... invalid'

    Windows Server 2013; Exchange Server 2013 with Cumulative Update 1
    Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with
    [xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.  See the Exchange setup log for more information on this error.
    [xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
    [xxx] [0] [ERROR] The supplied credential is invalid.
    (Crosses - XXX - replace original values.)
    I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely
    conincidental:
    The Security System could not establish a secured connection with the server
    ldap/xxx.xxx/[email protected] No authentication protocol was available.
    Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

    Hi vhr1,
    Based on my knowledge, the Event ID 40961 is a warning message.
    This behavior occurs when we restart the server that was promoted to a DC. The Windows Time service tries to authenticate before Directory Services has started.
    Found some resources for your reference even if the Exchange Version is mismatched:
    http://blogs.technet.com/b/jhoward/archive/2005/04/20/403946.aspx
    http://support.microsoft.com/kb/823712/en-us
    About the error message, "Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid."
    The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.
    Found a similar thread for your reference, hope it is helpful:
    http://social.technet.microsoft.com/Forums/en-US/98e26ad6-8e43-4ef5-8ff9-e9fee6e76bda/bind-operation-is-invalid?forum=exchangesvrdeploylegacy
    Feel free to contact me if there is any problem.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 SP1 Install fails on step 5 of 9: Mailbox Role: Mailbox Service

    We have exchange installed on a windows 2008 R2 box.
    We keep getting the following error when we try to install the update:
    Error:
    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{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$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)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox.".
    Error:
    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{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$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)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox.".
    Any help would be greatly appreciated!
    Thanks, 
    Wes

    Hello,
    Please make sure you do exchange server upgrading or a clean exchange 2013 installation. If you do a upgrading, please refer to the similar thread to assign a database to the arbitration mailbox "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}".
    http://social.technet.microsoft.com/Forums/en-US/239cb4a6-4a07-4b9a-800c-974573bbff32/error-installing-step-12-mailbox-role-service-on-exchange-2013-cu2?forum=exchangesvrdeploy
    Please make sure you have these permission "Schema Admins, Domain Admins and Enterprise Admins" to install exchange 2013 server.
    If this is a clean exchange 2013 installation, please try to recreate the system mailbox to check the result.
    Cara Chen
    TechNet Community Support

  • Security Update for exchange 2013 SP1 (KB3040856) failed mid-way / power problem mailbox server disconnected

    While applying todays security update for exchange 2013 (KB3040856) there was a power issue (sad story) and the update was interrupted halfway through.  A bunch of service were left deactivated and I beleive I brought them back.
    At this point the exchange admin center brings me to the login and when I do login, I get an enable to display page msg after the login.
    I have an ActiveSync error log  "cannot access the mailbox because the mail box server is disconnected"  translated from french.
    I also have ASP.NET 4.0 error "MapiExceptionMdbOffline"
    What could be the next step in fixing this if it is at all possible ?  I am not an expert in cmdlet but can manage if pointed in the right direction.
    Any help would be greatly appreciated.
    Thank you.

    I ran update KB3040856, and it disabled all Exchange services, and a few others besides (IIS and filtering). I ran the test-servicehealth cmdlet and eventually got all the services set to automatic and all running.
    This is really a stupid thing for an update to do, what is going on? Exchange 2013 is trouble enough already, we really do not need this sort of agro.

  • Exchange 2013 - Mailbox Setup Failed "The following error was generated when "$error.Clear()" 7 of 14

    I am getting the following error when I'm setting up the mailbox server as I'm currently doing a test virtual machine throughHyper-V, it seems to happen during the transport service phase of the installation which is 7/12
    Do i know need a D:\ drive for the mailbox server to work? as in my test i only have a c:\ drive but no d:\ drive
    Error:
    The following error was generated when "$error.Clear();
                if ($RoleProductPlatform -eq "amd64")
                    $useAttachMode = $false;
                    $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                    $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                    $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                    $dataFolderPath = $fastDefaultDataFolderPath;
                    if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                        $useAttachMode = $true;
                    else
                        if ($RoleIsDatacenter -eq $true)
                            $preferredDataFolderPathRoot = "D:\";
                            if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                                $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    $useAttachMode = $true;
                    if ($useAttachMode -eq $true)
                        &$command -action a -dataFolder $dataFolderPath -silent;
                    else
                        try
                            &$command -action i -dataFolder $dataFolderPath -silent;
                        catch
                            $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $errorMsg;
                            &$command -action u -silent;
                            try
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    [System.IO.Directory]::Delete($dataFolderPath, $true);
                            catch
                                $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
    + " - " + $_.Exception.Message;
                                Write-ExchangeSetupLog -Error $deleteErrorMsg;
            " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".
    Warning:
    An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear();
                if ($RoleProductPlatform -eq "amd64")
                    $useAttachMode = $false;
                    $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                    $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                    $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                    $dataFolderPath = $fastDefaultDataFolderPath;
                    if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                        $useAttachMode = $true;
                    else
                        if ($RoleIsDatacenter -eq $true)
                            $preferredDataFolderPathRoot = "D:\";
                            if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                                $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    $useAttachMode = $true;
                    if ($useAttachMode -eq $true)
                        &$command -action a -dataFolder $dataFolderPath -silent;
                    else
                        try
                            &$command -action i -dataFolder $dataFolderPath -silent;
                        catch
                            $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $errorMsg;
                            &$command -action u -silent;
                            try
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    [System.IO.Directory]::Delete($dataFolderPath, $true);
                            catch
                                $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
    + " - " + $_.Exception.Message;
                                Write-ExchangeSetupLog -Error $deleteErrorMsg;
            " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".
                     

    Hi 
    Most likely for these kind of issues its better you can  delete the hyper-v machine and create a new  os , ensure all the prerequisite are met and install the Exchange since this is a new installation.
    But as a try you can try giving full access to the admin account to the data folder  'C:\Program
    Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. which is giving the error and rerun the setup 
    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

  • Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

    Hi there,
    We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
    far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
    Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
    ===
    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
    ===
    I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
    with the installation or something else needs to be done first?
    Thanks in advance.

    I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
    That would be a huge disaster!
    Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
    no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
    Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
    Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
    setup /PrepareAD  /IAcceptExchangeServerLicenseTerms

  • Exchange 2013 SP1 readiness check failing

    Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
    Error:
    The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
    There are many more errors relating to Enterprise admin rights etc.
    Please note that:
    My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
    I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
    Active Directory is at 2008 R2 for domain and forest functional levels.
    I tried rejoining the new Exchange designated server to the domain
    I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
    There is a local domain controller that is a global catalog server on the new Exchange server subnet
    I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
    on the datacentre server
    AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
    This error is in the event log:
    The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ExSetupUI.exe
    6724
    Get Servers for domain.local
    TopologyClientTcpEndpoint (localhost)
    3
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    --- End of inner exception stack trace ---
    Server stack trace:
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at System.ServiceModel.ICommunicationObject.Open()
    at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
    at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
    the message resource is present but the message is not found in the string/message table

    So I decided to re-install the OS, worked perfectly now. Only difference from before would be:
    SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
    The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
    I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
    and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
    10 or so Microsoft Windows updates haven't installed on the new OS build yet.
    Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though. 

  • Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage

    Hello,
    I am trying to uninstall Exchange 2013 SP1 but it is failing while uninstalling Language step # 8 the error is;
    Error:
    The following error was generated when "$error.Clear();
                        $regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';
                        $PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";
                        $InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;
                        if(test-path ($regPath))
                            Write-ExchangeSetupLog -info ("Removing " +  $RoleLanguagePackType + " Language Packs.");
                            Get-ChildItem ($regPath) | foreach{
                                if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
                                    $langPackPackageCode = $matches['ProductCode'];
                                    if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne
    0) {
                                        Write-ExchangeSetupLog -info ("Removing package
    $langPackPackageCode");
                                        $language = $langPackPackageCode.Substring(20,4);
                                        $logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall")
    + '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
                                        uninstall-MsiPackage -ProductCode ($langPackPackageCode)
    -LogFile ($logFilePath);
                            Get-Childitem -Path $InstallPath -include "*.Localized.js","*.Localized.min.js" -recurse | foreach
    ($_) {remove-item $_.fullname};
                            Write-ExchangeSetupLog -info "Remove Language Packs completed.";
            " was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
    I am also attaching the snapshots. Please guide me how to uninstall Exchange 2013. I had some issue with Exchange Server and it need to uninstall and re-install the Exchange Server.

            " was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
    Hi,
    Based on this error, possible cause may the path of language package is too long. Please check the following things:
    Where is your language package installed? Please check it.
    Under 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}", please check the following entries. By default, it should be like this.
    InstallSource (Z:\Applications\Server\Exchange\2013\64-Bit\RTM\en\)
    ModifyPath (MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C})
    UninstallString MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C}
    Under 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup, check this entry MsiInstallPath. By default, the value should be “C:\Program Files\Microsoft\Exchange Server\V15\”
    Best Regartds.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Exchange 2013 Domain Prep Fails: Setup /prepareschema, setup /PrepareAD, Setup /PrepareDomain

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    whenever I try to run Setup /prepareschema OR setup /PrepareAD OR Setup /PrepareDomain
    I am working on a Server 2012 standard machine with Exchange 2010 currently installed. This server is a DC (bad I know), DNS, DHCP.
    I am trying to prep the domain so that I can install Exchange 2013 on a VM and eventually remove Exchange 2010 from the organization altogether.
    There are no other domain controlelrs in the domain. The domain started life as a SBS 2003 machine which was demoted and removed once the server 2012 box was up with exchange 2010 running.
    Any help would be greatly appreciated.
    Here is some info that may help:
    1. PrePare Schema
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareSchema
    This command should perform the following tasks:
    A: Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with 
    Exchange 2013 specific attributes. The LDIF files are copied to the Temp directory and then deleted after they are imported 
    into the schema.
    B: Sets the schema version (ms-Exch-Schema-Verision-Pt) to a Exchange 2013 value.
    This command fails with: Earlier versions of server roles that were installed were detected.
    First I confirmed that administrator account for domain is a member of schema admins and enterprise admins.
    Next I ran asdiedit.
    I navigated to: "CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=BDA,DC=LAN"
    and reviewed the current "rangeUpper" attribute.
    The ms-Exch-Schema-Verision-Pt is not updated to CU3 range Upper setting.
    The current range upper 14734 which means its still at Exchange 2010 SP3 settings. 
    In short, updaing the schema fails.
    2. Prepare Active Directory
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    setup /PrepareAD [/OrganizationName:<organization name>]
    This command fails with: Earlier versions of server roles that were installed were detected.
    schema update version 56
    I began reviewing the long, long list of the following containers and objects under
     CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
    which are required for Exchange 2013:
    missing cn=Auth Configuration
    missing CN=ExchangeAssistance
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Workload Management Settings
    Checked Management role groups within the Microsoft Exchange Security Groups OU
    missing Compliance Management group  --- Manually created this entry
    Step 3 Prepare Domain:
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareDomain
    This command fails with: Earlier versions of server roles that were installed were detected.
    confirmed the following:
    ObjectVersion property fails as it is still set to Echange 2010 sp3 -  13040
    You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers-DONE
    The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.-DONE
    On each domain controller in a domain in which you will install Exchange 2013, the Exchange Servers USG has permissions 
    on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.-DONE
    Thanks.

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    Hi,
    That tells us that you are trying to run the prep on your combined DC and Exchange 2010 Server - That will not work. Run it on the Server where you plan to install Exchange 2013.
    It is not mandatory to run this before the actuall Exchange install - It will run automatically for you, if it hasn't been done already and if you are logged on with an account with the proper permissions.
    Martina Miskovic

  • Exchange 2013 Sp1 says that it is 'Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup'

    So, I have decompressed my brand new download of Exchange 2013 SP1. This was downloaded from the link at the bottom of the post.
    So to start my upgrade I have tried to start by running the schema preparation which then advises me that I am welcomed to:
    'Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup'
    Is this poor QA or was the incorrect file uploaded?
    http://www.microsoft.com/en-us/download/details.aspx?id=41994

    Hello,
    Powershell need full path to file you want to run.
    So you should run .\setup.exe instead of just setup.exe.
    Hope this help.
    Regards, Pavel.

  • Exchange 2013 SP1 - The attempt to search the administrator audit log failed.

    During migration process from Exchange 2010 to 2013, after moving Arbitration mailbox from Exchange 2010 database to Exchange 2013 SP1 database, cmdlet Search-AdminAuditLog fails with following error.
    The attempt to search the administrator audit log failed. Please try again later.
    + CategoryInfo : NotSpecified: (:) [Search-AdminAuditLog], AdminAuditLogSearchException
    + FullyQualifiedErrorId : [Server=EX2013,RequestId=517873e3-a623-4363-bfdc-e5aa23595c33,TimeStamp=29. 4. 2014
    8:38:37] [FailureCategory=Cmdlet-AdminAuditLogSearchException] 2774D0CF,Microsoft.Exchange.Management.SystemConfig
    urationTasks.SearchAdminAuditLog
    + PSComputerName : ex2013.domainname.local

    Hi,
    First, please make sure the Microsoft Exchange Search and the Microsoft Exchange Search Host Controller service are running and please run the get-mailbox -arbitration cmdlet to check the result.
    Besides, please check the properties of the DiscoverySearchMailbox and verify that the homeMDB attribute is set to a mounted database.
    If the steps above don't work, please try to re-create a new Discovery System Mailbox to check the result. You can refer to the following article.
    Re-Create the Discovery System Mailbox
    http://technet.microsoft.com/en-gb/library/gg588318(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 SP1: Fix for failing MSExchangeTransport service

    We had a newly updated Exchange 2013 SP1 that would not start the Transport service
    "Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
    After many tears, I found this solution: 
    Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive.  Disable it.
    Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
    If both services restart normally, troubleshooting is complete.
    We use several custom connectors carried forward from the previous installation, which was SBS 2008.  If this applies to you, take notice.

    Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
    1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
    2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
    Step by Step Screencasts and Video Tutorials

Maybe you are looking for

  • Gmail push not working since upgrading to 4.0

    I have not been able to get my email to push since upgrading to 4.0. I have a 3GS and it worked great until the upgrade. Still have it set to push. Tried deleting itunes completely and then restore of iphone. Still no go. Please help.

  • Doubts in internal table logic

    Hi All, I have two internal table, according to the posnr value i need to add the kbetr value from the 2nd internal table and update the value in the 1st line internal table. below the example of my internal table. Here for the line item 0010 i need

  • Oracle Collaboration Suite download disappear

    Hi, Where can I download the Oracle Collaboration Suite. Few weeks back I was able to see the download page, now they are nowhere to find. Thank you.

  • Mosier

    I just purchased an new macbook air, i have been unable to install adobe flash, due to password problems.  I created an adobe id and password for the site, but when i go to use it to install flash, it won't work.  Any help on why, or what password to

  • I managed to uninstall/delete iMovie, how can I get it back?

    Hi All, iMovie was pre-installed on my MacBook Air but I managed to uninstall/delete it, how can I get it back without having to pay for it in the App Store? Cheers, SF