I am trying to install Exchange 2013 on server 2012 r2. AD level is 2012 r2 and I currently have exchange 2010 sp3 with all the rollups running. DCdiag passes with no errors.

The setup fails at the first step which is schema and AD preparation with the following error.

Error:
The following error was generated when "$error.Clear();
	install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema85.ldf")" was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema85.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\hhemmati\AppData\Local\Temp\ldif.err'
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

The file ldiff.err contains the following

Entry DN: CN=ms-DS-GeoCoordinates-Altitude,CN=Schema,CN=Configuration,DC=palatribe,DC=com
Add error on entry starting on line 134: Unwilling To Perform

The server side error is: 0x20bb Schema update failed: duplicate OID.

The extended server error is:

000020BB: SvcErr: DSID-032603C0, problem 5003 (WILL_NOT_PERFORM), data 8379


An error has occurred in the program

Hello all,

I have an exchange 2013 environment with two roles on two servers. I am planning to implement DAG exchange 2013 by using new servers(two for CAS and two for Mailbox role). Please advise on the documentation of which It could help me to move from the DB to the DB using DAG.

Regards,

Joel Chanda

ISSUE: Can't RPC Proxy Outlook Anywhere requests for Exchange 2010 mailbox users via the Exchange 2013 CAS.

SYMPTOMS: Externally with TestExchangeConnectivity.com, I get 'RPC Proxy Can't Be Pinged' with 'An HTTP 401 Unauthorized response was received from the remote Unknown server'.

SETUP:

Exchange 2013 CU2
Get-OutlookAnywhere Details:
ExternalHostname: webapp.mydomain.com
InternalHostname: ex2013.mydomain.local
ExternalClientAuthenticationMethod: Basic
InternalClientAuthenticationMethod: Ntlm
IISAuthenticationMethods: Basic, Ntlm, Negotiate
SSLOffloading: False

Certificate on 2013 server contains the names: ex2013.mydomain.local, webapp.mydomain.com, AutoDiscover.mydomain.local, AutoDiscover.mydomain.com, mydomain.local, mydomain.com

Exchange 2010 SP3 update rollup 1
Get-OutlookAnywhere Details:
ExternalHostname: webapp.mydomain.com
ClientAuthenticationMethod: Basic
IISAuthenticationMethods: Basic, Ntlm
SSLOffloading: False

Certificate on 2010 server contains the names: ex2010.mydomain.local, webapp.mydomain.com, autodiscover.mydomain.local, autodiscover.mydomain.com

Outlook providers:
EXCH  CertPrincipalName: msstd:webapp.mydomain.com
EXPR  CertPrincipalName: msstd:*.mydomain.com    (as I use an external reverse proxy with a public wildcard certificate)

ADDITIONAL DETAILS:
- With the above settings, Outlook 2010 doesn't seem to be able to proxy RPC through Exchange 2013.

Testing manually with RPCPING utility:
- Requests for port 6001 directed to Exchange 2010 for people with mailbox on Exchange 2010: works correctly
- Requests for port 6001 directed to Exchange 2013 for people with mailbox on Exchange 2013: works correctly
- Requests for port 6001 directed to Exchange 2013 for people with mailbox on Exchange 2010: error 401.1 Unauthorized

OWA and Activesync through Exchange 2013 for people with mailbox on Exchange 2010 are working fine.
Only RPC over HTTP seems to have problems.

- Here are some pertinent lines from the 2010 CAS server's IIS logs for a 2013 to 2010 RPC access:
2013-10-10 13:02:16 10.62.6.56 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001 443 - 10.62.6.50 MSRPC 401 1 2148074248 624
2013-10-10 13:02:16 10.62.6.56 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001 443 - 10.62.6.50 MSRPC 401 1 2148074248 624
2013-10-10 13:02:16 10.62.6.56 RPC_IN_DATA /rpc/rpcproxy.dll - 443 - 10.62.6.50 HttpProxy.ClientAccessServer2010Ping 401 2 5 780

- Here are some pertinent lines from the 2013 CAS server's IIS logs for the same 2013 to 2010 RPC access:
2013-10-10 13:02:14 10.62.6.50 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=b6464f37-a9fe-4f84-a32b-ff9af689607c&cafeReqId=b6464f37-a9fe-4f84-a32b-ff9af689607c; 443 - 10.62.7.15 MSRPC - 401 1 2148074254 4726
2013-10-10 13:02:14 10.62.6.50 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=4acc0118-7fac-49db-976d-152a4a6839b2&cafeReqId=4acc0118-7fac-49db-976d-152a4a6839b2; 443 - 10.62.7.15 MSRPC - 401 1 2148074254 0
2013-10-10 13:02:16 10.62.6.50 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=a591fb11-98c3-44e6-90c7-f719c7047fe4&cafeReqId=a591fb11-98c3-44e6-90c7-f719c7047fe4; 443 dom\2010user 10.62.7.15 MSRPC - 401 0 64 1544
2013-10-10 13:02:16 10.62.6.50 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=fbb94579-8d0b-41d7-8103-45c945141bd7&cafeReqId=fbb94579-8d0b-41d7-8103-45c945141bd7; 443 dom\2010user 10.62.7.15 MSRPC - 200 0 64 1700

Any thoughts or comments are highly appreciated. Let me know if additional details are needed.

I migrated from exchange 2010 to 2013 with DR.

Hopefully its working fine.

Now i am planning to decommission my exchange server 2010. It was powered off 15days back.

Could you please tell me the process of decommissioning exchange server 2010.

Also what are the things need to check before decommisioning..

thanks..

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.

I have an Exchange 2010 environment with the Edge role installed on TMG and its working fine.  All servers have had SP3 installed and rebooted.

I am trying to introduce my first Exchange 2013 server into the environment but the readiness check tells me not all the servers have SP3.  On the Edge server it shows SP3 is installed but from all other Exchange servers it shows SP2.

Any ideas?

Thanks

Is there any official documents of the Best Practices of migrating Linux Mail (Exim) to Exchange 2013?

I appreciate any help that I can receive. Thanks in advance.

My best regards.

Good Afternoon all;

We have just installed our first Exchange server (2013 SP1) on a 2012 r2 Standard server.

The installation went without any errors. I installed the mailbox and client access in one server. I followed technet 2013 help for installation (https://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx).

After installation , I can open up the toolbox and the exchange powershell without any problems. 

However, when I try to access https://localhost/owa or ecp , I can put my username and password (domain\username and password) , it gives a 500 internal error.

I have tried the following

• Resetting iis with iisreset (https://social.technet.microsoft.com/Forums/exchange/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients)
• Tried logging in with https://servername/ecp or owa (http://www.alihassanlive.com/e2k3/2014/2/9/cannot-open-eac-in-exchange-2013-500-internal-server-error.html)
• I did this redirect thing, it did not help (http://msexchangeguru.com/2013/10/30/http-redirect-owa-ecp/)
• Tried the netbios name (exchange) , it did not help, also tried netbios.domainname , it did not work either (http://community.spiceworks.com/topic/568178-http-500-internal-server-exchange-2013-ecp)
• I CAN NOT FIND THIS SERVICE ON MY SERVER , if someone knows how to enable or find it, that might be my problem(

Make sure that the Microsoft Exchange Forms Based Authentication service is started. ??? Any ideas where I can find this service , I looked everywhere and did not see it.

• I have not deleted the ECP or OWA directories from IIS yet.
• I did do the authentication stuff (enabling windows authentication, forms etc.)

Any ideas WHY am I having the error message still ?

Note : We have a lab , and only 2 servers, one has the AD and the other one is only exchange server.

Thank you 

Note 2 : I have not done anything with AD after I installed exchange server (the user thats logging into exchange server is the administrator in the AD)

We still have few machines running windows Xp, who cannot access Public folders after the upgrade to the latest CU7. Is there any fix for it other than moving them to Windows 7?

Hi 

I am running MS Ex2010 for a client

Recently we had a dismount because not enough space. 

Once i cleaned up the drive to allow more space the DB came back up no problem.

Now only 3 staff members can not get into their email unable to get mailbox from exchange server, OWA is not working either BUT they can still send and receive on their mobile phone. 

When looking at the exchange server on their profile, it errors out when you click on the calendar properties

Cannot open mailbox /o=RH /ou=Exchange Administrative Group 

(FYDIBOHF23SPDLT)/cn=configuration/cn=server/cn=ORG/cn=Microsoft System attendant. It was running the command 'Get-CalendarProcessing -Identity 'RH.local/Mybusiness/Users/SBSusers/Paul Langsam' -ReadFromDomainController'

Note: There are no more space issues

Why is this only affecting 3 staff members out of 40?

As an Exchange administrator, I am sure you are familiar with the kinds of the 9646 event error report in the application log. They can appear many times per day or only happen once a week. Although, it seems there is no user impact about this error, but the Boss may have concerns about the potential issues about this error.


[Symptoms]
============



 

[Cause]
=========
Connection and usage limits have been placed on the Exchange store to prevent a single application or a single user from using all the available connections to the Exchange store.

[Solution]
===========
Firstly, you need to check the application log and see if the user do have the requirements to raise the store limitation for them.

For Example, some VIPs may need to keep the mailbox open on multiple clients like Outlook, OWA, Mobilities, or they have requirements to share their mailboxes to secretaries. Then you may need to raise the MaxObjsPerMapiSession value for them in order to avoid this event error report.

1.Start Registry Editor (regedit).
2.Navigate to the following registry subkey:

\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

3.Right-click ParametersSystem, point to New, and then click Key. A new key is created in the console tree.
4.Rename the key MaxObjsPerMapiSession, and then press Enter.
5.Right-click MaxObjsPerMapiSession, point to New, and then click DWORD (32-bit) Value. The new value is created in the result pane.
6.Rename the key to <Object_type>, where <Object_type> is the name of the registry object type that you're modifying. For example, to modify the number of messages that can be opened, use objtMessage. Press Enter.
7.Right-click the newly created key, and then click Modify.
8.In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the object.
9.Restart the Microsoft Exchange Information Store service.

However, for some instances, the in question user may tell you that only Outlook is in use and there is no other live MAPI sessions he know. Based on my experience, this issue can occur due to third-party add-ins on Outlook or some third-party search indexing software on the Outlook client. To verify this issue, you can run Windows in Clean Boot mode (better to temporarily remove the searching software) and run Outlook without add-ins by “Outlook /safe”.

In summary, the 9646 Event reports are just the notification about the status of each Exchange Client that connect to the mailbox store. The user impacts may not be huge and you can choose different countermeasures according to the conditions.

More details:

http://support.microsoft.com/kb/842022
https://technet.microsoft.com/en-us/library/ff477612(v=exchg.141).aspx

Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I perform the Hybrid Configuration from that site:

https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-FQAIAAAAQAAAAA8AKFQAQAA~&f=255&MSPPError=-2147217396

When I try to do the moving step, I have those errors;

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:06


Test
Failed

Error:
Deserialization fails due to one SerializationException: System.Runtime.Serialization.SerializationException: Unable to find assembly 'Microsoft.Exchange.MailboxReplicationService.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
   at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
   at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, IMethodCallMessage methodCallMessage)
   at Microsoft.Exchange.Data.SerializationTypeConverter.<>c__DisplayClass3.<DeserializeObject>b__0()

Unable to find assembly 'Microsoft.Exchange.MailboxReplicationService.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Exchange Management Shell command attempted:
'50038459-45a0-4cf4-bc46-42d9d7158752' | New-MoveRequest -Remote -RemoteHostName 'mail.sqliaison.com' -RemoteCredential 'System.Management.Automation.PSCredential' -TargetDeliveryDomain 'inedge.mail.onmicrosoft.com'

Elapsed Time: 00:00:06

The user is in the cloud synchronized with my local DC and I have assigned a license to it.

Any help would be appreciated/

Hello,

I have two Exchange 2013 SP1 servers with DAG configured. I want to upgrade them with CU8. Kindly advise how to do or is there any step by step document available for upgrading the DAG member server.

Thanks in advance.

Hi There,
I am having massive issues with my Exchange Server.
I have 2 Nodes, one has CAS and Mailbox Roles, the other just Mailbox.

I "upgraded" the CAS server to CU7 without any errors / issues.

Once I had restarted, nothing worked any more..  I couldn't access ECP, OWA, Powershell, Autodiscover or get outlook to connect.

I managed to get Powershell working, but changing the physical directory to "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell" from "C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\PowerShell"

But for the life of me I cannot get ECP or OWA working (haven't even tried anything else)!

I am getting a load of Events with ID 1003.

The only error I am getting is:

Server Error in '/ecp' Application.

---

Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.

[MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.]
   Microsoft.Exchange.HttpProxy.ProxyModule.AllowAnonymousRequest(HttpRequest httpRequest) +0
   Microsoft.Exchange.HttpProxy.ProxyModule.OnAuthenticateInternal(HttpApplication httpApplication) +51
   Microsoft.Exchange.HttpProxy.<>c__DisplayClass5.<OnAuthenticateRequest>b__4() +447
   Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +40
   Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate) +408
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165

Which is almost meaningless...  but maybe someone out there has some idea?

Unfortunately this is very urgent for me a these are production servers and currently there is no email for my company.

So Please please please can someone help.

I have tried many many many things from various sites, and so far nothing has worked.

Thanks,

-Tim

We are in the process of migrating from 2010 to 2013.  Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"

alex serdyukov

Hi

A newly installed Exchange 2013 Server (Mailbox and Client Access roles) shows every 5 minutes the event id's 16025 and 205 in the eventlog.

Both events are shown twice at the same time. First 205 then 16025 and again 205 and 16025.

Level: Error
Id 205 - Source: MSExchange Common
Id 16025 - Source: MSExchangeFrontEndTransport

Both have exactly the same description:
No DNS servers could be retrieved from network adapter 0957d69c-9b06-4b72-aa6b-ac825435b485. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results

Get-NetworkConnectionInfo shows the following results:
RunspaceId  : e854435f-ffbe-4ccb-81d9-7e729284e26a
Name        : Microsoft Hyper-V Network Adapter
DnsServers  : {10.10.32.34, 10.10.32.42}
IPAddresses : {10.10.32.45, 10.10.32.44, fe80::9cb9:ad68:c7cc:2052}
AdapterGuid : 0957d69c-9b06-4b72-aa6b-ac825435b485
MacAddress  : 00:1D:D8:B7:1E:2A
Identity    : 0957d69c-9b06-4b72-aa6b-ac825435b485
IsValid     : True
ObjectState : Unchanged

Mailflow is working, I would like to get rid of these error events.

Any suggestions?

Regards
Peter

While installing Cumulative Update 8 on our exchange 2013 server it failed with the following error during the second to last step (client access role: client access front end).  Any advice on what may be causing this and how to fix? 

Error:
The following error was generated when "$error.Clear();
          $fe = get-ActiveSyncVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController -ErrorAction SilentlyContinue;

          if ($fe -eq $null)
          {
            new-ActiveSyncVirtualDirectory -DomainController $RoleDomainController -Role ClientAccess;
          }
          else
          {
            update-ActiveSyncVirtualDirectory $fe -DomainController $RoleDomainController -InstallIsapiFilter $true
          }
        " was run: "System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter' required by parameter 'Identity'. Specified method is not supported. ---> System.NotSupportedException: Specified method is not supported.
   at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

I recive this error when running the preparing AD for exchange 2013 on a 2012 r2 server. 

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;

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

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

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

           New-ManagementRoleAssignment -Role "Mailbox Search" -User $appAccount.Identity -DomainController $RoleDomainController;

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

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

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

         }

       " was run: "Couldn't find a user with the identity "ESL.LOC/Users/Exchange Online-ApplicationAccount".".

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;

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

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

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

           New-ManagementRoleAssignment -Role "Mailbox Search" -User $appAccount.Identity -DomainController $RoleDomainController;

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

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

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

         }

       " was run: "Couldn't find a user with the identity "ESL.LOC/Users/Exchange Online-ApplicationAccount".".