User rights to maintain exchange 2010 maintain

Hi,
Which permission/user rights is required to maintain exchange 2010 environment.
Thanks;
NA

See the below Technet article on RBAC, the permission model that was introduced in Exchange 2010.
Understanding Role Based Access Control
http://technet.microsoft.com/en-us/library/dd298183(v=exchg.141).aspx
For further questions about Exchange 2010, it is better if you post in the
Exchange 2010 Forum.
Martina Miskovic

Similar Messages

Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

We are in the process of migrating from 2010 to 2013. Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
alex serdyukov

Hi Alex,
As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
Cumulative Update 8 for Exchange Server 2013
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

User Migration from Parent Domain to Child Domain..The user is enabled with Exchange 2010 Mailbox in Parent Domain

We currently have a single Windows 2008 R2 Active Directory domain controller, and an Exchange 2010 server. We are in the process of adding a child domain on a second Active Directory server for an offsite office location for a subdivision of our company.
The two locations will be connected via VPN.
Currently users exist on the root domain with Exchange accounts who will be moving to the new offsite company/location. We would like to be able to move these user accounts to the child domain while maintaining their existing Exchange mailboxes and
email addresses. Is this possible, and if so how would we do it?

Hi Srinivasa,
According to your description, I think you have done all the preparation.
For DL migration, the following article may give your some hints:
How to Migrate Distribution Groups Across a Forest
Good Luck!
Niko Cheng
TechNet Community Support

Can I migrate users from a hosted Exchange 2010 to Office 365 Enterprise E1 without the need of third party software?

I am hoping I am posting to the correct forum. We are currently using a hosted Exchange 2010 service through Intermedia and due to continuing issues with them and the pricing, we are getting ready to migrate to Microsoft’s Office 365 Enterprise
E1 platform. My question is this, besides the fact that we will need to set up ADFS for SSO, will I be able to migrate our existing mailboxes from Intermedia to Office 365 without having to purchase additional software?
The current configuration we have with Intermedia allows for us to use OWA and our OST files for our current users are cached locally on the workstations.
We also do not have any public folders in use. I have searched the web, but I have not been able to find a definitive answer or steps that I should take to prepare for this type of migration.
Any suggestions on this matter would be appreciated. Thank you.

It looks as I should be able to from reading that article. Not sure why the company that want to set this all up for me wanted $12,000 for something I can do with 6 steps.
Thank you

Cannot send email via ActiveSync when user connect from Internet (Exchange 2010 SP3 RU5)

Hi All.
This is the first time I encounter this kind of issue, whenever user connect from the internet they cannot send email from their Phone or Windows Mail App, but they can retrieve email
But when they connect from Internal Network they can send email. I already test ActiveSync from internet using www.testexchangeconnectivity.com and it pass all tests.
I also check the Firewall and all the necessary ports already opened (we even open all ports) , the default TTL on the firewall 3600 second.
From what I read ActiveSync use some kind of HTTP POST or in MS terminology "PING" command, but still have no idea what kind of configuration that should be made to the Firewall so it can pass this "PING" command. Because from what I
see in Android Logcat the problem always related to this PING command
10-07 08:12:38.714 I/Exchange(31971): Interrupt with reason 1
10-07 08:12:38.714 I/Exchange(31971): Ping task ending with status: -1
10-07 08:12:38.904 D/Exchange(31971): created outputstream
10-07 08:12:39.204 W/Exchange(31971): IOException sending mail
10-07 08:12:39.204 E/Exchange(31971): Generic error for operation SendMail: status 200, result -100
10-07 08:12:39.204 W/Exchange(31971): Aborting outbox sync for error -99
10-07 08:12:39.274 I/Exchange(31971): Ping task starting for 3
10-07 08:12:39.304 D/SyncManager(644): failed sync operation [email protected] u0 (com.android.exchange), com.android.email.provider, USER, latestRunTime 71219435, EXPEDITED, reason: 10040, SyncResult: stats [ numIoExceptions: 1]
10-07 08:12:39.304 D/SyncManager(644): not retrying sync operation because SYNC_EXTRAS_DO_NOT_RETRY was specified [email protected] u0 (com.android.exchange), com.android.email.provider, USER, latestRunTime 71220078, EXPEDITED, reason: 10040

Hi ronaldosy,
How about the work flow of Outlook or OWA on PC internally/externally?
If only phone has this issue, I suggest ask ActiveSync Forum for help so that you can get more professional suggestions. For your convenience:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobility
Best Regards,
Allen Wang

Exchange 2010 Receive Connector intermittently getting an SMTP RSET from sending SMTP servers causing missing user email

Users are receiving about 95% of their messages from sending SMTP servers. Intermittently, sending SMTP servers send the Exchange 2010 Server a SMTP RSET command for no apparent reason. The RSET Command (by SMTP specification) causes the Exchange 2010 Server
to drop the message. The sending SMTP servers then do not resend the message after asking the Exchange server to drop the message. This means the message is marked as Sent by the sending servers but the dropped messages never show up in the users' Outlook
inbox.
Exchange 2010 Version 14.3 (Build 123.4)
Roles: Hub Transport, Client Access, Mailbox
What is going on?
Exchange Receive Connector log showing a RSET example:
2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,1,10.80.120.15:25,65.99.255.73:53479,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,2,10.80.120.15:25,65.99.255.73:53479,>,"220 vpn.a1expediting.com Microsoft ESMTP MAIL Service ready at Thu, 17 Jul 2014 08:47:06 -0400",
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,3,10.80.120.15:25,65.99.255.73:53479,<,EHLO inbound37.exchangedefender.com,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,4,10.80.120.15:25,65.99.255.73:53479,>,250-vpn.a1expediting.com Hello [65.99.255.73],
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,5,10.80.120.15:25,65.99.255.73:53479,>,250-SIZE 52428800,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,6,10.80.120.15:25,65.99.255.73:53479,>,250-PIPELINING,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,7,10.80.120.15:25,65.99.255.73:53479,>,250-DSN,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,8,10.80.120.15:25,65.99.255.73:53479,>,250-ENHANCEDSTATUSCODES,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,9,10.80.120.15:25,65.99.255.73:53479,>,250-AUTH,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,10,10.80.120.15:25,65.99.255.73:53479,>,250-8BITMIME,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,11,10.80.120.15:25,65.99.255.73:53479,>,250-BINARYMIME,
2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,12,10.80.120.15:25,65.99.255.73:53479,>,250 CHUNKING,
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,13,10.80.120.15:25,65.99.255.73:53479,<,MAIL FROM:<[email protected]> SIZE=165270,
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,14,10.80.120.15:25,65.99.255.73:53479,*,08D16FD38F3D3355;2014-07-17T12:47:07.370Z;1,receiving message
2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,15,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.0 Sender OK,
2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,16,10.80.120.15:25,65.99.255.73:53479,<,RCPT TO:<[email protected]> ORCPT=rfc822;[email protected],
2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,17,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.5 Recipient OK,
2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,18,10.80.120.15:25,65.99.255.73:53479,<,RSET,
2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,19,10.80.120.15:25,65.99.255.73:53479,>,250 2.0.0 Resetting,
2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,20,10.80.120.15:25,65.99.255.73:53479,<,QUIT ,
2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,21,10.80.120.15:25,65.99.255.73:53479,>,221 2.0.0 Service closing transmission channel,
Daniel

Hi,
According to the receive connector log, your emails were failed to be deliverd with DNR. If I misudnerstand the meaning, please feel free to let me know. If yes, I'd like to confirm the detail information in the DNR to narrow down the
cause.
Additionally, based on my research, the RSET command performs an SMTP reset, and then aborts the message that is currently being sent. Thus, the log didn't provide more information for troubleshooting. Is there any other error in your event log? please check
the event log when the issue happens again.
Thanks,
Angela Shi
TechNet Community Support

Migrating user from Exchange 2010 to Exchange 2013 succeeds but OWA redirects to 2010

Hello everyone,
I am migrating users from exchange 2010 to 2013, Users migration works perfectly and completes without any issue but after the user migration finishes I try to login to OWA but user goes to OWA exchange 2010 not 2013 as if the mailbox has not been migrated.
I have checked the HomeMDB attribute and I can see the new database on 2013 is located there. how to solve this? I have retransfered the user back to 2010 and 2013 but it didn't work.
I would appreciate your help.
Thanks
Mohammed JH

Hi Amit
After 30 mins approximately we checked the inboxes that have been migrted (2) and we found out they are working.
İ wonder why there is this delay ? İ have already done migration before but it never took this much time. İ would appreciate your reply.
Thanks
Mohammed JH

Outlook anywhere issue for exchange 2010 users

Hi Guys really hoping some one can help me out here.
I have just introduced 2 new exchange 2013 servers into our existing exchange 2010 environment. 1 CAS server and 1 mailbox server.
The issue i'm having is that any users that are on exchange 2010 mailbox servers can't connect to their profiles in outlook via the exchange 2013 cas box. OWA works fine and users that are on exchange 2013 mailboxes also work fine.
Authentication is set to on exchange 2013 and 2010 cas boxes to
Exchange 2013 cas
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
Exchange 2010 cas
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
I was also wondering should I have a reg key on my exchange cas box of HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy\validports_autoconfigure_exchange ???

Thanks for the reply i have changed it to the following
Exchange 2013 cas
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
Exchange 2010 cas
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
and reset iis but still no luck authenticating with outlook on existing profiles or a new profile.

Migrate Exchange 2010 to Exchange 2013, Need to defined win 7 users logon to Exchange 2010 & Win 8.1 users logon to Exchange 2013

Hi,
My organization have few win 7 and windows 8.1 clients. Now I want to migrate exchange server 2010 to 2013. And I don't want to remove exchange 2010 from the organization. Because I want to connect win 7 client through exchange 2010 and windows 8.1 user
connect to exchange 2013. Is there any way to define the win 7 users to connect to exchange 2010 and Windows 8.1 users to connect to exchange 2013?
Md. Ramin Hossain

The client connections are proxied to the mailbox servers that hold the mailbox.
You would need to have 2010 MBX servers with the mailboxes for the XP users, and 2013 MBX servers holding the mailboxes for the 7 users. And of course, the appropriate CAS servers.
Realistically, you need to migrate away from Windows XP. It is no longer supported.

OOF not working for mailboxes homed on Exchange 2010 server during migration

Hi There
I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also
enable OOF via exchange powershell.
Users homed on the exchange 2013 servers does not have any issues.
The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.
So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but
in the meantime I'm checking if anyone else had similar issues.
Any pointers will be welcome.

Hi ,
1.Please check the problematic exchange 2010 user account can able to access the ews virtual directory internal url and you can check that via browser's.It will prompt for the user name and password , please provide that .
EWS url wopuld be like - https://mail.youdomain.com/EWS/Exchange.asmx
2.Then the second step would be autodiscover check for the problematic user account.you can find that via test email configuration .There you came to know whether outlook is fetching up the proper url for ews and autodiscover.
3.Then please un check the proxy settings in browsers and check the same.
4.please use the command to check the auto discover
test-outlookwebservices
Please check the below links also.
http://exchangeserverpro.com/exchange-2013-test-outlook-web-service/
http://www.proexchange.be/blogs/exchange2007/archive/2009/07/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable-try-again-later.aspx
http://port25guy.com/2013/07/20/user-cannot-set-an-out-of-office-in-exchange-20102013-or-eventid-3004-appears-in-your-event-log/
http://www.theemailadmin.com/2010/06/exchange-server-2010-out-of-office/
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2010\Outlook Mail issues

Hi,
I am having some issues with mail disappearing and outlook not updating. The issues are:
When sending an email from Outlook it appears in the sent items for 30 seconds in Outlook and then disappears. It never shows up in OWA The email does send though. If an email is sent via OWA the email appears and stays in both OWA and Outlook. This is
happening in Outlook 2010\Exchange 2010
Updating issues on random folders in Outlook. This is happening on both Outlook 2013 and Outlook 2010 different users with the same Exchange 2010 back end.
Both users have cached email forced. I have tried rebuilding the mailbox locally.
Cheers,
Zac Avramides

Hi,
Thanks for your detailed information about the symptom.
It seems the issue is more related to the Outlook client since OWA works fine. I suggest we can follow the checkpoints below:
1. Rebuild Outlook profile.
2. Disable any third-party firewall or AV programs.
3. Run Windows in Clean Boot.
4. Run Outlook in safe mode by “Outlook /safe”.
What’s the result now?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Missed Call Notification in Exchange 2010/2013 coexistence mode

Dear all,
Context:
Lync 2013 Enterprise Voice, Exchange 2010 and Exchange 2013 in coexistence mode
Waiting complete migration, some users are always on exchange 2010
UM role is installed on both exchange server
The exchange servers UM are attached to only one UM Dial Plan
Scenario :
A call to a lync user. The caller hang-up before user announcement
Problem: Missed call notification doesn't work for user on Exchange 2010 (it's work fine for user on Exchange 2013)
Voice Messaging works fine
Troubleshooting / SIP Traces:
SIP Info is always send to Exchange 2013 even if user is on exchange 2010
SIP Info sent from Lync FE to Exchange 2013 UM :
TL_INFO(TF_PROTOCOL) [0]6330.3AE8::02/12/2015-12:25:23.575.015c018e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786->192.168.5.203:5061
INFO sip:outlook.mydomain.com:5061;ms-fe=exchange2013-UM.mydomain.localdomain;transport=Tls SIP/2.0
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;epid=8C75BE2D95;tag=35c2d8a65a
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;epid=C4C2F4F6BA;tag=ac126413f
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTACT: <sip:LyncFE-2013.mydomain.localdomain;transport=Tls>
CONTENT-LENGTH: 454
USER-AGENT: RTCC/5.0.0.0 Inbound Routing (Microsoft Lync Server 2013 5.0.8308.726)
CONTENT-TYPE: application/ms-rtc-usernotification+xml
- <UserNotification>
       <User>sip:[email protected]</User>
       <EumProxyAddress>EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain</EumProxyAddress>
       <Time>2015-02-12 12:25:23Z</Time>
       <Template>RtcDefault</Template>
    + <Event type="missed">
</UserNotification>
------------EndOfOutgoing SipMessage
Answer from Exchange 2013 UM
TL_INFO(TF_PROTOCOL) [1]6330.2DF4::02/12/2015-12:25:23.642.015c2481 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786<-192.168.5.203:5061
SIP/2.0 200 OK
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;tag=35c2d8a65a;epid=8C75BE2D95
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;tag=ac126413f;epid=C4C2F4F6BA
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTENT-LENGTH: 0
SUPPORTED: ms-dialog-route-set-update
SERVER: RTCC/5.0.0.0 MSExchangeUM/15.00.0995.028
ms-diagnostics-public: 15642;reason="Lync SIP INFO notifications are not supported for legacy users. User: EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain"
------------EndOfIncoming SipMessage
Gerald Cheminant

Hi,
This behavior is by design. Exchange 2010 server is not going to accept any SIP messages from Exchange 2013 server because it is not listed as UM IP Gateway. Therefore, even if Exchange 2013 redirected the SIP INFO packet to Exchange 2010, it will fail.
During migration\coexistance scenario, this feature (Missed call notifications from Lync server) will not work for legacy users whose mailbox is still in Exchange 2010.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Exchange 2010 sp2 OWA

Hi guys,
We have a specific user that cant use OWA nor outlook.
When the user tries to access Exchange 2010 OWA, it says that his account is disabled which isnt the case. I'v check in ad and his account is not disabled.
Here is the error:
Your account has been disabled.
Copy error details to clipboard
Show details
Request
Url: http://exchange.domain.com:80/owa/
User host address: 10.2.7.83
User: Francois Carstens
EX Address: /o=domain/ou=exchange administrative group (fydibohf23spdlt)/cn=recipients/cn=francois carstens
SMTP Address: [email protected]
OWA version: 14.2.247.5
Exception
Exception type: Microsoft.Exchange.Data.Storage.AccountDisabledException
Exception message: Cannot open mailbox /o=domain/ou=exchange administrative group (fydibohf23spdlt)/cn=recipients/cn=francois carstens.
Call stack
Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)
Microsoft.Exchange.Data.Storage.MailboxSession.Initialize(MapiStore linkedStore, LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, GenericIdentity auxiliaryIdentity)
Microsoft.Exchange.Data.Storage.MailboxSession.<>c__DisplayClass12.b__10(MailboxSession mailboxSession)
Microsoft.Exchange.Data.Storage.MailboxSession.InternalCreateMailboxSession(LogonType logonType, ExchangePrincipal owner, CultureInfo cultureInfo, String clientInfoString, IAccountingObject budget, Action`1 initializeMailboxSession, InitializeMailboxSessionFailure
initializeMailboxSessionFailure)
Microsoft.Exchange.Data.Storage.MailboxSession.CreateMailboxSession(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, CultureInfo cultureInfo, String clientInfoString, PropertyDefinition[]
mailboxProperties, IList`1 foldersToInit, GenericIdentity auxiliaryIdentity, IAccountingObject budget)
Microsoft.Exchange.Data.Storage.MailboxSession.ConfigurableOpen(ExchangePrincipal mailbox, MailboxAccessInfo accessInfo, CultureInfo cultureInfo, String clientInfoString, LogonType logonType, PropertyDefinition[] mailboxProperties, InitializationFlags initFlags,
IList`1 foldersToInit, IAccountingObject budget)
Microsoft.Exchange.Data.Storage.MailboxSession.Open(ExchangePrincipal mailboxOwner, WindowsPrincipal authenticatedUser, CultureInfo cultureInfo, String clientInfoString, Boolean wantCachedConnection)
Microsoft.Exchange.Data.Storage.MailboxSession.Open(ExchangePrincipal mailboxOwner, WindowsPrincipal authenticatedUser, CultureInfo cultureInfo, String clientInfoString)
Microsoft.Exchange.Clients.Owa.Core.OwaWindowsIdentity.CreateMailboxSession(ExchangePrincipal exchangePrincipal, CultureInfo cultureInfo, HttpRequest clientRequest)
Microsoft.Exchange.Clients.Owa.Core.UserContext.CreateMailboxSession(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.UserContext.Load(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.CreateUserContext(OwaContext owaContext, UserContextKey userContextKey, UserContext& userContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.AcquireAndPreprocessUserContext(OwaContext owaContext, HttpRequest request)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.OwaRequestEventInspector.OnPostAuthorizeRequest(Object sender, EventArgs e)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Inner Exception
Exception type: Microsoft.Mapi.MapiExceptionMailboxDisabled
Exception message: MapiExceptionMailboxDisabled: Unable to open message store. (hr=0x80004005, ec=2412) Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=422] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=232][latency=15]
Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropLogon [254] Lid: 17082 ROP Error: 0x96C Lid: 26937 Lid: 21921 StoreEc: 0x96C Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropLogon [254] Lid: 1219 StoreEc:
0x80070005 Lid: 3225 StoreEc: 0x8004010F Lid: 51399 Lid: 2567 StoreEc: 0x96C Lid: 19452 Lid: 2199 StoreEc: 0x96C Lid: 56415 Lid: 48223 StoreEc: 0x96C Lid: 17097 StoreEc: 0x96C Lid: 8620 StoreEc: 0x96C Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid:
21817 ROP Failure: 0x96C Lid: 26297 Lid: 16585 StoreEc: 0x96C Lid: 32441 Lid: 1706 StoreEc: 0x96C Lid: 24761 Lid: 20665 StoreEc: 0x96C Lid: 25785 Lid: 29881 StoreEc: 0x96C
Call stack
Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
Microsoft.Mapi.ExRpcConnection.OpenMsgStore(OpenStoreFlag storeFlags, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, MapiStore msgStorePrivate, String& correctServerDn, ClientIdentityInfo clientIdentityAs, String userDnAs, String applicationId, CultureInfo
cultureInfo)
Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo
cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, WindowsIdentity windowsIdentity, String
applicationId)
Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)

Hi Sembee,
We did this already.
We got it working now after doing above but with the shell.
First we confirmed if the mailbox is disabled with the following command: Get-MailboxStatistics -Database MBD01 | Where { $_.DisconnectReason -eq "Disabled" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason
It did show as disabled but when we try to enable it we got the following: This task does not support recipients of this type.
So we disabled the mailbox in the shell, enable it again and it was fine.
Get-MailboxStatistics -Database MBD01 | Where { $_.DisconnectReason -eq "Disabled" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason helped us, cause in the EMC exchange showed the user as enabled.
Thanks

Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

Hi
We have a coexistence environment where we are currently migrating from Exchange 2003 to 2010 and have 80% of the users already on the Exchange 2010 platform. This is all within the same AD forest, let's call it FOREST1.AD.
The problem I'm seeking help about is a message routing problem we had this morning where messages bound for the Exchange 2003 users started looping between Exchange 2003 and Exchange 2010. The problem started as a result of changing the accepted domain
type to 'internal relay domain' for the purposes of establishing SMTP namespace sharing with an external Exchange environment (different forest, let's call it FOREST2.AD). The expectation was that after changing the domain type from authoritative to 'internal
relay domain', Exchange 2010 would route messages for unknown recipients to the external environment and that would be the only effect of the change. The message routing to the external environment worked completely OK. However, later we noticed that Exchange
2003 stopped delivering messages to its local users and started routing them to Exchange 2010 which would route the messages back to Exchange 2003 as that's where the recipients existed, only to have Exchange 2003 send them back to Exchange 2010 again.
The Send connector to route the messages, for the shared namespace, to the external environment used the Exchange 2010 server as the source server. It makes sense and is expected that Exchange 2003 would send messages for any unknown recipients to Exchange
2010 for onward delivery via the Send connector. But it is not expected for Exchange 2003 to not deliver messages to its own users using the store driver and instead routing them on to Exchange 2010.
We fixed the problem by reversing the change and not only changed the domain type back to authoritative but also removed the Send connector for the specified shared namespace. However, we do need to understand why this problem happened and how to stop it
from happening.
We did test the shared SMTP namespace configuration using a test domain before applying the change to the domain that is used for production email traffic. Test users on Exchange 2003 with email addresses on the test domain did not experience this looping
problem. This has been tested again after the production domain experienced the problem and there is no looping for the test domain. The only difference I noticed between the configuration for the test domain and the production domain is that while both domains
existed as accepted domains of type 'internal relay domain' in Exchange 2010, there was a difference in configuration in Exchange 2003 where the test domain was not present on the recipient policy at all and the production domain was present there.
This also makes me wonder if Exchange 2003 and Exchange 2010 in the same organization keep a separate configuration to determine which domain they are authoritative for. When you install Exchange 2010, it does add all the domains on the recipient policies
to the accepted domains configuration but any new domains you add in accepted domains in Exchange 2010 are not added to the legacy recipient policy object.
Can someone please help clarify these grey areas and explain why the message looping was created and how to avoid it. I'm happy to provide any further information.
Thanks
Nauman.

Hello,
Why do you want to use the 'internal relay domain' authentication?
Thanks,
Simon Wu
TechNet Community Support

Configure Exchange 2010 internal mail routing

Hello,
I’m have an Exchange server system which includes exchange 2003 standard edition server and an Exchange 2010 server standard edition server, plus a public SMTP server. Each exchange edition is on a separate machine. The SMTP server is on a separate machine.
I am in the process of retiring the Exchange 2003 server per the following document:
http://support.microsoft.com/kb/822931
Inbound mail arrives at the SMTP server and is forwarded from there to the Exchange 2010 server. All user mailboxes have been moved to the Exchange 2010 server. There is a connector between the Exchange 2003 and Exchange 2010 servers. Both the Exchange 2003
and Exchange 2010 server have a connector to the public SMTP server.
In reviewing some of the log files, it appears that a lot of mail which originates from a user mailbox on the Exchange 2010 server is being sent from the 2010 server to the 2003 server and from there to the public SMTP server. I don’t know how to change
this priority so that no mail will be sent to the Exchange 2003 server. At this point there is no reason for any mail to travel to or from the Exchange 2003 server. Any suggestions on how to change this configuration so that mail goes directly from the Exchange
2010 server to the SMTP server?
Thank you for taking the time to read and hopefully provide a response!

Hi,
From your description, I would like to clarify the following thing:
If you have finished the migration successfully, and the Exchange server 2003 is unnecessary. You can remove the connector between Exchange 2003 to Exchange 2010 and the connector between Exchange 2003 to public SMTP server. And then the mail should go directly
from Exchange 2010 to the SMTP server.
Hope my clarification can be helpful.
Best regards,
Amy Wang
TechNet Community Support

User rights to maintain exchange 2010 maintain

Similar Messages

Maybe you are looking for