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.
Similar Messages
-
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 -
2012 r2 Essentials on premises Exchange 2013 integration failing
I have a new server in my development environment that I have installed Essentials and Exchange 2013 on with all of the latest updates. After getting Exchange 2013 installed I am unable to successfully run the Exchange Integration wizard. It fails saying
that it can't contact the exchange server.
I am able to access the Exchange Powershell, Exchange Admin center and OWA.
The Essentials Anywere Access has been setup and Is working as well.
any suggestions on where to go from here?Hi,
-->It fails saying that it can't contact the exchange server.
Can you ping the exchange server via server name and IP address? In addition, did you apply
Cumulative Update 5 for Exchange Server 2013 and reboot the Exchange server, then monitor the result? Just a confirmation, thanks for your understanding.
Please also refer to following article and check if can help you.
Integrate an On-Premises Exchange Server with Windows Server Essentials
In addition, if this issue still exists, please follow the path:
%programdata%\Microsoft\Windows Server\Logs and check log files if find more clues.
Windows Server Essentials 2012/2012 R2 Log Files
If any update, please feel free to let me know,
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Exchange 2013 Cu6 fails to install
When I attempt to install CU6 on Exchange 2013 I get this error message and cannot continue, occurs after reboot as well and trying to re-run setup. Any ideas how to fix?
Thanks,
Setup Error 2nd time 5 of 9 after restart
Error:
The following error was generated when "$error.Clear();
$name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
if( $dismbx -ne $null)
$srvname = $dismbx.ServerName;
if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
$mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
if( $mountedMdb -eq $null )
Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
mount-database $dismbx.Database;
$mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
if( $mountedMdb -ne $null )
$dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
$dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
if( $dmRoleGroup -ne $null )
trap [Exception]
Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
continue;
Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
" was run: "Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "Domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest
principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed.
at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
at System.Security.Principal.NTAccount.Translate(Type targetType)
at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".Hi,
Thanks. This did work for me. CU6 applied, Exchange back up. Go live in 2 weeks.
Delete the Discovery Search mailbox user from Active Directory. Start your Active Directory Users and Computers
mmc and look for your Discovery Search Mailbox user. Default this user will be placed in the Users organizational unit. It will be named something like: DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}. After deletion you can restart the installation
of your Exchange Service Pack. It will not show the error anymore.
To recreate the user use: setup
/PrepareAD /IAcceptExchangeServerLicenseTerms -
Installing Exchange 2013 CU7 fails - multiple Receive connectors
Coming from CU4 (aka SP1) and running this upgrade (to comply with hybrid requirements!), setup errors out on the transport role, that I have 2 receive connectors bound to the same IP address, and stops there.
The problem is that Exchange won't come back up for me to fix or delete the additional Recv connector.
Now what?
[12/17/2014 00:28:07.0489] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0489] [2] User specified parameters: -Identity:'MAIL\Default Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0490] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0494] [2] Searching objects "MAIL\Default Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0503] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0504] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0544] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0572] [2] Processing object "MAIL\Default Frontend MAIL".
[12/17/2014 00:28:07.0588] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0607] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0611] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0614] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0615] [2] User specified parameters: -Identity:'MAIL\Outbound Proxy Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0615] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0619] [2] Searching objects "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0630] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0631] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0669] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0696] [2] Processing object "MAIL\Outbound Proxy Frontend MAIL".
[12/17/2014 00:28:07.0711] [2] No properties changed for the object "MAIL\Outbound Proxy Frontend MAIL".
[12/17/2014 00:28:07.0711] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Outbound Proxy Frontend MAIL' have been modified.
[12/17/2014 00:28:07.0712] [2] Saving object "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
[12/17/2014 00:28:07.0712] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0714] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0717] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0718] [2] User specified parameters: -Identity:'MAIL\Client Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0718] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0723] [2] Searching objects "MAIL\Client Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0732] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0733] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0778] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0806] [2] Processing object "MAIL\Client Frontend MAIL".
[12/17/2014 00:28:07.0820] [2] No properties changed for the object "MAIL\Client Frontend MAIL".
[12/17/2014 00:28:07.0821] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Client Frontend MAIL' have been modified.
[12/17/2014 00:28:07.0821] [2] Saving object "MAIL\Client Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
[12/17/2014 00:28:07.0822] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0824] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0827] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0828] [2] User specified parameters: -Identity:'MAIL\Scanner email' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0828] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0832] [2] Searching objects "MAIL\Scanner email" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0840] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0841] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0884] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0912] [2] Processing object "MAIL\Scanner email".
[12/17/2014 00:28:07.0925] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0927] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0931] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0933] [1] The following 2 error(s) occurred during task execution:
[12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[12/17/2014 00:28:07.0965] [1] [ERROR] The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[12/17/2014 00:28:07.0965] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[12/17/2014 00:28:07.0966] [1] [ERROR] The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[12/17/2014 00:28:07.0966] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0967] [1] [ERROR-REFERENCE] Id=TransportCommonComponent___79d82f60693f413588aa8c3a58e90b41 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/17/2014 00:28:07.0980] [1] Setup is stopping now because of one or more critical errors.
[12/17/2014 00:28:07.0980] [1] Finished executing component tasks.
[12/17/2014 00:28:08.0061] [1] Ending processing Install-BridgeheadRole
[12/17/2014 00:28:40.0012] [0] CurrentResult setupbase.maincore:396: 0
[12/17/2014 00:28:40.0013] [0] End of Setup
[12/17/2014 00:28:40.0013] [0] **********************************************Someone already found a fix for this here:
https://exchangeshare.wordpress.com/2014/07/14/exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges/#comment-1219
Just in case this link won't work some day, here was the fix:
Open ADSI edit on your Domain Controller
Go to Configuration, and drill down Services, Microsoft Exchange, First Organization, Administrative Groups, Exchange Administrative Groups, Servers, <Your Server Name>, Protocols, SMTP Receive Connectors
Find the offending connector and delete it.
Setup will resume as normal, and recreate the connector after setup completes. -
I can't get Exchange 2013 to install in our Server 2008 R2 infrastructure. Setup fails with the following error when preparing AD. This is running on Server 2008 R2 SP1 VM's.
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
Organization Preparation
FAILED
The following error was generated when "$error.Clear();
install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in theI have set the PowerShell Execution Policy to unrestricted. After running setup /PS I get the following output
PS C:\Windows\system32> cd c:\temp\ex2013cu3
PS C:\temp\ex2013cu3> ./setup /ps /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
Extending Active Directory schema
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation completed successfully.
PS C:\temp\ex2013cu3>
The installation was started at 10:13am and hung for sometime at 94% of the prereq stage. Installation finally completed at 10:47am. The errors seem to indicate that setup will continue. However upon running setup /prepareAD the installation hangs for sometime
at 21% of Organization Preparation before finally failing with the following output....
PS C:\temp\ex2013cu3> ./setup /prepareAD /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
Organization Preparation
FAILED
The following error was generated when "$error.Clear();
install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS C:\temp\ex2013cu3> -
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,
JeffThanks 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 -
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 schemaprep failing
Trying to setup Exchange 2013 on a test domain with no prior Exchange.
All prereq's done, tried doing the schemaprep from one of the CAS servers, and it failed, also tried from one of the DC's. DC's are 2008R2. Domain and forest are at 2003 level. Running as the domain's "administrator" account, which is a domain admin, schema
admin and enterprise admin. Single forest, single domain.
Logs below:
Z:\>setup /prepareschema /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/04/2012 23:30:28.0234] [0] **********************************************
[12/04/2012 23:30:28.0234] [0] Starting Microsoft Exchange Server 2013 Setup
[12/04/2012 23:30:28.0234] [0] **********************************************
[12/04/2012 23:30:28.0234] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[12/04/2012 23:30:28.0234] [0] Operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1.
[12/04/2012 23:30:28.0234] [0] Setup version: 15.0.516.32.
[12/04/2012 23:30:28.0250] [0] Logged on user: HILLZ\Administrator.
[12/04/2012 23:30:28.0250] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/04/2012 23:30:28.0281] [0] Command Line Parameter Name='prepareschema', Value=''.
[12/04/2012 23:30:28.0281] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[12/04/2012 23:30:28.0296] [0] Command Line Parameter Name='sourcedir', Value='Z:\'.
[12/04/2012 23:30:28.0375] [0] RuntimeAssembly was started with the following command: '/prepareschema /iacceptexchangeserverlicenseterms /sourcedir:Z:"'.
[12/04/2012 23:30:28.0375] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[12/04/2012 23:30:28.0375] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[12/04/2012 23:30:28.0375] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/04/2012 23:30:28.0375] [0] Copying Files...
[12/04/2012 23:30:28.0390] [0] Starting copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/04/2012 23:30:45.0968] [0] Finished copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/04/2012 23:30:45.0968] [0] File copy complete. Setup will now collect additional information needed for installation.
[12/04/2012 23:30:45.0984] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[12/04/2012 23:30:46.0156] [0] [ERROR] The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
[12/04/2012 23:30:46.0156] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/04/2012 23:30:46.0171] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/04/2012 23:30:46.0171] [0] End of Setup
[12/04/2012 23:30:46.0171] [0] **********************************************
[12/05/2012 13:28:21.0046] [0] **********************************************
[12/05/2012 13:28:21.0062] [0] Starting Microsoft Exchange Server 2013 Setup
[12/05/2012 13:28:21.0062] [0] **********************************************
[12/05/2012 13:28:21.0062] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[12/05/2012 13:28:21.0062] [0] Operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1.
[12/05/2012 13:28:21.0062] [0] Setup version: 15.0.516.32.
[12/05/2012 13:28:21.0062] [0] Logged on user: HILLZ\Administrator.
[12/05/2012 13:28:21.0062] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/05/2012 13:28:21.0093] [0] Command Line Parameter Name='prepareschema', Value=''.
[12/05/2012 13:28:21.0093] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[12/05/2012 13:28:21.0093] [0] Command Line Parameter Name='sourcedir', Value='Z:\'.
[12/05/2012 13:28:21.0140] [0] RuntimeAssembly was started with the following command: '/prepareschema /iacceptexchangeserverlicenseterms /sourcedir:Z:"'.
[12/05/2012 13:28:21.0140] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[12/05/2012 13:28:21.0140] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[12/05/2012 13:28:21.0156] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/05/2012 13:28:21.0156] [0] Copying Files...
[12/05/2012 13:28:21.0156] [0] Starting copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/05/2012 13:29:06.0468] [0] Finished copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/05/2012 13:29:06.0468] [0] File copy complete. Setup will now collect additional information needed for installation.
[12/05/2012 13:29:06.0484] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[12/05/2012 13:29:06.0500] [0] [ERROR] The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
[12/05/2012 13:29:06.0515] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/05/2012 13:29:06.0515] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/05/2012 13:29:06.0515] [0] End of Setup
[12/05/2012 13:29:06.0515] [0] **********************************************Hi Troy12n,
Please make sure you install Exchange 2013 Prerequisites first:
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354.aspx
And if you didn't download Exchange 2013 from Microsoft download, please download it from there as well.
I prefer to create a dedicated account for Exchange management, e.g.
exadmin, and assign permission to it, then install & manage Exchange 2013.
If you have any feedback on our support, please click
here
Frank Wang
TechNet Community Support -
Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage
Hello,
I am trying to uninstall Exchange 2013 SP1 but it is failing while uninstalling Language step # 8 the error is;
Error:
The following error was generated when "$error.Clear();
$regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';
$PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";
$InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;
if(test-path ($regPath))
Write-ExchangeSetupLog -info ("Removing " + $RoleLanguagePackType + " Language Packs.");
Get-ChildItem ($regPath) | foreach{
if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
$langPackPackageCode = $matches['ProductCode'];
if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne
0) {
Write-ExchangeSetupLog -info ("Removing package
$langPackPackageCode");
$language = $langPackPackageCode.Substring(20,4);
$logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall")
+ '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
uninstall-MsiPackage -ProductCode ($langPackPackageCode)
-LogFile ($logFilePath);
Get-Childitem -Path $InstallPath -include "*.Localized.js","*.Localized.min.js" -recurse | foreach
($_) {remove-item $_.fullname};
Write-ExchangeSetupLog -info "Remove Language Packs completed.";
" was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
I am also attaching the snapshots. Please guide me how to uninstall Exchange 2013. I had some issue with Exchange Server and it need to uninstall and re-install the Exchange Server." was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
Hi,
Based on this error, possible cause may the path of language package is too long. Please check the following things:
Where is your language package installed? Please check it.
Under 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}", please check the following entries. By default, it should be like this.
InstallSource (Z:\Applications\Server\Exchange\2013\64-Bit\RTM\en\)
ModifyPath (MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C})
UninstallString MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C}
Under 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup, check this entry MsiInstallPath. By default, the value should be “C:\Program Files\Microsoft\Exchange Server\V15\”
Best Regartds.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support -
Exchange 2013 installation fails
We're in the process of migrating from Exchange 2007 to Exchange 2013. I've followed the prerequisites, and have the necessary account permissions, but when I start the installation it fails at step 1 of 5 (mailbox role:mailbox service).
This warning shows up in the application log:
Event ID 2397
Process ExSetupUI.exe (PID=9844). Object [CN=Mailbox Database 1783948598,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<domain>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=local]. Property [Server] is set to value [<Exchange 2013 server name>
DEL:492ae292-f89f-4a29-b009-22a60973a4bf], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
This error shows up in the Exchange install console, as well as the application log:
Event ID 1002
Exchange Server component Mailbox role: Mailbox service failed.
Error: Error:
The following error was generated when "$error.Clear();
if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
else
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
" was run: "The Exchange server for the database object "Mailbox Database 1783948598" wasn't found in Active Directory Domain Services. The object may be corrupted.".
I should also mention that this installation was attempted once before by an ex-coworker, and it failed. I've spent hours searching Google but haven't come up with a solution. Does anyone have any ideas?Check it at Exchange 2007 side, Get-MailboxDatabase -Server E2007ServerName or via EMC to confirm but if msExchOwningServer/msExchMasterServer
points to the server which is stale 2013 server then it shouldn't be connected to E2007 by any way and you are good to remove those...
But I wouldn't touch another DB which has just server name and not servername\0ADEL:guid
as it is not giving error (at least yet...) in the setup
Blog |
Get Your Exchange Powershell Tip of the Day from here -
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?
ThanksHi,
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 -
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 : ChangedOk. 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. -
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?).
bostjancShould 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
Maybe you are looking for
-
(266436851) Q: WWSD-28 How to remove applications?
Q:<WWSD-28> Can applications be undeployed AND removed (ie. deleted) with the console in WLS 6.1 or do you still need to edit the domains config.xml file manually? A<WWSD-28> Applications can be undeployed from the console but this does not necessari
-
After I updated my Ipad2 to IOS5 my calendar lost all appointments. After re-entering a couple of appointments it froze. After getting it going again, the calendar will not populate an end date for the current day and consequently I can't save the
-
All of a sudden (I think after the last firefox update) links in other web pages won't open firefox to access the page when firefox is my default browser but works when I change my default browser to Internet Explorer and I can't figure out why. Help
-
Hi Experts, Good day! I came across SYSFAIL queue errors in SAP CRM Outbound (SMQ1) with the specific message: "Overflow when converting from 32768", and searched for SAP OSS notes, but found none applicable to the system and application. Thanks in a
-
Maximum HDD capacity for Core Duo MacBook?
With both OS X and Windows installed, I'm running out of space with the 80GB HDD my Core Duo (not Core 2) MB came with and I'd like to replace the original drive with the 200GB drive that the new MacBook Core 2 Duo can be ordered configured with. But