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.

Similar Messages

  • Exchange 2013 - Location for SMTP Receive Connector verbose logs

    So I'm trying to troubleshoot a relay failure:
    + 1415809433 51000008 Wed Nov 12 11:23:53 2014
    F:[email protected]
    T:[email protected]
    A:c:\v1\temp\200046.pdf
    S:Sales Order Number  200046
    ! Error in SMTP conversation:
      550 5.7.1 Unable to relay
      dbmailsend error 8 (Error in SMTP conversation).
    ! Command-line dump follows (delimited by colons):
      [0]:c:\v1\dbmail\bin\dbmailsend:
      [1]:-vv:
      [2]:-a:
      [3]:c:\v1\temp\200046.pdf:
      [4]:-s:
      [5]:Sales Order Number  200046:
      [6]:-t:
      [7]:[email protected]
      [8]:-r:
      [9]:[email protected]
      [10]:-h:
      [11]:C:\Users\sagert\AppData\Local\Temp\dbf72A3.tmp:
    ! Error in SMTP conversation:
      451 4.7.0 Temporary server error. Please try again later. PRX5
      dbmailsend error 8 (Error in SMTP conversation).
    ! Unable to send report to administrator.
    Note the SMTP Converstion error, I've done the steps in this forum article:
    https://social.technet.microsoft.com/Forums/fr-FR/fc26dac5-d4e2-49da-903d-361ea8b85388/451-470-temporary-server-error-please-try-again-later-prx5?forum=exchangesvrgeneral
    but the issue still exists... so I need to review my Exchange logs for this relay (I've enabled verbose logging on the specific receive connector this should be using)

    Fromhttp://technet.microsoft.com/en-us/library/bb125140(v=exchg.150).aspx
    Set-ReceiveConnector
    The location of the Receive connector protocol logs for all Receive connectors configured in the Transport service on a Mailbox server or an Edge server is specified by using the Set-TransportService cmdlet with the ReceiveProtocolLogPath parameter.
    Run a get-transportservice|fl *logpath* and that should get you what you need.

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

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

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

  • Installing Exchange 2013 CU 6 failed

    Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:
    Error:
    The following error was generated when "$error.Clear();
              if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
              if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
              Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
              $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true
    -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");
              Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
    -ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information:
    General Error.
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
    globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
    globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)
       at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)
       at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)
       at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.
    Any ideas how to solve this?

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

  • Exchange 2013 CU7 - Frequent Outlook 2013 Disconnections and Delays

    We currently have the following environment:
    Windows 2012 VM on Hyper-V with 24GB of RAM and 4 virtual procs (1 socket)
    Cisco UCS, B200 M3 Blades
    Exchange 2013 CU7
    Exchange 2007 is in our environment, but public folders have been removed and only a few stale, unused accounts exist on it. 
    Two dual-role CAS/Mailbox servers
    Mailbox servers are in a DAG
    MAPI/HTTP is our connection protocol
    .NET Framework 4.5.2
    Clients are Outlook 2013 SP1 on Windows 7 and 8.1
    (Currently round robin DNS, but we have a hardware load balancer we've temporarily taken out of the mix to solve this problem)
    What we're seeing is frequent disconnections from Exchange, regardless of the CAS server. That is, both CAS servers will disconnect clients, but not at the same time.  When we look at the Exchange boxes, we notice that the CPU is 99% - 100% each time the
    disconnections occur.  When we hunt down the IISWorker process causing the sudden CPU run, we see it comes back to the following app pools:
    MSExchangeMAPIFrontEndAppPool
    MSExchangeMAPIMailboxAppPool
    (We were running RPC/HTTP, but switched to MAPI/HTTP to resolve the problem.  We had the same issue with equivalent RPC app pools at the time.)
    Eventually, within a minute or two, the CPU load will decrease and the clients connected via that CAS will regain connection.  As you can imagine, the pain is felt more frequently by uncached clients--although everyone, regardless of caching, will see
    the disconnections.
    Basically, the problem sounds exactly as shown in this KB:  http://support.microsoft.com/kb/2995145  Unfortunately, we already had .NET 4.5.2 installed, and have changed the environment variable and registry as shown in the article. 
    We're in contact with Microsoft Support, but thus far they're scratching their heads.
    I'm clearing up all small errors to decrease the noise in the application error logs, but the most persistent one is Event ID 106 (MSExchange Common):
    "Performance counter updating error. Counter name is Time in Resource per second, category name is MSExchange Activity Context Resources. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance 'ad-powershell-defaultdomain'
    already exists with a lifetime of Process.  It cannot be recreated or reused until it has been removed or until the process using it has exited."
    Loading/reloading and recreation of the performance counters does not fix the problem, by Microsoft Support or us.  Of course, this error existed before we started having issues; I'd just like to clean it up just in case it's a contributing factor.
    Has anyone seen anything similar? 

    We're using a Barracuda load balancer (641), but we've eliminated that as a source of the problem.  The CPU spikes and disconnections happen whether or not the load balancer is in use.
    This problem is still ongoing, and we're still working with Microsoft Support.  Right now they're focused on our environment, but having combed through it numerous times, there's nothing that stands out. I suspect this is a bug in CU7 (yet I would
    readily accept our environment being at fault if it means we can identify and resolve the problem), but that's not the road Support is going down.
    We've looked at storage I/O on the VM hosts (disk responses are 10 MS or less), added double the CPUs to each mail server (for a total of 8, each), disabled TCP chimney offload, run numerous Experfwiz log collections, etc...  Now
    the tech is focused on a particular mailbox database being the culprit because it also takes up more CPU when the MAPI app pools are gunning pretty high.  I suspect that it is a symptom and not the problem, but I have no choice but to follow his lead.
    What is your environment like? Are you also CU7?  And did the problem show itself after a cumulative update was applied?

  • 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

  • Installation Error Installing Exchange 2013 CU3 on Server 2012

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

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

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

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

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

  • Installé Exchange 2013 on win 2k8R2

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

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

  • Clean install Exchange 2013 on win2012 server and separate win2012 R2 DC not sending mail from Outlook

    Hello,
    I'm struggeling with a problem. I've a clean installed exchange 2013 on a windows 2012 server. The DC is on a separate server. But I can't send a mail from Outlook and the recieve connector is correctly configured. There are no error's and mail in the queue
    Even sending a mail from the OWA ends in the Drafts folder from that user.
    Can somebody help me with this?
    Thanks Michel

    Hello,
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.
    Cara Chen
    TechNet Community Support

  • Cannot install Exchange 2010 after installing Exchange 2013

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

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

  • Installing Exchange 2013 on Windows Server 2012 R2

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

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

  • Getting Error while installing Exchange 2013 on server 2012

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

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

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

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

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

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

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

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

Maybe you are looking for