Hi!

We have a single Exchange 2010 Server installed on win 2008 R2 which we need to migrate to a virtual Exchange 2013 on win 2012 Datacenter server. What is the proper way to do that and what is the hardware and memory requirements for 400 Users on a virtual server. Each mailbox will have maximum of 2GB size except 3 or 4 users who will have 10 to 15 GB limitations.

Thanks.

Hi

There is an Exchange 2007 Organisation that is only used internal. There is no connection to the internet and so there is no need for external access using OA, ActiveSync and OWA. Only internal Outlook Clients are accessing Exchange, and sometimes they use internal OWA to access mailboxes.

The question is about the legacy namespace.
If I install Exchange 2013 in the existing 2007 organization, do I have to maintain the legacy namespace?
Can't I just change the AutodiscoverServiceInternalUri to the Exchange 2013 CAS, and all the requests from users with a mailbox on Exchange 2007 are proxied to Exchange 2007?

If yes, does that work for internal OWA as well?

Thanks and regards
Peter

Hi,

In my test Platform I'm trying to install Exchange 2016.

This environment was restored out of my real environment for testing purposes.

I have one 2012R2 DC that I have granted 2012R2 functional level domain and forest (it was a 2003)

Apparently there was a rogue Exchange installation (years ago) that I cleaned in ADSI and ADUC.

I created a new VM joined to the domain, installed RSAT-ADDS, did a prepareschema, prepareAD everything went smoothly.

But during the installation at the Transport Role I get the following failure:

The object cannot be added because the parent is not on the list of possible superiors

Active Directory response: 00002099: NameError: DSID-030511B5, Problem 2005 (NAMING_VIOLATION) CN=TST-EXCH2016, CN=Servers, CN=Administrative Groups etc...)

I tried one more time to clean everything related to Exchange in ADSI (Services -> Microsoft Exchange) and retried, prepareAd, prepareschema no problem at all but I get stuck and have the very same error.

I found an article related to the poss-superior issue but don't really know how step by step hto apply this to my own issue.

https://adamsync.wordpress.com/2012/06/22/structure-rules-naming_violation-and-error-0x2099-the-object-cannot-be-added-because-the-parent-is-not-on-the-list-of-possible-superiors/

I guess this error is occuring because of a former Exchange installation but don't know how to get through it...

Look forward to hearing from you

I'm in the process of trying to install Exchange 2016 in my environment. I had a functioning Exchange 2013 installation and it crashed hard after attempting to apply a CU; it was dead, and not easily repairable, not a critical server. I manually removed the exchange server from ADUC and ADSI. I ran the PrepareSchems, PrepaerAD, and PrepareDomain all successful.

I started the installation and I receive the following error during the installation and I can't seem to figure out where to investigate. I have the setup logs if that's any help, but the error during installation.

-B

Hi, 

Please advise us the complete IT Infrastructure re-branding procedure, that we would require to do.

Our existing IT infrastructure details listed below:

Active Directory (sample domain name: abc.com) with Exchange 2013 (2 Mailbox /CA Server configured with HA).

so we need to change the existing domain name (abc.com) to new name (xyz.com) and we need to migrate the all mailboxes from existing domain to new domain.  

Kindly suggest how we can proceed for this.

Any advice will be very much appreciate.

Team,

One of the customer is planing to host new Exchange 2013 server in DMZ vlan instead of server vlan where my AD is residing at l3 switch. Please comment is this design will work . In case not than what will be challenge and in case of mail flow and client coneectivity.

Hi every one, i need some help. Setup process of Exchange 2016 finishing with Error on step 14:

Ошибка:
При выполнении "$error.Clear(); 
start-SetupService -ServiceName MSExchangeFrontendTransport

" произошла следующая ошибка: "Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Службе 'MSExchangeFrontendTransport' не удалось достичь состояния 'Running' на этом сервере.
   в Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   в Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   в Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   в Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   в Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Service MSExchangeFrontedTransport can not start. It begin starting and stoped, so many times. In System monitor there is id mistake 7031. I could not stop it manually - it starts and then stops automatically. If u have any ideas i will really appreciate it! Thanks!

All,

This is a pretty basic install of Edge Transport. It's running CU9. I stood up an additional CAS server a week ago and this weekend went to re-register the edge subscription which resulted in a failure.

I am running the Edge Subscription as the Local Administrator of that machine, but when I attempt to run New-EdgeSubscription -Filename "edgesub.xml", I'm getting a prompt for a smart card (which I definitely did not use when I built this). It then subsequently fails to connect to the LDAP (I assume ADAM) database on that server, but does create the edgesub file.

So I'm not really sure what's going on here, could anyone help?

Server is a workgroup server. Running from an elevated EMS prompt.

New-EdgeSubscription : Microsoft Exchange couldn't create or update the Edge Subscription account on the Edge
Transport server for the following reason: The LDAP server is unavailable.. Stack is    at
System.DirectoryServices.Protocols.LdapConnection.Connect()
   at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean
needSetCredential)
   at Microsoft.Exchange.MessageSecurity.EdgeSync.AdamUserManagement.CreateOrUpdateADAMPrincipal(String user, String
password, Boolean bootStrapAccount, TimeSpan expiry)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewEdgeSubscription.InitiateSubscriptionOnEdge()
At line:1 char:1+ New-EdgeSubscription -filename "c:\users\administrator\desktop\edgesub7.xml"+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : InvalidOperation: (:) [New-EdgeSubscription], InvalidOperationException+ FullyQualifiedErrorId : [Server=SMTP,RequestId=425da588-2e1e-4a79-93a1-a66e7d0143f7,TimeStamp=10/4/2015 8:18:10
   PM] [FailureCategory=Cmdlet-InvalidOperationException] AF48EF08,Microsoft.Exchange.Management.SystemConfigurationT
  asks.NewEdgeSubscription

Not sure what it is.  The server is running Server 2012 R2 and it is a VM.  It has exchange and associated necessary features, roles, and prerequisites and nothing else installed.  I have uninstalled and reinstalled Exchange 2013 CU7 3 times and each time this error has been present.  It happens twice at boot and seems to cause no problems.

Log Name:      Microsoft-Windows-Kernel-EventTracing/Admin
Source:        Microsoft-Windows-Kernel-EventTracing
Date:          12/23/2014 10:06:53 AM
Event ID:      2
Task Category: Session
Level:         Error
Keywords:      Session
User:          SYSTEM
Computer:      myserver.mydomain.local
Description:
Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
    <EventID>2</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>12</Opcode>
    <Keywords>0x8000000000000010</Keywords>
    <TimeCreated SystemTime="2014-12-23T17:06:53.273839900Z" />
    <EventRecordID>2</EventRecordID>
    <Correlation />
    <Execution ProcessID="3640" ThreadID="10016" />
    <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
    <Computer>Valis.PBJFS.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="SessionName">FastDocTracingSession</Data>
    <Data Name="FileName">
    </Data>
    <Data Name="ErrorCode">3221225525</Data>
    <Data Name="LoggingMode">9</Data>
  </EventData>
</Event>

Hi!

We are migrating from Ex2010 to 2013. We have moved Microsoft Exchange mailbox to Ex2013. There are some other mailboxes like

SystemMailbox{1f05a927...
FederatedEmail.4c1f4d8...

Which are shown when we type Get-Mailbox -Arbitration

Should we also move them to EX2013 and by creating a move request from ecp?

Thanks.

I have an admin who can't get the Exchange 2013 Management Tools to install. He's in site that only has a Read Only Domain Controller. I know installing Exchange Server requires a writable DC, but does this apply to installing the Management Tools?

Below is portions of the setup log showing the errors.

The strange part is tul-rdc01.dsroot.domain.com is the forest's root domain. Our users and computers are in corp.domain.com.

We're running setup.exe from an elevated command prompt. The domain controller we specify in the same site as the user.

[11/05/2015 14:07:38.0665] [0] RuntimeAssembly was started with the following command: '/mode:Install /Roles:MT /IAcceptExchangeServerLicenseTerms /DomainController:esh-cdc01.corp.domain.com /sourcedir:C:\IT\Exchange2013CU9'.

[11/05/2015 14:07:45.0386] [0] Setup is choosing the domain controller to use
[11/05/2015 14:07:45.0451] [0] We have a user-specified or previously-chosen domain controller: esh-cdc01.corp.domain.com
[11/05/2015 14:07:55.0264] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: The user-specified domain controller ESH-CDC01.Corp.domain.com is not available or cannot be contacted.  See the Exchange setup log for more information on this error.
[11/05/2015 14:07:55.0265] [0] Setup will use the domain controller ''.
[11/05/2015 14:07:55.0266] [0] Setup will use the global catalog ''.

[11/05/2015 14:08:09.0202] [1] Finished [Analysis:Prereq] [Duration:00:00:02.1531289]
[11/05/2015 14:08:09.0207] [1] Failed [Rule:CannotAccessAD] [Message:Either Active Directory doesn't exist, or it can't be contacted.]
[11/05/2015 14:08:09.0215] [1] [REQUIRED] Either Active Directory doesn't exist, or it can't be contacted.
[11/05/2015 14:08:09.0215] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
[11/05/2015 14:08:09.0231] [1] Ending processing test-SetupPrerequisites
[11/05/2015 14:08:09.0233] [0] CurrentResult console.ProcessRunInternal:136: 1
[11/05/2015 14:08:09.0234] [0] Exchange Server installation failed during prereq check. Trying to restore the server state back to active.
[11/05/2015 14:08:09.0234] [0] RestoreServer Script Path: C:\windows\Temp\ExchangeSetup\RestoreServerOnPrereqFailure.ps1
[11/05/2015 14:08:09.0397] [0] Beginning processing Write-ExchangeSetupLog
[11/05/2015 14:08:09.0399] [0] Trying to restore server state.
[11/05/2015 14:08:09.0400] [0] Ending processing Write-ExchangeSetupLog
[11/05/2015 14:08:09.0422] [0] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True',
[11/05/2015 14:08:09.0422] [0] User specified parameters:  -ErrorAction:'SilentlyContinue' -Identity:'ESH5NMPY52'
[11/05/2015 14:08:09.0422] [0] Beginning processing get-ExchangeServer
[11/05/2015 14:08:09.0455] [0] Searching objects "ESH5NMPY52" of type "Server" under the root "$null".
[11/05/2015 14:08:10.0081] [0] Previous operation run on domain controller 'tul-rdc01.dsroot.domain.com'.
[11/05/2015 14:08:10.0090] [0] Previous operation run on domain controller 'tul-rdc01.dsroot.domain.com'.
[11/05/2015 14:08:10.0091] [0] Preparing to output objects. The maximum size of the result set is "Unlimited".
[11/05/2015 14:08:10.0093] [0] The operation couldn't be performed because object 'ESH5NMPY52' couldn't be found on 'tul-rdc01.dsroot.domain.com'.
[11/05/2015 14:08:10.0107] [0] The operation couldn't be performed because object 'ESH5NMPY52' couldn't be found on 'tul-rdc01.dsroot.domain.com'.
[11/05/2015 14:08:10.0115] [0] Ending processing get-ExchangeServer
[11/05/2015 14:08:10.0122] [0] Beginning processing Write-ExchangeSetupLog
[11/05/2015 14:08:10.0126] [0] [WARNING] ESH5NMPY52 is not an Exchange Server. Unable to set monitoring and server state to active.
[11/05/2015 14:08:10.0129] [0] Ending processing Write-ExchangeSetupLog
[11/05/2015 14:08:10.0132] [0] CurrentResult launcherbase.maincore:90: 1
[11/05/2015 14:08:10.0132] [0] CurrentResult console.startmain:52: 1
[11/05/2015 14:08:10.0132] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
[11/05/2015 14:08:10.0133] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/05/2015 14:08:10.0133] [0] CurrentResult main.run:235: 1
[11/05/2015 14:08:10.0133] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[11/05/2015 14:08:10.0133] [0] CurrentResult setupbase.maincore:396: 1
[11/05/2015 14:08:10.0135] [0] End of Setup
[11/05/2015 14:08:10.0135] [0] **********************************************

Dear Team,



I have a problem while migrating mailboxes from exchange onpremise to Office365 environment, my hybrid setup completed successfully but still migration has lots of issues.



My exchange version: exchange 2013 CU6 and trying Remote move.

Problem Description:

1) Migration Endpoint could not get created with error below.

We couldn't detect your server settings. Please enter them. The ExchangeRemote endpoint settings could not be determined from the autodiscover response. No MRSProxy was found running at ‎'webmail.domain.com‎'.
Remote MRS proxy server:
The FQDN of the Exchange server that the Mailbox Replication Service (MRS) Proxy is on. 



2) At the the time of configuring migration endpoint from Office365 ECP, it doesnt detect wrong password of onpromise admin and it go ahead and asks for MRS proxy URL.

and one more thing i notice that there is no mrsproxy name insight thw web.config file available in below path, and just to update you my autodiscover is working fine.

C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\ews

We have migrated 2010 to 2013 and when we see the GAL it is showing "No" under "up to date" and the attached. Do we have to do anything to update it or configure it?

Hi!

After migrating from 2010 to 2013 we are getting the below message with our outlook clients. Mailbox move request is still running but the user who is receiving this message has already been moved to 2013.

Any Suggestions?

Thanks.

Greetings,

Is there any way, script or tool to reduce the URL path of a big batch of public folders to make it less than 256? Manually is not an option since there are too many of them. I'd greatly appreciate any help or pointer I can get.

Hello World.

Hi,

I am just finishing migrating from SBS2011 with Exchange 2010 to Server 2012 Standard with Exchange 2013.

The problem I am having is when I run the New-MigrationBatch script on the 2012 server to begin migration of public folders from the SBS2011 Server.

I have followed this https://technet.microsoft.com/en-GB/library/jj150486(v=exchg.150).aspx 

I run this cmdlet New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server sbserver) -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding Byte) -NotificationEmails

I then get this error 

A parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'.
    + CategoryInfo          : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
    + PSComputerName        : server2.domain.local

I have tried changing this to direct public folder database name but I still get errors.

Can anybody shed any light as to what I am doing wrong here?

Thanks in advance

Hi!

After migrating to 2013 from 2010 we are facing issue with outlook asking password again and again. When we run Get-OutlookAnywhere | FL

we got this:

The New server name is Mail-EX13 and old is Mail-Ex10. We restarted the new server but still the same problem. Should we restart the old server as well?

RunspaceId                        : 41fbdafe-0825-4605-9d03-9f4a1a720160

ServerName                        : MAIL-EX10

SSLOffloading                     : False

ExternalHostname                  : mail.server.com. 

InternalHostname                  :

ExternalClientAuthenticationMethod : Basic

InternalClientAuthenticationMethod : Ntlm

II uthenticationMethods          : {Basic, Ntlm}

XropUrl                           :

ExternalClientsRequireSsl         : True

InternalClientsRequireSsl         : False

MetabasePath                      : IIS://SERVER-EX10.server.com. /W3SVC/1/ROOT/Rpc

Path                              : C:\Windows\System32\RpcProxy

ExtendedProtectionTokenChecking   : None

ExtendedProtectionFlags           : {}

ExtendedProtectionSPNList         : {}

AdminDisplayVersion               : Version 14.3 (Build 123.4)

Server                            : SERVER-EX10

AdminDisplayName                  :

ExchangeVersion                   : 0.10 (14.0.100.0)

Name                              : Rpc (Default Web Site)

DistinguishedName                 : CN=Rpc (Default Web

                                    Site),CN=HTTP,CN=Protocols,CN=SERVER-EX10,CN=Servers,CN=Exchange Administrative

                                    Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=SERVER,CN=Microsoft

                                    Exchange,CN=Services,CN=Configuration,DC=server,DC=com,DC=

Identity                          : SERVER-EX10\Rpc (Default Web Site)

Guid                              : e0e74574-8115-4a87-bfe2-f759b709cc2e

ObjectCategory                    : server.com. /Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory

ObjectClass                       : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}

WhenChanged                       : 11/6/2015 6:19:29 AM

WhenCreated                       : 4/4/2014 1:31:29 AM

WhenChangedUTC                    : 11/6/2015 3:19:29 AM

WhenCreatedUTC                    : 4/3/2014 10:31:29 PM

OrganizationId                    :

Id                                : SERVER-EX10\Rpc (Default Web Site)

OriginatingServer                 : server-dc1.server.com.

IsValid                           : True

ObjectState                       : Changed

RunspaceId                        : 41fbdafe-0825-4605-9d03-9f4a1a720160

ServerName                        : SERVER-EX13

SSLOffloading                     : True

ExternalHostname                  : mail.domain.com.

InternalHostname                  : mail.domain.com.

ExternalClientAuthenticationMethod : Negotiate

InternalClientAuthenticationMethod : Ntlm

II uthenticationMethods          : {Basic, Ntlm, Negotiate}

XropUrl                           :

ExternalClientsRequireSsl         : True

InternalClientsRequireSsl         : True

MetabasePath                      : IIS://SERVER-EX13.server.com. /W3SVC/1/ROOT/Rpc

Path                              : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc

ExtendedProtectionTokenChecking   : None

ExtendedProtectionFlags           : {}

ExtendedProtectionSPNList         : {}

AdminDisplayVersion               : Version 15.0 (Build 1130.7)

Server                            : SERVER-EX13

AdminDisplayName                  :

ExchangeVersion                   : 0.20 (15.0.0.0)

Name                              : Rpc (Default Web Site)

DistinguishedName                 : CN=Rpc (Default Web

                                    Site),CN=HTTP,CN=Protocols,CN=SERVER-EX13,CN=Servers,CN=Exchange Administrative

                                    Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=SERVER,CN=Microsoft

                                    Exchange,CN=Services,CN=Configuration,DC=server,DC=com,DC=

Identity                          : SERVER-EX13\Rpc (Default Web Site)

Guid                              : f0bc18e3-6aea-4e41-b345-d6210296383d

ObjectCategory                    : server.com. /Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory

ObjectClass                       : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}

WhenChanged                       : 11/8/2015 10:25:49 AM

WhenCreated                       : 11/5/2015 10:34:50 PM

WhenChangedUTC                    : 11/8/2015 7:25:49 AM

WhenCreatedUTC                    : 11/5/2015 7:34:50 PM

OrganizationId                    :

Id                                : SERVER-EX13\Rpc (Default Web Site)

OriginatingServer                 : server-dc1.server.com.

IsValid                           : True

ObjectState                       : Changed

When attempting to updated Exchange 2013 from CU3 to CU10, I am getting an error during stage 1 (Organisation Preparation).

Full log can be seen below...

Error:

The following error was generated when "$error.Clear();

            #

            # O15# 2844081 - Create PartnerApplication "Exchange Online" in DC and On-Premise

            #

            $exch = [Microsoft.Exchange.Data.Directory.SystemConfiguration.WellknownPartnerApplicationIdentifiers]::Exchange;

            $exchApp = Get-PartnerApplication $exch -ErrorAction SilentlyContinue -DomainController $RoleDomainController | Where { $_.UseAuthServer };

            if ($exchApp -eq $null)

            {

                $exchAppName = "Exchange Online";

                $exchApp = New-PartnerApplication -Name $exchAppName -ApplicationIdentifier $exch -Enabled $RoleIsDatacenter -AcceptSecurityIdentifierInformation $false -DomainController $RoleDomainController;

            }

            # Create application account for Exchange

            $appAccountName = $exchApp.Name + "-ApplicationAccount";

            $appAccount = Get-LinkedUser -Identity $appAccountName -ErrorAction SilentlyContinue -DomainController $RoleDomainController;

            if ($appAccount -eq $null)

            {

                $appAccountUpn = $appAccountName.Replace(" ", "_") + "@"+ $RoleFullyQualifiedDomainName;

                $appAccount = New-LinkedUser -Name $appAccountName -UserPrincipalName $appAccountUpn -DomainController $RoleDomainController;

                Set-PartnerApplication -Identity $exchApp.Identity -LinkedAccount $appAccount.Identity -DomainController $RoleDomainController;

            }

            foreach ($roleName in ("UserApplication", "ArchiveApplication", "LegalHoldApplication","Mailbox Search", "TeamMailboxLifecycleApplication", "MailboxSearchApplication"))

            {

                $roleIdentity = Get-ManagementRole $roleName -DomainController $RoleDomainController;

                $roleAssignment = Get-ManagementRoleAssignment -Role $roleIdentity.Identity -RoleAssignee $appAccount.Identity -DomainController $RoleDomainController;

                if ($roleAssignment -eq $null)

                {

                    New-ManagementRoleAssignment -Role $roleName -User $appAccount.Identity -DomainController $RoleDomainController;

                }

            }

        " was run: "Microsoft.Exchange.Configuration.ObjectModel.PropertyValueExistsException: The value "Exchange_Online-ApplicationAccount@domain.local" of property "UserPrincipalName" is used by another recipient object. Please specify a unique value.

   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(LocalizedException exception, ExchangeErrorCategory category, Object target)

   at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.IsPropertyValueUnique(IRecipientSession recipientSession, ADScope scope, ADObjectId selfId, ADPropertyDefinition[] propertyDefinitionsToSearch, ADPropertyDefinition propertyDefinitionToReportError, Object value, Boolean showDuplicatedObjectInError, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate errorHandler, ExchangeErrorCategory errorLoggerCategory, Boolean includeSoftDeletedObjects)

   at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.IsUserPrincipalNameUnique(IRecipientSession recipientSession, ADRecipient recipient, String userPrincipalName, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate writeError, ExchangeErrorCategory errorLoggerCategory, Boolean excludeSelfCheck)

   at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.IsUserPrincipalNameUnique(IRecipientSession recipientSession, ADRecipient recipient, String userPrincipalName, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate writeError, ExchangeErrorCategory errorLoggerCategory)

   at Microsoft.Exchange.Management.RecipientTasks.NewLinkedUser.PrepareRecipientObject(ADUser user)

   at Microsoft.Exchange.Configuration.Tasks.NewRecipientObjectTaskBase`1.PrepareDataObject()

   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()

   at Microsoft.Exchange.Management.RecipientTasks.NewLinkedUser.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Does anyone have any steps to overcome this?