We have a CAS server (mail1, 10.1.0.26) and Mailbox server (mbx1, 10.1.0.25).  When I ran the update on the mailbox server, it failed with the following errors (see below).  The update completed successfully on the CAS server.  It appears I have a problem with receive connectors.  I really could use some help please.  Thank you. -Glen

Here are the results of the Get-ReceiveConnector PS script:

Identity                                               Bindings                                      Enabled
--------                                                --------                                        -------
MBX1\Default MBX1                             {0.0.0.0:25}                                True
MBX1\Client Proxy MBX1                       {10.1.255.26:25, 0.0.0.0:465}     True
MAIL1\Default Frontend MAIL1               {0.0.0.0:25}                               True
MAIL1\Outbound Proxy Frontend MAIL1  {0.0.0.0:717}                              True
MAIL1\Client Frontend MAIL1                 {0.0.0.0:587}                             True

Here are snippets of the failure results:

The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Client Proxy MBX1". A receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges.  Change at lease one of these settings.

The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Default MBX1". A receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges.  Change at lease one of these settings.

I have 3 new exchange 2013 physical servers, all 3 return this BPA critical error, see below - doesn't make sense.

Hi!

So I have been browsing through a lot of Exchange Server documentation, guides and best practice but I have not found (or misunderstanding) the CAS placement for my situation.

We are currently in the process of upgrading to Exchange server 2013. As we have an Exchange 2003 only deployment, we will first need to move to Exchange 2010 and get rid of all the Exchange 2003 servers and then move on to Exchange 2013. We have a single domain with 21 AD sites. 8 of these sites (Vessels at Sea) are connected by vSat the other 13 of these sites a remote offices with a more stable connection than vSat.

We want to have a MBX server at every site and what I get from the available documentation on the internet I will also need a HUB server per AD site. What I am not sure about is, do I also need a CAS server per site? What I get from this excerpt:"A new service was introduced with Exchange Server 2010 to allow these MAPI connections to be handled by the Client Access server. The RPC Client Access service provides data access through a single, common path of the Client Access server, with the exception of public folder requests, which are still made directly to the Mailbox server. This change applies business logic to clients more consistently, and provides a better client experience when failover occurs." (ref Understanding RPC Client Access.), is that I also need a CAS server per site.

Can somebody give me any definite insights in this one?

To summarize the question:
In a multi site AD with a MBX server per site, do I also need a CAS server per site?

Your help is much appreciated!

Regards,

Erik

I'm currently migrating AD Forest/Org A with mixed E2K3 (SP2) & E2K7 (SP1) into Separate AD Forest/Org B with E2013 SP1.  Most all MBs are still on 2K3.  SMTP Domain will not change so this will be a 'shared namespace' scenario.  Note that the new AD/Exch is a greenfield and trusts have been created/validated and DNS resolution via 2ndary zones on each side is working.

I’ve searched/dug reviewed and found all of the 2003-2013 KBs for handling the shared namespace but I think my scenario is not ‘standard’ because of the mixed source environment (maybe…)

SOURCE:

4 E2K3 servers – not true FE/BE config.

2 E2K7 Servers (1 CAS, 1 MBX)

TARGET: 

2 2013 CAS Servers – DNS Round Robin

4 2013 MBX Servers

Mail flow from 2013 to source org MBs (both 2K3 & 2K7) works fine via 'accepted domain', send connectors, etc.  However, my problem is with flow from 2K3/2K7 into 2013 target org.  When I reply back to the 2013 MB (or send to another known good in 2013), I get the 5.1.1 ‘e-mail account does not exist…’ NDR. 

I've modded the 2003 default recipient policy to make the shared namespace nonauthoritative for source org, assigned another domain as authoritative, & created the SMTP connector to 2013 for the shared domain namespace.  I also reset the shared namespace as the Primary SMTP in the default recipient policy due to the requirement that all new & existing users continue to be able to send/receive with our internet domain.

However, despite the org-level changes in 2K3, in 2K7 the shared namespace still shows up as authoritative.  Next, when I change the shared domain in 2K7 from authoritative to internal relay, the queues start filling up (either via the SMTP connector to 2013 or the outgoing internet queue).  Changing things back in 2K7 to authoritative allows the queues to empty out and mail to be delivered again.  Also, when I change the domain setting back in 2K7, the domain settings on the 2K3 recipient policies are reset back to authoritative as well!  

How do I handle this mixed/inconsistent configuration in my source/legacy environment?  Recipient policies have not been upgraded in the legacy environment to E2K7 yet, BTW.  Do I need to change things in both 2K3/7, or only manage things from one side?  If so, what and/or which one?  Since mail is being sent from 2013 into 2K3 (per the send connector) and arriving in both 2K3 & 2K7 mailboxes, is this even the issue?  I’m not sure where to go with this.

Thanks

John

Our Exchange 2010 Organization has Exchange servers deployed at multiple sites, AU, NZ and UK. 

We recently deployed a Exchange 2013 CAS/MBX server in AU site. Our OWA was cutover from the AU EX2010 CAS server to this EX2013 box. The OWA is still published as MAIL.CONTOSO.COM. The EX2013 server does not hold any mailboxes. 

After the cutover, we notice users with mailboxes on remote site Exchange 2010 servers are having problem to connect through Outlook Anywhere. OWA and ActiveSync work perfectly for those uses through MAIL.CONTOSO.COM which is hosted at AU site. However, AU mailbox Users does not have this problem. They can use Outlook Anywhere without any issues. Note their mailboxes are hosted on EX2010 server still.

I tried with TestExchangeConnectivity site and get RPC Proxy Ping failed error for NZ and UK mailbox users. In the mean time, on the Ex2013 server I see event source MSExchange Front End Proxy HTTP event 3005, it basic warns EX2013 has marked NZ and UK remote site EX2010 server as Unhealthy due to exception.

I then confirmed and tested with our network team that ports 6000-6005 and 443 between AU and NZ UK sites. There is no package been blocked or dropped and I can telnet to 6001 from AU EX2013 server to NZ and UK EX2010 servers fine.

I then notice people were mentioning about manually setting EXCH and EXPR value to msstd:mail.contoso.com as mentioned in this post http://social.technet.microsoft.com/Forums/exchange/en-US/728be9b1-4415-4df6-a997-5ecb9ded9a63/rpc-proxy-cant-be-pinged-20132010-coexistence-with-outlook-anywhere?forum=exchangesvrgeneral

But I suspect this is not relate to my case, as RPC Proxy works perfectly between the AU EX2013 and EX2010 server. 

Any suggestions?

Hi all, In order to get more free space in my Exchange Server 2010, I was thinking to delete a database after move all mailboxes that are in this database to office 365.

Is this a good idea?Because deleting logs is not enough for me, I need more free space. Which impact I will have if I do it after move all mailbox from this database to cloud?

Thanks so much!

This should be a relatively simple question. I've just set up the DAG on my new Exchange 2013 deployment, it spans two servers, MB1 and MB2.  Both are dual-horned, on both a replicator subnet and the LAN.  I notice that the 2013 DAG is automatically setup by default, so I want to make sure it's been setup optimally.  I'm going by this article:

http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx

My main concern is it looks like I should be seeing two DAG networks set up, as per this:

Enumerated DAG network settings for a multi-subnet DAG

But I'm only seeing a MapiDagNetwork in my list of DAG Networks.  Did it fail to install the ReplicationDagNetwork?  If so, what's the best way to go about fixing it?  Seems preferable to keep the automatic setup. 

----------- Ron E Biggs Network Administrator Entertainment Studios

Hi all. 

I'm a bit lost, it's my first exchange 2013 install and my first coexistence scenario. So I need help. 

I've got an existing Exchange 2007 SP3 CU 12 organization, with 3 servers : 

- Server38 and Server39 as Mailbox Server, CCR Cluster, virtual node isServer40

- Server41 as CAS Server. 

I want to migrate everything to Exchagne 2013 SP1 on Windows 2012 R2. I have 2 servers : 

- Server12 and Server13 are Multirole servers, CAS ans MBX. I have configured a DAG. It's working. 

To provide HA on CAS service, I put this in order : http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/

Clearly, I want my CAS Server to be accessed with mail.domain.com instead of Server12.domain.com or Server13.domain.com

So I configure Outlook Anywhere like this : "Set-OutlookAnywhere -InternalHostname mail.domain.com -InternalClientsRequireSsl $false"

Now, I don't really imagine how I can use this platform during coexistence. 

I want to set users on my new servers, but autodiscover is configured in DNS to point Server41. 

Users can access to their mails via OWA and Outlook. 

How can I configure autodiscover? Must I change autodiscover record in DNS to point to new servers or should I let it on Server41? 
How will Outlook work when I migrate one user to the new servers? Will I have to change config? 

Thanks

Hi Guys

Im planning to deploy a new domain Win 2012 and an Exchange server 2013, but I have doubts about the name for my domain, because of the SSL certificate.

Should I keep the domain.local convention name, domain.com or a subdomain like internal.domain.com convention.

I have this doubt because the SSL certificate cannot have the internal name for the autodiscovery.

Regards 

i installed the certificate from my exchange 2010 server and it was accepted as valid. it gave an error like in this link http://www.hsuconsulting.com/wildcard-ssl-certificate-exchange-2013-imap-and-pop-error/

but it was accepted as valid.

i changed ECP to connect as webmail.domain.com externally but no other changes. Now i get "The security certificate presented by this website was issued for a different website's address." whenever i try to open ECP.

I have a failing Exchange 2013 server.  I used database portability to move the failing server's data base to a new Exchange 2013 server.  This process essentially involves repairing the database (which was successful) and copying it to the new server and mounting it.  The copy of the database on the failing server is left in a dismounted state.  At the end of the portability process, the attributes of the users are updated so that their mailboxes are accessed from the database on the new server.

When I attempt to remove Exchange from the failing server, I am informed that the database contains "one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes, or arbitration mailboxes."  Using various get- powershell commands, I discovered that the Arbitration mailboxes still point to the old server.  (I don't have any public folders or archive mailboxes.)

I don't want to "move" the Arbitration mailboxes, because they should already exist on the new server's database.  So what do I do to get the Arbitration user accounts (I guess they are accounts) to point to the mailboxes on the new server?

More broadly, are there any other snags I'm going to run into while trying to decommission this server?

Migrating a customer to Exchange 2013 from SBS 2008.

Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.

The customer only has a single external IP address...

So what do I do for this external DNS of legacy.customer.com?

Hi,

we have three different mail domain hosted in different hosting companies, currently we need all mail domain should be work in exchange 2013. so we configured four servers 2 CAS server (RRDNS) 2 MB server with DAG, domains are hala.local hala.com esys.com ibas.com, hala.com is the main domain. we have 2 public ip for RRDNS. I have created three accepted domain and email policy for each domain groups. Here how can I create mx record for each what type of cert will purchase? What about internal DNS, do we need to create split dns for all domains?

1. A record to 213.x.x.11
2. A record to 213.x.x.12
3. 1Mx record mail.hala.com to 213.x.x.11
4. 2mx record mail.hala.com  to 213.x.x.12
5. Mx1 mail.esys.com point to 213.x.x.11/mx?
6. Mx2 mail.esys.com point to 213.x.x.12/mx?
7. Mx1 mail.ibas.com point to 213.x.x.11/mx?
8. Mx2 mail.ibas.com point to 213.x.x.12/mx?
9. One SAN cert with single domain name or all domain names what will be common name. if cert name is mismatched always users will get cert warning?. Is there any requirement for UC cert?

Thanks for Your support..

Regards

Riyatanu

hi,

Below are the details of issue I am facing:

1) No mail flow from EX2013 users to 2010

2) No mail flow from EX2010 users to 2013

3) If I make EX2013 primary server (Internet facing)

      a) Outlook connects

      b) Internet & Local works

      c) But OWA only connects to EX2013

      d) OWA EX2010 Users are reverted back to OWA login screen

      e) Users are repeatedly asked for password on IPhone but Androids work fine.

4) If EX2010 is Primary (Internet Facing)

      a) Outlook connects for EX2010 Users. All mail flow works

      b) Outlook Connects for EX2013 users but Inbox is not updated and Outlook says message sent whereas its in Outbox only

      c) EX2013 users have no access to OWA: ERROR: Server configuration change is temporally preventing access to your account.

Configuration details

1) EX2010 SP3 on Windows 2008R2

2) EX2013 SP1 on Windows 2012R2

Tried:

1) Rechecked all VDirs and authentications: Verified by 2 other admins

2) Created send & receive connectors on both servers with Exchange servers as Authentications & other servers IP included

3)Added all Host names, and FQDN and Updated SSL on both the servers.

Its been 3 weeks and I am pulling my hair out.... 

Anybody have any pointers or steps to resolve this issues.... will be very grateful

Thanks

BIKRAM

bikram

We recently migrated to exchange 2013. Since then, I'm working on getting the final bugs worked out. These are both related to the Unread Mail folder in Outlook 2010 Client.

Issue 1: All users effected:
Cannot delete a mail item (simply highlight and click delete) from the Unread Mail folder. We get the error:

"The item cannot be deleted. It was either moved or already deleted, or access was denied". 

If we go to the inbox and attempt to delete the item, no problem at all.

Issue 2: One user effected:
Items no longer show as read after they are opened.

Bonus Issue: Search folder seems slow and unresponsive.

A wise man is a fool, with a good memory.

We are running
- Exchange 2007 - a LOT of users and a LOT of PF
- Exchange 2010 ( currently very limited )
- Exchange 2013 - about 2000 users

The Exch 2010 environment was pretty much stood up and had 30 pilot accounts on it before we decided to go to Exch 2013 instead/ These account have since been migrated to Exch 2013, so it is currently VERY LIMITED use.

We have a large number of Public Folders in Exch 2007. We do not plan on using the Exch 2013 model of shared mailboxes, but are looking to create the Public Folders in the Exch 2010 environment so we can close down Exch 2007.

The bulk of my users are still on 2007, but I have a couple thousand already moved to 2013. All users can access the Public Folders on Exch 2007.

We have not created any Public Folders in Exch 2010 yet. Practically all the posts I read state to enable replication for the 2007 folders to get them to 2010, but what about NEW folders. If I create a new folder on Exch 2010, without configuring replication to 2007, will the Exch 2007 and Exch 2013 users be able to access it?

Tom

Hi,

I have a questions about cross forest mailbox moves.  I am running preparemoverequest.ps1 and then moving the mailbox cross forest successfully.  The problem is that I expected the move request to create a mail user with target address based on the specified "targetdeliverydomain" in the move mailbox command.

This works as expected when the AD account and mailbox are in the same source forest.  When the source AD account is in a separate trusted forest to the mailbox (linked mailbox) in an account/resource forest model there is no mail user created in the source after the mailbox move completes.

The concern is that the mailboxes still to be migrated will no longer see the moved mailbox(mail user) in the GAL of the source and be unable to query free busy, autodiscover etc.

The commands I am currently using are as follows:

prepare-moverequest.ps1 -remoteforestdomaincontroller sourcedc.source.local -remoteforestcredential $remotecredentials -localforestdomaincontroller targetdc.target.local -localforestcredential $localcredentials -targetmailuserou "ou=migrated,dc=target,dc=local" -verbose -identity testuser -mailboxdeliverydomain source.ex.local -linkedmailuser

new-moverequest -identity "testuser@xx.com" -targetdatabase "mailbox database 121434" -remotehostname "mail.exserver.local" -remotecredential $remotecred -targetdeliverydomain target.zxy.local -remoteglobalcatalog sourcedc.source.local -remote

Hopefully someone can assist?

Thanks

Hi

I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.

We have 800 mailbox in total

Our domain controllers are Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.

I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.

Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.

I currently only have 1 exchange server 2007, with all the roles on the one server.  I would like to keep that same as well with exchange 2013.

Thanks