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

Similar Messages

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

Support for TLS 1.2 over Exchange 2013 on Server 2012?

Greetings,
We're trying to roll out TLS 1.2 in our test environment and can't seem to get Exchange to work with the protocol.
We've been using this method to enable TLS 1.2 (and disable the other protocols - TLS1.0, SSL2.0, SSL3.0, PCT1.0): http://www.adminhorror.com/2011/10/enable-tls-11-and-tls-12-on-windows_1853.html
We originally tried using Exchange 2010 on 2008 R2, but then I ran across this article saying that it is not supported: http://support.microsoft.com/kb/2709167/en-us
We've since tried to set it up with Exchange 2013 on Server 2012. Still no luck. The only time Exchange wants to work is when TLS1.0 is enabled.
I suspect that TLS1.1 and TLS 1.2 are also not supported on Exchange 2013, or that I'm changing the wrong registry keys, but I wanted to find confirmation. I've searched extensively and can't find any documentation leading me to believe one way or the other
if it's supported.
Any help or insight would be greatly appreciated. Thanks!
--Aric

hi All,
Even i have tried enabling TLS 1.2 on Exchange 2013 from registry. i followed the below article.
http://jackstromberg.com/2013/09/enabling-tls-1-2-on-iis-7-5-for-256-bit-cipher-strength/
When i check OWA in chrome and check the connection information it says "The connection uses TLS 1.2.
However when i run the below command to check for TLS 1.2 i get the following O/P.
Command: java -jar TestSSLServer.jar ns-ex13.gtestexchange.com 443
O/P:
Supported versions: SSLv3 TLSv1.0 TLSv1.1
Deflate compression: no
Supported cipher suites (ORDER IS NOT SIGNIFICANT):
SSLv3
RSA_WITH_RC4_128_MD5
RSA_WITH_RC4_128_SHA
RSA_WITH_3DES_EDE_CBC_SHA
TLSv1.0
RSA_WITH_RC4_128_MD5
RSA_WITH_RC4_128_SHA
RSA_WITH_3DES_EDE_CBC_SHA
RSA_WITH_AES_128_CBC_SHA
RSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
(TLSv1.1: idem)
Server certificate(s):
1979e6bdbd9b8e197d00c45534959eaba82b6f40: CN=ex10.gtestexchange.com, OU=Domain
Control Validated
Minimal encryption strength: strong encryption (96-bit or more)
Achievable encryption strength: strong encryption (96-bit or more)
BEAST status: vulnerable
CRIME status: protected
===================================================
It doesnt says anything about TLS 1.2.
Any suggestions from your side?

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

Cannot install Exchange 2013 on Server 2012 R2

I receive the following error when attempting to install Exchange Server 2013 on the same machine running Windows Server 2012 R2 Essentials:
"An unsupported operating system was detected. Exchange Server 2013 Client Access and Mailbox Server roles support Windows Server 2008 R2 SP1 or later and Windows Server 2012"
SP1 for Exchange Server 2013 was released but I'm not sure how to integrate it or whether or not I even need to. Please let me know if there is a fix or workaround.
Thank you.

This is correct, Essentials is not supported to host Exchange 2013
You need to install Exchange on supported OS:
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Exhcange 2003 on a 2003 server to exchange 2013 on a 2012 server - problems...

Hi
I removed my 2003 exhcange server physically and installed a 2012 server with exchange 2013 on it.
How do I get it to work? Where do I manage the exh 2013 server, through web interface only?
It installed, and worked for a few days (after i first had to remove the 2003 exchange server).
Now i only get "done" in the web interface after loggin in, outlook does'nt find the server when trying to connect to accounts and i can't access it through powershell (exchange management shell) and the Exchange Toolbox does not work neither... The
services are running though, but that's about it.
It won't uninstall cause there is mailboxes etc on the mailbox database..
My servers are on a standalone network, cut of from the internett..
How do I get a clean slate to install echange from scratch?? We only have a few users, so they won't mind..
Any help would be appreciated.. As of now, the server does nothing...

Hi andjohnsen,
What error did you get when you access it through EMS (exchange management shell)?
In addition, I recommend you remove all the exchange 2003 residual information and check if any helps:
Remove (legacy) Exchange server using ADSIEdit
Best regards,
Niko Cheng
TechNet Community Support

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 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 Windows Server 2012 NLB and DAG on the same server

Hi all, I am installing Exchange 2013 infrastructure with two servers.
Both servers have the CAS and Mailbox roles.
For mounting on High Availability, will create a DAG.
Client Access I have no external Network Load Balancer.
I thought about installing the NLB servers in the DAG members, this could not be done before.
I do not know if in Windows Server 2012 and Exchange 2013
Can I install NLB on members of a DAG?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
I’m afraid that WNLB and DAG cannot coexist in the same server. Because WNLB is incompatible with Windows failover clustering. If we're using an Exchange 2010 DAG and we want to use WNLB, we need to have the Client Access server role and the Mailbox server
role running on separate servers.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

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.

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!

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

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.

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

Is it possible to migrate Small Business Server 2008 to Exchange 2013 install on it's own member server?

Trying to figure out of migration to Exchange 2013 is possible on a existing SBS 2008 with Exchange 2007. If it's possible, is it support by Microsoft as well?
Thank you!

Are you planning to get rid of the SBS server or you would like to keep it as a DC, DHCP, DNS, and SharePoint server?
You should be able to upgrade to Exchange 2013, but there are more details to consider. The following six part series outlines this process:
Migrate from SBS 2008 or 2011 to Standard Edition Products
Step by Step Screencasts and Video Tutorial

Fresh Exchange 2013 install on 2012 R2

Similar Messages

Maybe you are looking for