Exchange 2013 mailbox added to the CAS array

We are upgrading to Exchange 2013 from Exchange 2010. Following the development guide, we have
installed the first mailbox server in the Exchange 2010 environment which has 3 Exchange 2010 CAS server
in the array. When installing the mailbox role, we did not choose the client access role but after
the installation we can see that the Exchange 2013 Mailbox server is added to the CAS array and yet
we did not choose the client access role. How does this happen, and to proceed ?

I see the same thing in my lab:
Get-ClientAccessArray | FL
RunspaceId        : 16b992b3-270f-4ae1-a3c3-fa9e2ea73d69
ExchangeLegacyDN : /o=Wingtiptoys/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Ou
                    tlook.wingtiptoys.ca
Fqdn              : Outlook.wingtiptoys.ca
Site              : wingtiptoys.ca/Configuration/Sites/Default-First-Site-Name
SiteName          : Default-First-Site-Name
Members           : {EXCH-2010, EXCH-2013}
AdminDisplayName :
ExchangeVersion   : 0.1 (8.0.535.0)
Name              : Outlook.wingtiptoys.ca
DistinguishedName : CN=Outlook.wingtiptoys.ca,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administr
                    ative Groups,CN=Wingtiptoys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wingtiptoys,DC=ca
Identity          : Outlook.wingtiptoys.ca
Guid              : 27968af1-1624-4ff3-85c8-e38e68183afe
ObjectCategory    : wingtiptoys.ca/Configuration/Schema/ms-Exch-Client-Access-Array-2
ObjectClass       : {top, server, msExchExchangeServer, msExchClientAccessArray}
WhenChanged       : 4/12/2014 12:51:18 PM
WhenCreated       : 4/12/2014 12:51:18 PM
WhenChangedUTC    : 4/12/2014 7:51:18 PM
WhenCreatedUTC    : 4/12/2014 7:51:18 PM
OrganizationId    :
OriginatingServer : DC-1.wingtiptoys.ca
IsValid           : True
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

Exchange 2013 - Mailbox Setup Failed "The following error was generated when "$error.Clear()" 7 of 14

I am getting the following error when I'm setting up the mailbox server as I'm currently doing a test virtual machine throughHyper-V, it seems to happen during the transport service phase of the installation which is 7/12
Do i know need a D:\ drive for the mailbox server to work? as in my test i only have a c:\ drive but no d:\ drive
Error:
The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;
                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                    $useAttachMode = $true;
                else
                    if ($RoleIsDatacenter -eq $true)
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                $useAttachMode = $true;
                if ($useAttachMode -eq $true)
                    &$command -action a -dataFolder $dataFolderPath -silent;
                else
                    try
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    catch
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                        catch
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
+ " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
        " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".
Warning:
An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;
                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                    $useAttachMode = $true;
                else
                    if ($RoleIsDatacenter -eq $true)
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                $useAttachMode = $true;
                if ($useAttachMode -eq $true)
                    &$command -action a -dataFolder $dataFolderPath -silent;
                else
                    try
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    catch
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                        catch
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
+ " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
        " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".


Hi
Most likely for these kind of issues its better you can delete the hyper-v machine and create a new os , ensure all the prerequisite are met and install the Exchange since this is a new installation.
But as a try you can try giving full access to the admin account to the data folder  'C:\Program
Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. which is giving the error and rerun the setup
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Using new computer, existing mailbox user Outlook 2010 Auto-configuration points to the Mailbox Server rather than CAS Array ?

People,
I'm having a problem with the current AD user account & mailbox user where they cannot get the Outlook 2010 automatically configured to point into the CAS array ?
This is happening when the existing user get new computer replaced or login to the Terminal Server where their account never set before, it always points to the Mailbox Server instead of the Client Access Server array virtual name.
The work around that I provided is typing the Client Access Array address and then specify Outlook.domain.com to match the Windows NLB name (and Get-ClientAccessArray result).
Single AD Domain forest
AD Site DataCenter contains:
Domain Controllers: PRODDC01-VM, PRODDC02-VM, PRODDC03-VM
Exchange Server 2010 SP3 - CAS&HT: PRODMAIL01-VM and PRODMAIL01-VM (Configured with WNLB as outlook.domain.com)
Exchange Server 2010 SP3 - Mailbox: PRODMAILBOX01-VM and PRODMAILBOX01-VM (no DAG is set)
Terminal Server (RDSH 2008 R2): PRODTS01-VM ... PRODTS60-VM (when user logged in to new TS, it got the same error).
AD Site HQ contains - This site has no issue:
Domain Controllers: HQDC01 and HQDC02
Workstations using Outlook 2010 and 2013
AD Site SiteOffice1 contains - This site has problem:
Domain Controllers: none but the majority of the workstations LOGONSERVER is pointing to PRODDC03-VM
Workstations using Outlook 2010 and 2013
All of the Exchange environment here is using Exchange Server 2010 SP3 for all server roles.
Any help would be greatly appreciated.
Thanks
/* Server Support Specialist */

Hi,
Yes, the RPCClientAccessServer should point to the CAS array. What's more, I would like to clarify the following things:
1. Run the Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri cmdlet to make sure that it displays the correct Uri.
2. Run the Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL to ensure that URL for EWS points to the CAS array.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Amy Wang
TechNet Community Support
Here's the result:
[PS] C:\>Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri
AutoDiscoverServiceInternalUri : https://PRODMAIL02-VM.domain.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceInternalUri : https://PRODMAIL01-VM.domain.com/Autodiscover/Autodiscover.xml
[PS] C:\>Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL
Identity : PRODMAIL01-VM\EWS (Default Web Site)
CertificateAuthentication :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : False
DigestAuthentication : False
WindowsAuthentication : True
InternalNLBBypassUrl : https://PRODMAIL01-VM.domain.com/ews/exchange.asmx
InternalUrl : https://PRODMAIL01-VM.domain.com/EWS/Exchange.asmx
ExternalUrl : https://email.domain.com/ews/exchange.asmx
Identity : PRODMAIL02-VM\EWS (Default Web Site)
CertificateAuthentication :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : False
DigestAuthentication : False
WindowsAuthentication : True
InternalNLBBypassUrl : https://PRODMAIL02-VM.domain.com/ews/exchange.asmx
InternalUrl : https://PRODMAIL02-VM.domain.com/EWS/Exchange.asmx
ExternalUrl : https://email.domain.com/ews/exchange.asmx
The IP address of email.domain.com and outlook.domain.com are the same IP address, this IP address is servec by WNLB.
/* Server Support Specialist */

Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

Hi Team,
I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
open and throws an error of some "cannot open set of folders".
Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
Kindly share some KB or tip. Any help is appreciated. Thank You.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Performance counters for exchange 2013 mailbox & cas servers?

what are the Performance counters for exchange 2013 mailbox & cas servers?
similar to rpc request for troubleshooting exchange slowness, I haven't found any technet article for exchange 2013.

Hi,
Please see this:
Ask the Perf Guy: Sizing Exchange 2013 Deployments
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
Hope it is what you need.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 mailbox auditing command with showdetails parameter in ps1 script is not working via task scheduler

Hi All ,
In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the ps1 script in exchange management shell ,i can able to get the relevant output.
CMDLETS in powershell script :
Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
Note : we are having only the above commands in ps1 script , apart from that we don't have anything in it .
Sametime i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it .
Steps handled on my side to run the powershell script in task scheduler:
1.when i remove the parameter showdetails in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
The Difference what i have seen between exchange 2010 and exchange 2013
when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
I am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments : -PSConsoleFile "E:\Program Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
Error message : "the requesting account does not have permission to access the audit log"
Please help me out to resolve this case .
Thanks
S.Nithyanandham

Hi All ,
In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the ps1 script in
exchange management shell,i can able to get the relevant output.
CMDLETS in powershell script :
Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
Note : we are having only the above commands in ps1
script , apart from that we don't have anything in it .
In case, if i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it .
Steps
handled on my side to run the powershell script in task scheduler:
1.when i remove the parameter showdetails
in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
The
Difference what i have seen between exchange 2010 and exchange 2013
when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
I
am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments : -PSConsoleFile "E:\Program
Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
Error message : "the requesting account does
not have permission to access the audit log"
Please help me out to resolve this case .
Thanks
S.Nithyanandham

Exchange 2013 Mailbox Role Installation Error

Hi All,
I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
. HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
   at System.DirectoryServices.DirectoryEntry
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.RefreshCache()
   at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
   at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Any views on this is appreciated.
Regards
Boniface
Senior Systems Administrator

Hi,
After uninstalling the IIS, please run the following command to install prerequisites.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
In addition, please disable any third-part software for troublwshooting.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

Hi All,
we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013 and i have to add the 2013
servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
Thanks, Venkatesh. "Hardwork Never Fails"

For a step by step follow the deployment assistant
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2007 - Exchange 2013 Mailbox Migration Issues

Exchange 2013 - Mail Flow is working. OWA Access is great. We have issues connecting Outlook 2010 Clients. If I create a new user and mailbox Outlook 2010 works fine. However, if we migrate a user's mailbox to the new Exchange
2013 server. Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server" There is something different about a newly created account and a migrated account. Any help would be great. I did check
inheritance in AD and it was on for these accounts. This occurs with any account migrated to the new server.

1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
generates and provides the correct information.
2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
Step by Step Screencasts and Video Tutorials

Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
the following command:
Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
Many thanks.

Hi Dennis,
Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
Please check your connection authentication. We can run the following command to set your Outlook Anywhere for Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
In Outlook side, please ensure the following settings in Account Settings:
In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

Hello guys,
I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
What should I check and configure to make it work?

Hi,
I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact EMC supplier to improve it.
By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

Here is our current scenario,
Exchange 2007
2 - Hub Transport Servers
2 - CAS servers (cluster NLB)
2 - Mailbox servers (clustered)
Exchange 2010
2 - Huib Transport Servers
3 - CAS servers (array NLB)
2 - Mailbox servers (1 DAG)
We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

Hi,
As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
For more information, you can refer to the following article:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks,
Angela Shi
TechNet Community Support

Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

Hi,
I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
Configuration server Exchange 2007 SP3 :
Domain : test.com
OS : Windows 2008 server SP2 (not R2)
Firewall : OFF
Exchange roles are on separate three servers : CAS - MAILBOX - HUB.
Configuration Server Exchange 2013 :
Domain : new.com
OS: Windows 2012 R2
Firewall : OFF
This environment is on a closed network unable to reach internet.
I have try to restart the Replication service, but it didn't worked.
I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
Anyone ever had this issue?
Thanks you and have a nice day.

Hi ,
Based on my knowledge below things need to checked.
1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
DataMoveReplicationConstraint : None
Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
3.Restart the Microsoft exchange mailbox replication service and check the results.
4. Have you tried moving the same mailboxes to the different databases.
5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Exchange 2013 or SP1 Installaing Single CAS Role not installaing EWS virtual directory in mixed environment

Hi Experts,
I am facing issue while installing exchange 2013 sp1 in mixed(2007, 2010 and 2013) environment, the issue is: CAS role not installing/configuring "Echangeweb" (ews) virtual directory if i install only CAS role. If i install CAS role and mailbox
role then there is no issue, everything is fine.
In single CAS role installation, "EWS" folder is creating inside "Exchangeweb" folder but it shows empty folder.
If any one have any idea please let me know, why this is happening? was i am doing anything wrong while installing?
Regards,
Ravi Nalla
Hewlett-Packard
ravinalla

Hi Ravi,
Agree with Martina. I install Exchange 2013 CAS server and Mailbox server separately. "exchweb" folder exists on Mailbox server only. Here is the exchweb folder information on Mailbox server for your reference.
Here is the ews folder information on CAS server for your reference.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013 mailbox takes a long time to connect with Outlook 2010

We just installed a 2013 CAS/Mailbox server in our Exchange 2007 environment and are running in coexistence while we migrate users over. So far I have only moved one 2007 mailbox over, a new account used for testing. Everything is working fine, OWA,
ECP, ActiveSync, etc... When connecting Outlook to a 2007 mailbox autodiscover takes a couple seconds and Outlook opens fine. The problem is when connecting Outlook to a mailbox on the 2013 server. Autodiscover takes about a minute before it finally finds
the settings and the mailbox takes about 30 seconds to open everytime. It generally times out, I click retry and the mailbox opens. Once in everything is good but the initial loading always takes a long time, double the time when opening Outlook with a shared
mailbox attached. All autodiscover is autodiscover.domain.com, Exchange 2007 is all legacymail.domain.com aside from the components that need to point to 2013. We do not have any certificate issues, well that's not true, at some time in the last couple years
someone applied a 3rd party cert to our domain.com root but not sure if that would cause this issue. Also, these are internal clients we are trying to get going with the 2013 mailbox, not external. I just applied a registry change that helped someone else
out there by disabling IPv6 for all components but that did not work for us MS KB929852. Any suggestions? Right now I am thinking of changing the internalURI for autodiscover to the FQDN of the server but wanted to see if anyone had any ideas.
Jeremy

Hi Angela, thanks for the response. I cannot post links or pictures as my account has not been verified?
The autoconfiguration tests passed, I will paste the xml below. Ping times were all under 1ms. When I entered the IP for the 2013 serve I received errors that the connection to Exchange is unavailable followed by another one that the name cannot be resolved.
I did this test by removing the Outlook profile and creating one manually without Autodiscover. I am able to ping the server by all names from the command prompt.
Our autodiscover.domain.com points to our 2013 server and the name is resolvable both internally and externally. Our certificates cover the internal server name fqdn as well as external names. I am doing all testing in the internal network.
Pinging 2013server.fqdn.com [172.16.xx.xx] with 32 bytes of data:
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
Ping statistics for 172.16.xx.xx:
    Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns= removing link for post, points to the schema . microsoft . com ... 2006
<Response xmlns= removing link for post, points to the schema . microsoft . com ... 2006a
    <User>
      <DisplayName>2013user</DisplayName>
      <LegacyDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=91d6299a8d1440e6b80fcc854dc3f860-2013user</LegacyDN>
      <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
      <DeploymentId>565c12be-83dc-44c7-a843-37b9bf26b9db</DeploymentId>
    </User>
    <Account>
      <AccountType>email</AccountType>
      <Action>settings</Action>
      <MicrosoftOnline>False</MicrosoftOnline>
      <Protocol>
        <Type>EXCH</Type>
        <Server>[email protected]</Server>
        <ServerDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
        <ServerVersion>73C082C8</ServerVersion>
        <MdbDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>webmail.company.com</PublicFolderServer>
        <AD>SMS-AD1-SRV11.domain.ca</AD>
        <ASUrl>https://webmail.company.com/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://webmail.company.com/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://webmail.company.com/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.ca</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.ca</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.ca</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.ca</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.ca</EcpUrl-sms>
        <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=domain.ca</EcpUrl-publish>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.ca</EcpUrl-photo>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.ca</EcpUrl-extinstall>
        <OOFUrl>https://webmail.company.com/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://webmail.company.com/ews/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
        <ServerExclusiveConnect>off</ServerExclusiveConnect>
      </Protocol>
      <Protocol>
        <Type>EXPR</Type>
        <Server>webmail.company.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Basic</AuthPackage>
        <ASUrl>https://webmail.company.com/EWS/Exchange.asmx</ASUrl>
        <EwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EwsUrl>
        <EmwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EmwsUrl>
        <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.ca</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.ca</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.ca</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.ca</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.ca</EcpUrl-sms>
        <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=domain.ca</EcpUrl-publish>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.ca</EcpUrl-photo>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.ca</EcpUrl-extinstall>
        <OOFUrl>https://webmail.company.com/EWS/Exchange.asmx</OOFUrl>
        <UMUrl>https://webmail.company.com/EWS/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
        <ServerExclusiveConnect>on</ServerExclusiveConnect>
        <EwsPartnerUrl>https://webmail.company.com/EWS/Exchange.asmx</EwsPartnerUrl>
        <GroupingInformation>Acheson</GroupingInformation>
      </Protocol>
      <Protocol>
        <Type>WEB</Type>
        <Internal>
          <OWAUrl AuthenticationMethod="Basic, Fba">https://2013server.domain.ca/owa/</OWAUrl>
          <Protocol>
            <Type>EXCH</Type>
            <ASUrl>https://webmail.company.com/ews/exchange.asmx</ASUrl>
          </Protocol>
        </Internal>
        <External>
          <OWAUrl AuthenticationMethod="Fba">https://webmail.company.com/owa/</OWAUrl>
          <Protocol>
            <Type>EXPR</Type>
            <ASUrl>https://webmail.company.com/EWS/Exchange.asmx</ASUrl>
          </Protocol>
        </External>
      </Protocol>
      <Protocol>
        <Type>EXHTTP</Type>
        <Server>webmail.company.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Ntlm</AuthPackage>
        <ASUrl>https://webmail.company.com/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://webmail.company.com/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://webmail.company.com/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.ca</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.ca</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.ca</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.ca</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.ca</EcpUrl-sms>
        <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=domain.ca</EcpUrl-publish>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.ca</EcpUrl-photo>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.ca</EcpUrl-extinstall>
        <OOFUrl>https://webmail.company.com/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://webmail.company.com/ews/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
        <ServerExclusiveConnect>On</ServerExclusiveConnect>
      </Protocol>
      <Protocol>
        <Type>EXHTTP</Type>
        <Server>webmail.company.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Basic</AuthPackage>
        <ASUrl>https://webmail.company.com/EWS/Exchange.asmx</ASUrl>
        <EwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EwsUrl>
        <EmwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EmwsUrl>
        <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.ca</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.ca</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.ca</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.ca</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.ca</EcpUrl-sms>
        <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=domain.ca</EcpUrl-publish>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.ca</EcpUrl-photo>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.ca</EcpUrl-extinstall>
        <OOFUrl>https://webmail.company.com/EWS/Exchange.asmx</OOFUrl>
        <UMUrl>https://webmail.company.com/EWS/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
        <ServerExclusiveConnect>On</ServerExclusiveConnect>
      </Protocol>
    </Account>
</Response>
</Autodiscover>
Thanks,
Jeremy

Exchange 2013 mailbox added to the CAS array

Similar Messages

Maybe you are looking for