Curve 9320: Connect with Exchange 2007 without BES ?

Hello,
is it possible to connect with the Curve 9320 to a MS Exchange Server 2007 without a BES like with an Android Smartphone ? Our company have not a BES. Can i use WhatsApp & Co. without BES ?
Greatings
sky

Hi and Welcome to the Community!
sky2000 wrote:
is it possible to connect with the Curve 9320 to a MS Exchange Server 2007 without a BES like with an Android Smartphone ? Our company have not a BES.
Depending on what your email admins face to the internet, maybe. Via BIS, a BB can integrate with most all POP, IMAP, and OWA internet-facing systems. But, it will depend on what faces the internet:
KB03119 Requirements for integrating IMAP and POP email accounts with a BlackBerry Internet Service account
KB04478 Integrate POP accounts with the BlackBerry Internet Service
KB10154 How to integrate a POP or IMAP email account through advanced integration
KB03133How to integrate a Microsoft Outlook Web Access email address on BlackBerry smartphone
Depending on what your email system faces to the internet, one of those should get you going.
sky2000 wrote:
Can i use WhatsApp & Co. without BES ?
I know what "WhatsApp" is, but what is "WhatsApp & Co."? In any event, WhatsApp does not require BES (I have heard others report that it does require BIS though).
Good luck!
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

Similar Messages

Does anyone know how to get apple mail in Lion to connect with Exchange 2007?

Does anyone know how to get apple mail in Lion 10.7.2 to connect with Exchange 2007? It worked perfectly with Snow Leopard... upgraded to lion and it won't work. We use Exchange 2007 with SP 3 and Rollup 4. Won't connect... and I can't get Apple to give me any direction.

We finally got it to work today. We had to call and pay for the microsoft support service, but the issue was on the server end. We had to go into the iis manager... went to sites... when to default website...and changed the SSL settings for Auto Discover, EWS Exadmin, echange, exchweb, owa... and the rest..
Change the settings to ignore client certificates.
Problem solved. Can finally send and receive.

How do I set up my ipad to work with Exchange 2007 without VPN (via port 443)?

Hi,
we currently use blackberries on a BES server, but planning to migrate to iPhones to use ActiveSync via https to get mail pushed out to our devices on and iPhone 5 we have yet to purchase. We have and ipad 3 i'm trying to get to work on before purchasing an iphone.
i have an MS Exchange Server 2007 on one box, and i have a firewall/VPN device on another box.
i've gotten the ipad to connect to MS Exchange when using the Cisco ipsec VPN, but would like to know if it's possible to have MS Exchange push out emails to our devices (by not using POP3, but to use https)
i've tried opening tcp 443 on the firewall and using the firewall/VPN device as the server address (didn't work)
i've stumbled across this 3rd party software that connects VPN on demand (isimplyconnect), but that doesn't seem to push emails correctly to the ipad.
can someone help me out a bit?
thank you.

ok, so i got my iphone online and able to receive mail outside of the network, but when i bring my iphone inside my corporate network on to my internal wifi, i cannot receive mail. I know this is a firewall setting issue, but is there another way around it besides creating another mail profile for inside the network?
and another thing, i'm missing my notes sync with Active sync, any ideas why this is missing?
i've cleared out my notes on both ends and adding a new note in outlook, but the sync option is missing.

Unity Connection 8.5.1ES16.11900-16 upgrade for Single Inbox with Exchange 2007 ?

Hello friends,
I'm currentely running Unity Connection 8.5.1ES16.11900-16.
I would like to use the single inbox feature with Exchange 2007.
It is in the documentation that we need at least Unity Connection 8.5(1) Service Update 1 (UCSInstall_UCOS_8.5.1.11900-21.sgn.iso).
I downloaded, checked MD5 but when searching on the FTP directory it won't accept it (No valid upgrade options were found). Is this a supported upgrade?
Same happens with the localization file in Portuguese that i need to install: uc-locale-pt_PT-8.5.1.1-16.cop.sng ...
Please can you give me some hints about what I may be doing wrong?
Thank you very much and warm regards,
met

Hi Met,
Hope all is well
I think you are hitting this caveat. Although the numbers don't match exactly I'm
pretty sure you will need to wait for an 8.5.1.12xxx.x ES
If the Connection server is running an engineering special with a full Cisco Unified Communications
Operating System version number between 8.5.1.11001-x and 8.5.1.11899-x, do not upgrade the server
to Connection 8.5(1) SU 1 because the upgrade will fail. Instead, upgrade the server with an ES released
after 8.5(1) SU 1 that has a full Unified Communications OS version number of 8.5.1.12xxx.x or later
to get the SU 1 functionality.
http://www.cisco.com/web/software/282074295/44508/851su1cucrm.pdf
Cheers!
Rob

ICal still does not sync with exchange 2007 in Lion

Dear,
In Snow Leopard, iCal was not syncing with Exchange 2007. I read a lot of things on this and it all led to recurring events. Indeed, after deleting them, things started to work. But I cannot delete recurring events! I need them!
Seeing that there was soo much talk on this all over on apple, I assumed that Apple would fix it. Instead, all we're seeing is some enhanced UI.
Can somebody at Apple please make sure that this thing finally gets fixed? Really, how hard can it be, knowing that the hardware based i devices can sync without any trouble?
Just for extra information, so you know what direction to look for:
I have Windows SBS 2008 in Dutch language. Timezone is Brussels. Exchange 2007 and all updates.
The system is running a self signed certificate
Outlook works fine on the Mac. I don't want to use Outlook on the Mac but am forced to at the moment.
Mail/Addressbook sync fine. Only Outlook doesn't!
I did try deleting recurrent events and this worked for a day. Basically stopped working I think when I added again those recurring events.
There are some errors in the console:
21/07/11 11:42:36,563 iCal: Couldn't find an NSTimeZone to match the SerializableTimeZone
21/07/11 11:42:36,563 iCal: WARNING: Failed to find TimeZone Identifier for Windows MeetingTimeZone: (GMT+01:00) Amsterdam, Berlijn, Bern, Rome, Stockholm, Wenen
21/07/11 11:42:36,580 iCal: error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken." UserInfo=0x7fbe94adb8b0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7fbe94102d40>, NSLocalizedDescription=iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken., NSLocalizedFailureReason=De account 'Exchange' kan momenteel niet worden bijgewerkt.}
Please fix this,
Guido
Message was edited by: guido4096. Added error message

Hi all,
I do have exactly the same problem.
But I am adding a new flavor, but I can not understand it.
I've setup two Exchange calender connections. Both servers are inhouse. The setup of the Exchange servers are most likely the same.
But one works and one not! How could this be explained?
I like to express my deep disappointment about iCal and partly Apple Mail. It is unbelievable for me, that years after Apple's cooperation with Microsoft there are still such problems.
I like my Macbooks and I certainly have the absolutely full bandwidth of all Apple products in my household and companies. But I think I have to go back to Microsoft and Sony Laptops in the near future.
Although this kind of bugs are small one's, but the hurt constantly. Apple - please fix that.
Here just for the interested reader is my console error message:
3/15/12 11:51:29.819 AM iCal: error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal can’t refresh events in the calendar “Kalender”." UserInfo=0x7f856d4bddb0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7f856c5ca060>, NSLocalizedDescription=iCal can’t refresh events in the calendar “Kalender”., NSLocalizedFailureReason=The account "DR InfoDyn" currently can’t be refreshed.}

Assertion Failures using Mail.app with Exchange 2007...

We have been implementing and migrating our end-users to Exchange 2007. In doing so we found that Mail.app end-users were experiencing Assertion failures in Console.app. They used to cause Mail.app to crash and lose connectivity frequently to the Exchange 2007 server. We made a change to the firewall to allow communication to happen between domain controllers, but haven't been able to determine if this in fact resolved or helped hide the root cause. We seem to be no longer crashing Mail.app or losing connectivity, but the same logs when we would crash/lose connectivity are still happening when you look in Console.app.
*Here is an example of an Assertion failure where "The Operation couldn't be completed":*
+11/12/10 1:19:36 PM Mail[3201] * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSConnection.m:374+
+Received an unexpected error: Error Domain=NSXMLParserErrorDomain Code=5 "The operation couldn’t be completed. (NSXMLParserErrorDomain error 5.)", response: (null)+
+ 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
+ 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
+ 2 Message 0x00007fff8036301b -[EWSConnection sendMessage:forRequest:] + 1117+
+ 3 Message 0x00007fff8036e5b9 -[EWSGateway sendMessage:forRequest:] + 79+
+ 4 Message 0x00007fff80381a63 -[EWSRequestOperation executeOperation] + 104+
+ 5 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
+ 6 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
+ 7 Foundation 0x00007fff8662abeb __doStart2 + 97+
+ 8 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
+ 9 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
+ 10 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
+ 11 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
*I also get this Assertion failure every time I re-open Mail.app that shows up in Console.app that says "Mail did something wrong: The specified folder could not be found in the store.":*
+11/12/10 12:44:22 PM Mail[3201] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
+Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x1012f1830> (EXECUTING)+
+ 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
+ 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
+ 2 Message 0x00007fff80382956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295+
+ 3 Message 0x00007fff80377aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88+
+ 4 CoreFoundation 0x00007fff879c26d7 __NSArrayEnumerate + 1399+
+ 5 Message 0x00007fff80377d86 -[EWSGetFolderResponseOperation executeOperation] + 445+
+ 6 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
+ 7 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
+ 8 Foundation 0x00007fff8662abeb __doStart2 + 97+
+ 9 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
+ 10 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
+ 11 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
+ 12 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
+11/12/10 12:44:22 PM Mail[3201] Recieved EWS error: Error Domain=MFEWSErrorDomain Code=79 UserInfo=0x1148c1d10 "The specified folder could not be found in the store."+
We are getting these Assertion Failures for other end-users as well that are using Mail.app and connecting to Exchange 2007 Server. I have wiped my mail.app account and started from fresh and that didn't help. I did it manually as well ensuring that preference files, caches, and passwords related to mail.app, ical.app, and Address Book.app were removed. That did not work. I just went from 10.6.4 to 10.6.5 hoping that would correct the issue, it did not. I even set up on another Mac a baseline Snow Leopard and patched it and then configured my mail account and still got the same errors.
What I am hoping for is not a miracle (Fixing the problem), but being told what these errors mean and if there is any risks to be concerned with. In other words, can I ignore these error messages or should I be concerned? Like I said it was causing us to get the sideways thunderbolt or triangle with an exclamation point and even crashing Mail.app at times. That hasn't happened since we let the all of the domain controllers talk to each other, even though they shouldn't have to.

I echo your hope for someone shedding a light on this. I too am geting Assertion failures, every few days, though without much in the way of crashes.
Here is an example of a log entry describing one recent such failure:
+5.12.2010 11:04:40 Mail[17075] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
+Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x11d80ec70> (EXECUTING)+
0 Message 0x00007fff81f7d6e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff81f7d649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Message 0x00007fff81ede956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295
3 Message 0x00007fff81ed3aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88
4 CoreFoundation 0x00007fff8448c6d7 __NSArrayEnumerate + 1399
5 Message 0x00007fff81ed3d86 -[EWSGetFolderResponseOperation executeOperation] + 445
6 Message 0x00007fff81f8bab9 -[MonitoredOperation main] + 229
7 Foundation 0x00007fff847b4de4 -[__NSOperationInternal start] + 681
8 Foundation 0x00007fff84893beb __doStart2 + 97
9 libSystem.B.dylib 0x00007fff85f6b2c4 dispatch_call_block_andrelease + 15
10 libSystem.B.dylib 0x00007fff85f49831 dispatch_workerthread2 + 239
11 libSystem.B.dylib 0x00007fff85f49168 pthreadwqthread + 353
12 libSystem.B.dylib 0x00007fff85f49005 start_wqthread + 13
Perhaps coincidentally, I am having trouble with syncing iCal with my Exchange account. Ii have only found this thread on the subject, and am in the process of trying to find there the solution to that problem:
http://discussions.apple.com/thread.jspa?threadID=2138051
Any and all insight would be greatly appreciated.

Outlook 14.4.8 not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox"

Outlook 14.4.8 on iMAC Retina and Yosemite 10.10.2 is not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox".
Accessing Mails with Webbrowser and from Windows Outlook is working correctly.
All Macs (also the ones with OS 10.6.8) do not anymore show any new messages in inbox.
Restarted Server, tried to disable autodiscover on macs and deleting/adding account and repairing database does not fix the problem. Also restarted server several times.
We have the same problem on 2 imacs retina with yosemite and on 2 mac pro with 10.6.8 and different office 2011 versions.
i tried to configure the exchange account in apple mail on yosemite and it also states "connected" and does list some folders but no new mails are getting in.
Windows clients and outlook on them works and syncs fine, and also when connecting via webbrowser at owa it must be a mac-specific/webdav issue.
exchange 2007 Sp3 Version 8.3 (bild 83.6) and Update Rollup 15 for sp3 (automatic updates "HIGH" for server and clients)
there is one update popping up again and again even after everytime successull installation: Windows Mlicious Software Removal Tool x64 - October 2010.
i tried to configure a new user with empty mailbox and configured it with microsoft mail (mac - yosemite) as exchange and was able to send a mail from there (even if quite delayed).
but there are not coming in any mails.
same exchange accounts triggered by imap do work and also via owa.
Exchange Accounts in Outlook for MAC and also in Mail (Yosemite) do show the folder structures but there is no mails showing up. I can send mails from the exchange accounts created but they seem to be processed with a delay of like 15minutes and outlook
is giving error "end of file reached" but messages are send after some time.
Does seem like EWS is extremely slow, to slow perhaps to sync and therefore ending in timeout.
Also i cannot reach the server from externally over ssl https 443. if testing port 443 of exchange from outside the port seems closed even firewall settings of sbs 2008 and sonicwall ports are correctly open.
could it be there is something in regarding webdav which is very slow and leading to timeouts ?
in application log i do have the following two information events every few minute:
The Exchange Web Services started successfully. Event ID 1
and
Process STORE.EXE (PID=3688). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
SERVER.org.local CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
Errors in Application log:
The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section
The entry <C:\WSUS\WSUSCONTENT\CONTENTFOLDERACLSCHECK.TXT> in the hash map cannot be updated.
An exception Microsoft.Exchange.Data.Storage.ConversionFailedException occurred while converting message Imap4Message 69447
Also outlook 2011 clients are asked by time to time to reenter pwds and errors like "connection is closed. 13"
Faulting application taskeng.exe, version 6.0.6002.18342, time stamp 0x4cd34898, faulting module ntdll.dll, version 6.0.6002.18881, time stamp 0x51da3d16, exception code 0xc000071b, fault offset 0x0000000000082445, process id 0x3288
Certificate Services Client Provider pautoenr.dll raised an exception. Exception code 3221225477.
Backup Exec:
FULL_BACKUP -- The job failed with the following error: A failure occurred querying the Writer status.
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The
error returned from CoCreateInstance
Exchange VSS Writer (instance 2d932ef8-6319-4ab8-a45f-1242480b44ad:15) failed with error code 1295 when processing the backup completion event.

Hi,
Since Outlook running on Windows works well, it seems an issue on the Mac side. I suggest ask Mac for help so that you can get more professional suggestions.
More information for your reference:
Please try to verify whether there is any expired certificate from the computer personal store.
If it is the case, please remove them.
Thanks
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]
Mavis Huang
TechNet Community Support

Migrate SBS Server 2008 with Exchange 2007 to Exchange 2013

I have looked at the documentation to co exist 2007 and 2013. However I am concerned as it talks about changing the dns name to something like legacy, as the dns name that is used for outlook to connect is the name of the server. So here
is my question. Would I have to change the name of the actual server itself? and if I choose not to, and use a new name for the 2013 server, such as mail, would the users that get migrated, would they automatically update the
name change? Also note the SBS server with exchange 2007 is also their file server at present but will be changing.

Hi ,
Thank you for posting your question in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback
on our support quality, please send your feedback here.
Andy Qi
TechNet Community Support

Inconsistencies connecting to Exchange 2007

Greetings:
We have just migrated a high-demand client to Exchange 2007, and are using a combination of Apple Mail and Entourage for a few different users.
Users are reporting messages coming into their Blackberries and Entourage almost immediately after sending.
Yet in Apple Mail, we are seeing issues where some of the mail is not being received by Mail for sometimes up to 30 minutes later.
We're trying to nail this down to see if it has to do with certain messages that use attachments. It has been difficult to reproduce, but we've had many complaints in the last 2 weeks since we made the switch.
Additionally, when we were on Exchange 2003, two of the users liked using POP because of the sheer number of messages and attachments they received. On the new server, POP became impossible to use because Apple Mail would start downloading the same messages two, three, sometimes even four times, causing massive amounts of duplication.
Attachments haven't been consistent in Mail. I will sometimes see messages via OWA that have the attachment, but Mail will not show the attachment. We are having users quit Mail and restart it, and sometimes this can correct the flow of messages, as well as attachments showing up or not.
There is another issue that has been plaguing us: at least 2 or 3 times in the last couple of weeks, someone has deleted a message by accident. And when going into the Trash to find the message (Mailbox behaviors are set to store deleted items on server), the message has just disappeared. They've been able to pull it from the Blackberry in some cases, because Mail does not always resolve the deletion quickly.
We wanted to know: what are the caveats of using Apple Mail with Exchange 2007? Does the newest rollup make all the difference? Are there issues that we should know about? The "slowness" issue is the biggest complaint we're getting on a regular basis.
Internet connections vary, since the principles of the company are spread out between Hollywood, Palm Springs, and Tulsa - and the reports we're getting back are coming from all of those locations.

The first thing to check is how often Mail is polling the server for new messages. Mail does not support Push messaging from Exchange, so you have to set the frequency of message checking appropriately. I have mine set to check every minute.
I can't address the issue with attachments, though we have had similar problems with Outlook clients that have turned out to be problems with the user's Exchange profile (Blackberry systems use RIM's own mail servers, not the Exchange server, so you can't really compare experiences there). For deleted messages, there may be more than one folder in which deleted messages may be put, so it may be that your users just aren't looking in the correct folder; there may be the Mail Trash, but also a Deleted Items folder down in the list of folders.
Hope this helps.

Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

I have exchange 2013 and 2007 set up in a coexist environment. At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007. I found an article
that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.) I would like someone to confirm
if the change I am about to make from doing research will help me in my situation.
Current Setup:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: NTLM
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod: Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
New Settings I am considering based on research:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {NTLM}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {Basic}
Will this work and eliminate my popups?

Hi,
The following TechNet article indicates that:
“In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
Exchange Deployment Assistant. Specifically,
you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
Client Connectivity in an Exchange 2013 Coexistence Environment
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Regards,
Winnie Liang
TechNet Community Support

Unrecognized certificate when Outlook 2010 tries to connect to Exchange 2007 on SBS 2008

Hi all,
I believe this is a security issue rather than a connectivity or configuration problem.
Running Outlook 2010 on Windows 7 trying to connect to Exchange 2007 on SBS 2008, I receive the following error:
"The name of the security certificate is invalid or does not match the name of the site"
When I view the certificate I see that it was issued to "zx-server" by "zx". This is NOT my domain CA nor is it a certificate I recognize. I use a self-issued certificate (i.e. issued by the SBS box). I also receive this certificate error when I browse to
the internal website (companyweb). No other computers on the network are seeing this behaviour.
I have checked the certificate stores in certmgr and I can't find any such certificate or CA. I have also searched the entire hard drive with no luck. I have run Kaspersky AV, Malwarebytes and MS Security Essentials several times but I can't find any malware.
I also recently installed Comodo Firewall (the problem began after this).
I need to find and remove the certificate and prevent it from being presented to me every time I try to connect to the server. All help, advice and suggestions appreciated.
Aide

Hi,
It’s really a common issue.
This issue occurs if the following conditions are true:
You replace the default self-signed Exchange Server 2007 or Exchange Server 2010 certificate with a different certificate.
Note The Setup program in Exchange Server 2007 or in Exchange Server 2010 creates a default self-signed certificate when Exchange Server 2007 or Exchange Server 2010 is installed.
The common name on the replacement certificate does not match the fully qualified domain name (FQDN) of the URL that is stored in the following objects:
o
The Service Connection Point object for the Autodiscover service
o
The
InternalUrl attribute of Exchange 2007 Web Service (EWS)
o
The
InternalUrl attribute of the Offline Address Book Web service
o
The
InternalUrl attribute of the Exchange unified messaging (UM) Web service
By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the
following URL is stored:
https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml
This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate
may have an FQDN that resembles the following FQDN:
mail.contoso.com
This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook
2007 to the mailbox.
For more detailed information about the procedures to fix the issue, please refer to the following KB article:
Title: Security warning when you start Outlook 2007 and then connect to a mailbox
that is hosted on a server that is running Exchange Server 2007 or Exchange Server 2010: "The name of the security certificate is invalid or does not match the name of the site"
URL:
http://support.microsoft.com/kb/940726
Regards,
James
James Xiong
TechNet Community Support

Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

HI, i need help here
I have Win 2008 with Exchange 2007 and Symantec Mail Security. Symantec was working fine until the license expired but it was still fine until yesterday, we realize that we cannot receive email with attachment. after stopping the symantec services, mail
flow went back to normal. We then remove the program from the control panel.
Then i found that i cant retrieve or find those emails that was sent to us during a period of ard 6 hours. i tried looking the the Symantec quarantine folder but it is not there.
Can someone point to me where should i look for the missing mails? When i do a mail flow troubleshoot i can see the logs that it is sent to the mailbox, but from users's outlook inbox, there is no email ??
Much Appreciated

Symantec's support group should be able to tell you what happened.
--- Rich Matheisen MCSE&I, Exchange MVP

Has anyone managed to create an email account on the OS X mail client with Exchange 2007?

Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen

jthurner wrote:
Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen
No workaround needed, open Mail, Contacts and Calendars (in System Preferences) select Exchange, enter your email address and password, opt to setup Contacts and Calendars as well as mail and hit enter. That should set it up (assuming your apparently witless IT dept has setup the autodiscover record correctly at their end)

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Curve 9320: Connect with Exchange 2007 without BES ?

Similar Messages

Maybe you are looking for