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

Similar Messages

Multiple owa sites on a single server 2012 with exchange 2013 (mailbox, cas)

hi,
I'm trying to
set up an exchange server 2013 on windows 2012 with all roles installed for 2 owa virtual directory, one for integrated windows authentication and the other for forms-based authentication.
I followed a tutorial for exchange 2010.
http://technicaljeditrials.info/2011/02/28/exchange-2010-multiple-owaecp-directories-part-1/
Step 1: IP Address
Obtain a second IP address and add it to the NIC of your server.
Step 2: DNS
Add a DNS entry for That secondary IP address for the name we will want to use in the new FBA OWA Web site.
I have chosen "testwebmail."
Be sure there is a valid SSL certificate (recommended to have UC or SAN
SSL certs) on the server Which has the new name "testwebmail" that will be used in the certificate.
Step 3: New Web Site
Create a new web site in IIS on the Client Access Server and bind it to the new IP address used in step 1.
Step 4: Adding Exchange Virtual Directories
The web site has been created and bound to the secondary IP address of our server.
Also the DNS record That will be used to access the OWA FBA new page was added to DNS.
The next step is to go into EMS and begin adding our virtual directories for OWA and ECP.
Login to the Exchange server and open the Exchange Management Shell.
Then run Get-Get-OWAVirtualDirectory and ECPVirtualDirectory to see the default OWA and ECP directories.
New-OWAVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/owa
New-ECPVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/ecp
Step 5: Configure the Virtual Directories
To configure the virtual directories we will disable FBA on the Default Web Site OWA and ECP virtual directories
Set-OWAVirtualDirectory -Identity "OWA (Default Web Site)" -WindowsAuthentication
$true -BasicAuthentication $false -FormsBasedAuthentication $false
Set-ECPVirtualDirectory -Identity "ECP (Default Web Site)"
-WindowsAuthentication $true -BasicAuthentication $false -FormsBasedAuthentication
$false
Step 6: iisreset
now if I access the default site I log in with
windows integrated authentication, but when I try to access the second site with forms authentication tells me username or password incorrect
Tell me you know where I'm wrong?
thanks
Greetings
Daniele

Hello,
Something like this:
New-OWAVirtualDirectory -WebSiteName "FBA"
Enable the Basic authentication via running the following command:
Set-OWAVirtualDirectory -Identity "yourservername\owa (FBA)" -BasicAuthentication $true
Restart the IIS admin service in services.msc
Thanks,
Simon Wu
TechNet Community Support

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.

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.

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

Security Update for exchange 2013 SP1 (KB3040856) failed mid-way / power problem mailbox server disconnected

While applying todays security update for exchange 2013 (KB3040856) there was a power issue (sad story) and the update was interrupted halfway through. A bunch of service were left deactivated and I beleive I brought them back.
At this point the exchange admin center brings me to the login and when I do login, I get an enable to display page msg after the login.
I have an ActiveSync error log "cannot access the mailbox because the mail box server is disconnected" translated from french.
I also have ASP.NET 4.0 error "MapiExceptionMdbOffline"
What could be the next step in fixing this if it is at all possible ? I am not an expert in cmdlet but can manage if pointed in the right direction.
Any help would be greatly appreciated.
Thank you.

I ran update KB3040856, and it disabled all Exchange services, and a few others besides (IIS and filtering). I ran the test-servicehealth cmdlet and eventually got all the services set to automatic and all running.
This is really a stupid thing for an update to do, what is going on? Exchange 2013 is trouble enough already, we really do not need this sort of agro.

Jetstress tool for Exchange 2013

Greetings
I am upgrading the Exchange 2013 environment and want to run the Jetstress tool before putting the servers in production.
I have 2 Mailbox servers as member of DAG.
Please provide me inputs on below mentioned points:
1. As per microsoft recommendations, the Jetstress tool should be run before installing Exchange Server.
However, i have already installed Exchange server and done the CAS Virtual Directories configuration.
Is it possible if i can run Jetstress after installing Exchange Server.
2. Now, the Exchange is already installed. DO i need to run Jetstress on all DAG members.
Thanks in advance.

Hi
Preferably, Jetstress testing should be performed before you install Exchange on the server. There are some well-known risks associated with running Jetstress on a machine with Exchange installed. If you use a version of Jet (ESE.DLL and ESEPERF.*) different
than the version installed with Exchange, the registration of the Jet database counters in the Jetstress install directory will broke the database counters for Exchange after Jetstress is removed. You may have to uninstall the existing Exchange Database Engine
counters before you run Jetstress, by running unlodctr ESE at a command prompt. However, you will still have to uninstall and reinstall the Exchange version of the Exchange Database Engine counters when testing is completed.
Summary - It is not advisable to run jetstress on a production exchange server which will lead to multiple complications.
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 Thanks Sathish
(MVP)

Error During Exchange 2013 Mailbox Transport Role Install On Server 2012

I was installing Exchange 2013 on Server 2012. The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin. There has never been an Exchange instance on this domain. I got past
the prerequisite checks, and the installer showed 15 steps, so I walked away. When I came back, I saw this:
Step 8 of 15: Mailbox role: Transport service
Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;
          while($currTime -le $timeout)
            $setSharedCDCErrors = @();
            try
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
              if($successfullySetConfigDC)
                break;
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            catch
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          if( -not $successfullySetConfigDC)
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "Unable to set shared config DC.".
The only option on the screen was exit, so I did. I checked the start menu, and there were two new Exchange icons, but I did not click them. I ran the installer again, and it detected an incomplete install, the only option was to click next to
finish the install, so I clicked next. This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service." I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013
came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh. Any suggestions?

I've tried three times since my last post, following
http://msexchange2010.info/archives/2330 as closely as possible the most recent time. I am consistently getting the same error that appears to imply I don't have write access to the domain. I don't understand this, because I am using the
same domain admin account I have been using all along. Nonetheless, here is the powershell output starting with the first Exchange setup.exe step (all other steps were already performed, all available updates were installed, and the server was rebooted
prior to this):
Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.
PS (domain admin home)> D:
PS D:\> .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Extending Active Directory schema COMPLETED
The Exchange Server setup operation completed successfully.
PS D:\> .\Setup.exe /PrepareAD /OrganizationName:PRD-INC /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis COMPLETED
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
aspx
Configuring Microsoft Exchange Server
Organization Preparation COMPLETED
The Exchange Server setup operation completed successfully.
PS D:\> .\Setup.exe /Mode:Install /Roles:ClientAccess, Mailbox, ManagementTools /t E:\Exchange /IAcceptExchangeServe
rLicenseTerms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Languages
Management tools
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Client Access role: Front End Transport service
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup COMPLETED
Stopping Services COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Exchange Management Tools COMPLETED
Mailbox role: Transport service COMPLETED
Mailbox role: Client Access service COMPLETED
Mailbox role: Unified Messaging service COMPLETED
Mailbox role: Mailbox service FAILED
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox.".
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox. Property Name: Database".
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS D:\>
I am cleaning out in ADSI and rebuilding the server for now, because the server is behaving oddly (not as oddly as it was with 6GiB, but oddly, nonetheless). I probably won't try to install Exchange again before tomorrow. What should I do to prevent
encountering the above again and/or if I encounter it again?

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.

Migration Exchange 2010 to Exchange 2013 with CAS Array and DAG

Dear All,
I am starting the migration of Exchange 2010 2 servers (CAS/Mailbox) with DAG no CAS Array to Exchange 2013 with 2 servers CAS array and 2 Mailbox servers with DAG. I read on some blogs that no requirement of CAS array on Exchange 2013. My concern how to
configure NLB on CAS servers for the client to connect.
Please guide and have any deployment guide for this, kindly share.
Thanks

Hi ,
As you said there is no use and meaning of having the cas array in exchange 2013 and also thanks a lot to Microsoft for introducing an single namespace facility in exchange 2013.
My suggestion and Microsoft recommendation should be to go with hardware load balancers for exchange 2013 rather than using the windows NLB and round robin method.
Why we need to go for HLB ?
Disadvantages
of some load balancing methods :
Windows
NLB :-
If you use Windows NLB then it can provide redundancy on server level failure and not on application level.
DNS
round robin :-
In case if we use the windows round robin method for load balancing then it wouldn't provide server level
and application level redundancy during the failures.At the Same time we need to manually adjust the DNS records during the server failure but on the client end dns caches will create the issues.
Configuring NLB for exchange 2013 :
http://msexchangeguru.com/2013/08/14/windowsnlb/
NLB configurations for exchange 2010 and 2013 will be same.
Configuring round robin for exchange 2013 :
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Advisable method is to have the CAS and MBX roles on the same box if NLB not comes it to play.Because windows failover clustering and NLB cannot be configured on the same box.In exchange 2013 cas role is a stateless server role so there is no need to have
that role on a separate box.
Thanks & Regards S.Nithyanandham

Disaster Recovery site for Exchange 2013

Hi, I have to build DR site with Exchange 2013 environment and unable to see document for Exchange 2013 perspective.
In new environment will contain 10 CAS/MBS co-located servers in primary datacenter with two mailbox copies and disaster recovery site with 5 Exchange 2013 CAS/MBS co-located servers with one database copy in blocked activation mode. Any document related
to this screnario would be helpful. The required solution is when all the servers in PDC goes down then DR site would be activated at DMZ level and Server level. Can I use same IP subnet/Site for the DR site?

Hi,
Yes, you can use the same subnet for DR site. If you use the same subnet, you need to use stretched VLAN.
Here is a related thread for your reference. (This case is for Exchange 2010, but it also applies to Exchange 2013 DAG deployment)
http://social.technet.microsoft.com/Forums/exchange/en-US/80ca452f-f950-4496-83e8-3067d571bb57/exchange-2010-dag-across-sites-different-subnets-vs-stretched-vlan?forum=exchangesvravailabilityandisasterrecovery
Best regards,
Belinda Ma
TechNet Community Support

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

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

KeepAlive settings for Exchange 2013 environment

Hello All,
We have very weired problem in our environment. Our environment consists of 10 Exchange 2013 multi-role servers in Primary DC with Wind 2012 OS and 5 servers in Secondary DC with Wind 2012. We have F5 LB & Cisco f/w
Sometime back users reported the outlook disconnection issue and we've implemented following settings in the environment based on MS support team recommendation
1) Configure the Idle session time out on the Network devices to 2 hours.
2) Add the registry key “MinimumConnectionTimeout” with value as 120
seconds as per below article on all the Exchange 2013 Servers. Once this registry key is added, we need to restart the Server for the changes to take effect..
Path: HKLM\Software\Policies\Microsoft\Windows NT\RPC
Type: REG_DWORD
Name: MinimumConnectionTimeout
Value: 120 (Decimal)
3) Add the KeepAliveTime registry key on all the Exchange 2013 Servers
to reduce the Keep alive from default 2 hours to 5 minutes. Once this registry key is added, we need to restart the Server for the changes to take effect.
Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters
Value name: KeepAliveTime
Type: REG_DWORD
Value: 300000 (Decimal)
This value controls how frequently TCP tries to verify that an idle
connection is still intact by sending a keep-alive packet. If the remote computer is still reachable, it acknowledges the keep-alive packet. The recommended value setting is 300,000 (5 minutes).
After applying these settings we've started facing the ACTIVESYNC issue in the environment. We've changed the keep alive setting in exchange server to 29 mins and now activesync issue is solved but outlook disconnect issue started
IS THERE ANYONE who can recommend what is the correct KEEP ALIVE value should be kept in such environment
Our environment has 27K mailboxes totally spread across 50 DBs apprx
Appreciate experts help here !!!
Vinoth Kumar. M
Vinoth Kumar. M

Just to add one more point here
All our network devices including F5 LB has 30 mins as the idle time out value.
We've added below registry values also in all AD DC & Exchange servers
MaxConcurrentAPI
http://support.microsoft.com/kb/2688798
5 in DC
10 in Exchange servers
Vinoth Kumar. M

Enable legacy public folders for Exchange 2013 prior to migration?

We're about ready to migrate to Exchange 2013 from 2010. We have a public folder database on 2010 that users can't see once migrated to 2013. If I run through the commands according to the technet article "Configure legacy public folders where user
mailboxes are on Exchange 2013 servers" (https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx), will users who's mailboxes are still on Exchange 2010 be able to see these public folders?

I know they've made alot of changes recently in how legacy public folders are handled in Exchange 2013 (mostly CU7), but I haven't had to do anything more than just setting the proper public folder database on the Exchange 2013 databases.
That being said, looking over the article you are not doing any moves, and it looks eerily similar to this blog post:
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
So I don't think this would hurt Public Folder access for your users in your legacy environment.
Did you deploy CU7? If so, then do what both articles say. If not try using Set-MailboxDatabase -Identity <2013 db name> -PublicFolderDatabase <PF DB NAME>
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Performance counters for exchange 2013 mailbox & cas servers?

Similar Messages

Maybe you are looking for