Installing Exchange 2013 CU 6 failed

Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:
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;
          Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");
          Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
-ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;
          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: "Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information:
General Error.
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)
   at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)
   at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.
Any ideas how to solve this?

Hi,
From the description of the error “ Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information: General Error. ”
Appeared to have some valid proxy address. Please check if there are invalid characters in the admin account proxy address.
To find the proxy address, take the following steps:
Open ADUC, Click View in the menu then click
Advanced Features.
Navigate to yourOrganization >> Users, choose the admin account, right-click to
Properties.
Under Attributes Editor tab, find the proxyaddresses
Attribute, then check the address.
Hope this will be helpful for you.
Best Regards.

Similar Messages

  • Reading Exchange Online tenant version failed due to an exception when trying to install Exchange 2013 in a hybrid environment.

    We currently have an Exchange 2010 hybrid install and we have migrated all of our email accounts to Office 365.  Now, I want to do an on-premise install of Exchange 2013 to better manage the hybrid setup.  When I try to install Exchange 2013 it
    asks for my O365 credentials to do a hybrid check but always fails with the above message.  I've done quite a bit of searching but haven't come up with anything useful.
    Here is what appears in the exchange setup log:  
    [09/22/2014 15:48:27.0024] [0] Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log for more information.
    [09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, 
    [09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, 
    [09/22/2014 15:48:27.0147] [0] Session=Tenant Total Cmdlet Time=1.6931035s
    [09/22/2014 15:48:27.0148] [0] Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetectionException: Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log
    for more information. ---> System.TypeLoadException: Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,

    Hi,
    I recommend you post this in
    office 365 forum also, as they should have more professional knowledge on hybrid deployments
    and you may get effective solution timely.
    In addition, I found a similar thread for you reference:
    http://community.office365.com/en-us/f/156/t/255739.aspx
    According to the reply of this thread, if you run the HCW (Hybrid Configuration Wizard) to deploy the Exchange Hybrid environment, there will generate an HCW log
    file for this deployment.
    Additional troubleshooting information is available in the Update-HybridConfiguration log file located at C:\Program Files\Microsoft\Exchange Server\V1*\Logging\Update-HybridConfiguration\HybridConfiguration****.log
    Best regards,
    Niko Cheng
    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

  • Installation Error Installing Exchange 2013 CU3 on Server 2012

    Hello,
    When Installing Exchange 2013 on server 2012 I get the following error during Step 1 of 8 of Transport Service. I have installed and unistalled Exchange a few times, restarted the machine manually and removed exchange from AD, etc. to no avail.
    Any suggestions will be very much appreciated.
    Thank You.
    VK
    Error:
    The following error was generated when "$error.Clear();
              install-MsiPackage `
              -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASDat.MSI") `
              -LogFile ($RoleSetupLoggingPath + "\InstallASDat.msilog") `
              -PropertyValues ("ALLUSERS=1") `
              -UpdatesDir $RoleUpdatesDir
            " was run: "Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. This action is only valid for products that are currently installed. Error
    code is 1605.".

    Martina,
    Thank you for your response. KB says that Machinepolicy and Userpolicy are to be set to Undefined and that is what I have.
    Windows PowerShell
    Copyright (C) 2013 Microsoft Corporation. All rights reserved.
    PS C:\Users\Administrator> get-executionpolicy –list
    Scope                                            
    ExecutionPolicy
    MachinePolicy                                                  
    Undefined
    UserPolicy                                                  
    Undefined
    Process                                                  
    Undefined
    CurrentUser                                                  
    Undefined
    LocalMachine                                               
    RemoteSigned
    VK

  • Can't install Exchange 2013 after previous uninstall (insufficient user privileges with the same user)

    I have installed Exchange 2013 on Windows Server 2012, which ist a member of a Windows Server 2012 R2 Domain. All prerequisites and AD modifications were successfully  completed and I could install Exchange 2013. Unfortunately I made a mistake with
    the target directory and had to uninstal Exchange 2013. If I start the Setup again, it fails in prerequisite check - the current user should not be a member of Enterprise and Schema admin Group, but it's the same user, which comleted the previous Installation
    of Exchange 2013! Do you have any idea how to solve this Problem - I'm running out of ideas.

    Inhave tried to run setup /PrepareSchema again and get the following error in exchange setup log:
    [03.07.2014 19:25:53.0305] [0] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
    [03.07.2014 19:25:53.0337] [0] Validating options for the 0 requested roles
    [03.07.2014 19:25:53.0383] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
    [03.07.2014 19:25:53.0399] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    After removing all Exchange Parts by ADUC (advanced View) and ADSI Edit (Services) I'm able to install Exchnge 2013 again - the uninstall procedure seems not to work in a clean manner.

  • Installé Exchange 2013 on win 2k8R2

    hello please i have this error msg when installing exchange 2013 on win 2k8R2 on the maibox step
    $error.clear(); start-SetupService -ServiceName MSExchangeSubmission was run: service MSExchangeSubmission failed to reach status Running on this server..
    i done every thing that i see in the forum always nothing 

    yes i install all the prerequisites for exchange am on 2k8R2 do i need to install the both
    office filter pack

  • Cannot install Exchange 2010 after installing Exchange 2013

    Hi,
    I have the current setup as explained below.
    Exchange 2010 SP3 Version 14.3 (Build 123.4)
    I installed Exchange 2013 as well to the setup. After installation everything was fine, but my backup solution was not as good enough to support Ex2013. So, I had to roll back. I uninstalled Ex 2013.
    On the new server (on which I actually installed EX 2013) I tried installing Ex 2010 but it failed. But, when I execute Get-ExchangeVersion I get these two.
      AdminDisplayVersion                     ExchangeVersion
      Version 14.3 (Build 123.4)              0.1 (8.0.535.0)
      Version 14.0 (Build 639.21)             0.1 (8.0.535.0)
    The first one is the live Exchange 2010 ( The first one which we had). When I try to run the setup, I am getting the following Error.
    Error:
    The following error was generated when "$error.Clear(); get-OfflineAddressBook -DomainController $RoleDomainController | where { $_.IsDefault } | Enable-OabWebDistribution" was run: "Object is read only because it was created by a future version
    of Microsoft Exchange: 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).".
    What can I do now? My intention is just to create another Exchange Server for redundancy. I only have one EXchange server now. I tried installing EX 2013, and it seems not suit me because of backup issue. What I have in my mind is to get 2 Ex 2010 Servers.
    Should I try uninstalling EX 2010 and installing it from the beginning on the new EX Server?
    Thanks

    Hi Steve,
    I have the same situation, On a new server (on which I actually installed EX 2013) I tried installing Ex 2010.
    In the Client Access Role install setup, I getting:
    Error:
    the following error was generated when "$error.Clear(); get-OfflineAddressBook -DomainController $RoleDomainController | where {$_.IsDefault} | Enable-OabWebDistribution" was run: "Object is read only because it was created by a future version of Microsoft
    Exchange: 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0)
    Admin Display Version
    server 1 version 14.3
    server 2 version 14.0 (Client Access Role Error)
    how can I resolve this error?
    Thanks.
    Regards.

  • Exchange 2013 SP 1 fails MSSpeech_SR_TELE.ca-ES.msi

    Hi
    After trying to install exchange 2013 SP 1 it fails with the following error : MSSpeech_SR_TELE.ca-ES.msi couldn't be opened.
    I'm running the upgrade through the command line with elevated privileges.
    I've re downloaded the sp already 2 times to no avail.
    The file exists in the extracted version.
    Same error occurred in CU 2 I've read on forums.
    [03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\[03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\[03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify
    that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup'. This installation package could not be opened. Verify that the package exists and that you
    can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup'. This installation package could not be opened. Verify that the package exists and that you
    can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

    Thanks for the update John!
    From what I have read, it can work running the upgrade in Windows Powershell, but the syntax must be right.
    .\Setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
    compared to:
    Setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
    Rhoderick Milne has a great blog post about this, so check it out: 
    6 Mistakes To Avoid With Exchange 2013 CU Command Line Installations . Personally I haven't tried that - So used to always run any exchange CU/SP or Rollup in the command line :)
    Martina Miskovic

  • Installing Exchange 2013 on Windows Server 2012 R2

    Now that SP1 has been released, it is supported to run Exchange 2013 on Windows Server 2012 R2
    But since it is not yet possible to download Exchange 2013 with integrated SP1 (slipstreamed), is the following installation procedure supported:
    - Install Exchange 2013 (without SP1) on Windows Server 2012 R2
    - Install SP1 on top of Exchange 2013
    If this is not supported, can someone tell me when the Exchange 2013 with integrated SP1 (slipstreamed) download will be released?

    yes the SP1 is the full product. if you need step by step instruction to migrate to this new version you can get info here : http://buenoflex.com/install-exchange-2013-sp1/
    Arnaud Buonaccorsi - GSX Groupware Solutions
    http://www.buenoflex.com
    http://www.gsx.com <= The monitoring solution for Exchange and Sharepoint

  • Getting Error while installing Exchange 2013 on server 2012

    Error During Exchange 2013 Mailbox Transport
    Role Install On Server 2012 
    Exchange
    Server forums
     > 
    Exchange
    Server 2013 - Setup, Deployment, Updates, and Migration
    Question
    1
    Sign
    in to vote
    I was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past
    the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:
    Step 8 of 15: Mailbox role: Transport service
    Error:
    The following error was generated when "$error.Clear(); 
              $maxWait = New-TimeSpan -Minutes 8
              $timeout = Get-Date;
              $timeout = $timeout.Add($maxWait);
              $currTime = Get-Date;
              $successfullySetConfigDC = $false;
              while($currTime -le $timeout)
                $setSharedCDCErrors = @();
                try
                  Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
                  $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
                  if($successfullySetConfigDC)
                    break;
                  Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
                catch
                  Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
                Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
                Start-Sleep -Seconds 30;
                $currTime = Get-Date;
              if( -not $successfullySetConfigDC)
                Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "Unable to set shared config DC.".

    Hi Deepak,
    From the error description, I would like to clarify the following things:
    1. Please ensure that IPv6 on the network adaptor is turned on.
    2. Please check if the account that you used to install Exchange has necessary permissions to perform the installation.
    3. Make sure that DNS is configured correctly.
    Hope my clarification is helpful.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Is it ok to install Exchange 2013 on Windows Server 2012 Standard?

    Hello everyone,
    I'd like to know if it is ok/safe to install Exchange Server 2013 on Windows Server 2012 Standard?
    As I started doing some research and noticed a page where Microsoft states they don't recommend running Exchange on Server 2012 Standard, and recommend making 2 different servers one for Active Directory and another for Exchange.
    On that page they also listed some features that wouldn't work in case of Exchange is running on Server 2012. And that it may put a larger data load if setup this way.
    I am hoping someone knowledgeable can explain and tell me if it is safe to use such setup or if it is better to use something like SBS 2011 Standard instead, which has Exchange included?
    Has anyone installed Exchange 2013 on Server 2012 Standard successfully and used it for more then several months without problems?
    Also just to give an idea on my background, I've been in IT field fairly long but haven't really updated to newer versions much and mainly used SBS 2003 and 2008 only with a few clients so haven't used 2008 too much.
    Thanks in advance.

    Few things to note.
    There is
    NO SBS in 2012
    All you need is a Std edition of Windows for Exchange 2013, as there is no difference in features between Std and Datacenter as far as Exchange is concerned.
    For 10 users, you can have one box with both AD and Exchange. It is not MS recommeded, but it IS supported.
    Rajith Enchiparambil |
    http://www.howexchangeworks.com |

  • Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

    Dear all
    During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
    wa' on 'MONAMBX2'.".
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
    und on 'MonaDc1.mona.local'.".
    Any advice please !!

    I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive.  Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
    error messages saying the database does not exist.  It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting.  To get around it, I deleted the database and created a new one on the drive
    where we wanted it.
    I discovered this when I was configuring the Antispam settings.  I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server.  The shell on 2013 was making changes to 2007.
    I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens.  Or maybe my issues will be fixed if I just remove the Exchange 2007 server?  I'm not ready to do that yet because I can't configure the spam filtering
    on 2013 yet with its shell not being able to make the changes that we need.
    I don't know if your environment is in coexistence mode like mine.
    Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server.  Does this happen after the 2007 server is removed?

  • Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

    I currently have an Exchange 2010 server with all the roles installed.  Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error.  When I installed Exchange 2013, I got an error saying I
    had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left.  There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group.  This deletion caused my access
    to my public folders to get messed up.  I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA.  I also get this error when
    trying to access either Default or System Public Folders.  "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
    -server 'ExchangeServer' "
    My Public Folder Database exists and is mounted.  Any help is appreciated.

    Hi Belinda,
    Thank you for responding.  Yes you do understand my problem correctly.  One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA.  I followed these steps in the below article:
     http://blog.bruteforcetech.com/archives/766
    After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
    Here are the results to your requests:
    et-PublicFolder -Recurse | Format-List Name
    Name : IPM_SUBTREE
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    [PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
    Name : NON_IPM_SUBTREE
    Name : EFORMS REGISTRY
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
    CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

  • Re-install Exchange 2013

    I started a basic install of Exchange 2013 on Windows 2012 on a network with an existing Exchange 2007 (SBS 2008) org.
    Things went well with prerequisites and AD Prep but the actual install ended up freezing up. I ran it on a VM with 2GB RAM and all I can guess is that services couldn't start etc with only that much RAM. I did the install through a remote desktop session
    and when I returned after kicking off the install process that session was completely frozen up with a black screen. All I could do was reboot the server. I noticed messages that implied the completely new/blank Exchange install was unhappy with 2GB so I raised
    it to 10GB, but still things just didn't work. Most significantly I couldn't even load the Management Console replacement web site. I just would get 404 not found.
    Thinking the original install never completed properly I simply deleted the VM, re-created a new one with the same config (and 10GB RAM) with the same name, joined the domain, installed pre-requisites and re-started the install, but now I'm getting
    "Exchange Server in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer"...
    Of course now I get other errors because "Disaster Recovery setup needs access to the mailbox database drive (prior install location)" etc. and of course I have no backups or anything because there was nothing but deployed install media on the
    prior server.
    How do I re-install? Do I need to clean up AD references to the prior install?
    Regards,
    Steve Ware

    Hello,
    Yes. You should check if the uncompleted exchange server is in AD. If it is in AD, please remove it and then reinstall it.
    And you can remove the VM, and create a new VM, and then install new exchange server whose name is different from the uncompleted exchange server.
    Additional article for your reference.
    Install Exchange 2013 in an Existing Exchange 2007 Organization
    http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Installing Exchange 2013 errors

    Problems installing Exchange 2013 on a new Server 2012 r2.   Existing Exchange is 2007 on a SBS 2008r2. 
    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.".

    Hi
    Remove thinking of SBS server because this part might scare you . It is just the same process of migrating it from Exchange 2007 to Exchange 2013 . You just need both the server operating smoothly until this migration is complete.
    First Make sure you're running Rollup 10 of SP3 for Exchange 2007 and that you have atleast Exchange 2013 CU1  else the installation won't proceed further.
    You need to have a seperate box for installing Exchange 2013.
    I would recommend you to follow this artilcle which has clear cut information
    http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
    http://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
    Please let us know if you have already tried the above things. You can paste any errors generated in the app and sys logs in the installation server.
    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.
    Regards
    Sathish

Maybe you are looking for