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

Similar Messages

Outlook PRF file settings for Exchange 2013 environment

Hi Team,
Client - Outlook 2007
Existing environment - exchange 2007
New environment - exchange 2013
Recently migration of exchange 2007 to exchange 2013 happened in our environment subsequently some users mailboxes are moved from exchange 2007 to exchange 2013.
In the Exchange 2007 environment, users outlook profile settings are applied via importing the below prf file and it works fine.
;Automatically generated PRF file from the Microsoft Office Customization and Installation Wizard
; Section 1 - Profile Defaults
[General]
Custom=1
ProfileName=outlook
DefaultProfile=Yes
OverwriteProfile=Yes
ModifyDefaultProfileIfPresent=false
; Section 2 - Services in Profile
[Service List]
ServiceX=Microsoft Outlook Client
ServiceEGS=Exchange Global Section
Service1=Microsoft Exchange Server
ServiceEGS=Exchange Global Section
; Section 3 - List of internet accounts
[Internet Account List]
; Section 4 - Default values for each service.
[ServiceX]
CachedExchangeMode=0x00000002
CachedExchangeSlowDetect=true
[ServiceEGS]
CachedExchangeConfigFlags=0x00000900
MailboxName=%UserName%
HomeServer=mailboxserver.exchange.xxx.xx
[Service1]
OverwriteExistingService=No
UniqueService=Yes
MailboxName=%UserName%
HomeServer=mailboxserver.exchange.xxxx.xa
AccountName=Microsoft Exchange Server
; Section 5 - Values for each internet account.
; Section 6 - Mapping for profile properties
[Microsoft Exchange Server]
ServiceName=MSEMS
MDBGUID=5494A1C0297F101BA58708002B2A2517
MailboxName=PT_STRING8,0x6607
HomeServer=PT_STRING8,0x6608
OfflineAddressBookPath=PT_STRING8,0x660E
OfflineFolderPathAndFilename=PT_STRING8,0x6610
[Exchange Global Section]
SectionGUID=13dbb0c8aa05101a9bb000aa002fc45a
MailboxName=PT_STRING8,0x6607
HomeServer=PT_STRING8,0x6608
RPCoverHTTPflags=PT_LONG,0x6623
RPCProxyServer=PT_UNICODE,0x6622
RPCProxyPrincipalName=PT_UNICODE,0x6625
RPCProxyAuthScheme=PT_LONG,0x6627
CachedExchangeConfigFlags=PT_LONG,0x6629
[Microsoft Mail]
ServiceName=MSFS
ServerPath=PT_STRING8,0x6600
Mailbox=PT_STRING8,0x6601
Password=PT_STRING8,0x67f0
RememberPassword=PT_BOOLEAN,0x6606
ConnectionType=PT_LONG,0x6603
UseSessionLog=PT_BOOLEAN,0x6604
SessionLogPath=PT_STRING8,0x6605
EnableUpload=PT_BOOLEAN,0x6620
EnableDownload=PT_BOOLEAN,0x6621
UploadMask=PT_LONG,0x6622
NetBiosNotification=PT_BOOLEAN,0x6623
NewMailPollInterval=PT_STRING8,0x6624
DisplayGalOnly=PT_BOOLEAN,0x6625
UseHeadersOnLAN=PT_BOOLEAN,0x6630
UseLocalAdressBookOnLAN=PT_BOOLEAN,0x6631
UseExternalToHelpDeliverOnLAN=PT_BOOLEAN,0x6632
UseHeadersOnRAS=PT_BOOLEAN,0x6640
UseLocalAdressBookOnRAS=PT_BOOLEAN,0x6641
UseExternalToHelpDeliverOnRAS=PT_BOOLEAN,0x6639
ConnectOnStartup=PT_BOOLEAN,0x6642
DisconnectAfterRetrieveHeaders=PT_BOOLEAN,0x6643
DisconnectAfterRetrieveMail=PT_BOOLEAN,0x6644
DisconnectOnExit=PT_BOOLEAN,0x6645
DefaultDialupConnectionName=PT_STRING8,0x6646
DialupRetryCount=PT_STRING8,0x6648
DialupRetryDelay=PT_STRING8,0x6649
[Personal Folders]
ServiceName=MSPST MS
Name=PT_STRING8,0x3001
PathAndFilenameToPersonalFolders=PT_STRING8,0x6700
RememberPassword=PT_BOOLEAN,0x6701
EncryptionType=PT_LONG,0x6702
Password=PT_STRING8,0x6703
[Unicode Personal Folders]
ServiceName=MSUPST MS
Name=PT_UNICODE,0x3001
PathAndFilenameToPersonalFolders=PT_STRING8,0x6700
RememberPassword=PT_BOOLEAN,0x6701
EncryptionType=PT_LONG,0x6702
Password=PT_STRING8,0x6703
[Outlook Address Book]
ServiceName=CONTAB
[LDAP Directory]
ServiceName=EMABLT
ServerName=PT_STRING8,0x6600
UserName=PT_STRING8,0x6602
UseSSL=PT_BOOLEAN,0x6613
UseSPA=PT_BOOLEAN,0x6615
EnableBrowsing=PT_BOOLEAN,0x6622
DisplayName=PT_STRING8,0x3001
ConnectionPort=PT_STRING8,0x6601
SearchTimeout=PT_STRING8,0x6607
MaxEntriesReturned=PT_STRING8,0x6608
SearchBase=PT_STRING8,0x6603
CheckNames=PT_STRING8,0x6624
DefaultSearch=PT_LONG,0x6623
[Microsoft Outlook Client]
SectionGUID=0a0d020000000000c000000000000046
FormDirectoryPage=PT_STRING8,0x0270
WebServicesLocation=PT_STRING8,0x0271
ComposeWithWebServices=PT_BOOLEAN,0x0272
PromptWhenUsingWebServices=PT_BOOLEAN,0x0273
OpenWithWebServices=PT_BOOLEAN,0x0274
CachedExchangeMode=PT_LONG,0x041f
CachedExchangeSlowDetect=PT_BOOLEAN,0x0420
[Personal Address Book]
ServiceName=MSPST AB
NameOfPAB=PT_STRING8,0x001e3001
PathAndFilename=PT_STRING8,0x001e6600
ShowNamesBy=PT_LONG,0x00036601
; Section 7 - Mapping for internet account properties. DO NOT MODIFY.
[I_Mail]
AccountType=POP3
;--- POP3 Account Settings ---
AccountName=PT_UNICODE,0x0002
DisplayName=PT_UNICODE,0x000B
EmailAddress=PT_UNICODE,0x000C
;--- POP3 Account Settings ---
POP3Server=PT_UNICODE,0x0100
POP3UserName=PT_UNICODE,0x0101
POP3UseSPA=PT_LONG,0x0108
Organization=PT_UNICODE,0x0107
ReplyEmailAddress=PT_UNICODE,0x0103
POP3Port=PT_LONG,0x0104
POP3UseSSL=PT_LONG,0x0105
; --- SMTP Account Settings ---
SMTPServer=PT_UNICODE,0x0200
SMTPUseAuth=PT_LONG,0x0203
SMTPAuthMethod=PT_LONG,0x0208
SMTPUserName=PT_UNICODE,0x0204
SMTPUseSPA=PT_LONG,0x0207
ConnectionType=PT_LONG,0x000F
ConnectionOID=PT_UNICODE,0x0010
SMTPPort=PT_LONG,0x0201
SMTPSecureConnection=PT_LONG,0x020A
ServerTimeOut=PT_LONG,0x0209
LeaveOnServer=PT_LONG,0x1000
[IMAP_I_Mail]
AccountType=IMAP
;--- IMAP Account Settings ---
AccountName=PT_UNICODE,0x0002
DisplayName=PT_UNICODE,0x000B
EmailAddress=PT_UNICODE,0x000C
;--- IMAP Account Settings ---
IMAPServer=PT_UNICODE,0x0100
IMAPUserName=PT_UNICODE,0x0101
IMAPUseSPA=PT_LONG,0x0108
Organization=PT_UNICODE,0x0107
ReplyEmailAddress=PT_UNICODE,0x0103
IMAPPort=PT_LONG,0x0104
IMAPUseSSL=PT_LONG,0x0105
; --- SMTP Account Settings ---
SMTPServer=PT_UNICODE,0x0200
SMTPUseAuth=PT_LONG,0x0203
SMTPAuthMethod=PT_LONG,0x0208
SMTPUserName=PT_UNICODE,0x0204
SMTPUseSPA=PT_LONG,0x0207
ConnectionType=PT_LONG,0x000F
ConnectionOID=PT_UNICODE,0x0010
SMTPPort=PT_LONG,0x0201
SMTPSecureConnection=PT_LONG,0x020A
ServerTimeOut=PT_LONG,0x0209
CheckNewImap=PT_LONG,0x1100
RootFolder=PT_UNICODE,0x1101
[INET_HTTP]
AccountType=HOTMAIL
Account=PT_UNICODE,0x0002
HttpServer=PT_UNICODE,0x0100
UserName=PT_UNICODE,0x0101
Organization=PT_UNICODE,0x0107
UseSPA=PT_LONG,0x0108
TimeOut=PT_LONG,0x0209
Reply=PT_UNICODE,0x0103
EmailAddress=PT_UNICODE,0x000C
FullName=PT_UNICODE,0x000B
Connection Type=PT_LONG,0x000F
ConnectOID=PT_UNICODE,0x0010
I have changed the home server in [ServiceEGS] and [Service1] with the CAS Array VIP configured with the DNS name
autodiscoverservices.exchange.xxxx.xx but it is not working and getting "Exchange server unavailable" error. Some one have any idea how to
configure the user outlook profile via a prf file which works with exchange server 2013 autodiscover services. Is there any more settings to be applied to the PRF file to make it work.
[ServiceEGS]
CachedExchangeConfigFlags=0x00000900
MailboxName=%UserName%
HomeServer=autodiscoverservices.exchange.xxxx.xx
[Service1]
OverwriteExistingService=No
UniqueService=Yes
MailboxName=%UserName%
HomeServer=autodiscoverservices.exchange.xxxx.xx
AccountName=Microsoft Exchange Server

May I ask why you changed the home server to autodiscoverservices.exchange.xxxx.xx?
Basically, we set it to Microsoft Exchange server address.
Flynn

Exchange 2010 in a Exchange 2013 Environment

I am trying to install Exchange 2010 in an Exchange 2013 environment which was migrated from Exchange 2007 earlier.
Exchange 2010 sp1 Mailbox and Hub roles installed fine however I cannot install the CAS role. Saw some references to change the OAB to a non exchange 2013 version - however that is the only version we have = OAB 2013.
This is the error I get:-
Error:
The following error was generated when "$error.Clear();
get-OfflineAddressBook -DomainController $RoleDomainController | where { $_.IsDefault } | Enable-OabWebDistribution
" was run: "The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).".
The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:02:15
Finalizing Setup
Cancelled
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

Hi,
Please temporary remove all the OAB objects then try re-install the CAS server again.
After installing CAS server, we can re-build the OAB on Exchange 2013.
More details in the following articles:
Remove-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/aa995963(v=exchg.150).aspx
New-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/bb123735(v=exchg.150).aspx
Hope it is helpful.
If the CAS server still cannot be installed, please post the details of setup log.
Thanks
Mavis

Is smb 3.0 already supported for exchange 2013

Hello,
We are looking to deploy exchange 2013. We have a netapp storage and vmware environment.
I was wondering if smb 3.0 is already supported for exchange 2013. I read in a blog of 2012 that it wasn't supported at the time. We would like to use it instead of a iscsi lun.

Hi,
Based on my knowledge, it is still not supported for Exchange 2013 up to now.
Here is an article for your reference, please refer to the "Exchange storage requirements" section.
Exchange 2013 Virtualization
http://technet.microsoft.com/en-us/library/jj619301.aspx#BKMK_Prereq
Another related article for your reference.
Exchange 2013 Storage Configuration Options
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Best Practice Analyzer for Exchange 2013

Greetings,
I have upgraded the messaging infrastructure from Exchange 2007 to Exchange 2013.
I want to test the Health of the system through ExBPA for Exchange 2013.
But i don't find any setup for Exchange 2013 like it was in 2010.
I went through an article by Office365 community, according to which for In-premises Exchange also we need to have office 365 account (can use trial account also) to get the downloader file for ExBPA 2013.
http://community.office365.com/en-us/w/deploy/office-365-best-practices-analyzer-for-exchange-server-2013.aspx
But to run the setup the servers needs to be connected to internet.
And, i don't want to expose my environment to internet in any condition.
Somebody, please suggest me if there is any setup available so that i can install directly without exposing to internet.
Thanks in advance.
Best Regards,
K2

Welcome to Exchange 2013.
Exchange Server 2013 doesn't come with ExBPA for health check. This might help
http://exchangeserverpro.com/powershell-script-health-check-report-exchange-2010/
Apart from that you can run these commands too
Get-ServerHealth -Identity Exchange2013ServerName
Test-ServiceHealth
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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.

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)

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

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

Configuring Lync Server 2013 to be a partner Application for Exchange 2013

Hello Guys,
I just want to share my experience while configuring Lync server 2013 to be a partner Application for exchange 2013 sever.
As mentioned on technet you need to run Configure-EnterprisePartnerApplication.ps1 script that ships with Exchange 2013.
But when I tried to run the script as described on the technet article, I found it always fails with " the accepted domain is not valid"
I have checked my accepted domains many times and i found that there's no issues with my configured accepted domain.
So I started to review the script to find the issue and I found that the script was configured as below
$acceptedDomains = Get-AcceptedDomain ;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains[0].Name;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
which is totally wrong as below:
firstly it makes $AcceptedDomain variable to equal the Name of the accepted domain.
Not all customers configure the name of the Accepted Domain to be the Domain Name.
Secondly it makes $AcceptedDomain variable to equal the name of the first Accepted Domain.
The first domain may be not the default Accepted Domain.
So I have configured the script as below
$acceptedDomains = Get-AcceptedDomain | ? {$_.Default -eq "True"} ;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains.DomainName;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
I hope This help.
Thanks
Ahmed Fouad

Hi,
This is helpful, thanks for sharing.
Best regards,
Belinda Ma
TechNet Community Support

It is there an alternative to the Test-SystemHealth powershell cmdlet for Exchange 2013?

Hello
The Powershell cmdlet Test-SystemHealth, that was available on Exchange 2010, is no longer available on Exchange 2013.
Test-SystemHealth cmdlet gathered data about the Microsoft Exchange system and analyzed the data according to best practices.
Are there any alternatives to this for Exchange 2013?
Thanks!

Haven't really played with it too much, but check out Get-ServerHealth
http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
Looks to have replaced Test-SystemHealth.

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

EXMON "exchange server user monitor" for Exchange 2013?

Hello,
it Looks like EXMON is not supported for Exchange 2013. Is this correct or can i use it with Server 2012 R2 and Exchange 2013 (CU6++) ?
Is there any alternative to check high log growth rate to see which user is responsable for this?
Thanks for Feedback.
best,
Martin

Hi Martin,
Yes, ExMon is not supported for exchange 2013.
Except the suggestion above, here is an exclusive application for you reference, it could retrieve statistics for all or selected mailboxes in a specified database and server, it may give you some help:
Exchange Server Mailbox Statistics Tool - v1.6.2
The tool retrieves mailbox statistics which includes Folder Count, Total Items, Associated Items, Deleted Items, Total Items Size, Deleted Items Size, Oldest Item Date, Newest Item Date, Items Age, Mailbox Age and Quota details. It also includes an additional
option named "Archive Statistics Planner" which will let you search mailboxes and provide statistics report with specific dates.
Best regards,
Niko Cheng
TechNet Community Support

BPA for Exchange 2013 still in beta!?

Exchange 2013 is over 2 years old.
Is Microsoft ever going to release a BPA for their flagship messaging platform that's NOT in beta?

Hi,
At present, there is only a beta of Best Practices Analyzer for Exchange 2013 available. If you want to get the latest information about it, please pay attention to the Exchange blog.
For your convenience:
http://blogs.technet.com/b/exchange/
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

PowerGUI Powerpack for Exchange 2013

Is there a powerpack that can be added to the powerGUI script editor for scripting in exchange 2013?

Hi,
Based on my search, currently, there is no official document about
PowerGUI Powerpack for Exchange 2013.
However, we can connect to Exchange server using remote shell.
For more details about this, please refer to the following article.
https://technet.microsoft.com/en-us/library/dd335083(v=exchg.150).aspx
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Transport agent for Exchange 2013

Hello!
I write transport agent for Exchange 2013 and I have two questions:
1. How I can determine is AD OU of recipient different from OU of sender?
2. How I can change routing of message from internal to external for such recipient.
Thanks in advance

1. You can't get that information from within a Transport Agent directly so you need to either use LDAP to lookup the sender (which from a performance point of view isn't a wonderful idea) or some form of cache etc.
2. You can use a routing override to do this see
http://blogs.technet.com/b/appssrv/archive/2009/08/26/how-to-control-routing-from-your-own-routing-agent.aspx for an example
Cheers
Glen

KeepAlive settings for Exchange 2013 environment

Similar Messages

Maybe you are looking for