Changes Ex2010 & Ex2013 DAG

What changes between Exchange 2010 DAG and EX2013 DAG .

Hello,
Exchange 2013 uses DAGs and mailbox database copies, along with other features such as single item recovery, retention policies, and lagged database copies, to provide high availability, site resilience, and Exchange native data protection. The high availability
platform, Exchange Information Store and Extensible Storage Engine (ESE) have all been enhanced to provide greater availability and easier management, and to reduce costs.
Exchange 2013 provides a 50 percent reduction in IOPS over Exchange 2010.
Please refer to the "Changes to high availability from exchange 2010" section and "Reduction in IOPS over Exchange 2010" section in the following article:
http://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
Cara Chen
TechNet Community Support

Similar Messages

Ex2010 Ex2013 - Outlook Anywhere client authentication

Hi,
I have an Exchange 2010 server with all roles installed and users mailboxes on it. Most users are domain-joined, but some are external 'home' users and connect via Outlook Anywhere.
I also have an Exchange 2013 server (again, all roles) which is mostly set-up and is in co-existence with Ex2010. I have moved one test mailbox onto this server. One issue is accessing Public Folders, which are still on the Ex2010 mailbox user. I get a password
prompt (which doesn't accept my password) and if I click cancel, I get an error "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available, etc, etc"
Other info
-My servers are fully patched and up-to-date and I'm using the latest Office service packs on Windows 7
-I have a split DNS (webmail.domain.co.uk points to Ex2013)
-I have no TMG
As I understand it, the problem may well be the difference between authentication methods on Ex2010 and Ex2013. I understand I need to use the same authentication method but herein lies my problem.
Get-OutlookAnywhere on Ex2010
ExternalHostName: webmail.domain.co.uk
ClientAuthenticationMethod: Basic
IISAuthenticationMethod: {Basic, NTLM}
Get-OutlookAnywhere on Ex2013
ExternalHostName: webmail.domain.co.uk
InternalHostName: webmail.domain.co.uk
ExternalClientAuthenticationMethod: Basic
InternalClientAuthenticationMethod: NTLM
ISSAuthenticationMethods: {Basic, NTLM, Negotiate}
If I change Ex2010 to NTLM (to match Ex2013) then it will break my home users.
If I change Ex2013 to Basic (to match Ex2010) then it will annoy my domain-joined users as they will constantly need to enter credentials.
So, I need to use NTLM internally, but Basic for external 'home' users.
Although currently domain-joined Outlook users on Ex2010 are configured for Outlook Anywhere, they connect over RPC, not HTTP, therefore the Basic setting on Ex2010 is not affecting them. However, I cannot migrate them to Ex2013 as the Public Folder issue is
a problem.
Comments and suggestions gladly welcome
Thanks.

Thanks
To answer your question, yes this has been done and my values are now
(from Get-OutlookAnywhere on Ex2013)
ServerName: Ex2010
ExternalHostName: webmail.domain.co.uk
InternalHostName: {empty}
ExternalCLientAuthenticationMethod: NTLM
InternalCLientAuthenticationMethod: NTLM
IISAuthenticationMethods: {Basic. NTLM}
ServerName: Ex2013
ExternalHostName: webmail.domain.co.uk
InternalHostName: webmail.domain.co.uk
ExternalCLientAuthenticationMethod: NTLM
InternalCLientAuthenticationMethod: NTLM
IISAuthenticationMethods: {Basic. NTLM, Negotiate}
What this has fixed is now when I test Outlook Anywhere, to a mailbox on Ex2010, from outside my domain, I can login successfully on the first attempt. Great.
What still doesn't work is accessing Public Folder which are on Ex2010 whilst using Outlook as a user with a mailbox on Ex2013. When I click on the Public Folder tree, I get a password prompt. Cancelling that, I get an error as described in my first post.
May I ask, is there a difference between
ExternalClientAuthenticationMethod and InternalClientAuthenticationMethod if I use split DNS?
Thanks.

Autodiscover fails in Ex2010/Ex2013 co-existence

Dear readers,
Currently we are in the preparation phase of the migration from Exchange 2010 to Exchange 2013. I have followed the Exchange Deployment Assistant, but unfortunately it does not work as expected.
I think i might have created an autodiscover loop and I don’t know how to fix it. Our setup
2x 2010CAS 192.168.2.10, 192.168.2.11
2x 2010MBX 192.168.2.20, 192.168.2.21 (DAG01)
2x 2013CAS 192.168.2.110, 192.168.2.111
2x 2013MBX 192.168.2.120, 192.168.2.121 (DAG02)
autodiscover.ourextdomain.com for internal clients point to 192.168.2.110
webmail.ourextdomain.com for internal clients point to 192.168.2.110
For now company policy does not allow making the Exchange services available externally. So all the clients only connect internally (on the corporate network or using VPN), also webmail is only accessible internally.
On all the CAS servers (meaning both 2010 and 2013) I have set the internal and external URL for every service (EWS, ECP, OWA, OAB, ActiveSync, Autodiscover, Outlook Any Where) to point to the same external domain: webmail.ourextdomain.com and autodiscover.ourextdomain.com.
(This is how I interpreted it from the Exchange Deployment Assistant).
If an internal Outlook 2010 user tries to use autodiscover to connect to his mbx on 2010, he gets httpstatus 401 and 401 errors and autodiscover to <url> failed 0x80004005, 0x800C8203 and is unable to successfully connect. An outlook 2010 user with a
2013 mbx can connect successfully.
If I change autodiscover.ourextdomain.com to point to 192.168.2.10, it is the other way around. The outlook 2010 user with 2010 mbx can connect, but the outlook 2010 user with 2013 mbx cannot.
My guess is that the configuration for the internal and external URLs is not correct, but I am not sure how to fix this. Does anyone have an idea? We have a third part wildcard certificate which I installed on all the CAS servers. This gave certificate errors
at first, for some reason clients were still trying to connect to a .local server address. This seems to be fixed after I re-created the Autodiscover vdirs.
As we have had a lot of issues with the certificate (a lot of calls at the service desk) I am a little less enthusiastic about
changing the internal and external URLs again, until I am a little more certain it is the right change to make.
Maybe useful info:
- Exchange 2010 did not have Outlook Anywhere enabled until I started following the Exchange deployment assistant
- Exchange 2010 has been an upgrade from Exchange 2003 (there are no Exchange 2003 servers anymore, as than I would not be able
to start the 2013 installation at all).
- Running Exchange 2010 SP3 ur7, migrating to Exchange 2013 cu6
Anyone any ideas or pointers in the right direction?

Hi,
1.What about configuring outlook 2010 manually for exchange 2010 mailbox users instead of using the auto discover service ? Just tell me whether it will get succeed or not ?
I really hope you mean for just one user to test it, because we are not going to manually reconfigure outlook for 3500 users! If i manually configure one user it succeeds, if I create a new profile using auto discover where exchange 2013 is the
CAS it fails if Exchange 2010 is the CAS is works.
2.Did you have the cas array configured on exchange 2010 ?If so what is the rpc client access attribute value for all the exchange 2010 databases?
Exchange 2010 DB's:
RpcClientAccessServer : cas.ourintdomain.local
Exchange 2013 DB's
RpcClientAccessServer : cas.ourintdomain.local
3.Please run the below mentioned command on exchange 2010 / 2013 cas servers and also share me the output.
get-ClientAccessServer -Identity CASServer | fl *internal*
https://autodiscover.ourextdomain.com/Autodiscover/Autodiscover.xml
4.make sure the names utilized in your environments are available on the SAN certificate .Most importantly we need to check the certificate is enabled for both exchange 2010 and 2013 services like pop,imap,iis,smtp and also certificate status should have to
be valid.
Get-ExchangeCertificate -Server "ClientAccess2010" | fl
EXCHANGE 2010 CAS O1
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcc
essRule}
CertificateDomains : {EX2010CAS01, EX2010CAS01.ourintdomain.local}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=DEX2010CAS01
NotAfter : 7/28/2019 12:33:20 PM
NotBefore : 7/28/2014 12:33:20 PM
PublicKeySize : 2048
RootCAType : None
SerialNumber : [intentionally removed]
Services : IMAP, POP, SMTP
Status : Valid
Subject : CN=EX2010CAS01
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {*.ourextdomain.com, ourextdomain.com}
HasPrivateKey : True
IsSelfSigned : False
Issuer : CN=GlobalSign Domain Validation CA - G2, O=GlobalSign nv-sa, C=BE
NotAfter : 12/18/2018 12:06:29 PM
NotBefore : 2/19/2014 9:52:02 AM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : [intentionally removed]
Services : IIS, SMTP
Status : Valid
Subject : CN=*.ourextdomain.com, OU=Domain Control Validated
Thumbprint : [intentionally removed]
EXCHANGE 2010 CAS O2
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcc
essRule}
CertificateDomains : {EX2010CAS02, EX2010CAS02.ourintdomain.local}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=DEX2010CAS02
NotAfter : 7/28/2019 12:33:20 PM
NotBefore : 7/28/2014 12:33:20 PM
PublicKeySize : 2048
RootCAType : None
SerialNumber : [intentionally removed]
Services : IMAP, POP, SMTP
Status : Valid
Subject : CN=EX2010CAS02
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {*.ourextdomain.com, ourextdomain.com}
HasPrivateKey : True
IsSelfSigned : False
Issuer : CN=GlobalSign Domain Validation CA - G2, O=GlobalSign nv-sa, C=BE
NotAfter : 12/18/2018 12:06:29 PM
NotBefore : 2/19/2014 9:52:02 AM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : [intentionally removed]
Services : IIS, SMTP
Status : Valid
Subject : CN=*.ourextdomain.com, OU=Domain Control Validated
Thumbprint : [intentionally removed]
EXCHANGE 2013 CAS O1
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {EX2013CAS01, EX2013CAS01.ourintdomain.local}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=EX2013CAS01
NotAfter : 11/20/2019 5:42:31 PM
NotBefore : 11/20/2014 5:42:31 PM
PublicKeySize : 2048
RootCAType : Registry
SerialNumber : [intentionally removed]
Services : IMAP, POP, SMTP
Status : Valid
Subject : CN=EX2013CAS01
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {WMSvc-EX2013CAS01}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=WMSvc-EX2013CAS01
NotAfter : 11/17/2024 4:03:29 PM
NotBefore : 11/20/2014 4:03:29 PM
PublicKeySize : 2048
RootCAType : Registry
SerialNumber : [intentionally removed]
Services : None
Status : Valid
Subject : CN=WMSvc-EX2013CAS01
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=Microsoft Exchange Server Auth Certificate
NotAfter : 10/23/2019 7:05:50 PM
NotBefore : 11/18/2014 6:05:50 PM
PublicKeySize : 2048
RootCAType : None
SerialNumber : [intentionally removed]
Services : SMTP
Status : Valid
Subject : CN=Microsoft Exchange Server Auth Certificate
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {*.ourextdomain.com, ourextdomain.com}
HasPrivateKey : True
IsSelfSigned : False
Issuer : CN=GlobalSign Domain Validation CA - G2, O=GlobalSign nv-sa, C=BE
NotAfter : 12/18/2018 12:06:29 PM
NotBefore : 2/19/2014 9:52:02 AM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : [intentionally removed]
Services : IIS, SMTP
Status : Valid
Subject : CN=*.ourextdomain.com, OU=Domain Control Validated
Thumbprint : [intentionally removed]
EXCHANGE 2013 CAS O2
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {EX2013CAS02, EX2013CAS02.ourintdomain.local}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=EX2013CAS02
NotAfter : 11/20/2019 5:42:31 PM
NotBefore : 11/20/2014 5:42:31 PM
PublicKeySize : 2048
RootCAType : Registry
SerialNumber : [intentionally removed]
Services : IMAP, POP, SMTP
Status : Valid
Subject : CN=EX2013CAS02
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {WMSvc-EX2013CAS02}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=WMSvc-EX2013CAS02
NotAfter : 11/17/2024 4:03:29 PM
NotBefore : 11/20/2014 4:03:29 PM
PublicKeySize : 2048
RootCAType : Registry
SerialNumber : [intentionally removed]
Services : None
Status : Valid
Subject : CN=WMSvc-EX2013CAS02
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=Microsoft Exchange Server Auth Certificate
NotAfter : 10/23/2019 7:05:50 PM
NotBefore : 11/18/2014 6:05:50 PM
PublicKeySize : 2048
RootCAType : None
SerialNumber : [intentionally removed]
Services : SMTP
Status : Valid
Subject : CN=Microsoft Exchange Server Auth Certificate
Thumbprint : [intentionally removed]
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule,
System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {*.ourextdomain.com, ourextdomain.com}
HasPrivateKey : True
IsSelfSigned : False
Issuer : CN=GlobalSign Domain Validation CA - G2, O=GlobalSign nv-sa, C=BE
NotAfter : 12/18/2018 12:06:29 PM
NotBefore : 2/19/2014 9:52:02 AM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : [intentionally removed]
Services : IIS, SMTP
Status : Valid
Subject : CN=*.ourextdomain.com, OU=Domain Control Validated
Thumbprint : [intentionally removed]
We are using a 3rd party wildcard certificate for all our CAS servers *.ourextdomain.com

What new in Exchange 2013 DAG

Hi Team,
What's the difference between Ex2010 & Ex2013 on DAG enviroment.

Hi,
The articles provided above are very helpful, one thing I like is that we can now use a third location for hosting the witness server. This is not recommended or not possible in previous versions of Exchange.
If you deploy the DAG's witness server in the third location, then the DAG can automatically failover databases to the other datacenter in response to a datacenter-level failure event. In Exchange 2010, we have to failover to another datacenter manually.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Mailboxes migrated to Exchange 2013 - some Outlook profiles do not auto-update

** EDIT WITH SIMPLIFIED QUESTION:
Should I be able to manually create a profile in my Exchange 2013 environment without knowing the
GUID@DOMAIN server name? When I specify the Ex2010 server name and Outlook Anywhere settings, the server name does not auto-resolve to the GUID as other threads suggest. I am curious whether others are able to manually
create a profile without knowing the GUID@domain.
Hi all,
Our computers have Outlook configured to automatically configure a profile without any intervention. The profile is pointing to Exchange 2010, which is still running in our environment with Exchange 2013. When a user logs into a computer and
launches Outlook for the first time, Outlook fails to connect and a "Cannot open your default-email folders" error occurs.
I have verified that the Outlook Anywhere settings are configured correctly.
If I delete the profile and create a new one using Autodiscover, everything works fine.
Occurs on all clients - 2007, 2010, 2013, fully patched).
To troubleshoot, I attempted to manually create a new profile. I supplied the Exchange 2010 server name, and configured Outlook Anywhere. When hitting "Check Name", the server name stays to Exchange 2010 (does not switch to
[email protected]). When I launch Outlook, the connection fails. Again, an autodiscovery succeeds.
From my reading, it appears that Outlook should be updating the profile with the new GUID server name when it attempts to connect. The RPCClientAccessServer setting on the Exchange 2013 databases points to the Exchange 2010 CAS Array names.
Any ideas?
Thanks for your hel

Thanks for the reply .
AutodiscoverInternalURI is pointing to the Exchange 2013 environment, and is working fine when auto creating the profile. The Test Autodiscover function returns the correct URL for the mailboxes. The problem comes when manually creating
a profile. Other threads indicate that a manually created profile should auto change the server name when the Check Name option is selected, but mine remains with the Ex2010 cas name listed on the database, and the creation fails.
However, if the user had previously connected to Ex2010 prior to the mailbox move, the profile successfully changes to Ex2013. Only during manual creation does it fail, which is a problem because our existing PCs are configured to create
profiles without autodiscover.

Receiving emails from outside

Hello,
I have a exchange 2010 server and two exchange 2013 exchange servers on a coexistence environment.
the ex2013 servers are using a single namespace via the F5 loadbalancer ( virtual IP).
all emails and everything is working fine. I am in a point to do a final cut over. we are sending/receiving emails behind a iron-port spam guard.
currently it seems like the ex2013 servers are receiving emails from outside the network( external) via the ex2010 server.
how can I make the ex2013 receive email from outside without going to ex2010?
I can send emails to outside world fine as I have a send connector to the spam-gaurd.
do I need to make a new receive connector? if so what IP should I use in the receive connector?
Please advice.
Thank you
Sham

Hi Thanks,
When I match settings as the ex2010 emails stop coming from outside and they are queued up in the ex2010. ex2013 is not receiving them.

Event ID 9877, Exchange 2010 SP3 RU4

On 2/19 I installed RU4 for Exchange 2010 SP3 on a server at a client's site. This is a single server with all the roles on it, with about 40-45 mailboxes. Ever since then, during the busiest hours of the day (around 7AM to 5:30PM or so), I get the
following event log error on this server:
Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          2/20/2014 6:58:49 AM
Event ID:      9877
Task Category: Content Indexing
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: Mailbox Database 0784353824
Error Code: 0x80043629
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeIS Mailbox Store" />
    <EventID Qualifiers="49198">9877</EventID>
    <Level>2</Level>
    <Task>46</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-20T11:58:49.000000000Z" />
    <EventRecordID>423922</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security />
</System>
<EventData>
    <Data>CISearch::EcGetRowsetAndAccessor</Data>
    <Data>Mailbox Database 0784353824</Data>
    <Data>0x80043629</Data>
    <Binary>5B444941475F4354585D00000E020000FFC8070000000000000300020000EBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C710100000008085C710100000008085C7101000000080BDCC101000000C00D4224010E7FAFFFFEBD410101B0000008B3B4010E7FAFFFFEBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C710100000008085C710100000008085C7101000000080BDCC101000000C00D4224010E7FAFFFFEBD410101B0000008B3B4010E7FAFFFFEBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C7101000000080D25560200F01048040008F6600000C00D25560200F01048040008F661B000000AD0C4010BFF9FFFFE3D400101B00000029D14010E7FAFFFFADC34010E7FAFFFF53BD00101B000000D25560200F01048040008F66E7FAFFFFD25560200F01048040008F6600000080D25560200F01048040008F6600000C00C5C14010EE030000715D4010EC030000D25560200F0104800B00AA671B000000543760201DFAFFFF0B005C0EE7FAFFFFD42160200F0104800B005C0EE7FAFFFFD25560200F0104800B005C0E00000080D25560200F01048040008F660000008023C3001000000C0023FC4010370A0000D25560200F01048040008F66E7FAFFFF</Binary>
</EventData>
</Event>
The frequency of these errors varies and it definitely seems to be related to the amount of traffic. Over the weekend it only occured about 5-10 times a day. For the past couple of days, it's been pretty constant about every 15 minutes or
so all day.
I've looked this up, but I've only found a few posts mentioning similar errors, all relating to earlier versions of Exchange 2010. Supposedly this problem was fixed in one of the rollups to SP1 or SP2, I think. I never saw these errors, though,
until the SP3 RU4 rollup. I haven't heard any complaints from users, but I'm concerned that this might escalate and start causing noticeable searching issues.
Any ideas would be appreciated.
Deb

Hi Deb,
We're getting the same error as you on Exchange 2010. We have exchange 2010 and exchange 2013 running in a coexisting environment. Since we applied Service Pack 1 for Exchange 2013, we've had nothing but issues!
I've tried the rebuild of the index catalogues by following these instructions:
http://ghousewin.blogspot.in/2012/08/not-able-to-search-in-owa-event-id-9877.html
This failed to resolve the issues too. We've rebooted the server, restarted all the search services and still nothing! We're pulling our hair out here!
The only thing I haven't tried is the prepareAD commands in this post:
http://social.technet.microsoft.com/Forums/exchange/en-US/7a4a7400-a582-4f95-9360-6d84e66e87ad/ex2010-2node-dag-search-in-owa-not-working-caused-by-eventid-9877-content-indexing-function
I'm unable to try this during the day as we have no testing
environment and would hate to mess the production environment up if this went wrong.
If you're able to try this during the day, would you let us know how it goes?
Many thanks,
Stephen

Changing a Network Interface in DAG Replication Network after going P2V

I have a DAG member suffering severe hardware failure so I have gone P2V with it. It's functioning fine, except that the DAG Network Interfaces have changed - The MAPI Interface was on "Local Area Network" on the physical server, and is now
on Local Area Connection 7 on the VM. However, the DAG settings still point to "Local Area Network" and will not let me change it. Same thing for the replication network.
I have lost redundancy due to this, so I need to get it repaired pretty promptly.
Removing and re-adding the subnet in the DAG network has no effect - it still references the old physical NIC instead of the new virtual NIC, despite the new virtual NIC having the same IP as the old physical NIC.

Try to change the network binding on the server
http://technet.microsoft.com/en-us/library/cc732472(WS.10).aspx
Try to delete the hidden network adapters as well.
Open Device Manager, from the File menu, expand the View and select the Show Hidden Devices option. This will enable and show any old un-used devices in the window
http://www.gfi.com/blog/how-to-remove-hidden-network-adapters-from-virtual-machines/
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Ex2007 - Ex2013 Migration - Change in Send Connector = Transport.ServerCertMismatch.Monitor

I am in the final stages of a 2007->2013 migration that has gone very well. I was just about to move my Send Connector over to the Exchange 2013 side when my monitors alarmed that "Transport.ServerCertMismatch.Monitor" had gone unhealthy.
There is not a whole lot of information out there, but I did find this in each of the MBX logs:
Microsoft Exchange could not find a certificate that contains the domain name mail.domain.com in the personal store on the local computer. Therefore, it is unable to support
the STARTTLS SMTP verb for the connector Internet e-mail with a FQDN parameter of mail.domain.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there
is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
I checked my SAN and I do have mail.domain.com in it. I also confirmed that the Send Connector was using mail.domain.com as its HELO/EHLO reply. I have cycled the service and that did not seem to help either. Mail will still flow in my
testing, but I do not like unhealthy statuses so I would prefer to fix it.
Thoughts?

Did you install and enable an SSL certificate with the "mail.domain.com" SAN on the Exchange 2013 CAS for the available Exchange services?
Normally, when migrating from Exchange 2007, you need to request a new SSL certificate which includes the legacy namespace in the SAN field and install it both on the new Exchange 2013 and the legacy Exchange 2007 servers.
Step by Step Screencasts and Video Tutorials

Mailbox move failure - EX2010 to 2013 - IExchangeFastTransferEx.SetProps failed ‎(hr=0x8004010f, ec=0)‎

Hi,
I've been having problems moving my mailbox from Exchange 2010 to 2013 as part of an upgrade I'm doing. I've moved a couple of other mailboxes without issues, and the account can move between different DAG groups on Exchange 2010.
The process does the initial move quite quickly, and then stalls when it gets to 95% going into a loop of retries for up to 5 hours before failing.
The essential error information is as follows,
Error: MigrationPermanentException: Error: MapiExceptionNotFound: IExchangeFastTransferEx.SetProps failed ‎(hr=0x8004010f, ec=0)‎
Request Username (40db3a16-4427-4690-bf7e-15db185c8e03) failed.
Error code: -2147221233
MapiExceptionNotFound: IExchangeFastTransferEx.SetProps failed (hr=0x8004010f, ec=0)
Context:
Operation: IMapiFxProxy.ProcessRequest
OpCode: SetProps
DataLength: 261
Operation: IMapiFxProxy.ProcessRequest
Operation: IMapiFxProxy.ProcessRequest
OperationSide: Target
Primary (40db3a16-4427-4690-bf7e-15db185c8e03)
OpCode: SetProps
DataLength: 261
Operation: ISourceMailbox.CopyTo
Operation: ISourceMailbox.CopyTo
OperationSide: Source
Primary (40db3a16-4427-4690-bf7e-15db185c8e03)
PropTags: [count:2, 0x360e000d(ContainerHierarchy); 0x360f000d(ContainerContents)]
I've tried a lot of trouble shooting and haven't found anyone with a similar problem via google etc, things I've done.
Tried different EX2013 MB stores
Created a 2nd exchange org admin account
Tried a domain admin account
Removed my Exchange archive
Cleaned up various folders\views\rules
reset the AD account ACL's
Checked out the mailbox via MFCMapi and purged several items.
Moved the mailbox via PS with the ignoresignature setting
I'd rather not export the mailbox to PST in case this happens to multiple accounts, it will also mess up recurring meetings etc as well.
Any thoughts?
Thanks
Jeff

Hi,
This is the output of the logfile, the formatting is not great but it essentially does the first part of the move, then repeats the final sync for about 4-5 hours until it gives up, I've removed most of it as it is just the same. the errors at the start
of the message are what appears in the event log on the MRS target server.
Unfortunately I can't see anything obvious in it.
I'd still like to persevere a little bit more but I'm rapidly running out of things to try. I don't want to recreate the mailbox if possible as there are meetings that were created by other people which would need to be recreated and I'm worried the
same thing happens elsewhere with someone who can't have the meetings recreated so easily.
I've only moved about 4 mailboxes so far, the others worked fine but I've got about ~2500 more to do, I was moving mine to test\move forward.
BTW, thanks for the tips Ilantz, just in case!
Thanks
Jeff
27/12/2013
10:28:42 [EX2013MBX] '' created move request.
27/12/2013 10:28:46 [EX2013MBX] The Microsoft Exchange Mailbox Replication service 'targetserver' (15.0.775.35 caps:3F) is examining the request.
27/12/2013 10:28:46 [EX2013MBX] Connected to target mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'EX2013MBStoreTest', Mailbox server 'targetserver' Version 15.0 (Build 775.0).
27/12/2013 10:28:46 [EX2013MBX] Connected to source mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'DAGStore02', Mailbox server 'sourceserver' Version 14.3 (Build 158.0).
27/12/2013 10:28:46 [EX2013MBX] Request processing started.
27/12/2013 10:28:46 [EX2013MBX] Source mailbox information:
Regular Items: 2324, 73.31 MB (76,872,795 bytes)
Regular Deleted Items: 1052, 3.213 MB (3,368,908 bytes)
FAI Items: 516, 0 B (0 bytes)
FAI Deleted Items: 41, 670 B (670 bytes)
27/12/2013 10:28:46 [EX2013MBX] Mailbox signature will not be preserved for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)'. Outlook clients will need to restart to access the moved mailbox.
27/12/2013 10:28:47 [EX2013MBX] Stage: CreatingFolderHierarchy. Percent complete: 10.
27/12/2013 10:28:47 [EX2013MBX] Initializing folder hierarchy from mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 127 folders total.
27/12/2013 10:28:47 [EX2013MBX] Folder creation progress: 0 folders created in mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)'.
27/12/2013 10:28:56 [EX2013MBX] Folder hierarchy initialized for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 127 folders created.
27/12/2013 10:28:56 [EX2013MBX] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
27/12/2013 10:28:56 [EX2013MBX] Initial sync checkpoint progress: 0/127 folders processed. Currently processing mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)'.
27/12/2013 10:28:59 [EX2013MBX] Initial sync checkpoint completed: 119 folders processed.
27/12/2013 10:28:59 [EX2013MBX] Stage: LoadingMessages. Percent complete: 20.
27/12/2013 10:29:04 [EX2013MBX] Messages have been enumerated successfully. 2926 items loaded. Total size: 74.57 MB (78,195,169 bytes).
27/12/2013 10:29:04 [EX2013MBX] Stage: CopyingMessages. Percent complete: 25.
27/12/2013 10:29:04 [EX2013MBX] Copy progress: 0/2926 messages, 0 B (0 bytes)/74.57 MB (78,195,169 bytes), 41/127 folders completed.
27/12/2013 10:32:46 [EX2013MBX] Copying messages is finished. Copying rules and security descriptors.
27/12/2013 10:32:47 [EX2013MBX] A corrupted item was encountered: Folder property ""
27/12/2013 10:32:56 [EX2013MBX] Initial seeding completed, 2926 items copied, total size 74.57 MB (78,195,169 bytes).
27/12/2013 10:32:56 [EX2013MBX] Stage: IncrementalSync. Percent complete: 95.
27/12/2013 10:32:56 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 0 deleted folders.
27/12/2013 10:32:56 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 0 changed folders, 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Stage: IncrementalSync. Percent complete: 95.
27/12/2013 10:32:57 [EX2013MBX] Final sync has started.
27/12/2013 10:32:57 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 1 deleted folders.
27/12/2013 10:32:57 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 1 changed folders, 0 changed messages.
27/12/2013 10:32:57 [EX2013MBX] Source mailbox information:
Regular Items: 2324, 73.31 MB (76,872,795 bytes)
Regular Deleted Items: 1052, 3.213 MB (3,368,908 bytes)
FAI Items: 516, 0 B (0 bytes)
FAI Deleted Items: 41, 670 B (670 bytes)
27/12/2013 10:32:57 [EX2013MBX] Stage: FinalIncrementalSync. Percent complete: 95.
27/12/2013 10:32:57 [EX2013MBX] Transient error MapiExceptionNotFound has occurred. The system will retry (1/10).
27/12/2013 10:33:31 [EX2013MBX] The Microsoft Exchange Mailbox Replication service 'targetserver' (15.0.775.35 caps:3F) is examining the request.
27/12/2013 10:33:31 [EX2013MBX] Connected to target mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'EX2013MBStoreTest', Mailbox server 'targetserver' Version 15.0 (Build 775.0).
27/12/2013 10:33:31 [EX2013MBX] Connected to source mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)', database 'DAGStore02', Mailbox server 'sourceserver' Version 14.3 (Build 158.0).
27/12/2013 10:33:31 [EX2013MBX] Request processing continued, stage IncrementalSync.
27/12/2013 10:33:32 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 0 deleted folders.
27/12/2013 10:33:32 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 0 changed folders, 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Stage: IncrementalSync. Percent complete: 95.
27/12/2013 10:33:32 [EX2013MBX] Final sync has started.
27/12/2013 10:33:32 [EX2013MBX] Folder hierarchy changes reported in source 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed folders, 1 deleted folders.
27/12/2013 10:33:32 [EX2013MBX] Content changes reported for mailbox 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)': 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Incremental Sync 'Primary (40db3a16-4427-4690-bf7e-15db185c8e03)' completed: 1 changed folders, 0 changed messages.
27/12/2013 10:33:32 [EX2013MBX] Source mailbox information:
Regular Items: 2324, 73.31 MB (76,872,795 bytes)
Regular Deleted Items: 1052, 3.213 MB (3,368,908 bytes)
FAI Items: 516, 0 B (0 bytes)
FAI Deleted Items: 41, 670 B (670 bytes)

Migration Planning: What will happen with clients when changing namespace?

Hello,
We are planning to upgrade our EX2010 enviroment to EX2013.
Sadly our namespace in EX2010 is right now owa2.domain.com. The name owa2 is coming from last migration between ex2003 and ex2010. I'd like to remove this minor flaw if possible.
But what will happen with all the clients and mobile devices which are right now bound to owa2.domain.com? Is it possible to change the name back to owa.domain.com without manual interaction with the clients?
Kind Regards

Hi ,
Based on my knowledge for services like pop,imap and active sync we need to have the manual interaction.Without manual intercation we cannot achieve this.
Same time we need to have the new name on the SAN certificate .
For owa users you can simply communicate the new url via email and then for internal outlook and external outlook connectivity we need to repair the profiles to force the autodiscover service to fetch up the new name.On my experience most of the times repair
will not help.So again your only hope would be reconfiguring the existing profiles.
Note : Most importantly before renaming the host A record on the external and internal dns all you need is to reduce the TTL value for the existing host A record on the name owa2.domain.com.So
that external and internal clients will not have the dns cache for a long period.
Anyhow we will wait for some expert inputs on this case.Because their ideas might be good and different than me.
Thanks & Regards S.Nithyanandham

Rpcclientaccess value blank on Active DAG member - normal?

Hi,
I decomissioned a Ex2010 server after moving all the mailboxes over to a new server in the same site a few weeks previously. Exchange was un-installed with no issues and no refernces were left in AD.
Now, even though the mailboxes are accessible in Outlook on the existing profiles, I'm unable to set up a new profile as it defaults to the old server name, which no longer exists. Also, the users (thankfully only 3 on this DB) Blackberrys have stopped working.
Done some troubleshooting and found that the BES is still seeing the old FQDN for these users. Upon checking the mailstore on the server, I found that its LegacyDN shows the old FQDN and that RcpClientAccessServer is blank. This mailstore is the active member
of a DAG set up after the move so, it is normal for this to be blank?
If not, would setting this to the correct FQDN help rectify the profile and BB resolver issue or would I need to change the LegacyDN as well?
The Server is running Ex2010 SP1 with all roles (Its a small remote office so this is suffices).
Any help would be appreciated.

Hi,
As far as I know, the RPCClientAccessServer value is established when the database is created.
For more information about the basic rules used for determining the value, you can refer to the partition named configure your mailbox database in the following article:
http://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx
Thus, it’s not normal for the value to be blank.
We can try Lrok’s suggestion to set the value.
Please note that we should recreate the profile after we change the value to ensure client connectivity.
Best regards,
Angela Shi
TechNet Community Support

Updateable Snapshot changes not getting propagated

Hi,
I am using Oracle 8.1.7 with Updateable snapshot replication. When I do a dbms_snapshot.refresh as the repadmin user from the snapshot site, the changes I made to the table I am refreshing are not pushed to the master site. Also, the update is actually overwritten by the value that exists on the master site.
Here is the actual refresh call sql:
EXECUTE dbms_snapshot.refresh('scpa.dag', 'F', NULL, TRUE, TRUE, 1, 0, 0, TRUE);
What table can I look in to see whether or not my update on the snapshot site is queued.
I get no errors when I do the refresh.
Thanks,
Chris

Try check deferror view on master site. When you call refresh procedure you set parameter refresh_after_errors to True, so there can be same unresolved replication conflict. In DBA studio it is tab Errors for node
DB->Replication->Administration
If there are no record in deferror on master site, check if you snapshot is a member of snapshot group. If not changes is not propagated.

Background image path changes in Template

I have a template I've created, but whenever I attempt to
create a new page from that template the path to the background
image changes automatically causing it to disappear.
The template displays this path:
body {
background-image: url(../img/bg.gif);
background-repeat: repeat-y;
background-position: center;
background-color: #E8F1FA;
While the page created from the template shows this path:
body {
background-image: url(file:///B|/Web
Development/website/img/bg.gif);
background-repeat: repeat-y;
background-position: center;
background-color: #E8F1FA;
What is causing this? Thanks in advance.

Answered on DW forum.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"logicore" <[email protected]> wrote in
message
news:gecn6f$dag$[email protected]..
>I have a template I've created, but whenever I attempt to
create a new page
> from that template the path to the background image
changes automatically
> causing it to disappear.
>
> The template displays this path:
>
> body {
> background-image: url(../img/bg.gif);
> background-repeat: repeat-y;
> background-position: center;
> background-color: #E8F1FA;
> }
>
> While the page created from the template shows this
path:
>
> body {
> background-image: url(file:///B|/Web
Development/website/img/bg.gif);
> background-repeat: repeat-y;
> background-position: center;
> background-color: #E8F1FA;
> }
>
> What is causing this? Thanks in advance.
>
>
>

Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine (external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Send Connectors are the default ones created during install. Receive connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
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 email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for many hours with no progress.
I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine.
Incoming mail from external senders is also fine. -
external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Receive Connectors are the default ones created during install. Send connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
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 email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for several days with no progress.
I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
Even more info - Further troubleshooting -
I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/
The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
when you domain name is apple.com - But through extensive research I still can't resolve the issue.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Changes Ex2010 & Ex2013 DAG

Similar Messages

Maybe you are looking for