Cisco IronPort with On Premise Exchange 2013

Hello All
The company I work for is in the process of starting an on premise Exchange 2007 to Exchange 2013 migration.
Most of the issues I don't think I'll have an issue with; however, where I am not finding much info is in regards to other companies using Cisco IronPort with Exchange 2013.
SO, I have two questions within this topic...
One, is anyone using Cisco IronPort with Exchange 2013 (on premise) out here?
Two, my manager is very controlling. I am the Exchange Admin; however, anything having to do with this IronPort thing with regards to Exchange HE has to do it. So, if anyone is familiar with this IronPort thing... How much work on the IronPort is going
to have to be done during this migration to keep things going?

It shouldn't be any different with Exchange 2013 than it is with Exchange 2007.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Getting EOP to send mail to On premises Exchange 2013

one of may clients has Office 365 Enterprise E1 for Nonprofits and on premise exchange 2013 server which I'm trying to implement the EOP service.
but i cannot get the exchange online outbound connector to forward on the emails to the on premise server.
i have active directory sync working.
i.e when i add a new user on premises it creates it online.
could anybody let me know how to get this service to work.
what i would like is
1 mx record to point to eop service and collect and filter email.
(which i have done by adding mx records as per dns instructions. checks show as fine.but changed back to on premises server because emails where only staying in online inbox. the on premises domain name has been setup within office 365 as default domain and
in accepted domains within exchange online.both exchange online and on premises default domain name our the same.)
2 filter mail to be forwarded to correct mail box to on premises server.
( which i have setup outbound connector with exchange online to point to our on premises exchange server but does not receive any emails they are received in office 365 online mailbox and not forwarded on)
3 on premises server to forward mail to EOP service
( which i have done by creating inbound connector in exchange online and adding it as smart host to on premises outbound connector and appears to be working fine.)
am i missing something?
any help would be gratefully appreciated
Many Thanks
Stephen
1 first server (AD,AD CS,DC,Dhcp,dns servers and Hyper V)
setup physical server with windows server 2012 r2 standard Essentials Experience Role installed and hyper v role
2nd server server (exchange 2013)
VM with windows server 2012 r2 with exchange server 2013 installed and all updates done including exchange cu1 update.

Matthew thank you your reply but No it is set for Authoritative. would this be the problem.
many thanks
Stephen

Migrate Office 365 To On-Premise Exchange 2013

hello
My client attempts to migrate the mailboxes hosted from Office 365 to Exchange 2013 on-premise hosted in the client's company.
However, despite all attempts , it appears that no procedure works correctly. All's time , something wrong appears Inside the process.
Indeed, on Office 365 we don't see the servers in our on-premise exchange 2013.
the Exchange Hybrid are set correctly and to exchange 2013 migration attempts to run Office 365. (MRS proxy select)
All servers are in the same Update. My client can't update with the last CU6 all server and want to stay with the CU3
Thanks for your read and for your help
Best regard
Alexis

Bonjour,
J'ai deja réalisé ce type de mission, si celle-ci est tout à fait possible en utilisant uniquement les outils intégrés à Exchange, elle nécessite beaucoup de préparation, notament en terme d'AD, et selon la configuration dans laquelle vous êtes, peut etre
*non* transparente pour vos utilisateurs.
" My client can't update with the last CU6 all server and want to stay with the CU3"
C'est par contre un point plus que géneant, le CU3 n'est plus supporté par MS, la compatibilité avec O365 n'est donc pas garantie.
Si vous souhaitez un echange plus sérieux sur ce sujet, vous pouvez me contacter.
Bruce Jourdain de Coutance - Consultant MVP Exchange http://blog.brucejdc.fr

Setting up Push Notification from on premise exchange 2013

We have been trying to get push notifications to work with the OWA for IPhone/Ipad app using the information provided in the below TechNet article. We have an exchange 2013 on premise installation and going by the info in the article, are attempting to create
a relationship with the office 365 servers. We already have our domain configured in office 365. When we attempt to create the New-Authserver, we receive the following error.
New-AuthServer MicrosoftSts -AuthMetadataUrl https://accounts.accesscontrol.windows.net/metadata/json/1/?realm=DOMIAN
Cannot acquire auth metadata document from 'https://accounts.accesscontrol.windows.net/metadata/json/1/?realm=DOMAIN.
Error: An exception occurred during a WebClient request..
    + CategoryInfo          : ResourceUnavailable: (:) [New-AuthServer], AuthMetadataClientException
    + FullyQualifiedErrorId : [Server=MAIL SERVER,RequestId=9dd5e9ff-71cc-455f-9efb-5bb98c2d1f83,TimeStamp=5/13/2014 9:1
   3:13 PM] [FailureCategory=Cmdlet-AuthMetadataClientException] DEDA18E3,Microsoft.Exchange.Management.SystemConfigu
rationTasks.NewAuthServer
    + PSComputerName        : CAS server
http://technet.microsoft.com/en-us/library/dn511017(v=exchg.150).aspx
The Oauth certificate was successfully created and exported to the various mail servers. Does anyone have any ideas and what the issue could be?
Thank
Jorge

you may find posting in the Lion Server forum to be more helpful.

2012 r2 Essentials on premises Exchange 2013 integration failing

I have a new server in my development environment that I have installed Essentials and Exchange 2013 on with all of the latest updates. After getting Exchange 2013 installed I am unable to successfully run the Exchange Integration wizard. It fails saying
that it can't contact the exchange server.
I am able to access the Exchange Powershell, Exchange Admin center and OWA.
The Essentials Anywere Access has been setup and Is working as well.
any suggestions on where to go from here?

Hi,
-->It fails saying that it can't contact the exchange server.
Can you ping the exchange server via server name and IP address? In addition, did you apply
Cumulative Update 5 for Exchange Server 2013 and reboot the Exchange server, then monitor the result? Just a confirmation, thanks for your understanding.
Please also refer to following article and check if can help you.
Integrate an On-Premises Exchange Server with Windows Server Essentials
In addition, if this issue still exists, please follow the path:
%programdata%\Microsoft\Windows Server\Logs and check log files if find more clues.
Windows Server Essentials 2012/2012 R2 Log Files
If any update, please feel free to let me know,
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

OneDrive for Business iPad App with on-premise SharePoint 2013

I don't know if this has more to do with OneDrive for Business or SharePoint 2013 itself.
Basically we are trying to log into OneDrive for Business on the iPad app but it says "Sorry, this app doesn't support this type of authentication"
We are using Claims Based Authentication with our On-premise SharePoint 2013 environment, which according to this table is a supported method: h**p://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/use-the-onedrive-for-business-app-on-an-iphone-or-ipad-HA104005688.aspx#_Supported__authentication
We have tried different combinations of the username and url. Windows username, DOMAIN\username, email address, username@domain, etc. nothing seems to work.
Any ideas on how to fix this?

according to office blog, it does support SharePoint on prem with following authentication(NTLM & FBA)
Introducing OneDrive for Business for iOS v1.2
Q. Does this announcement apply to customers who have deployed SharePoint 2013 on-premises?
A. Yes. The OneDrive for Business for iOS v1.2 app does support some SharePoint on-premises configurations (NTLM & FBA). We are committed to providing customers access to their OneDrive for Business in SharePoint 2013 on-premises. We also recently introduced
new capabilities in SharePoint 2013 SP1 to more seamlessly connect on-premises investments to OneDrive for Business in Office 365. More information to be shared at SharePoint Conference 2014 (March 3-6 in Las, Vegas); we will link to the relevant information
once it has been posted next week.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

What is the best practices to apply two factor authentication on on-premise Exchange 2013 Environment ?

Hi, Everyone
i want to know what is the requirements to apply two factor authentication in Exchange 2013, Through Mobile or SMS.
what is the third party solutions of Microsoft solutions

Hi,
If we can deploy Active Directory Federation Services (AD FS) 2.0, it means that Outlook Web App and EAC in Exchange 2013 SP1 can support multifactor authentication methods, such as certificate-based authentication, authentication or security tokens, and
fingerprint authentication.
Additional, we can use TMG or Microsoft UAG to deploy MFA, please refer to:
https://social.technet.microsoft.com/Forums/exchange/en-US/f355ffbd-7d03-45d8-b4b1-987b2db5eadf/is-there-a-way-to-do-two-factor-authentication-with-outlook-web-app-2010?forum=exchangesvrgenerallegacy
Best Regards,
Allen Wang

Problem with Fresh/New Exchange 2013 - Exchange Account, Unable to verify account information

hi!
For a client, i just setup AD (windows 2012 R2), and Exchange 2013 installed on Windows 2012 R2.
The AD is brand new, the exchange is installed correctly, i setup send connectors, and i could send and receive emails succefully.
But, when i want to use mobile devices like iphone, i receive the error as in title.
I've not changed anything from the default policies of Mobile devices policy...
What could be the problem?
how can i fix?
Regards!
Lasandro Lopez

Hi Lasandro,
Agree with Dare, Exchange 2013 is not supported to run on Windows Server 2012 R2.
Exchange 2013 SP1 will add Windows Server 2012 R2 as a supported operating system for Exchange Server 2013 with SP1.
For more information, here is a blog for your reference.
Exchange Server 2013 Service Pack 1 Coming in Early 2014
http://blogs.technet.com/b/exchange/archive/2013/11/20/exchange-server-2013-service-pack-1-coming-in-early-2014.aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

GSSAPI with IMAP on Exchange 2013 SP1

We are setting up Exchange 2013 SP1 in our Exchange 2010 test environment to verify our upcoming migration. I have found out that for some reason I can't get the IMAP service in Exchange 2013 to work with Kerberos (GSSAPI) authentication with Thunderbird
as a client. It does work fine in Exchange 2010 SP3 though.
Exchange 2010 SP3 response in Thunderbird:
* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
Exchange 2013 SP1 response in Thunderbird:
* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
AUTH=GSSAPI is missing and therefore I can't blame Thunderbird from complaining about this. If I compare the output from Get-ImapSettings I can't find anything that would indicate why I shouldn't work. EnableGSSAPIAndNTLMAuth is $true on both server
and LoginType is SecureLogin.
On
http://technet.microsoft.com/en-us/library/jj619283(v=exchg.150).aspx I found out that NTLM is not supported on Exchange 2013 for POP3 and IMAP4 but Kerberos (GSSAPI) and Plain Text Authentication with SSL still is.
Has anyone got IMAP to work with Kerberos authentication on Exchange 2013 SP1?

Hello,
According to your description, we are unable to see the AUTH=GSSAPI in Exchange 2013.
My environment is Exchange 2013 CU1. I get the same result as yours. Looks Like Exchange 2013 IMAP does not support GSSAPI as authentication mechanism.
Cara Chen
TechNet Community Support

Managing User Photos with On Premise Lync 2013 & Office 365

Hello, I'm just looking for a little clarity in terms of expected behavior when using the various methods of modifying user images on these systems.
For example, I've read that Lync 2013 can utilize the high resolution photo that is stored within the user's Exchange mailbox. That would work good in theory, but what about Lync users who do not have an Exchange mailbox (or UM voicemail box)? Presumably
in that case you could use one of the AD attributes, thumbnailPhoto or jpegPhoto, the latter being preferred as it allows for higher resolution images. However in my experience, when using the jpegPhoto attribute, dirsync does successfully replicate the photo
and it shows up on the O365 portal, but the on-premise Lync server/clients have inconsistent success displaying them. Some user's can see other user's photos, but they can see eachothers or vice versa and eventually the Lync client stops displaying any of
these photos.
Ideally for us, if we could use the jpegPhoto attribute for all users, as opposed to using exchange attributes for some, that would be best, but is it designed to work this way?

Hi FuzzMunk,
I don’t think that Lync Server will
synchronize the photo from
JPEGPhoto attribute, as I know
it only synchronizes the photo from
thumbnailPhoto attribute in Active Directory.
You can see the photo displayed on Office365 portal
because it synchronizes the photo from both the
thumbailphoto and jpegphoto attributes.
Some related articles and cases for your reference.
http://blogs.technet.com/b/nexthop/archive/2010/11/22/microsoft-lync-2010-photo-experience.aspx
https://technet.microsoft.com/en-us/library/jj688150.aspx
https://social.technet.microsoft.com/Forums/lync/en-US/3ffc4fcd-eefc-4eca-bc7e-bcd007157199/lync-photo-from-active-directory
https://social.technet.microsoft.com/Forums/windowsserver/en-US/53859480-a345-4ce0-a04e-9f1fc7a947c2/what-is-the-difference-between-jpegphoto-and-thumbnailphoto-attribute-in-ad?forum=winserverDS
Best regards,
Eric

Exchange 2013 Office 365 Hybrid Cloud On-Premise Outlook Connection Problem

Hi Everyone,
We are required to migrate FROM the cloud TO an on-premise Exchange 2013 server. We set up a trial of Office365 and linked our test domain to that account. The test domain mimics our current domain, but ends in .net instead of .org.
We set up a test Exchange 2013 server with a few database servers. Internally, we can connect without issue (Outlook). We mapped our test CAS to face the Internet, and can access what we need without issue. We also set up the Hybrid
configuration on both the Exchange 2013 and Office365 servers. We have validated that DirSync works, and migration can occur up to the cloud and back down to the on-premise server.
Now, here is the issue:
We have our DNS records still pointing to Office365, so when we add an Office365 mailbox to Outlook (internal to the network or outside the network) we see absolutely no issues. We migrated a mailbox today to our on-premise server, but upon doing so,
can no longer connect to, or add, that mailbox to Outlook. When we put this integration in to effect for production, we want to be able to migrate mailboxes on-premise from the cloud, and we want to make sure users can still access their mailboxes. This
also goes for distribution groups, conference rooms, etc.
I see that most suggestions say to change your DNS record to point to the on-premise Exchange server, which is great, but after doing so Office365 accounts experience the same issue as above. We NEED to make sure that when we batch migrate, the users
DO NOT lose connectivity to their accounts. We need both Office365 accounts and Exchange on-premise accounts are accessible internally and externally. As an extra tid-bit, we HAVE configured Outlook Anywhere on Exchange 2013, but see no difference.
Any thoughts on this? Office365 and Exchange 2013 see eachother and recognize that the hybrid environment is set up good, but it appears we are missing some configurations. Currently, we have a CNAME record points our autodiscover to autodiscover.outlook.com.
Any help would be MUCH appreciated. Thanks!
Dan

Hi,
Here is an article on Move mailboxes between on-premises and Exchange Online organizations in 2013 hybrid deployments, for your reference:
http://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
I want to make sure OWA works well with the moved mailbox.
To use CNAME based autodiscover method, we need to have all domain names present in a SAN certificate.
With Exchange 2013 CU1, we now have the option of adding multiple SMTP domains to Exchange Federation/Hybrid configuration and we can specify which of these domains should act the "autodiscover" domain.
To configure an SMTP domain as the autodiscover domain, you can run following command:
Set-HybridConfiguration -Domains "domain1.com, domain2.com, domain3.com", "autod:domain.com"
More details, please refer following blogs:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part11.html
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part12.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above links.
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 mailbox migration from third party cloud to on premises

Hi,
we are currently utilizing a third party exchange 2013 cloud service to host user's mailboxes ( intermedia), now we implemented an exchange 2013 on-premises environment in Hyper V infrastructure and want to plan migration of mailboxes and related configuration.
cloud and on-premises environment have same SMTP domain ( Eg: XYZ.ORG) and currently an additional Temporary SMTP domain ( XYZ.CO ) used to test the external mailflow of on-premises since xyz.org is registered with cloud.
we need to migrate all mailboxes to on premises and enable XYZ.ORG for on-premises.
Pls suggest the prerequisites,steps, best practices for migration
Thanks in advance.

Hi Sumesh,
1. Please make sure your mails are flowing correctly using XYZ.CO domain. Hope you have XYZ.ORG also created in Exchange.
2. Hope you already created the users in your Exchange2013 server and distribution groups for current users
3. You plan a weekend for changing your MX records.
4. Change MX and A records to a lower TTL days before the migration to decrease DNS update time on migration day
5. Export Hosted Exchange data for each user to PST files using the PST capture tool and move your PSTs to a centralized location.
6. Change MX and A records to point to on-premises Exchange 2013
7. Import Hosted Exchange data from PST files into the new Exchange profiles
Please check these as well
http://community.office365.com/en-us/b/office_365_community_blog/archive/2011/08/15/exchange-hybrid-configuration-tips-moving-cloud-based-mailboxes-to-the-on-premises-organization.aspx
http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/microsoft-pst-capture-tool-part1.html
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

SME 7.1 not working with Exchange 2013 SP1 CU6

Hello, i tried upgrading to SME 7.1 on our Exchange 2013 SP1 CU6, but when trying to configure the Exchange Server in the SME management console using the configuration wizard, it gave an error before the LUN mapping page, saying "Failed to get Exchange information for server" and "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.". I upgraded Snapdrive to 7.1, verfied all credentials according to the manuals, re-installed and rebooted multiple times (registry and filesystem cleaned, even tried to rename the existing SnapInfo directory, ...), stopped all other services on the server but without any change... Every time when trying to run the configuration wizard, the debug log shows no errors, lists all Exchange information and ends with the following lines:[11/18 12:51:58 155] Exit CSmeCDOExm::GetExchangeStructureInternal 0x0
[11/18 12:51:58 155] Exit CNtapSnapMgr::GetExchangeStructure: 0x0
[11/18 12:51:58 233] Enter CSmeServerBase::~CSmeServerBase ...
[11/18 12:51:58 248] m_ptrSnapShot released
[11/18 12:51:58 248] m_pISnapShot4 released
[11/18 12:51:58 248] m_pISnapShot5 released
[11/18 12:51:58 248] m_pISnapShot6 released
[11/18 12:51:58 248] m_pISnapShot7 released
[11/18 12:51:58 248] m_pISnapShot8 released
[11/18 12:51:58 248] m_pISnapShot9 released I ended up uninstalling SME 7.1 and re-installed SME 7.0 which is working. Exchange Server: ESXi 5.5 VM, Windows Server 2012 R2 (with current patches), Exchange 2013 SP1 CU6 - no DAG, single server installation (in co-existence with Exchange 2010), 4 iSCSI LUNs created with Snapdrive (1x Log, 3x Store), System drive and Exchange installation drive on vmdk Disks (via ESXi -> NFS store on the same NetApp)NetApp: FAS 2240-2 with Data ONTAP 8.1.4P1 7-mode (with complete license bundle) Anyone else got this problem or even better - a solution?

We could not reproduce the error with the upgrade workflow.Looking at the error and the relevant function, we could force the problem in following conditions: -SME is configured or ran at the DAG level-one of the following services is stopped or not responding on one nodes of the DAG Snapdrive Service, Snapmanager Service, Snapdrive Storage Management Service,Snapdrive Management Service. Would be good if we could get the output of following powershell cmdlet before and after the upgrade: Get-Service –ComputerName Node1, Node2, Node3 –name Snap*, SDMGMT*, SWSvc Best regards,Dan

TLS connection failure with Exchange 2013 (SEC_E_WRONG_PRINCIPAL)

Hi all -
I have Lync 2013 with a single front-end server and am trying to properly integrate with a single Exchange 2013 SP1 server. The Exchange server has certificate signed by GeoTrust, assigned to all roles - IIS, SMTP, POP, IMAP, UM, and UMcallrouter. I'm
seeing the below in my FE logs and am unsure as to why Lync is using the .local address when I have been specifying external FQDNs for the mail server in Lync.
TLS outgoing connection failures.
Over the past 1 minutes, Lync Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090322(SEC_E_WRONG_PRINCIPAL) while trying to connect to the server "MAIL.xxxx.local" at address [172.16.3.14:5061],
and the display name in the peer certificate is "Unavailable".
Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate
root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
Resolution:
Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by DNS refer to
a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.
Any advice/pointers you can give are greatly appreciated.

When integrate Lync and Exchange UM, you need to generate new certificate. The certificate should contain the server’s FQDN.
Lisa Zheng
TechNet Community Support

Exchange 2013 CU7 - Frequent Outlook 2013 Disconnections and Delays

We currently have the following environment:
Windows 2012 VM on Hyper-V with 24GB of RAM and 4 virtual procs (1 socket)
Cisco UCS, B200 M3 Blades
Exchange 2013 CU7
Exchange 2007 is in our environment, but public folders have been removed and only a few stale, unused accounts exist on it.
Two dual-role CAS/Mailbox servers
Mailbox servers are in a DAG
MAPI/HTTP is our connection protocol
.NET Framework 4.5.2
Clients are Outlook 2013 SP1 on Windows 7 and 8.1
(Currently round robin DNS, but we have a hardware load balancer we've temporarily taken out of the mix to solve this problem)
What we're seeing is frequent disconnections from Exchange, regardless of the CAS server. That is, both CAS servers will disconnect clients, but not at the same time. When we look at the Exchange boxes, we notice that the CPU is 99% - 100% each time the
disconnections occur. When we hunt down the IISWorker process causing the sudden CPU run, we see it comes back to the following app pools:
MSExchangeMAPIFrontEndAppPool
MSExchangeMAPIMailboxAppPool
(We were running RPC/HTTP, but switched to MAPI/HTTP to resolve the problem. We had the same issue with equivalent RPC app pools at the time.)
Eventually, within a minute or two, the CPU load will decrease and the clients connected via that CAS will regain connection. As you can imagine, the pain is felt more frequently by uncached clients--although everyone, regardless of caching, will see
the disconnections.
Basically, the problem sounds exactly as shown in this KB: http://support.microsoft.com/kb/2995145 Unfortunately, we already had .NET 4.5.2 installed, and have changed the environment variable and registry as shown in the article.
We're in contact with Microsoft Support, but thus far they're scratching their heads.
I'm clearing up all small errors to decrease the noise in the application error logs, but the most persistent one is Event ID 106 (MSExchange Common):
"Performance counter updating error. Counter name is Time in Resource per second, category name is MSExchange Activity Context Resources. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance 'ad-powershell-defaultdomain'
already exists with a lifetime of Process. It cannot be recreated or reused until it has been removed or until the process using it has exited."
Loading/reloading and recreation of the performance counters does not fix the problem, by Microsoft Support or us. Of course, this error existed before we started having issues; I'd just like to clean it up just in case it's a contributing factor.
Has anyone seen anything similar?

We're using a Barracuda load balancer (641), but we've eliminated that as a source of the problem. The CPU spikes and disconnections happen whether or not the load balancer is in use.
This problem is still ongoing, and we're still working with Microsoft Support. Right now they're focused on our environment, but having combed through it numerous times, there's nothing that stands out. I suspect this is a bug in CU7 (yet I would
readily accept our environment being at fault if it means we can identify and resolve the problem), but that's not the road Support is going down.
We've looked at storage I/O on the VM hosts (disk responses are 10 MS or less), added double the CPUs to each mail server (for a total of 8, each), disabled TCP chimney offload, run numerous Experfwiz log collections, etc... Now
the tech is focused on a particular mailbox database being the culprit because it also takes up more CPU when the MAPI app pools are gunning pretty high. I suspect that it is a symptom and not the problem, but I have no choice but to follow his lead.
What is your environment like? Are you also CU7? And did the problem show itself after a cumulative update was applied?

Cisco IronPort with On Premise Exchange 2013

Similar Messages

Maybe you are looking for