Unified Messaging Exchange 2010 with Jabber

Is anyone aware of a way to have Jabber integrate with Exchange 2010 for voice-mail?
I have CUCM trunked to the server, the calls are going to the server and you can leave a voice mail and phone MWI lights up.
I have the voice-mail icon on the jabber client and when I press it, it goes to the voice mail box.
The issue is that it says its not connected, and when people leave a voice-mail, Jabber does not indicate you have a message.
We are running CUCM 9.1, CUPS 9.1, Jabber4W 9.7
Any input would be greatly appreciated.
Thanks
Phil

Jabber for windows 9.7; only supports VMREST voicemail access. The only option for this is unity connection 8.5 and above. Connection to Exchange 2010 form of unified messaging (voicemail service through exchange server alone) is not supported.
Please refer to the following link;
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97/JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97_chapter_01.html#JABW_RF_SEF029A0_00
On-Premises Servers for Cisco Jabber for Windows and Cisco Jabber for Mac
Cisco Jabber supports the following on-premises servers:
Cisco Unified Communications Manager version 8.0(1) or later
Cisco Unified Presence version 8.0(3) or later
Cisco Unity Connection version 8.5 or later

Similar Messages

BIS and Exchange 2010 with TMG

Dear all,
I stumped into this problem whereby my client has an Exchange 2010 with mixed-mode mobile users of Active Sync and BlackBerry.
They have this [url]https://mail.***.com.my[/url] as their OWA URL and credentials should be entered as:
Username: Domain\Username
Password: Password
This convention is the same irregardless users accessing from OWA or to setup Active Sync or BlackBerry.
Question are:
1. How do I setup BIS account on my BlackBerry? Method I use is log into my telco portal but the credentials I entered does not recognised by the system.
2. Alternatively, I tried to set it direct on my BlackBerry but was prompt the same error as above which is 'Username must be at least 4 characters'.
3. Does naming convention setup same for Active Sync users and BlackBerry users?
Any help would be greatly appreciated.

Hi and Welcome to the Forums!
rizauden wrote:
1. How do I setup BIS account on my BlackBerry? Method I use is log into my telco portal but the credentials I entered does not recognised by the system.
2. Alternatively, I tried to set it direct on my BlackBerry but was prompt the same error as above which is 'Username must be at least 4 characters'.
BIS itself is provided to you by your wireless service provider. With hundreds of different carriers in the world and dozens of different methods each, there's no way to be sure how to guide you with specifics. I suggest you ring them up and talk to them about how to enable BIS on your BB.
rizauden wrote:
3. Does naming convention setup same for Active Sync users and BlackBerry users?
I'm not sure how ActiveSync works, but the configuration instructions for OWA are here:
KB03133How to integrate a Microsoft Outlook Web Access email address with a BlackBerry Internet Service account
And here are some further helpful KBs on the topic:
KB15173Locate the mailbox name for a Microsoft Outlook Web Access 2007 email account
KB02858Unable
to integrate a Microsoft Outlook Web Access or IBM Lotus Domino Web
Access email address with a BlackBerry Internet Service account
KB04804Error message appears when attempting to integrate a Microsoft Outlook Web Access 5.5 or 2010 account
KB18567BlackBerry
Internet Service cannot connect to a Microsoft Outlook Web Access
account using Microsoft Exchange 2007 or Microsoft Exchange 2010
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

I can no longer log into my ichat linked to my gmail. right after opening up ichat, receive the following message: lost connection with jabber. the server has unexpectedly disconnected.

i can no longer log into my ichat linked to my gmail. right after opening up ichat, receive the following message: lost connection with jabber. the server has unexpectedly disconnected. how to troubleshoot? thanks.

Hi,
There can be many reasons why the Login is "up the creek".
Any break in the network at your end whilst logged in will cause an issue.
A sort of discrepancy between what iChat thinks the state should be and what the server thinks.
If they don't agree the server will refuse to accept.
A Crash at the server end which does not log you out properly will also do it.
Any file at any time can be come corrupted.
Luckily with the iChat .plists they are recreated if removed with an iChat Restart.
If it were AIM you can also get your Account Suspended and this will not log you in.
(It tends to happen from Chat rooms where people notify AIM about bad behaviour (as they see it) and you have to apply to get Un-suspended).
Most of the big IM services use multiple servers.
Sometimes these go out of Sync.
In the case of AIM this happens when they remove Old unused Screen Names from people's Buddy List prior to making them available for re-registration. I am not sure if this happens at Google.
You seem to be talking about an account that has worked at Work and having new computer at home.
As I mentioned the Priority thing you have not said that it has coincided with the new computer logging in (this will kick the work Computer out of Google whether you are logged in on the Web Mail page or in iChat)
IN addition to that iChat stays partially logged in for Off Line IMs
This is done in the background by a support app called iChatAgent
If your Computer is ON but ichat is not started people can still send you Messages.
Instead of saving these on the server until you login iChat will start up.
Depending if the home Mac is effecting the Work Login it may be holding sway over your Login.
Using your girlfriend's login may have booted her Off Line where she normally uses the name/login.
The AIM Side can be specifically set to allow Multiple Logins and therefore NOT allow them. If this happens you get a warning and messages to do something about it.
You do not get these in any Jabber or Google Login as the Priority setting is supposed to take care of it.
If the Login works at the Web Mail Login and on one computer then the .plist on the work computer is the most likely issue.
There is a small chance that a Corrupt Buddy Pic (Home Folder/Library/Caches/com.apple.iChat/Pictures) may be the cause.
Set this folder to icon view and also use the Finder's View Menu > Show View Options and select icon view.
This should show all pics as their icon.
Check that all display properly.
At this point I would try a COMBO version update install of the last Update you did over what you have.
This often corrects hard to trace things
The 10.5.8 COMBO is here
11:28 PM Monday; June 20, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.7)
 Mac OS X (10.6.7),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Cannot read message bodystructure from Exchange 2010 with IMAP

Hi,
I'm trying to read mails from MS Exchange 2010 that have multipart/mixed content type and contain only one text/html part. I'm using IMAP and the newest Javamail 1.4.3. The mail processing fails when trying to fetch the bodystructure. I can process the same message perfectly well from Exchange 2003:
BODYSTRUCTURE from Exchange Server 2003 (Works fine with javamail)
* 1 FETCH (BODYSTRUCTURE (("TEXT" "HTML" ("charset" "UTF-8") NIL NIL "7BIT" 242 5 NIL ("inline" NIL) NIL) "mixed" ("boundary" "----=_Part_28_1466852274.1263305065649") NIL NIL))BODYSTRUCTURE from Exchange Server 2010 (Does not obey specification, doesn't work with javamail)
* 1 FETCH (BODYSTRUCTURE ("multipart" "mixed" ("boundary" "----=_Part_1_1045289550.1263292469650") NIL NIL NIL 0 NIL NIL NIL NIL))Does anyone have same kind of problems? This seems to me like a bug in Exchange 2010, but does anyone know any work-around for this other than using POP3 that works with the same message?
Here's the message (slightly edited to protect the guilty):
Received: from XXX (10.1.2.152) by
YYY (10.1.3.154) with Microsoft SMTP Server id
14.0.639.21; Tue, 12 Jan 2010 12:34:29 +0200
From: "XXX@YYY" <XXX@YYY>
Reply-To: <XXX@YYY>
To: Receiver <XXXX@YYY>
Message-ID: <1765234390.11263292469652.JavaMail.XXX@YYY>
Subject: Phone order: Mobile phone for mobile employees
Content-Type: multipart/mixed;
 boundary="----=_Part_1_1045289550.1263292469650"
Return-Path: ZZZ@YYY
Date: Tue, 12 Jan 2010 12:34:29 +0200
X-MS-Exchange-Organization-AuthSource: XYZ
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
------=_Part_1_1045289550.1263292469650
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 I would like to order the following phone:
 Mobile phone for mobile employees
 
 
 Best regards,
 XXX@YYY
 
------=_Part_1_1045289550.1263292469650--Cheers,
Kai

Yup, looks like a bug in Exchange 2010, please report it to Microsoft.
If Microsoft gives you a bug ID or any way to track this bug, please let me know.
Try this workaround:
[http://java.sun.com/products/javamail/FAQ.html#imapserverbug|http://java.sun.com/products/javamail/FAQ.html#imapserverbug]

Installing / Upgrading Exchange 2013 to Exchange 2010 with a o365 Hybrid environment

Hi
I am trying to install a new server with Exchange 2013 on an environment with an existing Exchange 2010 Sp3. Reason for that is that I have a o365 hybrid environment and need to disconnect my on-line and on-premise e-mail connection. I want to completely
run all my mailboxes on o365 no-longer dependent on on-premise exchange but the Exchange 2010 doesn't have a functionality to 'dismantle' the hybrid.. we need to have exchange 2013.
When I try to install Exchange 2013 I get an error message that I need to upgrade my o365 tenant. : my o365 tenant version is : AdminDisplayVersion : 0.20 (15.1.49.12) :IsUpgradingOrganisation : False.
Is there a better way of updating my environment.
Regards

Post the error from setup log for more information.
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.

Outlook 2013 - Lost Ability to Send Text Messages - Exchange 2010

Hi Folks,
I have an exchange 2010 server that has been up and running for 3+ years. I use MS exchange and Outlook 2010/2013 for receiving and replying to text messages on an Android based phone.
Without upgrading or changing anything, this past week one of my Outlook 2013 clients lost the ability to send or reply to text messages. In Outlook under "Home:New Items" the "New Text Message" option was gone. The exchange account was
still receiving text messages that were sent to the phone. But when I hit reply it said account not setup.
I checked on another computer with an Outlook 2013 client, and it still had the option for "New Text Message". I contacted Outlook support, and they just wasted 45 minutes of my times and said they can't help because exchange was involved.
Now several days later, all my clients have lost the option of "New Text Message". It's not greyed out from the list, it's gone.
Thanks for the help!
Dave B

I recommend that you post this in the Outlook Forum: http://social.technet.microsoft.com/Forums/en-US/outlook/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

What is the best way to get activesync to work on Exchange 2010 with co-existing Exchange 2003?

I currently have all my mailboxes on my Exchange 2003 server and I introduced my first Exchange 2010 server into the same environment so they are running co-existent. The mailflow is functioning properly so now I need to test out the activesync. From
what I've read, you have to create a SSL certificate with SAN on the Exchange 2010 server and create a legacy.domain.com name to point to the Exchange 2003 server. Then replace out the existing SSL certificate on the Exchange 2003 server with the
new one that was created for the Exchange 2010 server. However, my question is that if this does not work could I easily revert back to the original settings where Exchange 2003 server is doing the activesync instead of Exchange 2010? That way
I would not disrupt activesync from working.

The legacy url is not important for activesync, but:
Enable Integrated Windows authentication on the Microsoft-Server-ActiveSync virtual directory on the
Exchange 2003 back-end server
http://technet.microsoft.com/en-us/library/ee332348(EXCHG.140).aspx
once you point your external url for active sync at your 2010 it should proxy the 2003 active sync

Exchange 2010 with Outlook 2007 Shared Contacts with Attachments

We have an Exchange 2010 server. There is only one Exchange server so all roles are on this server.
Found out that sharing contacts between users misses something.
If a user has Attachments or Notes in their contacts we can see via the Attachment column in Contacts that there are attachments.
But another user viewing the shared Contacts of the user above, cannot see if the Contacts have Attachments unless they open each one. The Attachment column states there are no Attachments. Is this how it is? Is it a syncing issue?
The image I have attached is what the user sees accessing a shared contact address book. It shows Notes and the Attachments columns. The contacts with partial words visible in the Notes column should have a Paper Clip Icon as they also have attached items.

Hi,
There is no related feature in Exchange server to manage Outlook view.
Additionally, I shared my Contact with another user in my Exchange 2010 SP3 with Outlook 2013 environment. And it showed the same results as yours. The attachments icon was not shown in the list view in another user’s Outlook but it appeared in my own Contact.
Thanks,
Winnie Liang
TechNet Community Support

Out of office sending out old messages - Exchange 2010 - Outlook 2007

Tracking down an issue of a user (I think it's only one) having their Out of Office Message always being a previous message from a year or two back. Doesn't matter if it's changed in Outlook 2007 or in OWA.
I've read some older post on this, but didn't find a clear answer.
This current Exchange 2010 setup is a migration from 2003. Could this be a leftover migration issue?
Anybody have this happen recently?

Hi,
How do you know this is an old reoccurring message? Based on the content or time?
Since the MailboxAutoReplyConfiguration is correct, I suspect the issue can occur by certain client machine. At this stage, I suggest you disable OOF and re-enable
OOF on the problematic machine. If the issue persists, please refer to the following article to clean the problematic client’s Outlook rules. (run Outlook.exe /cleanrules in Run console.)
http://www.tech-recipes.com/rx/2161/outlook_2007_clean_up_command_line_switches/
Thanks.
Novak Wu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
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.

Exchange 2010 with Forefront, can't receive large attachments from outside ONLY.

I am able to send and receive large files internally now. Also I am able to send large files to the outside. But I can't receive anything larger then defaulted 10mb. My Environment is 2 Edge boxes, 2 cas HT boxes, 2 mx DB boxes.
I was asked to increase the size of the emails my organization can receive, I went ahead and adjusted the following:
EDGE
1. Receive and Send connectors, set to 40mb.
2. Forefront -->Advanced Options--> Threshold Levels--> all max sized are at 50mb.
CASHT
1. Organization Configuration--> Hub Transport -->Send Connectors and GLOBAL SETTINGS
2. Server Configuration--> HUB Transport--> all the connectors
3. Recipient Configuration--> Mailbox --> users.
All sizes are set to 40mg!
I am able to send large files (24354K), but not able to receive
The following is output from Get-TransportConfig:
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 40 MB (41,943,040 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 40 MB (41,943,040 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo :
LegacyJournalingMigrationEnabled : False
MaxDumpsterSizePerDatabase : 60 MB (62,914,560 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : unlimited
MaxRecipientEnvelopeLimit : unlimited
MaxSendSize : unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
Rfc2231EncodingEnabled : False
ShadowHeartbeatRetryCount : 12
ShadowHeartbeatTimeoutInterval : 00:15:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowRedundancyEnabled : True
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Also my antispam cloud service sent me the following logs:
10:10:38.662 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: MAIL FROM:<[email protected]> SIZE=34140018
10:10:38.771 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 250 2.1.0 Sender OK
10:10:38.771 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY
10:10:38.896 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 250 2.1.5 Recipient OK
10:10:38.896 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: DATA
10:10:39.021 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 354 Start mail input; end with <CRLF>.<CRLF>
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
abort request
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
write failed. Error Code=socket aborted
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
[1959469085] failed to send. Error Code=socket aborted
AND
Also another error from Appriver:
08:48:34.798 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: MAIL FROM:<[email protected]> SIZE=34148430
08:48:34.907 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 250 2.1.0 Sender OK
08:48:34.907 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY
08:48:35.032 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 250 2.1.5 Recipient OK
08:48:35.032 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: DATA
08:48:35.157 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 354 Start mail input; end with <CRLF>.<CRLF>
08:53:34.718 3 SMTP-929371(workemail.com.smtpip.com:25)
write failed. Error Code=connection reset by peer
08:53:34.718 3 SMTP-929371(workemail.com.smtpip.com:25)
[1959495450] failed to send. Error Code=connection reset by peer
I am out of options here, wondering if anyone know's anything about this?
Vladimir

Cara,
Yes I have looked at smtp receive protocol logs, below is a log from one failed transmission, I don't see anything that jumps out at me:
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,MAIL FROM:<[email protected]> SIZE=24042643,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,08D0340D4EB7692B;2013-06-10T18:41:06.863Z;1,receiving message
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:06
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.0 Sender OK,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
+,,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:07
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
+,,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:07
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,,Ignored X-OriginatorOrg header value 'outside.com' because session capabilities do no
2013-06-10T18:41:07.457Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,,Ignored X-OriginatorOrg header value 'outside.com' because session capabilities do no
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,+,,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeader
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,<,EHLO YPICASHT1.YPI.com,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-SIZE 42949632,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-PIPELINING,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-DSN,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-STARTTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-AUTH,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-X-EXPS NTLM,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-8BITMIME,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-BINARYMIME,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-CHUNKING,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-XEXCH50,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250 XSHADOW,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,<,X-ANONYMOUSTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,220 2.0.0 SMTP server ready,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Sending certificate
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CN=YPIEDGE1,Certificate subject
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CN=YPIEDGE1,Certificate issuer name
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,7CERT#,Certificate serial number
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CERT,Certificate thumbprint
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,YPIEDGE1;YPIEDGE1.edge.local,Certificate alternate names
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Received certificate
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CERT,Certificate thumbprint
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Received DirectTrust certificate
Vladimir

Load Balancing Exchange 2010 with Citrix Netscaler

Hi All,
I have two exchange multirole server(cas/ht/mb) EXCH1 and EXCH2 both are configured in DAG (dag1.example.com) and also both are configured with CAS array (casarray.example.com)
We have Cirtix Netscaller hardware load balancer. I have to configure Load balancing for CAS array, ActiveSync, OWA, Outlook Anywhere.
Please guide me through the configuration for citrix netscaler as i am new with Citrix Netscaler.
Regards,
Pravin

Hi,
In order to resolve this issue more efficiently, I recommend you contact support from Citrix, you might get a better answer there. Thanks for your understanding.
https://www.citrix.com/community.html
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Personalize email disclaimer in exchange 2010 with alias?

Hello all,I would like to notify everyone in my email disclaimer that our email domain will be changing. I need the old email and the new email address for this. I can use %%Email%% but is there a way I can use the alias alone?
I think it can't be done unless I make a custom attribute or something or am I missing something?
some more info here: technet.microsoft.com/en-us/library/bb124352(v=exchg.141).aspx#ADAttributes (this is a link but I am not allowed to post it)
Thanks in advance!

Hi,
According to your description, I am not quite sure about your requirement. Could you please provide more information about your issue, such as why do you want to use %%Email%% or alias to filter the disclaimer as a condition?
Generally, if you want to notify everyone that the email domain will be changing by using email disclaimer. We can add a disclaimer to all domain messages by a transport rule. For example, the following rule can add “Our email domain will be changing” at
the start of the newest e-mail message for all messages which are sent and received inside the organization:
If you just want to add this disclaimer in a specific user’s message, we can do the following:
Apply this rule if…
The sender is Administrator,
Do the following…
Append disclaimer text and fallback to action if unable to appy…
Regards,
Winnie Liang
TechNet Community Support

Cisco 5 with Exchange 2010 and Database Availability Groups

Hi,
Unity 5 was installed a long time. Recently installed with the latest ES88 to the system. The fact is we have Exchange 2007 (clustered) mailbox server in the network environment, and introduced the Exchange 2010 (with DAG activated).
So far we didn't do any "re-partnering" from the Exchange 2007 to Exchange 2010. The end users are working fine by leaving voice message and can retreive their voice without too much issue, no matter where the End Users account are located, Exchange 2007 or Exchange 2010.
But lately, there was some actions taken in the Exchange environment. Some Exchange 2010 mailstore databases in one of the Exchange 2010 server, with DAG has been activated.
In this case, we are now unable to leave any voice messages to the end usrs. All the voice messages are now being held in C:\CommServer\UnityMTA.
Want to ask, does Unity 5 and Exchange 2010 compatible with DAG? Also, is that my problem is caused by re-partnering server not taken place? If yes, which Exchange 2010 mailbox database server I should point to? Reason is, there will have 3 physical servers, and with several DB mailstore, if I select one of the physical server, and one of the D mailstore, will this be affected when the DAG is activated?
Thanks
Timothy

Hi Yancy,
If you're referring to integrating Microsoft Exchange 2010 with Cisco Unified Communications Manager (CUCM) 5.x for voicemail purposes, via a SIP Trunk, then you could certainly have a go at it (a Media Termination Point would be required and the codec would be G.711). However, I'm not aware of anyone having properly tested it with CUCM 5.x; given that it's not having software maintenance releases written for it anymore. CUCM 5.0 stopped having software maintenance releases written for it in June 2009, and CUCM 5.1 in February this year.
The following Tech Tip is likely to assist:
https://supportforums.cisco.com/docs/DOC-12544
Kind regards,
Craig

Exchange 2007 and 2010 with Unity Connection 8.6

Hi all,
We have unity connection 8.6 and exchange 2007 currently in place and runnign fine. I am ready to start migrating mailboxes over to our new exchange 2010 farm and as such we will be in co-exsistance with exchange 2007 and 2010 for awhile. What are the steps or procdures to also include exchange 2010 with the 2007 in unity connections? Currently under Smart Host is the IP address of our exchange 2007 server.
Thank you.

Hi,
This depends on how you plan on performing the migration. I would suggest the following:
-Creating a new unified messaging service for Exch 2010. You can re-use the same service account name as long as you completed the configuration steps for that integration.
-As you move over user's mailboxes from 2007 to 2010, you can delete the 2007 UM service and add the new 2010 UM service. If you want to change many users at a time you'll need to use bulk administration to change them. If you use BAT to change accounts, see the link below where I have listed them out for another CSC user.
-You can change the Smart Host setting once you have configured the Exch 2010 enviornment to handle your main corporate mail (changing the MX records to point to a 2010 Edge Transport).
Changing the UM service with BAT:
https://supportforums.cisco.com/message/3572200#3572200
Good luck.

Exchange 2010 SP3 OWA with certificate based authentication

Hi,
I have a bizarre problem in my customer’s environment. Maybe someone has an idea.
Exchange 2010 with SP3, latest cumulative Update installed.
The problem I’m having is that when I enable Certificate based authentication (require client certificate option in IIS) on OWA and ECP virtual directories in conjunction with forms based authentication (this is the requirement – the user
must have a client certificate and type in username and password to log in to OWA), the result is that after the user selects the certificate he wants to use, he is logged into OWA automatically, but cannot use the website, because it’s being constantly automatically
refreshed (or redirected to itself or something like that). The behavior occurs with all users, with any browser. If client certificate is on required, forms based authentication works just fine. If I switch to “Basic Authentication” and enable client certificate
requirement, then OWA act’s as it should be – so no problems. The problem only occurs when authentication type is forms based and client certificates are required.
I have tried the exact same settings (as far as I can tell) on one other production server and one test server, and encountered no such problems.
Anyone – any ideas?

Hi McWax,
According to your description and test, I understand that all accounts cannot login OWA when select require client certificate.
Is there any error message when open OWA or login? For example, return error ”HTTP error: 403 - Forbidden”. Please post relative error for further troubleshooting.
I want to confirm which authentication methods are used for OWA, Integrated Windows authentication or Digest authentication? More details about it, for your reference:
http://technet.microsoft.com/en-us/library/bb430796(v=exchg.141).aspx
If you select another authentication method, please check whether Client Certificate Mapping Authentication services is installed, and also enabled in IIS, please refer to:
http://www.iis.net/configreference/system.webserver/security/authentication/clientcertificatemappingauthentication
To prevent firewall factor, please try to sign in OWA at CAS server. Besides, I find a FAQ about certificate:
http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
Best Regards,
Allen Wang

Unified Messaging Exchange 2010 with Jabber

Similar Messages

Maybe you are looking for