WAAS secured_client detected

Unanswered Question
Sep 19th, 2008

why is the above error regarded as a major error? when it is an information message only.

It means there is a secured mapi client detected

also I cannot find the release notes for WAAS 4.1.1a.10 I take it there are some fixes not in

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
dstolt Fri, 09/19/2008 - 03:26

The release notes for 4.1.1a10 are included in the general 4.1.1 notes. See http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v411/release/notes/ws411rn.html

I took a look at that alarm and it is documented that it is a major level. If you have MAPI enabled, the product is telling you it cannot accelerate these clients. So do you have some of your clients encrypted and some not? If this is common and it continues to cause the alarm to show, I'm sure we can submit a request to make the alarm informational only.


Brian Cartledge Tue, 09/23/2008 - 05:27

Hi there,

I'm also seeing this alarm in 4.1.1a at a few of our sites. I'm told that we aren't using encryption for our email clients, but we are piloting Microsoft Office Communicator.



Zach Seils Tue, 09/23/2008 - 08:22


What version email clients are you using?

The alarm is generated by EPM, so it could come from any MS-RPC based communication.


Zach Seils Wed, 09/24/2008 - 05:38

My understanding is that Outlook 2007 uses encryption by default. Has that been explicitly disabled in your environment?



Brian Cartledge Wed, 09/24/2008 - 05:51

Yes, encryption is disabled at the client and server end.

Is there a way to view the IP of the client causing the alarm?



jwisman Wed, 09/24/2008 - 15:27

Yes the syslogs tell you which IP. Do WAAS support any way to accelerate the traffic or is the only way to disable the encryption? Soon all our clients will be encrypted becuase of outlook 2007

Zach Seils Fri, 09/26/2008 - 20:22

In the 4.1.1 release encrypted traffic is not handled by the MAPI AO. We are working on support for encrypted MAPI in a future release.


Brian Cartledge Mon, 10/06/2008 - 02:05

FYI, the "client" causing the encryption connection error is our Unity voicemail server.




This Discussion