Exchange 2013 CAS-MBX / Exchange 2007 Edge Mail flow

I am in the process of migrating from Exchange 2007 to Exchange 2013. I have installed my 2013 Cas/MBX into my environment with the existing 2007 Hub/MBX and existing 2007 Edge. Mail flow on the 2007 side is unchanged (working) but on the 2013
side I am able to receive mail but I can't send (from test mailbox). It just sits in the que on the 2013 CAS/MBX until it expires.
Any ideas? My Exchange 2007 servers are both upgraded to SP3 Rollup 13 so the versions should be fine.

I redid my edge subscription (applying the xml on the 2013 hub). All works the same (mail flow on the 2007 side works fine but unable to send out for mailbox's that live on the 2013 side). One thing I noticed is that when I ran start-edgesynchronization
I get the following:
RunspaceId : xxxxxx
Result : CouldNotConnect
Type : Recipients
Name : XXXX
FailureDetails : The LDAP server is unavailable.
StartUTC : 9/15/2014 2:03:23 AM
EndUTC : 9/15/2014 2:03:23 AM
Added : 0
Deleted : 0
Updated : 0
Scanned : 0
TargetScanned : 0
RunspaceId : xxxxxx
Result : CouldNotConnect
Type : Configuration
Name : XXXX
FailureDetails : The LDAP server is unavailable.
StartUTC : 9/15/2014 2:03:23 AM
EndUTC : 9/15/2014 2:03:23 AM
Added : 0
Deleted : 0
Updated : 0
Scanned : 0
TargetScanned : 0
I am able to ping my domain controllers / edge server and I can also telnet to ports 389 & 3268. I have restarted my Active directory topology service

Similar Messages

Exchange 2007 edge server with ironport

I currently have a frontend exch 2003 and backend exch 2003 server with ironport. my mx record is the ironport which then forwards into the backend server. The frontend server was only used for owa and using outlook with https connection to exchange.
With 2007 it has more functionality and the front end server is now called an edge server. Should I have mx go there then to ironport or vice versa? I'm thinking ironport to edge server to hub transport server. Is that correct? will it work?
anyone have exchange 2007 edge server with ironport? what are you doing?

well that wouldve been nice to know a little earlier. anyway I have ironport successfully sending mail to the edge server who sends it on to the hub transport server. right now the client access server is on the same as the hub but can be easily moved later. this is for very few people so its not like I need to off load anything as its a powerful dual core server. anyway now with the edge server I can test how effective it is versus the ironport. I'll let everyone know when you can ditch the ironport for msft's edge server. (Don't hold your breath).

Exchange 2013 upgrade from 2010 and no mail flow and cannot move mailboxes

I am in the process of moving to Ex 2013 from 2010. I have installed Ex 2013 SP1 on a new server 2012 R2. All of my Ex 2010 servers are SP3 RU 5. Ex 2013 is running and I can connect through the EAC and see all other Exchange servers and connectors that
were already in existence. Several puzzling things are happening now that the servers are in coexistence:
1) As soon as Ex 2013 was installed on the network, many Outlook users are continuously being prompted to enter their domain credentials. They can cancel the prompt and Outlook still sends/receives email. No user mailboxes are on Ex 2013 yet.
Why is this happening?
2) I am following the Ex 2013 Deployment Assistant and I get to the step to move the Ex 2010 Arbitration mailbox to Ex 2013 and the move does not happen--it just says "syncing" and never completes. I tried moving a test mailbox from Ex 2010
to the 2013 database and I get the same result. I created the move request on the Ex2013 server and I see it as queued on the Ex2010 server, so I know they are "talking" to each other. However, when reviewing the status of the move I
see "MapiExceptionNoAccess: Unable to open message store".
3) There seems to be no mail flow on the same Ex2013 server or between the Ex 2010 and 2013 servers. I created two new test user mailboxes in Ex 2013. The Ex2013 mailboxes cannot send/receive to each other or to Ex 2010 users. This
seems strange, unless I am completely missing something in the Ex 2013 install?
I know this is a lot in one post, but following the Deployment assistant, I was hoping this would be something that others have faced. Thanks for any input here.

Does the below points already fit for you.
Exchange 2013 Supported with the following minimum versions of Exchange:
1) Exchange*** 2010 SP3 on all Exchange 2010 servers in the organization, including Edge Transport servers.
2) Exchange 2013 CU2 or later on all Exchange 2013 servers in the organization.
*** If you want to create an EdgeSync Subscription between an Exchange 2010 Hub Transport server and an Exchange 2013 SP1 Edge Transport
server, you need to install Exchange 2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport server.
Thanks Prem P Rana MCSA Messaging 2003 MCSE 2003 Server MCTS MCITP Exchange 2007, 2010 Gurgaon, India http://blogs.msexchange-experts.com

Exchange 2007 - Mac mail broken?

Since yesterday I have not been able to receive email on Mac mail connecting to hosted Exchange 2007 from GoDaddy.
I have deleted the account twice now, both times the mail synchronises up to current mail and then no new mail comes in.
When I try to send mail I get :
'Cannot send message using the server [email protected] (exchange). The exchange server 2007 connection to server ex1.secureserver.net failed '
Funny thing is the mail does actually arrive with recipient but it remains in my mac mail outbox.
Email is working fine using web/owa and fine on iPhone. This also works fine on my Windows 7 Machine using Outlook 2007 so it is no GoDaddy's issue.
Did Apple break something in an update?

I have just been able to verify that this is indeed a GoDaddy issue. I have two Exchange accounts, one hosted with GoDaddy and one on a corporate Exchange server.
My GoDaddy hosted Exchange account is not working at all right now, after the issue started yesterday I deleted the account, rebooted and added it again and I now don't see ANY emails now in my Inbox or other folders on the Exchange server. I also lost all of my calendar and delegate calendar info in iCal (but it's all still on the server). OWA, iPhone, and Outlook on a virtual PC continue to work fine.
My corporate Exchange account continues to work as expected in Mail. I just had a colleague send me several test emails and meeting requests, I was able to see the message contents (not just the header like I was seeing on the other account yesterday), reply, and accept the meeting request.
I guess the fun part starts now - getting the dipsh**s at GoDaddy to figure out what they broke.

Problem moving folders on exchange 2007 in mail.app

Hi,
I've got a problem i'm fairly certain is a bug. If I accidentally drag an exchange folder into another folder in Mail, there is no way to drag it back out. I can only drag it into another folder. Let me try to replicate my folder setup here:
Facebook
Personal
Company
   Newsletters
eBay
Faxes
Someones Name
Server Messages
   LFD Messages
If I want to drag a folder (say Newsletters) out of another folder (Company), my options are a follows:
A) I can drag it into any other unopened folder (It highlights the folders)
or
B) the following lines appear in the lineup
Facebook
Personal
Company
   o---------
   Newsletters
   o---------
eBay
Faxes
Someones Name
Server Messages
   o----------
   LFD Messages
   o----------
I would expect full length lines to appear, such as:
INBOX
o-------------
o-------------
   Someones Name
o-------------
   Server Messages
      o----------
      LFD Messages
      o----------
o-------------
But the full-width bars do not appear and thus do not allow me to reposition folders or drag a folder out of a subfolder.
The only thing unique about my installation seems to be this:
A) The last folder in the list has a subfolder
B) I've got 16,000+ messages (the darn "server messages" folder!)
Any help would be much appreciated!
I've got a Mac Pro running 10.6.2 with Mail version 4.2 build 1077.

I had the same problem with a test install of Exchange 2007.
While making yet another pass through IIS settings, I noticed that the www service was set to run in "IIS 5.0 isolation mode" (Web Sites Properties dialog --> Service tab). After removing the check from the box and restarting IIS, OWA 2007 worked as advertised. Haven't tried ActiveSync yet.

Exchange 2013 CAS-MBX recipient validation rejects entire message if any of recipients are invalid

Hi,
How can I enable recipient validation work in this design:
2 Exchange 2013 servers with CAS and MAILBOX roles both, DAG and Hardware Load balancer for HTTP and SMTP traffic.
From Exchange documentation:
http://technet.microsoft.com/en-us/library/bb125187%28v=exchg.150%29.aspx
Although the Recipient Filter agent is available on Mailbox servers, you shouldn't configure it. When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid recipients, the message is rejected.
If you install the anti-spam agents on a Mailbox server, the Recipient Filter agent is enabled by default. However, it isn't configured to block any recipients. For more information, see
Enable Anti-Spam Functionality on Mailbox Servers.
If You have a setup like this:
Install antispam agents:
Identity Enabled Priority
Transport Rule Agent True 1
Malware Agent True 2
Text Messaging Routing Agent True 3
Text Messaging Delivery Agent True 4
Content Filter Agent True 5
Sender Id Agent True 6
Sender Filter Agent True 7
Recipient Filter Agent True 8
Protocol Analysis Agent True 9
Have Recipient validation enabled:
Name Enabled RecipientValidationEnabled---- ------- --------------------------RecipientFilterConfig True True
Have AcceptedDomain AddressBook enabled:
DomainName DomainType AddressBookEnabled
contoso.com Authoritative True
Then You have a situation, where a single invalid recipient on an incoming email message would reject the entire message! I guess this is because the recipient filtering happens on the mailbox server.
So .. HOW? Is it possible without Edge servers? Have I missed something?
I hope this feature isn't "missing by design", because it will be very difficult to explain to the client, that such an expensive product cannot do what any mail server can - reject unknown recipients before taking E-Mail data. There are a lot
of issues with this feature missing (possible DDOS with max attachments, or spoofed sender e-mail address that is a spamtrap, so NDR from Exchange would get You to SBL, etc.).
Sincerely,
Vince

Hello Vince,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
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

Emails are Blocked from domains which are added to "BypassedSenderDomains" in Exchange 2007 Edge server

Hi,
We have an Exchange server 2007 and an Edge server 2007 is configured in the perimeter network. Most of our clients use Public email domains such as Yahoo and Gmail. Last few weeks it has been a major issue for us that most of the emails from Yahoo/Gmail
get blocked by our Edge server calming the sender IP address is in Block Lists.
As a solution I've added yahoo.com/gmail.com/aol.com/hotmail.com to "BypassedSenderDomains" hoping if emails receive from one of these domains it will bypass the connection filtering. But still some of our customers complain that their emails are
still not passing to us and blocked by our edge server. They have provided me the error message they receive.
Our clients get following error message
edgexch gave this error: Recipient not authorized, your IP has been found on a block list
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction
may be preventing delivery.
550 5.7.1 Recipient not authorized, your IP has been found on a block list
When I check the Agent logs in Edge server I found specific email had been blocked. Please check one of the log entry.
Timestamp       : 1/30/2014 1:45:15 PM
SessionId       : 08D0E865200E7CBF
IPAddress       : 98.139.213.140
MessageId       :
P1FromAddress   : Sender Email Address (@yahoo.com)
P2FromAddresses : {}
Recipients      : {Recipient Email address}
Agent           : Connection Filtering Agent
Event           : OnRcptCommand
Action          : RejectCommand
SmtpResponse    : 550 5.7.1 Recipient not authorized, your IP has been found on a block list
Reason          : BlockListProvider
ReasonData      : bl.spamcop.net
This troubles me because I've added Yahoo.com to "BypassedSenderDomains" on 1/28/2014 and this email was blocked on 1/30/2014. I've checked whole Agent logs from 28th to-date and found most of the messages from white-listed domains bypassed
the content filtering but some were still getting blocked. Most of the messages from white-listed domains were blocked from "bl.spamcop.net " IP block list provider.
As a solution for the current situation I've disabled "bl.spamcop.net" from the "IP block List Providers". But the issue is, why the mails are getting blocked even the domains were white-listed. I though after white-listing emails domains,
messages will bypass the content filters if the email generates from one of the white-listed email domain.
I've also added the "Content Filter Config" for your reference.
[PS] C:\Windows\system32>Get-ContentFilterConfig
Name
: ContentFilterConfig
RejectionResponse
: Message rejected as spam by Content Filtering.
OutlookEmailPostmarkValidationEnabled
: True
BypassedRecipients
QuarantineMailbox
: [email protected]
SCLRejectThreshold
: 7
SCLRejectEnabled
: False
SCLDeleteThreshold
: 9
SCLDeleteEnabled
: False
SCLQuarantineThreshold
: 5
SCLQuarantineEnabled
: True
BypassedSenders
BypassedSenderDomains
: {yahoo.com, gmail.com, hotmail.com, aol.com}
Enabled
: True
ExternalMailEnabled
: True
InternalMailEnabled
: False
AdminDisplayName
ExchangeVersion
: 0.1 (8.0.535.0)
DistinguishedName
: CN=ContentFilterConfig,CN=Message Hygiene,CN=Transport Settings,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,CN={4546F49-6BC5-4F7A-848F-03E4652528A6}
Identity
: ContentFilterConfig
Guid
: c501959c-b062-4f59-8f0c-404c53f54a34
ObjectCategory
: CN=ms-Exch-Message-Hygiene-Content-Filter-Config,CN=Schema,CN=Configuration,CN={4546F4196BC5-4F7A-848F-03E4652528A6}
ObjectClass
: {top, msExchAgent, msExchMessageHygieneContentFilterConfig}
WhenChanged
: 1/28/2014 8:48:49 PM
WhenCreated
: 1/8/2012 8:42:18 PM
OriginatingServer
: localhost
IsValid
: True
It would be great if someone could help me to resolve this issue because this is a major problem since we lost mails from our valuable customers.
Thanks in advance.
Tharaka

Here is a similar issue someone with Exchange 2010 -
http://social.technet.microsoft.com/Forums/exchange/en-US/36aec4f6-6d73-4d71-ab64-e7f3d817b39b/exchange-2010-still-blocks-mail-from-domain-on-dnsbl-even-though-its-on-bypassedsenderdomain?forum=exchange2010. So in essence, use the exceptions tab for
the IP Block List Providers. See if that will work as a solution for you.
JAUCG - Please remeber to mark replies as helpful if they were or as answered if I provided a solution.

Exchange 2007 not showing all mails

There are a lot of mails within folder not shown within apple mai! I connect with the Exchange 2007 setting and it just does not sync well. I tried Exchange IMAP which works, but lead to different problem like having a separate 'Sent' folder!
If I check those folders with OWA ord Outlook I'v got hundrets of mails. Even my iPhone shows all mails! But Apple Mail doesn't.
The Syncing of Exchange 2007 with Mail is broken! We are three people working with it (all software developers) and there are so many problems...
i.e. renaming folders if you have the option 'keep mails and attachments' set and several people are using the same account for archiving mails within project folders...

I removed now the whole mail profile (the folder with finder). I added the account again and still I'v got folders which just show mails up to december 2009. That's **** for us.
I have no way of 'resyncing' the folder...

Mail flow broken in my lab

I have a exchange 2013 lab. Internal and external mail flow were there but now suddenly it's not working. When I try to do internal relay it through me error "451 4.7.0 Temporary server error. Please try again later. PRX4"
Note: License got expired. Will it affect even
the internal mail flow???
Mailbox, Client Access
Version 15.0 (Build 516.32)
Standard Trial Edition
Licensed
Unlicensed
220 EXUM13.lyncnet.net Microsoft ESMTP MAIL Service ready at Fri, 26 Sep 2014 11
:43:21 -0600
ehlo lyncnet.net
250-EXUM13.lyncnet.net Hello [fe80::9044:afda:cf11:30ee%14]
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
mail from: [email protected]
250 2.1.0 Sender OK
rcpt to: [email protected]
250 2.1.5 Recipient OK
data
354 Start mail input; end with <CRLF>.<CRLF>
test mail from sivakumar
451 4.7.0 Temporary server error. Please try again later. PRX4
Please help!
Thanks
Funnyghost

2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,48,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,*,,"Some EHLO options between current hub and proxy target do not match. Non-matching options: Xrdst,
XAdrc, XExProps, . Continuing proxy"
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,49,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,>,X-EXPS EXCHANGEAUTH SHA256 ,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,50,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,>,<Binary Data>,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,51,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,<,235 <authentication information>,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,52,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,>,XPROXY SID=08D1A7CA03298D91 IP=::1 PORT=56130 DOMAIN=SmtpClientSubmissionProbe,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,53,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,<,250 XProxy accepted,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,54,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,>,AUTH LOGIN,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,55,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,<,334 <authentication information>,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,56,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,>,<Binary Data>,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,57,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,<,334 <authentication information>,
2014-09-26T21:24:32.669Z,Client Proxy Send Connector,08D1A7CA03298D92,58,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,>,<Binary Data>,
2014-09-26T21:24:32.747Z,Client Proxy Send Connector,08D1A7CA03298D92,59,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,<,235 2.7.0 Authentication successful,
2014-09-26T21:24:32.747Z,Client Proxy Send Connector,08D1A7CA03298D92,60,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,*,,Proxy session successfully set up for
[email protected]. Inbound session will now be blindly proxied
2014-09-26T21:24:32.747Z,Client Proxy Send Connector,08D1A7CA03298D92,61,[fe80::9044:afda:cf11:30ee%14]:56135,[fe80::9044:afda:cf11:30ee%14]:465,-,,Local
Funnyghost

Cannot send mail from Exchange 2013 to Exchange 2007

I have an
Exchange 2007server with all roles in the same server (Version:
08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
(full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
few articles on the Internet.
Any suggestions?

These two sentences are in conflict : "I can also send
internal mail
from Exchange
2007 to
Exchange 2013. But
the problem is
that I am unable
to send from Exchange
2007 to
Exchange 2013. "
Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

Exchange 2013 MB/CAS integration with legacy Exchange 2007 CAS/MB/Trans server

Hi All,
I have an existing running Exchange 2007 SP3 RU13 server acting as MB,CAS,Transport using a Barracuda SPAM for SMTP (MX Record is assigned to here), and a TMG2010 server performing all ActiveSync, Outlook Anywhere, and OWA connectivity.
I have built a new Exchange 2013 SP1 server that will (for the meantime) act as a MB & CAS server only.
I successfully migrated a testuser mailbox to the new EX2013 server from the EX2007 server. The problem is that once migrated, OWA and Outlook can't access the mailbox.
OWA form our URL gives the message: Outlook Web Access is currently unavailable. If the problem continues, contact technical support for your organization and tell them the following: No Client Access servers of the appropriate version can be accessed from
the Internet
If I run OWA from the EX2013 URL it works ok, but not for MBs on the EX2007 server.
I tested this configuration in a VM lab and it worked ok. All I had to do was move the mailbox, then run Outlook. Outlook automatically found the new server and opened the MB.
Basically what I need to do is move all our existing MBs from the old 2007 server to the new 2013 server. I want to continue to use the exisiting transport/CAS/EDGE services on 2007 without having to rebuild both the internal and external comunications
infrastructure at the present time.
How can I get the EX2013 server to act as the MB server for the EX2007 communications infrastructure?

Hi,
Please try to create a new user on Exchange 2013, and send/receive email via both Outlook and OWA to test whether the Exchange 2013 mail flow well.
If Exchange 2013 works well, please try to bypass the TMG on Exchange 2007 for a little while for testing.
Additionally, we can use CAS 2013 URL to proxy/redirect previous CAS, or publish both CAS 2007 and CAS 2013 to be internet facing server with separate URLs, as Ed suggested.
Thanks
Mavis Huang
TechNet Community Support

Establish mail flow from Exchange 2007 to Exchange 2013

I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

Was this question answered. We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped. Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
using "Custom Settings" - manually entered IPs for DNS in the Exchange Admin Center "DNS Lookups".
Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.
Any assistance will be greatly appreciated.

Migrating from Exchange 2007 to exchange 2013 ( special case )

Hello ,
what is the BEST scenario ( fastest , most efficient , most secure in terms of data loss ) , to migrate from exchange 2007 ( one server , all exchange roles installed on this server , 1200 mailbox ) , to exchange 2013 ?
knowing my environment needs to be connected to their mailboxes , 24/7 !
it's very frustrating .
and i have no clue even if this is the right place to post about this , if not please refer me as to where to post .
Also , All my domain controllers are 2008 .

It's fine to post your question here, and you are fine with Server 2008 Domain Controllers - that is a supported scenario.
If you haven't performed such an upgrade and you need to have 24/7 mailbox availability, I would seriously recommend you to duplicate the production environment on a test network and run through the upgrade at least once.
Most people neglect the Outlook clients requirements - they need to be updated and include several specific updates, which allow the automatic reconfiguration of internal clients. If you are preparing for this upgrade, you should be aware that all internal
Outlook clients switch to Outlook Anywhere. Clients that miss these updates will get connectivity problems.
Another common problem is the configuration of the Exchange URL - I mean the Exchange 2013 URL and the modified Exchange 2007 URL that will allow the co-existence. In your case, you definitely need to plan for co-existence - that includes requesting and
installing a new Exchange UCC (Multiple Domain Certificate) on both Exchange servers, configuring Split DNS (or preferably PinPoint DNS zones), and correct timing when replacing the existing Certificate on the Exchange 2007 server. Failure to configure the
correct URL (and it's quite easy to miss one, so triple check them) will get you in trouble.
Once you get through the switchover (switching the mail flow and Client Access through the Exchange 2013 server), move just a couple of test mailboxes and check the result.
Finally, if you are moving the Public Folders, make sure that the lock is really applied before you complete the process. Most people proceed right away and that get's the process stuck. If you can afford it (the mailboxes are already on the Exchange 2013
server at that point), just restart the Exchange 2007 server (after locking the Public Folders) and then complete the Public Folder migration.
Good Luck with the project!
Step by Step Screencasts and Video Tutorials

Exchange 2007 CAS Unable To Display 2013 Mailbox Free/Busy to Clients

Hi,
I'm in the process of migrating to Exchange 2013 from an Exchange 2007 backend. I have 2 2007 CAS servers in a Windows NLB named webmail.domain.com, and I'm having a problem with only a single one of those CAS servers being able to display the free/busy
information of a mailbox residing on a 2013 mailbox server. The other CAS works fine.
Both CAS servers are Exchange 2007 SP3. Both CAS servers have their virtual directories named webmail.domain.com/{vitual direction url}. I built both servers from the ground up and configured them at the same exact time performing the same steps
on each. My 2013 CAS servers are in a Windows NLB for mail.domain.com, and they have all their virtual directories named for mail.domain.com. These are separate entries in DNS. Other autodiscover services are working fine. I have most
traffic flowing Exchange 2013 now as well.
I've done compares on the virtual directories for each 2007 CAS, and they appear to be the same. If I bypass the NLB and just go directly to the casname01/owa, I see free/busy no problem. If I go to casname02/owa, then free/busy doesn't work
ONLY for 2013 mailboxes. It will display 2007 mailbox free/busy fine. To complicate matters, I still have a 2010 CAS in the environment from a failed O365 pilot.
Where can I look to begin to troubleshoot this? Thanks.

In the App log on the 2007 CAS, I'm seeing an Event ID 4002 from MSExchange Availability (below). This made me check my 2013 CAS NLB. It looks like it is one of the 2013 CAS servers in the mail.domain.com NLB that is causing this behavior. I
could still use guidance. Thanks.
Process 3576[w3wp.exe:/LM/W3SVC/1/ROOT/EWS-1-130366189751718750]: Proxy request IntraSite from Requester:S-1-5-21-2089814041-428609448-1854500012-56527 to https://mail.domain.com/EWS/Exchange.asmx failed. Caller SIDs: S-1-5-21-2089814041-428609448-1854500012-56527.
The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because
the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.128.13.38:443
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()
at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult, Object& internalAsyncState, Stream& responseStream)
at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.CompleteRequest(). The request information is ProxyWebRequest type = IntraSite, url = https://mail.domain.com/EWS/Exchange.asmx
Mailbox list = <NA-Bedford Adriatic Conference Room>SMTP:[email protected], Parameters: windowStart = 1/26/2014 12:00:00 AM, windowEnd = 3/9/2014 12:00:00 AM, MergedFBInterval = 30, RequestedView = MergedOnly
.. Make sure that Active Directory site/forest containing the user mailbox has at least one local Exchange 2007 server running Exchange Availability service. Turn up logging for MSExchange Availability service and test basic network connectivity.

Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
A. For local clients
You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

Exchange 2013 CAS-MBX / Exchange 2007 Edge Mail flow

Similar Messages

Maybe you are looking for