Exchange 2010 and Powershell v3 Issue

I decided to take the plunge pray and install powershell v3. I like it so far but I am having a few problems. One problem occurs when running the search-mailbox cmdlet. It starts to run and as soon as it seems like it's finished my powershell windows closes
arbitrarily. Event ID 4999 show in the application log. Same with ISE.
Watson report about to be sent for process id: 3480, with parameters: E12, c-buddy-RTL-AMD64, 14.02.0247.005, PowerShell_ISE, unknown, M.E.D.S.N.PropertyDefinitionSets.BuildWellKnownSets, System.TypeInitializationException, b3a, unknown.
ErrorReportingEnabled: False
- System
- Provider
   [ Name] MSExchange Common
- EventID 4999
   [ Qualifiers] 16388
   Level 2
   Task 1
   Keywords 0x80000000000000
- TimeCreated
   [ SystemTime] 2012-10-03T18:07:40.000000000Z
   EventRecordID 31189
   Channel Application
   Computer computer.domain.local
   Security
- EventData
   3480
   E12
   c-buddy-RTL-AMD64
   14.02.0247.005
   PowerShell_ISE
   unknown
   M.E.D.S.N.PropertyDefinitionSets.BuildWellKnownSets
   System.TypeInitializationException
   b3a
   unknown
   False
Another problem im having is warning messages that show when running some cmdlets before they actually run. They are always the same so far.
below is the warning...
WARNING: The cmdlet extension agent with the index 0 has thrown an exception in OnComplete(). The exception is:
System.TypeInitializationException: The type initializer for
'Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary' threw an exception. ---> System.NotSupportedException:
Not supported field(MailEnabled) type(Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition).
   at Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary.PropertyDefinitionSets.BuildWellKnownSets()
   at Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition.TryFindEquivalentDefinition(PropTagKey key, Boolean
isCustom, PropType type, TypeCheckingFlag typeCheckingFlag, PropertyTagPropertyDefinition& definition, Boolean&
createNewDefinition)
   at Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition.InternalCreate(String displayName, PropTag propertyTag,
PropertyFlags flags, TypeCheckingFlag typeCheckingFlag, Boolean isCustom, PropertyDefinitionConstraint[] constraints)
   at Microsoft.Exchange.Data.Storage.PropertyTagCache.InternalPropertyDefinitionsFromPropTags(TypeCheckingFlag
propertyTypeCheckingFlag, MapiProp mapiProp, StoreSession storeSession, PropTag[] propTags, Int32& resolvedPropertyCount)
   at Microsoft.Exchange.Data.Storage.RecipientTable.GetRecipientPropertyDefinitionsFromMapiTable(Boolean&
originalColumnsChanged)
   at Microsoft.Exchange.Data.Storage.RecipientTable.BuildRecipientCollection(Action`2 recipientCollectionBuilder)
   at Microsoft.Exchange.Data.Storage.CoreRecipientCollection..ctor(ICoreItem coreItem)
   at Microsoft.Exchange.Data.Storage.CoreItem.Microsoft.Exchange.Data.Storage.ICoreItem.GetRecipientCollection(Boolean
forceOpen)
   at Microsoft.Exchange.Data.Storage.CoreItem.GetRecipientCharsetDetectionData(StringBuilder stringBuilder, Boolean
isComplete)
   at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.BuildCodePageDetector(MemoryStream& cachedHtmlBody)
   at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.DetectCpidWithOptions(Charset userCharset, MemoryStream&
cachedHtmlBody)
   at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.SetCachedBodyDataAndDetectCharset(Char[] cachedBodyData, Charset
userCharset, BodyCharsetFlags charsetFlags)
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.CalculateCharset()
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.OnBufferFull()
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.CloseDetectorConversionStream()
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.Flush()
   at Microsoft.Exchange.Data.TextConverters.ConverterEncodingOutput.Flush()
   at Microsoft.Exchange.Data.TextConverters.Internal.Text.TextCodePageConverter.Run()
   at Microsoft.Exchange.Data.TextConverters.Internal.Text.TextCodePageConverter.Flush()
   at Microsoft.Exchange.Data.TextConverters.ConverterWriter.Flush()
   at Microsoft.Exchange.Data.TextConverters.ConverterWriter.Dispose(Boolean disposing)
   at System.IO.TextWriter.Close()
   at Microsoft.Exchange.Data.Storage.BodyTextWriter.<CloseWriter>b__11()
   at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, LocalizedString exceptionString,
CtsCall ctsCall)
   at Microsoft.Exchange.Data.Storage.BodyTextWriter.CloseWriter()
   at Microsoft.Exchange.Data.Storage.BodyTextWriter.Dispose(Boolean disposing)
   at System.IO.TextWriter.Dispose()
   at Microsoft.Exchange.ProvisioningAgent.MailboxLoggerFactory.XsoMailer.Log(AdminLogMessageData data, LogMessageDelegate
logMessage)
   at Microsoft.Exchange.ProvisioningAgent.AdminLogProvisioningHandler.OnComplete(Boolean succeeded, Exception e)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.OnComplete(Task task, Boolean succeeded, Exception exception)
Exchange 2010 Version 14.02.0318.002
Problems occur on a Win7 client. The only thing that has changed was a powershell v3 install.
current powershell version shows version 3
any ideas?

Powershell v3 is not (yet) supported with Exchange 2010:
http://technet.microsoft.com/en-us/library/ff728623.aspx
Alexei

Similar Messages

Exchange 2010 and iphone calendar sync issues

Hey,
I know this question has been asked plenty of times before and just need a straight resolution. We have just migrated our environment to Exchange 2010 and the major issue is that when an event is created in Outlook 2011 it is not always showing up on their iphone and also vis versa. Is their a resolution to this problem so I can implement it in an emergency change. Thank you for all your help!

Here let me explain the scenario again any user who logs in to exchange from outlook working fine password not expired and he has iphone active sync working no issues , now while all devices are working when he starts his ipad after a week or so when he
opens his email on ipad it prompts the password on ipad and same time on iPhone , he does not want to enter the password and wants a technical justification , I told the user something to do with Exchange 2010 sp2 and ios 7 ,but that is invalid justification
. if you have any other valid justification please let me know. or a solution to this issue. user wants to login without any password prompt while the password is saved in device and not expired , is there any feature in Exchange 2010 sp2 that would recognize
how many days device has not logged it and would force to enter the password.

Exchange 2010 and 2003 Co-Existence Help

Hi All,
Hopefully someone out there can help me out.
As the subject says i have exchange 2010 and 2003 in a co-existence mode. I have configured public folder replications and plan to use the following guide to move the public folders:
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
I was about the use the MoveAllReplicas.ps1 powershell script when I had the idea to dismount the legacy (2003) public folder mail store as a test to ensure the public folders had replicated. I noticed under the 'Queues' of the legacy exchange emails were queuing
up withing 'Messages awaiting directory lookup'.
All other mail stores were dismounted, as a test I mounted a database (non public folder), did a force connection and refresh. All the emails disappeared from this list.
So my questions are:
1. Why would my exchange 2010 sever still be routing emails via the legacy server?
2. Why would the legacy exchange require a mailstore to be mounted for mail flow to work coming from the 2010 server?
Thanks

Thanks for the feedback.
The issue I am facing is that the emails I am seeing queued are not related to the public folder replications. Emails for the public folder replications normally have a subject line of: 'Backfill' or 'Folder Content'.
When all mail stores are dismounted on the legacy server some of the outbound emails sent by users who reside on the primary server (2010) are being sent to the legacy server. I can then see these emails queued and they will not be sent until a remount at
least one mail store.
E.g. All mailbox stores are dismounted on the legacy exchagn, John Smith's account is located on primary exchange (2010). John sends an email and I see it stuck in the queue on the legacy server 'Messages
awaiting directory lookup'.
NOTE: This does not happen for all users, It seems to happen at Random.
I also attempted to fix the issue by creating a new 'Send Connector' with a lower cost and defining the 'Source server as the primary server (2010)
So the question still remains why are some outbound emails still being sent out via the legacy server even though these users are on the primary exchange?
With regards to the public folders, I used the following to add the replicas between the legacy and primary exchange:
.\AddReplicaToPFRecursive.ps1 -TopPublicFolder “\” -ServerToAdd “Exchange2010″
When i dismount the public folders all the public folders are accisable via the 2010 server so it seems the replications have worked.
Would the above command not have added the replicas to all the public folders including the system public folders?

Outlook 2013/Exchange 2010 Free/Busy access issues.

Good Day Everyone,
I am running a Win 2008 R2 environment with Win7 users, using Exchange 2010 and Outlook 2013. Last week my users started experiencing issues with being able to view Free/Busy in the Calendar for any other user. I have checked past issues with this with patches
KB 2837618 and KB 2837643. Neither patch is showing as installed and I have tried a nummber of the suggested fixes offered for that issue to no avail. OWA seems to be working just fine.
Our Outlook version is: 15.0.4605.1003
I need a fix for Outlook users and since I havve 140 users, individual fixes are a not realistic option.
Any assistance would be greatly appreciated.

Hi,
Please test if Out of Office feature works well in Outlook. If Out of Office doesn't work either, it should be Autodiscover related.
Once Autodiscover has not been configured properly, the Free/Busy information may not display correctly. If you are also seeing issues with Out of Office assistant, we may assume that you haven’t correctly setup Autodiscover, since these two symtoms are
common when Autodiscover is not configured correctly.
To verify that, please test Outlook Autodiscover Connectivity:
http://technet.microsoft.com/en-us/library/bb123573.aspx
We can also learn Configure Exchange Services for the Autodiscover Service from:
http://technet.microsoft.com/en-us/library/bb201695.aspx
Regards,
Melon Chen
TechNet Community Support

Microsoft Exchange 2010 and Outlook 2013

My colleagues computer suddenly crashed yesterday and it wouldn't restart without a system restore.
Now when we try to open up Outlook it says that you must connect to Microsoft Exchange at least once before you can usse your Outlook Data file (.ost)
Also The PC has lost the trust relationship on the domain
We have exchange 2010 and the servers OS is Microsoft Windows Small Business Server 2011 and the Client PC is running off of Windows 8.
Can you please help me resolve this issue?
kind regards
Steve Bradshaw
[email protected]

It might be possible that the MAPI key (which enables Outlook to synchronize with Exchange) has been deleted due to the System crash. So, in order to establish the connection, you need to Reconnect the OST file to the original MAPI profile and then reconnect
then MAPI profile to Exchange Server.
If the above method fails to resolve the issue, then the best option for you would be to take the help of any professional OST to PST Conversion Software, which will help you to Extract data from your OST file and convert it to PST file which you can import
back to your Outlook to establish the connection with Exchange Server again.
You can check this
presentation for more info.

Single name space in between Exchange 2010 and 2013

Hi,
In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
couldn't be created. The error message is Access is denied. HResult = -2147024891"
Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
Thanks,

Hi,
See the below brief:
User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
Go through the full blog for better understanding of the redirection.
Client Connectivity with Exchange 2013
Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
Configuring DNS includes the following:
Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
DNS servers.
NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Who has full access on all mailboxes in Exchange 2010 using Powershell ?

Greetings,
Could you please tell me how can i know Who has full access on all mailboxes in Exchange 2010 using Powershell ?
Thanks.
Redouane SARRA

This is going to depend greatly on WHICH inherited permissions you plan to delete - there are some that you can never delete if you want the system to function properly. Now, that being said, let's look at some example permissions. First, here
are some permissions on a standard mailbox:
Identity             User                 AccessRights
IsInherited Deny
users.corp.... USERS\btwatcher    {FullAccess}
False       False
users.corp.... USERS\svcactAdmin {FullAccess}
True        False
users.corp.... CORP\Domain Ad... {FullAccess}
True        True
users.corp.... CORP\Enterpris... {FullAccess}
True        True
users.corp.... CORP\Organizat... {FullAccess}
True        True
users.corp.... CORP\adminact    {FullAccess}
True        True
users.corp.... CORP\esswin       {FullAccess}
True        True
users.corp.... USERS\svcactEncase {FullAccess}
True        False
users.corp.... CORP\Exchange ... {FullAccess}
True        False
users.corp.... NT AUTHORITY\SYSTEM {FullAccess}
True        False
As you can see, the first is not inherited. All others are, and two are from service accounts (svcact...). Also, some are Exchange system permissions, some are denies, and some are just administrative accounts. Once you determine which
you wish to remove, the SIMPLEST way to set the permissions you want is to open the account properties in ADSIEdit, and go to the Security tab. Here, click the Advanced button and find the inherited permission you wish to remove. ADSIEdit will
show where the permission is inherited from - you will need to go to that container to remove the inherited permission. You can also grant inherited denies at the same level(s).
Now, something you will need to understand is that if you hope to remove permissions granted to domain administrators, the system will replace them - these permissions are required by the system and can't be modified permanently.

Exchange 2010 and iOS 7

I am having multiple problems across multiple devices in Exchange 2010 SP2 and devices that upgraded to iOS 7. I have reset all the settings and re-added the accounts. Any other solutuons for this issue that apple swears is not a bug in the iOS?

I am running Exchange 2010 and have iOS7 on my phone, and have not seen any problems. My phone is not managed by configuratior.
What problems are you having?

Error synchronizing folder [8004010F-501-8004010F-0] - Exchange 2010 and Outlook 2010, multiple users get dozens of these per day

15:27:30 Synchronizer Version 14.0.6025
15:27:30 Synchronizing Mailbox 'abc xyz'
15:27:30 Error synchronizing folder
15:27:30
[8004010F-501-8004010F-0]
15:27:30
The client operation failed.
15:27:30
Microsoft Exchange Information Store
15:27:30
For more information on this failure, click the URL below:
15:27:30
http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=8004010f-501-8004010f-0
15:27:30 Done
kbj

Hi,
Please try below steps:
- Remove all organizational forms libraries (subfolders under EFORMS Registry) if they are not needed, and re-create the Outlook profile of affected users.
- Alternatively, if the organizational forms libraries are needed, remove the replica from Exchange 2010 and re-add it
Best Regards!

Exchange 2010 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
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! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
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! Off2work

Mail, Exchange 2010, and certificates

Hi.
The company I work for just upgraded their Exchange server to 2010 and all of a sudden my email account in Mail doesn't work anymore. In sheer desperation I tried to connect using Microsoft Outlook and the only way that I could create an account there was by submitting my certificate before entering my email account credentials. I get the feeling that this might be a kind of setting on the server side that someone turned on when we were transferred to Exchange 2010.
In Mail, when I try to set up my Exchange account there is no way of submitting my certificate, or am I missing something? If not, does anyone know a way around this (by associating Mail with my certificate somehow – I don't know...)
Many thanks in advance!
/Cristian

I added back the send connector on the 2010 exchange. everything still works fine since I still have the send connector on the 2003. However...
I connected through telnet to server2 (the exchange 2010) and was able to mail internally. however I couldn't send mail externally, it gives me a "cannot relay" error when I enter my rcpt to:... command.
I am guessing that this may be the reason why the queue is not emptying itself through that send connector.
Anything else I could try to test my "send connector" on the 2010 exchange?

Exchange 2010 and RMS

Hello Team,
We are running Exchange 2010 and RMS with Autonomy app which archives older than 30 day emails.
Parent company is in Tokyo, all incoming email goes through them and then via a hub transport service delivers email to North America. For some reason, emails are encrypted and the Archive app cant get to them.
I just want to find how to proceed further and what to do to exclude emails to North America from it.
Any suggestions would be appreciated !
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi Binu
I have written one for Exchange 2013
http://exchangequery.com/2014/08/12/steps-to-configure-irms-in-exchange-2013/
Its the same for Exchange 2010 as well
Also you can follow the below article for references
https://technet.microsoft.com/en-us/library/dd351035%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
http://www.msexchange.org/articles-tutorials/exchange-server-2010/compliance-policies-archiving/rights-management-server-exchange-2010-part5.html
Remember to 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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Primary mailbox (on Exchange 2010) and Personal Archive (on Exchange 2013), possible?

Current environment is Exchange 2010 SP3 RU5 supporting 4,000 Users. Client estate is Outlook 2010 SP1 going on SP2.
We're pulling our Archiving solution away from 3rd party and back into Exchange. Implementing a new set of Exchange 2010 Servers (old DAG or in a new Archive DAG) would be easy. But is there Exchange 2013 stepping stone potential?
Can the Archive DAG / Archive mailboxes be on 2013? i.e. for any given User, leave their primary mailbox on Exchange 2010 and create new Archive mailbox on 2013.
I want to avoid implementing 2010 Archive Servers and then go 2013 Archive 6 months or a year later.
This article suggests 'no':
http://technet.microsoft.com/en-gb/library/dd979800(v=exchg.150).aspx
"Locating a user’s mailbox and archive on different versions of Exchange Server is not supported."
I've found little info but the odd statement here / there.
Is this the latest position? Is it that cut & dry? Anyone tried it? Why won't it work (or will it but it's not supported)?
Thanks!

<I had a response from MS>
Below is a summary of the case for your records:
Symptom:
=============
Is it possible to implement a 2013 environment to host the Archive mailboxes? i.e. for any given User, their primary mailbox is on Exchange 2010 and their Archive
mailbox is on 2013.
Resolution:
=============
It’s not supported to have a user’s primary mailbox reside on an older Exchange version than the user’s archive. If the user’s primary mailbox is still on Exchange
2010, you must move it to Exchange 2013 before or at the same time when you move the archive to Exchange 2013.
http://technet.microsoft.com/en-us/library/jj651146(v=exchg.150).aspx
as per the repro in our lab, having the archive mailbox in higher version of exchange would fail with the error above
<the scenario isn't completely relevant, looks like he's trying to put the Primary on 2013 and not the Archive, no matter, we've established there are problems, question is whether they are looking into this area / to patch, they go on...>
At this point in time we don’t have a conformation from the product team, if the above would change in the future exchange versions.
<MS did say on the call that they were not looking at fixing it, naturally this isn't a "never", as per previous statement - they can't commit 100% to the future, but they've provided me the answer - they are not currently looking at resolving/providing
this as a migration scenario, end.>

Mail is Slow between Exchange 2010 and 2013 During Co-Existance Transition

Hello,
I recently migrated from a single Exchange 2003 server to a single Exchange 2010 server
I am now trying to Migrate from Exchange 2010 to Exchange 2013.
I have a test user on Exchange 2013, and Internet Mail works fine and quickly both inbound and outbound.
However, when I try and send between a 2010 user to my 2013 user, delivery takes around 10 minutes.
On the 2013 server I see health check messages, and my 2010 user's message stuck in retry status. The messages eventually clear and the mail is delivered. Any ideas what is causing this delay?
In terms of connectors I have all the defaults. And I created 1 for internal relays from devices. Which works fine.
I have two Exchange 2013 servers configured in a DAG, but I don't have a load balance in place as of yet. So only server 1 is being accessed as the CAS.
Thanks

Hi,
According to your description, the mail flow is slow only between Exchange 2010 and Exchange 2013 server. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if there are multiple NICs on your Exchange servers. And you can refer to the following thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/66f0629f-21fb-444b-b3f1-99ed8a4f52b2/slow-mail-flow?forum=exchangesvrsecuremessaging
We have ONLY 1 network adapter, but if we select "All network adapters" instead of Hyper-V, we will get delays.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2010 DAG netowrk replications issues - Causing database copies to be disconnected and resynchronizing.

My
environment is as follows.<o:p></o:p>
We have 3 exchange 2010 servers.<o:p></o:p>
EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
The dag is configured to to communicate to all three.<o:p></o:p>
The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
DREX1 is located in another network. It is in another building connected via vpn. The ip
for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
(These are not the actual address, but the concept is similar)<o:p></o:p>
The dag network configuration is as follows.<o:p></o:p>
DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
and 192.168.100.52<o:p></o:p>
DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
160.100.3.51 and 160.100.3.52<o:p></o:p>
Last Friday, 3/7/14 something happened.<o:p></o:p>
To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
full backups of our exchange databases when I reviewed the backup jobs, the
exchange database backups using dpm2010 failed all weekend long starting at
11:00pm that Friday.<o:p></o:p>
The issue that occurred was that the database copies went to a status of Disconnected and
Resynchronizing, and after about 30 seconds, the status would show
Resynchronizing.<o:p></o:p>
All attempts to resolve this with the research methods failed. Deleting the
logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
Creating a new database worked, creating a database copy worked, but seeding the copy
failed. All with the same pattern, a status of Disconnected and
Resynchronizing, and after about 30 seconds, and the status would show
Resynchronizing.<o:p></o:p>
The database was mounted on EX2, and seeding to EX1
DREX1 has no issues.<o:p></o:p>
All the DAG networks were in a good status, all Green and all up. I could ping from
EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
fix, but after rebooting EX2, it all resolved. It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
was all healthy.<o:p></o:p>
We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
issue occurred; a status of Disconnected and Resynchronizing, and after about
30 seconds, the status would show Resynchronizing.<o:p></o:p>
The database was mounted on EX2 and seeding to EX1 again. I did not notice the
issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
Late Monday morning, my boss and I were looking at more articles, but all the same results,
delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
I mentioned that it was strange because the networks were all up. What made us try the next
scenarios was just "luck" I guess. I made a statement about not remembering
which networks DAG replication took place over. Again, we have a LAN and
a BACKUP network. Bother were listed to use replication, so we decided to
disable replication over the BACKUP network in the EMC. Immediately, the
database copies switch to healthy and started seeding.<o:p></o:p>
Later that evening I enabled replication over the BACKUP network and it failed again with
a status of Disconnected and Resynchronizing, and after about 30 seconds, the
status would show Resynchronizing. I disabled the replication over the
BACKUP network and the database copy went back to healthy<o:p></o:p>
The last round of windows updates were pushed to these boxes the Friday before the
issues began, 2/28/14. I don't believe the updates to be the issue. <o:p></o:p>
Can anyone make any suggestions as to where to look? It worked with the BACKUP
network enabled to so long that is eluding me as to why the issues would start
all of a sudden. I am also confident that the switch configuration for the
BACKUP network has not been changed at all in at least 2-3 months. I am
still open to look at the config. Please help if you can.<o:p></o:p>
<o:p></o:p>
Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
the database copies so that I can be alerted when the status changes. We
use WhatsUpGold 16.2 to monitor the devices. <o:p></o:p>
Thanks for any future assistance.<o:p></o:p>
Ian
Ian

You don't have to enable the Replication on Backup Network.
You should collapse your DAG network.
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
Post the result of Below command:
Get-DatabaseAvailabilityGroupNetwork
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 and Powershell v3 Issue

Similar Messages

Maybe you are looking for