Exchange 2013 Install Readiness check problem

We have a test environment which was 2008R2 AD.  We properly went through the migration path and are currently at 2012R2 Active Directory functional level.
I'm installing Exchange 2013 with Sp1 into the domain.  I have successfully prepared the domain as outlined on technet, and verified its success with the logs and looking in ADSI edit.  No errors.  All seems to have ran correctly.
When I attempt to install the first exchange mailbox server, the Readiness check fails saying "the local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed"...  1 forest, 1 root domain, 1 child domain.
 The account I'm using is a member of Schema Admins, Enterprise Admins, Domain admins etc.  
Has anyone else come across this or have any suggestions?

Thanks for the replies.  Yes, replication has occurred.  We have 2 DC's in the root, and 2 DC's in the child.  After each prepare I ran "repadmin /syncall", each time completing successfully.  I also verified the settings in
ADSI edit, and all match up correctly to the chart.  The exchangesetup logs indicate each prepare runs successfully.
I have also rebooted all 4 DC's and the Exchange server I'm trying to install.  I have verified the record in DNS.  Where is the script that the Readiness check is running?  I may look into taking that check out of the script!
Also, looking at the exchangesetup log, it is showing different information in it than before (same error on the GUI screen).  
[04/09/2015 12:21:46.0081] [1] Failed [Rule:DomainPrepRequired] [Message:The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed.]
[04/09/2015 12:21:46.0081] [1] [REQUIRED] The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed.
[04/09/2015 12:21:46.0081] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DomainPrepRequired.aspx
[04/09/2015 12:21:46.0097] [1] Ending processing test-SetupPrerequisites
[04/09/2015 12:21:46.0097] [0] Exchange Server installation failed during prereq check. Trying to restore the server state back to active.
[04/09/2015 12:21:46.0097] [0] RestoreServer Script Path: C:\Windows\Temp\ExchangeSetup\RestoreServerOnPrereqFailure.ps1
[04/09/2015 12:21:46.0222] [0] Beginning processing Write-ExchangeSetupLog
[04/09/2015 12:21:46.0222] [0] Trying to restore server state.
[04/09/2015 12:21:46.0222] [0] Ending processing Write-ExchangeSetupLog
[04/09/2015 12:21:46.0222] [0] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'npsdom002.xxxx.xxxxx.pri', Preferred Global Catalog: 'npsdom002.xxxxx.xxxxx.pri', Preferred Domain Controllers:
'{ npsdom002.xxxxx.xxxxx.pri }'
[04/09/2015 12:21:46.0222] [0] User specified parameters:  -ErrorAction:'SilentlyContinue' -Identity:'NPSXMB002'
[04/09/2015 12:21:46.0222] [0] Beginning processing get-ExchangeServer
[04/09/2015 12:21:46.0222] [0] Searching objects "NPSXMB002" of type "Server" under the root "$null".
[04/09/2015 12:21:46.0238] [0] Previous operation run on domain controller 'npsdom002.xxxx.xxxx.pri'.
[04/09/2015 12:21:46.0238] [0] Previous operation run on domain controller 'npsdom002.xxxxxx.xxxxx.pri'.
[04/09/2015 12:21:46.0238] [0] Preparing to output objects. The maximum size of the result set is "Unlimited".
[04/09/2015 12:21:46.0238] [0] The operation couldn't be performed because object 'NPSXMB002' couldn't be found on 'npsdom002.xxxxx.xxxxx.pri'.
[04/09/2015 12:21:46.0238] [0] The operation couldn't be performed because object 'NPSXMB002' couldn't be found on 'npsdom002.xxxx.xxxxx.pri'.
[04/09/2015 12:21:46.0238] [0] Ending processing get-ExchangeServer
[04/09/2015 12:21:46.0238] [0] Beginning processing Write-ExchangeSetupLog
[04/09/2015 12:21:46.0238] [0] [WARNING] NPSXMB002 is not an Exchange Server. Unable to set monitoring and server state to active.
[04/09/2015 12:21:46.0238] [0] Ending processing Write-ExchangeSetupLog

Similar Messages

  • 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. 

  • 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 Server 2013 SP1 - Readiness Check Failing - Detected Non-existent Exchange 2007 Servers

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

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

  • SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

    SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The virtual directory 'ecp' already exists under 'server/name'.
    Parameter name: VirtualDirectoryName".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    !! And now transport service won't start and mail is unavailable !!
    Any help would be appreciated.
    I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

    Hi,
    Thanks for your response.
    From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange Server 2013 failing Readiness Checks

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

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

  • Exchange 2013 Install Failure

    I am REALLY struggling with this exchange install.  
    Current exchange environment is Exchange 2010 SP3.
    I am getting an error when trying to install the Mailbox Role: Mailbox Service.  I can see only one "error" but at this stage i'm sure my eyes aren't catching everything.
    "Address list or global address list "livingstonisd.com/Configuration/Deleted Objects/HIgh School Staff List
    DEL:acf86229-9d20-4e80-b99b-47daf139e822" was not found. Please make sure you typed the identity correctly.".
    I cannot seem to find this object its referencing.  I have checked in ADSI on AD inside of configuration and I cannot find THIS address book.  All of my ones that are supposed to be there are.
    I may well have this one pegged wrong.... here is the entire error so someone can tell me if I simply missed my problem in amongst all this.
    Error:
    The following error was generated when "$error.Clear(); 
              if (!$RoleIsDatacenter)
                $createNewOab = $false;
                $oabName = $null;
                $oabAddressList = $null;
                $oabVdirs = $null;
                $oabGlobalWebDistribution = $false;
                $oabConfiguredAttributes = $null;
                Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
                $defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
                if ($defaultOab -ne $null)
                  Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + "; checking its version");
                  if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -lt 0)
                    Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older; will create a new OAB");
                    $createNewOab = $true;
                    $oabName = $defaultOab.Name + " (Ex2012)";
                    $oabAddressList = $defaultOab.AddressLists;
                    $oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
                    $oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
                  else
                    Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2012 or newer; will not create a new OAB");
                else
                  Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
                  $createNewOab = $true;
                  $oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
                  $nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController -ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
                  if ($nonDefaultOabWithDefaultName -ne $null)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Offline address book " + `
                      $nonDefaultOabWithDefaultName.Name + `
                      " already exists: " + `
                      $nonDefaultOabWithDefaultName.DistinguishedName + `
                      ". Use administrative tools to change it to default OAB.");
                  $allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
                  if ($allGals -eq $null -or $allGals.Count -eq 0)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Couldn't find the default global address list. The default offline address book can't be created.");
                  elseif ($allGals.Count -gt 1)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Found " + $allGals.Count + " default global address lists. You can have only one default global address list in your organization. The default offline address book will
    not be created.");
                  else
                    $oabAddressList = $allGals[0];
                    Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
                if ($createNewOab)
                  if ($oabGlobalWebDistribution -eq $false)
                    $currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
                    $allOabVdirs = @(Get-OabVirtualDirectory -DomainController:$RoleDomainController);
                    $e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
                    if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
                      foreach ($oabVdir in $allOabVdirs)
                        if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion, $e15MinimumServerVersion) -gt 0)
                          $oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server -DomainController:$RoleDomainController).Site.DistinguishedName;
                          if ($oabVdirSiteDn -eq $currentAdSiteDn)
                            $oabVdirs = $oabVdir;
                            break;
                          elseif ($oabVdirs -eq $null)
                            $oabVdirs = $oabVdir;
                    if ($oabVdirs -ne $null)
                      Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual directory " + $oabVdirs.Name);
                    else
                      Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories; OAB will be configured without distribution.");
                  try
                    Write-ExchangeSetupLog -Info ("Creating new default OAB.");
                    $newOab = New-OfflineAddressBook `
                      -Name $oabName `
                      -AddressLists $oabAddressList `
                      -VirtualDirectories $oabVdirs `
                      -GlobalWebDistributionEnabled $oabGlobalWebDistribution `
                      -IsDefault $true `
                      -DomainController:$RoleDomainController;
                  catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
                    Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object already exists; it may have been created by another instance of setup.");
                  if ($oabConfiguredAttributes -ne $null)
                    Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " + $oabConfiguredAttributes);
                    Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
            " was run: "Address list or global address list "livingstonisd.com/Configuration/Deleted Objects/HIgh School Staff List
    DEL:acf86229-9d20-4e80-b99b-47daf139e822" was not found. Please make sure you typed the identity correctly.".
    Error:
    The following error was generated when "$error.Clear(); 
              if (!$RoleIsDatacenter)
                $createNewOab = $false;
                $oabName = $null;
                $oabAddressList = $null;
                $oabVdirs = $null;
                $oabGlobalWebDistribution = $false;
                $oabConfiguredAttributes = $null;
                Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
                $defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
                if ($defaultOab -ne $null)
                  Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + "; checking its version");
                  if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -lt 0)
                    Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older; will create a new OAB");
                    $createNewOab = $true;
                    $oabName = $defaultOab.Name + " (Ex2012)";
                    $oabAddressList = $defaultOab.AddressLists;
                    $oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
                    $oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
                  else
                    Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2012 or newer; will not create a new OAB");
                else
                  Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
                  $createNewOab = $true;
                  $oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
                  $nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController -ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
                  if ($nonDefaultOabWithDefaultName -ne $null)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Offline address book " + `
                      $nonDefaultOabWithDefaultName.Name + `
                      " already exists: " + `
                      $nonDefaultOabWithDefaultName.DistinguishedName + `
                      ". Use administrative tools to change it to default OAB.");
                  $allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
                  if ($allGals -eq $null -or $allGals.Count -eq 0)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Couldn't find the default global address list. The default offline address book can't be created.");
                  elseif ($allGals.Count -gt 1)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Found " + $allGals.Count + " default global address lists. You can have only one default global address list in your organization. The default offline address book will
    not be created.");
                  else
                    $oabAddressList = $allGals[0];
                    Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
                if ($createNewOab)
                  if ($oabGlobalWebDistribution -eq $false)
                    $currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
                    $allOabVdirs = @(Get-OabVirtualDirectory -DomainController:$RoleDomainController);
                    $e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
                    if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
                      foreach ($oabVdir in $allOabVdirs)
                        if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion, $e15MinimumServerVersion) -gt 0)
                          $oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server -DomainController:$RoleDomainController).Site.DistinguishedName;
                          if ($oabVdirSiteDn -eq $currentAdSiteDn)
                            $oabVdirs = $oabVdir;
                            break;
                          elseif ($oabVdirs -eq $null)
                            $oabVdirs = $oabVdir;
                    if ($oabVdirs -ne $null)
                      Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual directory " + $oabVdirs.Name);
                    else
                      Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories; OAB will be configured without distribution.");
                  try
                    Write-ExchangeSetupLog -Info ("Creating new default OAB.");
                    $newOab = New-OfflineAddressBook `
                      -Name $oabName `
                      -AddressLists $oabAddressList `
                      -VirtualDirectories $oabVdirs `
                      -GlobalWebDistributionEnabled $oabGlobalWebDistribution `
                      -IsDefault $true `
                      -DomainController:$RoleDomainController;
                  catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
                    Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object already exists; it may have been created by another instance of setup.");
                  if ($oabConfiguredAttributes -ne $null)
                    Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " + $oabConfiguredAttributes);
                    Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
            " was run: "Cannot bind argument to parameter 'Identity' because it is null.".
    I am completely lost.  Thanks for any and all help/suggestions.

       $oabName = $defaultOab.Name + " (Ex2012)";
    Hi,
    That tells us that you are trying to install Exchange 2013 RTM.
    Do note that you CU1 was the first build of EX13 where coexistence with earlier versions was supported.
    Now when
    CU2 is out, I highly recommend that you install that build, even if I don't think using wrong build is the reason for your problem.
    Can you check your OABs and make sure that they don't have any orphaned Address Lists assigned to them?
    Martina Miskovic

  • Exchange 2013 Install Issues

    Hi everyone -
    I'm having BIG issues with my Exchange setup.  First off, I walked into a nightmare of a situation here and it seems everything is completely jacked up in terms of network and servers...  I'm actually contemplating starting over 100% with everything,
    but when I bring that up to upper management, they say it's not feasible.
    We currently have Exchange 2007 SP3 with RU11.  I found out that when SP3 was installed, whoever did it never updated AD or the schema.  Now I can't do that because i'm on RU11 and it's giving me a version mismatch error.  So I've decided
    to move on to just upgrade to Exchange 2013.
    I am on the beginning steps of doing this and I just ran:  setup /PrepareAD /IAcceptExchangeServerLicenseTerms.  When doing this I get the following nasty little error:
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    FAILED
     Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
    een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
     Cannot find the Recipient Update Service responsible for domain 'DC=kuder,DC=local'. New and existing users may not be
    properly Exchange-enabled.
         One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003. Installa
    tion can't proceed until all Exchange 2000 or Exchange 2003 servers are removed.
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    A couple of notes about this error:
    1. I swear I've gotten some errors about the Recipient Update Service with Exchange 2007.  I'm think that might have lead me to the schema upgrade issue I talked about earlier.
    2.  We DO NOT have Exchange 2000 or 2003 in our environment!!!  Not sure where to even begin to remove the remnants of this!
    Any help would be greatly appreciated.
    Thanks,
    Jeff

    Thanks for the reply Cara...  After further investigation last night it is clear to me that whoever upgraded us from Exchange 2003 to Exchange 2007, definitely didn't decommission the 2003 box correctly.  (this was all done WELL before I came around). 
    I've checked into a few things that you asked about:
    1.  In ADSI Edit, I have 2 Administrative groups.  the first one (Exchange Administrative Group (FYDIBOHF23SPDLT)) shows the correct 2007 server in the CN=Servers, the other one (first administrative group) shows the old 2003 box
    under CN=Servers.
    2.  I did get the schema update for 2007 SP3 to finally go.  so when I looked in ADSI Edit, the Exchange Schema version is 14625 which according to that article is Exchange Server 2007 SP3, which is correct.  Last time I looked, it was 14622,
    which was for SP2.  So we should be good there now.
    3.  The error with the RUS, was in Exchange 2007 BPA.  After investigating this further last night, this is again because of failure to properly decommission the old 2003 box.  Looks like I maybe need to remove any entries for Recipient Update
    Service under ADSI Edit:  CN=Configuration,DC=domainname -> CN=Services -> CN=Microsoft Exchange -> CN=First Organization -> CN=Address List Container -> CN=Recipient Update Services.  There are two items in that location now, CN=Recipient
    Update Service (domain) and CN=Recipient Update Service (Enterprise Configuration).  From what I've read I can delete both of these since 2007 no longer uses this service.
    4.  No errors in the Application Log currently.
    Other Notes:
    1.  Everything with 2007 appears to be working fine.  No major issues.. I just want to upgrade us to Exchange 2013.
    2.  From the 2007 EMS, I ran: exchangeserver | ft name,admindisplayversion,exchangeversion.  This showed me the following:
    Name                       AdminDisplayVersion        ExchangeVersion
    ADELSB01                   Version 6.5 (Build 7638... 0.0 (6.5.6500.0)
    K01SIT003                  Version 8.3 (Build 83.6)   0.1 (8.0.535.0)
    Definitely still showing the old 2003 Exchange box in there.
    Thanks!

  • Unable to access ECP on a new Exchange 2013 Install

    I have a standalone exchange 2010 server (setup with all roles) and yesterday went ahead to setup an Exchange 2013 Server. Installed both CAS and mailbox roles for Exchange 2013 but after the install, I am unable to access the Exchange Admin Center. 
    If i try to access to https://EXCHANGE 2013 FQDN\ecp , after inserting my login information, it asks for the login information again and redirects to webmail. I have read all posts of users experiencing similar issues and tried all possible measures. 
    As the 2013 coexists with Exchange 2010 and mailboxes still reside on 2010, I have tried the URL
    https://EXCHANGE 2013 FQDN/ecp?ExchClientVer=15 but got the same result.
    Also, the CAS is installed on the server and i see the ECP virtual directory and URL.
    please see below the output for Get-ExchangeServer | FL and Get-EcpVirtualDirectory | FL
    [PS] C:\Windows\system32>Get-ExchangeServer | FL
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : NYC-HQXCH-02
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
    Domain                          : company.loc
    Edition                         : Enterprise
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQXCH-02
    ExchangeLegacyServerRole        : 0
    Fqdn                            : NYC-HQXCH-02.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : False
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : False
    IsFrontendTransportServer       : False
    NetworkAddress                  : {ncacn_vns_spp:NYC-HQXCH-02, netbios:NYC-HQXCH-02, ncacn_np:NYC-HQXCH-02,
                                      ncacn_spx:NYC-HQXCH-02, ncacn_ip_tcp:NYC-HQXCH-02.company.loc, ncalrpc:NYC-HQXCH-02}
    OrganizationalUnit              : company.loc/NYC-HQXCH-02
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Site                            : company.loc/Configuration/Sites/NewYorkHQ
    ServerRole                      : Mailbox, ClientAccess, HubTransport
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        :
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       : 02064-110-8022196-75756
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : NYC-HQXCH-02
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : 1745c93f-419d-402c-b832-708958fc502c
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 4/2/2014 1:50:56 PM
    WhenCreated                     : 8/25/2013 11:12:43 AM
    WhenChangedUTC                  : 4/2/2014 6:50:56 PM
    WhenCreatedUTC                  : 8/25/2013 4:12:43 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : NYC-HQARC-02
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
    Domain                          : company.loc
    Edition                         : Enterprise
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQARC-02
    ExchangeLegacyServerRole        : 0
    Fqdn                            : NYC-HQARC-02.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : False
    IsClientAccessServer            : False
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : False
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : False
    IsFrontendTransportServer       : False
    NetworkAddress                  : {ncacn_vns_spp:NYC-HQARC-02, netbios:NYC-HQARC-02, ncacn_np:NYC-HQARC-02,
                                      ncacn_spx:NYC-HQARC-02, ncacn_ip_tcp:NYC-HQARC-02.company.loc, ncalrpc:NYC-HQARC-02}
    OrganizationalUnit              : company.loc/NYC-HQARC-02
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Site                            : company.loc/Configuration/Sites/NewYorkHQ
    ServerRole                      : Mailbox
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        :
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       : 02064-110-8022196-75187
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : NYC-HQARC-02
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=NYC-HQARC-02,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : c07f34f4-92f1-49f0-a412-d7094eaaba3b
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 4/2/2014 1:50:57 PM
    WhenCreated                     : 9/9/2013 3:27:16 PM
    WhenChangedUTC                  : 4/2/2014 6:50:57 PM
    WhenCreatedUTC                  : 9/9/2013 8:27:16 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : SVR-EXCH-01
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox
    Domain                          : company.loc
    Edition                         : StandardEvaluation
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SVR-EXCH-01
    ExchangeLegacyServerRole        : 0
    Fqdn                            : SVR-EXCH-01.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : True
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : True
    IsFrontendTransportServer       : True
    NetworkAddress                  : {ncacn_vns_spp:SVR-EXCH-01, netbios:SVR-EXCH-01, ncacn_np:SVR-EXCH-01,
                                      ncacn_spx:SVR-EXCH-01, ncacn_ip_tcp:SVR-EXCH-01.company.loc, ncalrpc:SVR-EXCH-01}
    OrganizationalUnit              : company.loc/SVR-EXCH-01
    AdminDisplayVersion             : Version 15.0 (Build 847.32)
    Site                            : company.loc/Configuration/Sites/Chicago-COLO1
    ServerRole                      : Mailbox, ClientAccess
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        : DefaultWorkloadManagementPolicy_15.0.825.0
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       :
    IsExchangeTrialEdition          : True
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 179.06:13:25.2449639
    Identity                        : SVR-EXCH-01
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=SVR-EXCH-01,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : 91eb6d6b-bfd0-4ce0-80ce-67585e7cbeae
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 5/13/2014 6:54:13 PM
    WhenCreated                     : 5/13/2014 6:41:08 PM
    WhenChangedUTC                  : 5/13/2014 11:54:13 PM
    WhenCreatedUTC                  : 5/13/2014 11:41:08 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    [PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    AdminEnabled                    : True
    OwaOptionsEnabled               : True
    Name                            : ecp (Default Web Site)
    InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
    MetabasePath                    : IIS://NYC-HQXCH-02.company.loc/W3SVC/1/ROOT/ecp
    BasicAuthentication             : True
    WindowsAuthentication           : True
    DigestAuthentication            : False
    FormsAuthentication             : False
    LiveIdAuthentication            : False
    AdfsAuthentication              : False
    OAuthAuthentication             : False
    DefaultDomain                   : company.loc
    GzipLevel                       : High
    WebSite                         : Default Web Site
    DisplayName                     : ecp
    Path                            : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp
    ExtendedProtectionTokenChecking : None
    ExtendedProtectionFlags         : {}
    ExtendedProtectionSPNList       : {}
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Server                          : NYC-HQXCH-02
    InternalUrl                     : https://webmail.companytravel.com/ecp
    ExternalUrl                     :
    ExternalAuthenticationMethods   : {Fba}
    AdminDisplayName                :
    ExchangeVersion                 : 0.10 (14.0.100.0)
    DistinguishedName               : CN=ecp (Default Web
                                      Site),CN=HTTP,CN=Protocols,CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative
                                      Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Identity                        : NYC-HQXCH-02\ecp (Default Web Site)
    Guid                            : 0963f097-ff86-4d8f-a98a-8be409068eae
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
    ObjectClass                     : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
    WhenChanged                     : 4/2/2014 1:50:57 PM
    WhenCreated                     : 8/30/2013 1:06:50 PM
    WhenChangedUTC                  : 4/2/2014 6:50:57 PM
    WhenCreatedUTC                  : 8/30/2013 6:06:50 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    IsValid                         : True
    ObjectState                     : Changed
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    AdminEnabled                    : True
    OwaOptionsEnabled               : True
    Name                            : ecp (Default Web Site)
    InternalAuthenticationMethods   : {Basic, Fba}
    MetabasePath                    : IIS://SVR-EXCH-01.company.loc/W3SVC/1/ROOT/ecp
    BasicAuthentication             : True
    WindowsAuthentication           : False
    DigestAuthentication            : False
    FormsAuthentication             : True
    LiveIdAuthentication            : False
    AdfsAuthentication              : False
    OAuthAuthentication             : False
    DefaultDomain                   :
    GzipLevel                       : Low
    WebSite                         : Default Web Site
    DisplayName                     : ecp
    Path                            : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp
    ExtendedProtectionTokenChecking : None
    ExtendedProtectionFlags         : {}
    ExtendedProtectionSPNList       : {}
    AdminDisplayVersion             : Version 15.0 (Build 847.32)
    Server                          : SVR-EXCH-01
    InternalUrl                     : https://svr-exch-01.company.loc/ecp
    ExternalUrl                     :
    ExternalAuthenticationMethods   : {Fba}
    AdminDisplayName                :
    ExchangeVersion                 : 0.10 (14.0.100.0)
    DistinguishedName               : CN=ecp (Default Web Site),CN=HTTP,CN=Protocols,CN=SVR-EXCH-01,CN=Servers,CN=Exchange
                                      Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                      Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Identity                        : SVR-EXCH-01\ecp (Default Web Site)
    Guid                            : 052fdd05-42f4-471b-8759-525e93d6b97d
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
    ObjectClass                     : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
    WhenChanged                     : 5/13/2014 6:52:11 PM
    WhenCreated                     : 5/13/2014 6:52:11 PM
    WhenChangedUTC                  : 5/13/2014 11:52:11 PM
    WhenCreatedUTC                  : 5/13/2014 11:52:11 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    IsValid                         : True
    ObjectState                     : Changed

    Ok. Went ahead and tried https://<EX2013_FQDN/ecp/?ExchClientVer=15
    Still took me to the webmail.
    I also tried creating a user on 2013 mailbox database. gave all permissions. Still no luck.

  • Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

    Hi guys (and girls)!
    Hear me up. The idea is like this:
    A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
    doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
    Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
    because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
    One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
    with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    bostjanc

    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    already answered by PS CL above
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    Just install the Edge Transport Server and make sure you install ADLDS services.
    as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
    Where Technology Meets Talent

  • Exchange 2013 Daily Health Check Script

    Hi All,
    I recently migrated from Exchange 2010 to Exchange 2013. Prior to the migration the daily health check was being used daily to send my team and I the HTML report.
    I have downloaded the new v1.07 script and followed the same rules and settings I used for Exchange 2010 when setting up the script.
    The script only runs now via Exchange shell and does not send the HTML report and I am unable to run the script via a batch file that called the ./ps1 file in a windows command prompt and am also unable to as a result, use the task scheduler to schedule
    this task.
    I am desperately in need of getting this morning report as its been so useful, I cant do without it now.
    Any advise would be greatly appreciated.
    Thanks so much
    Alton

    So, could you please check this link, it provide the solution to check the daily health of exchange 2013 :
    http://exchangeserverpro.com/troubleshooting-exchange-server-2013-with-test-cmdlets/

  • Fresh Exchange 2013 install on 2012 R2

    Hi Everyone-
    I'm a bit confused on the steps to install Exchange 2013 SP1 on 2012 R2 in a new environment (no 2013 installed).  I've seen many mixed install guides recommending I install non-sp1, preparing the domain/schema first, install CAS/MBX roles.  Once
    complete run the Sp1 upgrade starting with the domain/scheme upgrade, and then run the EXE.  
    I've also read that the 2013 SP1 download (http://www.microsoft.com/en-us/download/details.aspx?id=41994) is a full version of Exchange and can be ran as a clean install - so essentially just preparing the domain/schema and run the install once.  I
    find this hard to believe as the ISO I've downloaded from VLSC is 3.5gb, yet the SP1 exe is 1.5gb.  
    Can anyone confirm which is the correct path to take?
    Thanks

    Hi,
    Can't think of a good reason to install any other build of Exchange 2013 then SP1. The EX13 SP1 download is a full install and the only one that is supported on 2012 R2. The bits is packed in a different way so the download is smaller.
    Martina Miskovic

  • Exchange 2013 install fails on Organisation preparation Stage

    Hey Guys ,
     I'm facing an issue while installing exchange 2013 on existing 2010 organisation , below are the details . I'm installing it on test bed however i'm failing at organisation preparation stage.
    I do have existing exchange 2010 on ma domain
    I would really appreciate your help.
    Configuring Microsoft Exchange Server
        Organization Preparation                                  FAILED
         The following error was generated when "$error.Clear();
              install-RuleCollection -Name:"ClassificationDefinitions" -DomainContro
    ller $RoleDomainController;
              New-ClassificationRuleCollection -InstallDefaultCollection
            " was run: "Unable to continue processing classification rule collection
     payload for decryption or further validations. Payload may contain invalid data
    Thanks 

    Hi
    When you prepared the Schema and AD did you run the commands and did you run the install from an elevated prompt?
    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Exchange 2013 Public Folder Migration Problem

    Hi All,
    Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
    I have followed the guide for public folder migration here
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
    We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
    However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them
    fine from the ECP - just not from outlook.
    It also appears some users cannot see some folders that they have permissions to.
    Can anyone assist with some ideas to resolve ?
    Thanks.

    Question?
    Are you able to create the Folder in OWA?
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:
       LinkedIn:
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
    it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
    My Bad, that's what I was trying to say.
    Testing the same thing in the LAB, should have some update tomorrow morning.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Renaming domain with Exchange 2013 installed in AD

    Hello, 
    We installed Exchange 2013 into a Windows 2003 Domain (Forest and Domain are Native 2003).  The internal FQDN is for example internal.local  and the external FQDN is external.com. 
    We created a certificate request in exchange that included both the internal and external FQDN’s for a 5 domain UCC certificate from godaddy.com.  When requesting the cert all
    of the .local addresses were removed (was 10 domain names but who wants to pay more).  When we install the certificate on the exchange server and assign services to the certificate, OWA works externally without issue but internally OWA and outlook do
    not work (certificate errors).
    Is the following our only course of action or do we have another option?
    Un-install Exchange (we’ll backup the user mailboxes via pst file as there are less than 10 mailboxes)
    Rename the domain
    Install Exchange 2013 again
    Re-build the mailboxes

    As others mentioned, it would not be a good idea here to rename your domain. It would be better to review the DNS names used internally to make sure that they are in the scope of the used certificate. You might consider using a split-DNS setup for internal
    users if the certificate you use contains only external DNS domains.
    For renaming an AD domain, you can refer to that: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Get Active Directory User Last Logon
    Create an Active Directory test domain similar to the production one
    Management of test accounts in an Active Directory production domain - Part I
    Management of test accounts in an Active Directory production domain - Part II
    Management of test accounts in an Active Directory production domain - Part III
    Reset Active Directory user password

Maybe you are looking for