Unity Connection 8.5 Exchange 2010

Does the exchange server need to be in the same location as the Unity Connection 8.5 server for single inbox to work?

In the single inbox design guide here....
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg032.html
Calculating the Number of Connections for a Connection Cluster
If both Connection servers in a cluster are in the same location, so they have the same latency when synchronizing with Exchange, you can calculate the number of connections the same way you do for one Connection server.
If one server in a cluster is collocated with the Exchange servers and the other is in a remote location:
•Install the publisher server in the location with the Exchange servers. The publisher server should always be the primary server unless the server is offline for maintenance or is unavailable for some other reason.
Also here in this guide....
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp459928
Unified Messaging Requirements: Synchronizing Connection and Exchange Mailboxes (Single Inbox) (Connection 8.5 and Later Only)
Revised February 22, 2011
•Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:
–Exchange Server 2010 with Update Rollup 3 or later (All editions are supported.)
–Exchange Server 2010 with Service Pack 1 (All editions are supported.)
–Exchange Server 2007 with Service Pack 2 or later (All editions are supported.)
To synchronize Connection and Exchange 2007 mailboxes, you must install Connection 8.5(1) Service Update 1 (SU1), which is available on the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.
In the tree control on the Downloads page, expand Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity Connection > Cisco Unity Connection Version 8.5. On the Select a Release page, select SU1, and the download buttons appear on the right side of the page.
–Exchange Server 2003 with Service Pack 2 (All editions are supported.)
To synchronize Connection and Exchange 2003 mailboxes, you must install Connection 8.5(1) Service Update 1 (SU1). For download instructions, see the previous bullet.
Microsoft Business Productivity Online Suite is not supported.
•Exchange servers and Active Directory domain controllers/global catalog servers (DC/GCs) can be installed in any hardware virtualization environment supported by Microsoft. (Cisco does not provide technical support for message-store servers or for DC/GCs.)
•The Microsoft Exchange message store can be stored in any storage area network configuration supported by Microsoft. (Cisco does not provide technical support for message-store servers.)
•Exchange clusters are supported.
•To access Exchange servers in more than one forest, you must create at least one unified messaging service for each forest. Connection supports a maximum of 20 unified messaging services per Connection server.
•Depending on the number of voice messaging ports on each Connection server, the path of connectivity must have the following guaranteed bandwidth with no steady-state congestion:
–For 50 voice messaging ports on each server—7 Mbps
–For 100 voice messaging ports on each server—14 Mbps
–For 150 voice messaging ports on each server—21 Mbps
–For 200 voice messaging ports on each server—28 Mbps
–For 250 voice messaging ports on each server—35 Mbps
The bandwidth numbers above are intended as guidelines to ensure proper operation of mailbox synchronization. For information on bandwidth requirements for Connection clusters, see the "Requirements for a Cisco Unity Connection 8.x Cluster" section. Additional conditions such as network congestion, CPU utilization, and message size may contribute to lower throughput than expected. Call-control and call-quality requirements are in addition to the guidelines above and should be calculated by using the bandwidth recommendations in the applicable Cisco Unified Communications SRND at http://www.cisco.com/en/US/partner/solutions/ns340/ns414/ns742/ns818/landing_uc_mgr.html.
•The default Connection configuration is sufficient for a maximum of 2000 users and 80 milliseconds of round-trip latency between Connection and Exchange servers. For more than 2000 users and/or more than 80 milliseconds of latency, you can change the default configuration. For more information, see the " Latency" section in the "Single Inbox in Cisco Unity Connection 8.5 and Later" chapter of the Design Guide for Cisco Unity Connection Release 8.x. at http://www.cisco.com/en/US/partner/docs/voice_ip_comm/connection/8x/design/guide/8xcucdgx.html.
•Users must be assigned to a class of service that is enabled for using single inbox.
•For each user configured for single inbox, an email client that is configured to access the user's Exchange mailbox. For full single-inbox functionality, we recommend that you use Microsoft Outlook and install Cisco ViewMail for Microsoft Outlook. ViewMail for Outlook is required to:
–Review secure Connection voice messages by using Outlook.
–Compose, reply to, or forward synchronized voice messages by using Outlook.
Other email clients can be used to access Connection voice messages in Exchange, but users will not have the functionality provided by ViewMail for Outlook.
For information on Connection support for Outlook, see the "Requirements for Accessing Voice Messages by Using Cisco ViewMail for Microsoft Outlook 8.5 and Later" section.
•For users who are configured for single inbox and SpeechView transcriptions, the message in Exchange is not updated with the transcribed text. You can configure Connection to send a notification message that contains the transcription.
•When message expiration and single inbox are configured, the .wav file is not deleted from the message in Exchange. Voice messages in Connection are still removed from user mailboxes and are replaced with a recording that tells the user "This message is expired."
Specifically teh bandwidth requirements. Typically it's always best to have Exchange as close as possible to the CUC servers for performance to be ideal but this should give you some guidelines.
Tray

Similar Messages

Outlook 2010/2013 clients, outside of our main office, can't connect to our Exchange 2010 server

Hi,
Our remote users had been connecting to our Exchange server at our office since the Exchange server was installed in 2011.
Starting last Wednesday, Outlook 2010/2013 clients, outside of our main office, can't connect to our Exchange 2010 server. Outlook kept asking for a username and a password. At the same time, entries of Event 4625 were generated on the Event
log on out Exchange server.
Events 4625 has the following properties, "Logon Type: 3", "Failure Reason: An Error occured during Logon.", "Status: 0xc000006d", "Logon Process: NtLmSsp", and "Authentication Package: NTLM".
By the way, I had used a laptop to test this problem. Its Outlook work fine ion the main office, but it won't work outside of our office.
Does anyone have any idea?
Thanks.
Johnnie :(
Johnnie

http://blogs.technet.com/b/rmilne/archive/2015/03/17/update-015_2d00_027-revised-_2800_3002657_2900_.aspx
For additional people reading this thread, please update to v2 of that update.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Unity 5.01 and Exchange 2010

Hi,
I know the update/ES patch for Exchange 2010 support is coming out later from other postings I've read, etc. But I've had a client replace their Exchange 2007 with a Exchange 2010 server and move all the mailboxes over to the new 2010 server. I didn't know about this, was done on their own.
Now after breaking the news to them, they want to bring the old Exchange 2007 server back online and have it connect to the users on 2010 server.
Is this possible for time being, or what is the best way out of this situation until Unity has Exchange 2010 support?
Should I have them move all the mailboxes back to the old exchange server?
Thanks, Erick

There are apparently some big changes to the MAPI client in Exchange 2010 which is what Unity uses to communicate with Exchange. So, I can't say whether trying to use Exchange 2007 as a bridgehead to the Exchange 2010 environment will work or not as far as Unity is concerned. In either case, if you have issues you're highly unlikely to receive support from Cisco as this is still currently unsupported.
Hailey
Please rate helpful posts!

Outlook 2013 client, not in domain, can't connect to the Exchange 2010 server

Good Aftermoon,
Having issues it seems getting to the right forum but here is what I have. Currently we are running an Exchange 2010 server. OWA is configured and I am not having any issues with people connecting through it. The issue I am having is that any user that tries
to connect through Outlook 2013 gets an error message about the proxy server and then a certificate error. I have run the tests through the toolbox and get the following results.
Attempting to test potential Autodiscover URL https://autodiscover.westmoreland-county.org:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 694 ms.
Test Steps
Attempting to resolve the host name autodiscover.westmoreland-county.org in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 69.89.25.150
Elapsed Time: 284 ms.
Testing TCP port 443 on host autodiscover.westmoreland-county.org to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 164 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 245 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.westmoreland-county.org on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=*.bluehost.com, OU=PositiveSSL Wildcard, OU=Domain Control Validated, Issuer: CN=PositiveSSL CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
Elapsed Time: 201 ms.
Validating the certificate name.
Certificate name validation failed.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_ctl02_ctl01_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Host name autodiscover.westmoreland-county.org doesn't match any name found on the server certificate CN=*.bluehost.com, OU=PositiveSSL Wildcard, OU=Domain Control Validated.
Elapsed Time: 1 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Elapsed Time: 234 ms.
Test Steps
Attempting to resolve the host name autodiscover.westmoreland-county.org in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 69.89.25.150
Elapsed Time: 14 ms.
Testing TCP port 80 on host autodiscover.westmoreland-county.org to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 83 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.westmoreland-county.org for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
Additional Details
The URL specified in the location HTTP header was not HTTPS. URL: http://autodiscover.bluehost.com/Autodiscover/Autodiscover.xml
HTTP Response Headers:
Keep-Alive: timeout=10, max=500
Connection: Keep-Alive
Content-Length: 356
Content-Type: text/html; charset=iso-8859-1
Date: Wed, 03 Dec 2014 18:10:08 GMT
Location: http://autodiscover.bluehost.com/Autodiscover/Autodiscover.xml
Server: Apache
Elapsed Time: 135 ms.
Our setup currently our domain is being hosted and the web master has control of domain settings.
I am fairly new to the Excchange Server world so any suggestions that you may have as to how I can resolve this would be great.
Bill

Hi Bill
Thank you for your pos.
You can use the following command to check whether you have purchased the certificate of audiscovery.westmoreload-country.org in your organization:
Get-ExchangeCertificate –server CASServerName | fl
For example: you want to return all certificates stored on the Client Access server named ClientAccess01, you will type the follow command in EMS.
Get-ExchangeCertificate -Server ClientAccess01 | fl
If you didn’t purchased the certificate of audiscovery.westmoreload-country.org, you could contact your certificate supplier.
You could refer to the following link:
https://support.microsoft.com/kb/940726?wa=wsignin1.0
If there are any questions regarding this issue, please be free to let me know.
Best regard,
Jim

Cannot send email via ActiveSync when user connect from Internet (Exchange 2010 SP3 RU5)

Hi All.
This is the first time I encounter this kind of issue, whenever user connect from the internet they cannot send email from their Phone or Windows Mail App, but they can retrieve email
But when they connect from Internal Network they can send email. I already test ActiveSync from internet using www.testexchangeconnectivity.com and it pass all tests.
I also check the Firewall and all the necessary ports already opened (we even open all ports) , the default TTL on the firewall 3600 second.
From what I read ActiveSync use some kind of HTTP POST or in MS terminology "PING" command, but still have no idea what kind of configuration that should be made to the Firewall so it can pass this "PING" command. Because from what I
see in Android Logcat the problem always related to this PING command
10-07 08:12:38.714 I/Exchange(31971): Interrupt with reason 1
10-07 08:12:38.714 I/Exchange(31971): Ping task ending with status: -1
10-07 08:12:38.904 D/Exchange(31971): created outputstream
10-07 08:12:39.204 W/Exchange(31971): IOException sending mail
10-07 08:12:39.204 E/Exchange(31971): Generic error for operation SendMail: status 200, result -100
10-07 08:12:39.204 W/Exchange(31971): Aborting outbox sync for error -99
10-07 08:12:39.274 I/Exchange(31971): Ping task starting for 3
10-07 08:12:39.304 D/SyncManager(644): failed sync operation [email protected] u0 (com.android.exchange), com.android.email.provider, USER, latestRunTime 71219435, EXPEDITED, reason: 10040, SyncResult: stats [ numIoExceptions: 1]
10-07 08:12:39.304 D/SyncManager(644): not retrying sync operation because SYNC_EXTRAS_DO_NOT_RETRY was specified [email protected] u0 (com.android.exchange), com.android.email.provider, USER, latestRunTime 71220078, EXPEDITED, reason: 10040

Hi ronaldosy,
How about the work flow of Outlook or OWA on PC internally/externally?
If only phone has this issue, I suggest ask ActiveSync Forum for help so that you can get more professional suggestions. For your convenience:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobility
Best Regards,
Allen Wang

Unity 5.0(1) with Exchange 2010

According to the following link, Unity 5.0 supports Exchange 2010 as the partner Exchange server.
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html#wp47622
However, when I get to step 14 of this document (installing ExchangeMapiCdo.exe) I get an error saying it can't be installed with this version of Exchange.
I was just wondering if anyone elsel had tried to run Exchange 2010 with Unity 5.0 and if so, how you were able to get it to work. I followed all the steps in this document and everything seemed to be working until this step.

3 things:
1) You should get a TAC case going, if you haven't already.
2) For Unity 5x, ES83 was replaced by ES85 (which was yanked off the download site almost like a ghost in the night) and now there is ES86. You may want to read up on what is fixed here in this ES.
3) I think you may have your service account mailboxes homed in the wrong place. If you note there, is a section for where to put the mailbox for the UnityMsgStoreSvc. Excerpts I'm looking at are:
Adding One or More Exchange 2010 Servers to an Existing Cisco Unity 7.0 and/or 5.0 Installation
Step 14 On the Cisco Unity server, install ExchangeMapiCdo.exe, which you downloaded in Step 4.
Step 15 On the Cisco Unity server, install the version of the Permissions wizard that you downloaded in Step 2.
Step 16 Run the Permissions wizard, and select the Exchange 2010 message stores in which mailboxes for Cisco Unity subscribers will be homed.
Step 17 At the end of the Permissions wizard, on the You Have Completed the Cisco Unity Permissions Wizard page, click Granting Microsoft Exchange Administrator Rights, and do the procedure in the Help file to add the installation and directory services accounts to the Exchange 2010 Organization Management role group.
Step 18 Restart the Cisco Unity server.
Step 19 Move or create a mailbox for the Cisco Unity message store services account (typically UnityMsgStoreSvc), as applicable:
Exchange 2003 or Exchange 2007
mailbox already exists
Move the mailbox for the account to Exchange 2010.
No mailbox
Create a mailbox for the account in Exchange 2010.
Step 20 Remove the Exchange 2010 RPC limit for the message store services account by creating and applying a new mailbox policy to the message store services account:
a. Open an Exchange 2010 Management Shell window.
b. Create a new policy with unlimited RPC connections, for example:
new-throttlingpolicy -name "Unity Exchange 2010 Policy" -RCAMaxConcurrency $null
c. Apply the new policy to the message store services account, for example:
set-mailbox -identity "UnityMsgStoreSvc" -throttlingpolicy "Unity Exchange 2010 Policy"
d. Confirm that the mailbox is using the new policy, for example:
get-mailbox -identity "UnityMsgStoreSvc" | fl | findstr "Throttling Policy"
e. If you have more than one Cisco Unity server: Repeat Step c and Step d for every message store services account in the forest.
We recommend that you apply the policy to all message store service accounts, even the accounts for Cisco Unity servers for which you do not currently intend to home subscriber mailboxes in Exchange 2010 message stores. Applying the policy does not affect Cisco Unity performance, and it ensures that you will not encounter problems if you later move mailboxes to an Exchange 2010 server.
f. On each Exchange 2010 server with the CAS role, restart the Microsoft Exchange RPC Client Access service.
Personally, I would make sure you have all of these items down to a tee because, IMO, there is likely something that went astray in the install/backout/fix process.
Hailely

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Cannot connect my exchange 2010 from outlook outside of my LAN

I have problem connecting to my exchange 2010 server from outside of my LAN.
I have configured Outlook Anywhere and its working.
After i enter all the details it is asking again for password and once i entered the password i receive the error "The action cannot be completed. The Connection to Microsoft Exchange is unavailable etc ... "
Kindly suggest

Hi Angela,
Thanks for the support, kindly check the requested.
[PS] C:\Windows\system32>Get-ExchangeCertificate |fl
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule}
CertificateDomains : {autodiscover.mydomain.com, mydomain.com}
HasPrivateKey : True
IsSelfSigned : False
Issuer : CN=StartCom Class 1 Primary Intermediate Server CA, OU=Secure Digital Certificate Signing, O=Start
Com Ltd., C=IL
NotAfter : 2/25/2015 3:41:54 AM
NotBefore : 2/24/2014 9:47:31 AM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : 0EB79F
Services : IIS
Status : Valid
Subject : [email protected], CN=autodiscover.mydomain.com, C=KW, Description=vlkZ61QVKE36hUW5
Thumbprint : 2687AAECFD7C53DA14DDEB421D547B42A33E67BA
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule}
CertificateDomains : {*.mydomain.com}
HasPrivateKey : True
IsSelfSigned : True
Issuer : C=KW, S=Kuwait, L=Kuwait, O=mydomain.com, OU=IT, CN=*.mydomain.com
NotAfter : 2/11/2015 3:58:45 PM
NotBefore : 2/11/2014 3:38:45 PM
PublicKeySize : 2048
RootCAType : None
SerialNumber : 6DFCB427D57AE58746B5DF8B070E6455
Services : None
Status : Valid
Subject : C=KW, S=Kuwait, L=Kuwait, O=mydomain.com, OU=IT, CN=*.mydomain.com
Thumbprint : 4A90303EBFA71BB73928E9BFB9FD5D129EEC9270
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcc
essRule}
CertificateDomains : {exchange, exchange.mydomain.com}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=exchange
NotAfter : 2/11/2019 6:30:52 AM
NotBefore : 2/11/2014 6:30:52 AM
PublicKeySize : 2048
RootCAType : None
SerialNumber : 7BBA32A69E5DC2B2404406700225B006
Services : IMAP, POP, SMTP
Status : Valid
Subject : CN=exchange
Thumbprint : 565B3D127A98DB2D25FAE71864E58B427F17FC3C
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {WMSvc-EXCHANGE}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=WMSvc-EXCHANGE
NotAfter : 2/8/2024 3:44:28 PM
NotBefore : 2/10/2014 3:44:28 PM
PublicKeySize : 2048
RootCAType : Registry
SerialNumber : 168EC4DED2C01B874C8BD6F16E231229
Services : None
Status : Valid
Subject : CN=WMSvc-EXCHANGE
Thumbprint : 736EF13159F0F851EFCC20709C00AE60D5A54C94
Thanks

Mail 4.4 and Exchange 2010: not staying connected

I am using Mail 4.4 connected to an Exchange 2010 account, and with an SMTP server instead of the actual Exchange connection to send outgoing mail due to the "no from: field" issue.
I have noticed that Mail is not staying connected to the server. IIRC, Exchange is intended to be a live connection, and messages that arrived quite some time ago are nowhere to be seen until I click "Get Mail." Up to now, I've relied on IMAP with IDLE for mail, as I'd rather receive everything in real time instead of relying on a scheduled polling interval.
Why is this? Is it just an issue of being Exchange 2010 instead of Exchange 2007, or is there something I can do to fix it?
My iPhone running iOS 4.2 works perfectly with the same Exchange account.

IMAP with IDLE for mail, as I'd rather receive everything in real time
Certainly in the current version of Mail, you'll get more of a push effect if you use IMAP IDLE instead of EWS for communication with an Exchange server. Exchange Web Services feel less responsive.
The Get Mail routine is much quicker with IMAP IDLE than with EWS. With EWS: the more mailboxes you have, the longer it takes.
However: if you use IMAP instead of EWS, some features of Exchange will appear less graceful. Noticeable with e.g. messages relating to calendaring.
(Note to self: I should review this after our organisation has completed its transition from Exchange Server 2003 to Exchange Server 2010.)
messages that arrived quite some time ago are nowhere to be seen until I click "Get Mail."
Using EWS: in the absence of a real-time/push effect, three approaches come to mind:
a) pull manually (click Get Mail)
b) prefer a schedule
c) simply move or delete any message to trigger an update of that mailbox.
For my Inbox, I prefer (c). An update of the Inbox alone is much faster than the (Get Mail) update of all mailboxes.
Eventually, I guess that Apple will improve Mail to make it respond immediately to changes on the EWS side.
Then, I'll go back to using e.g. GrowlMail to weed most messages immediately, as each one appears (much more pleasing than ploughing through a massive Inbox).

SAP Groupware Connector 5.0 Installation - Connect MS Exchange 2010

I try to install the SAP Groupware Connector 5.0 to connect a MS Exchange 2010 Server.
My host computer has an MS Windows Server 2008 operation system.
After starting the setup.exe and fill in the entries Exchange Server, Mailbox, User, Domain, Password I Get an error message:
"Validation of connection to Exchange Server failed"
"CDO library is not available."
"[0x80040154] Class not registered"
I am the opinion that I don't need a CDO, because I am useing a MS Exchange 2010 Server ....
Can somebody help me?!
Thanks

Hi Chrisitan,
Perhpas I wan'st clear in my previous reply. You cannot connect Groupware connector 5.0 to MS Exchange 2010 Server.
I've just checked, and found that exchange 2007 is now supported, but not 2010.Further information is available from the following link:
[http://help.sap.com/saphelp_crm70/helpdata/en/44/559f3699d908fae10000000a422035/frameset.htm]
Sorry I can't give a different answer....
Brian.

Outlook 2013 cannot connect to Exchange 2010 SP2 server, Outlook 2010, OWA work fine. Ideas?

After upgrading a laptop from Outlook 2010 to 2013 it can no longer connect to our Exchange 2010 SP2 environment. OWA works, Outlook 2010 works, but Outlook 2013 will not create a profile via AutoDiscover. The first two checks go, the last check
Log On To server will not.
We can take the laptop to a different network and it works fine with Outlook 2013.
What is different with Outlook 2013 where it will not connect.
Jason Meyer

Does it work when we recreate a new Outlook profile?
At this point, We high recommand that we run Microsoft Connectivity Analyzer Tool from the folloing link to check what was happening
https://testconnectivity.microsoft.com/
Cheers,
Tony Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact
[email protected]

Exchange 2013 CAS server connection to Exchange 2010 Mailbox server

Hi Guys,
I have a quick question i am planning to upgrade my infra from Exchange 2010 to Exchange 2013 and i have come across a small question, my infra looks likes below
3 Exchange server (CAS+ HT + MBX roles) Exchange 2010
1 Exchange server MBX role For journlaing Exchange 2010
1 CAS for internet owa access Exchange 2010
Now i will be installing exchange 2013 CAS on 2 box and MBX on 3 box
will decomm the 3 exchange box which has (CAS+ HT + MBX roles) and 1 CAS which we use for owa access.
will keep the Journaling server as it is will not be decomming it as of now.
My question is is will i be able to connect to the journaling mailbox's which are hosted on exchange 2010 journaling server without actually having any 2010 cas server, will exchange 2013 cas directly help me to connect to the journal mailbox or would i need
to add CAS role on Exchange 2010 journaling server and enable outlook anywhere configure the directories with the url's to make it working.
Please suggest on the same.
BR/Deepak

Hi TheLearner,
Thank you for your question.
Exchange 2013 didn’t connect to the journal mailbox directly when we access it by outlook/OWA. The journal mailbox will connect the former Exchange 2010 CAS. Or we could migrate Journaling mailbox to Exchange 2013. Because Exchange 2010 could communicate
with Exchange 2010 by RPC, but Exchange 2013 could communicate with Exchange 2013 by HTTPS.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Unity 5 with Exchange 2007 - adding Exchange 2010

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
We will be adding and Exchange 2010 server to the existing Exchange environment and then migratomg user mailboxes to the new 2010 server. My question is, does the mere presence of the Exchange 2010 server require me to update Unity with ES patches, or can I wait until I am ready to start migration mailboxes?
I would like to do this in steps:
1. Add Exchange 2010 to the existing Exchange group, without moving mailboxes.
2. Updated Unity to support 2010
3. Migrate a few mailboxes and test
4. After testing move all mailboxes.
5. Change the Partner server to Exchange 2010.
From all the reading I've done, it seems like this should not be a problem, but I am not 100% sure.
Thanks!

Hi -
I have previous experience doing the exact same procedure you described, in test and in production. Only when you move a Unity subscriber mailbox to Exchange 2010 do you have to have Unity running the ES for 2010. I recommend testing just basic email routing between two test mailboxes, one on Exchange 2010 and the other on 2007 before moving forward with Unity. Applying the ES to Unity is straight forward. Changing the partner server to Exchange 2010 is the more complex part, in that you have to replace ESM on Unity with exchangemapicdo. Follow Cisco's document to the letter and also make sure the exchangemapicdo version is the same on Unity as on Exchange. There are a few forum trains here that will help (relates to issues with MWI).
Sincerely, Ginger

Windows 8.1 Mail app and Exchange 2010 EAS partnership - "Make Windows user account an Administrator" to meet security requirements?

As the title says, I have a new Windows 8.1 based device which I'm trying to connect to my Exchange 2010 box (SP3 Update Rollup 2). I currently have my iphone set up as an EAS client with no problems. I have an EAS policy on my mailbox
with the following settings surrounding passwords :
Require Password, Require Encryption, Allow Simple Password, Time without user input - 10 minutes. Allow non-provisional devices is also checked.
The Windows 8.1 device has Bitlocker enabled, which meets the encryption requirement - I know this because the 1st time I tried this it moaned about Bitlocker needing to be enabled to meet requirements, though at that time the local user account on the Windows
8.1 device was an admin level account so it never mentioned this issue, it worked normally.
Now, while using a std user account on the Windows 8.1 device and trying to connect up via EAS, it complains that my local windows user account must be an ADMIN level account to meet the security requirements...?
Anyone encountered this?

Did anyone solve this problem? I'm also struggling with this issue.
this is still a problem. I'm just hitting it now and it's not doing much for management's love of Microsoft devices.
Evidently, it has to be an admin to set the policies on the device to match the policies on the EAS. And once set, a user can be changed back.
But this is seriously not cool. Don't the "app" folks and the enterprise folks talk to each other?

Issue with SLA reports of Exchange 2010 MP in SCOM 2007 R2 !!

Hi,
I have issues with Exchange 2010 MP SLA reporting. Whenever report is run it fails on some or the other dataset(Outage**,SLAbyDAte etc.) When I digged in, I found that it is connecting to DW Exchange 2010 Availability tables + Planned maintainance +
outage table. The tables were not available in the DW, not sure how it got removed. Initially I tried by uninstalling and installing MP(Exchange 2010 & Exchange 2010 reports both) if relevant tables get created automatically but it did
not help and I was still facing the same issue. Then I tried to create the tables manually and check if it could resolve the issue. There was unique ID associated(different in different computer) with the name of most of the tables. I tool it from Exchange
report data source which exists in reporting server. But I could see that table remain empty with no records there and SLA report start giving different issues stating table instances do not exist.
Could anyone help me to restore the SLA report of Exchange 2010 MP ? How should I ensure that data start populating the tables ? I am also helpless here because we do not have correct DW dump to restore back to earlier when it was working fine.
//BR

Hi,
Based on my research, to correctly install the Correlation Engine, consider the following when you install the Exchange 2010 Monitoring Management Pack:
Determine which server will host the Correlation Engine. While not strictly required, it's strongly recommended that the Correlation Engine be installed on the Root Management Server computer.
Make sure that you download and install the Exchange 2010 Management Pack that matches the operating system for the selected server. You can install the 32-bit or 64-bit version.
Make sure that you run the Microsoft Installer (.msi) package on the server where you want the Exchange 2010 Management Pack and the Correlation Engine to be installed.
After the installation is complete, the Correlation Engine service will have been installed on the server, and the Management Pack files will have been copied to the
System Center Management Packs folder. By default, the installation directory is C:\Program Files\System Center Management Pack.
Quote from:
http://technet.microsoft.com/en-us/library/ee758051(v=exchg.140).aspx
In addition, here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/e75e84d9-0c9e-4d83-b3da-45a143757f85/exchange-2010-monitoring-with-scom-2012-correlation-service-issue
Regads,
Yan Li
Regards, Yan Li

Unity Connection 8.5 Exchange 2010

Similar Messages

Maybe you are looking for