Exchange 2013 CU2/Exchange 2010 SP3 Coexistance OWA Redirection

Hi, 
I am trying to sign into OWA 2013 with a 2010 mailbox user and I just get the following page
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
Want to be able to use your email when you're offline?
Next time you are connected:
1. At the top of Outlook Web App, next to your name, click Settings
2. Click Offline settings and turn on offline access
3. That's it! You'll never see this message again.
I checked the logs and it looks like it might be trying to redirect to the Exchange 2010 Front end. 
Exchangecas13 is the 2013 CAS server, Exchangefe1 is the 2010 CAS/Transport Server.  
2013-07-26T20:42:01.691Z,8e66a7cb-63bc-4651-b769-d0062f7c7665,15,0,712,12,,,,,,,,,,,,,EXCHANGECAS13,,,,,,,,,,,,,,,,,,,,,,,,,,600050.0544,,,,,,,,,,,,,,,,,,S:ActivityStandardMetadata.Action=GlobalActivity;I32:ADR.C[SUPPR]=6;F:ADR.AL[SUPPR]=2.428583;I32:ADS.C[SUPPR]=1;F:ADS.AL[SUPPR]=2.1359,
2013-07-26T20:42:18.433Z,17bed7ea-9bce-4759-bdd5-c8a25667f521,15,0,712,12,,Owa,exchangecas13,/owa/,,FBA,False,,,,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C;
.NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,302,,,,,,,,,,,,0,,,,,,,,,,,,,2,,,,,,,,,,,,1,1,1,1,,,OnBeginRequest=0;NoCookies=302 - GET/E14AuthPost;,
2013-07-26T20:42:18.438Z,41574515-5ea0-43b4-8a13-d327ec109d19,15,0,712,12,,Owa,exchangecas13,/owa/auth/logon.aspx,,FBA,False,,,,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
.NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,200,,,,,,,,,,,,0,,,,0,,,,,,,,,1.9969,,,,,,,,,,,,1,1,1,1,?url=https%3a%2f%2fexchangecas13%2f&reason=0,,OnBeginRequest=0;,
2013-07-26T20:42:18.464Z,02c9d811-e43d-4dab-a1eb-78a85b73f3e5,15,0,712,12,,Owa,exchangecas13,/owa/auth/logon.aspx,,FBA,False,,,,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
.NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,200,,,,,,,,,,,,0,,,,0,,,,,,,,,2.0001,,,,,,,,,,,,1,1,1,1,?replaceCurrent=1&url=https%3a%2f%2fexchangecas13%2f,,OnBeginRequest=0;,
2013-07-26T20:42:24.930Z,54e8f566-4c32-4fbe-9e84-d56bee916785,15,0,712,12,,Owa,exchangecas13,/owa/auth.owa,,FBA,True,LWGINC\pslager,,Sid~S-1-5-21-1186999560-1424097373-3473557-14162,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2;
.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,302,,,POST,,,,,WindowsIdentity,,,,121,,,,1,17,,0,,0,,0,0,19.9095,0,,,,,,,,17,1,,18,18,19,19,,,OnBeginRequest=0;DownLevelTargetHash=0/0/1;ClientAccessServer=EXCHANGEFE1.LWGINC.com;ResolveCasLatency=0;,
2013-07-26T20:42:24.937Z,f81832cf-43c4-49ed-942f-3ff1e951bd6a,15,0,712,12,,Owa,exchangecas13,/owa/auth.owa,,FBA,True,LWGINC\pslager,,Sid~S-1-5-21-1186999560-1424097373-3473557-14162,Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2;
.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; MS-RTC EA 2; Media Center PC 6.0; InfoPath.3),192.168.1.30,EXCHANGECAS13,302,,,POST,,,,,WindowsIdentity,,,,121,,,,0,1,,0,,0,,0,0,2.9963,1,,,,,,,,1,0,,2,2,2,2,,,OnBeginRequest=0;DownLevelTargetHash=0/0/1;ClientAccessServer=EXCHANGEFE1.LWGINC.com;ResolveCasLatency=0;,
Any ideas?

Hi
One try, please move administrator mailbox to 2013 server
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

Similar Messages

  • Exchange 2013 CU2, Alert for OWA Health set unhealthy from SCOM 2012

    I am facing issue in Exchange 2013 CU2, I got this alert from SCOM 2012 atleast 5-6 times a day, OWA health set is unhealthy, I have done all the steps mentioned in this web link. Authentication type for OWA Virtual directory is integrated windows and Basic.
    I have 2 CAS servers, and this alert generated from both of them.
    http://technet.microsoft.com/en-us/library/ms.exch.scom.OWA(EXCHG.150).aspx?v=15.0.712.24
    Alert: Health Set unhealthy
    Source: EX-CAS - OWA
    Path: EX-CAS;EX-CAS
    Last modified by: System
    Last modified time: 1/5/2014 8:15:08 PM
    Alert description: Outlook Web Access logon is failing on ClientAccess server EX-CAS.
    Availability has dropped to 0%. You can find protocol level traces for the failures on C:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\OWA\ClientAccessProbe.
    Incident start time: 1/6/2014 4:05:08 AM
    Last failed result:
    Failing Component - Owa
    Failure Reason - CafeFailure
    Exception:
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
    Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
    Failure source: Owa
    Failure reason: CafeFailure
    Failing component:Owa
    Exception hint: CafeErrorPage: CafeFailure Unauthorized Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
    ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
    Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
    WebExceptionStatus: Success
    GET https://localhost/owa/ HTTP/1.1
    User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
    Accept: */*
    Cache-Control: no-cache
    X-OWA-ActionName: Monitoring
    Cookie:
    HTTP/1.1 401 Unauthorized
    request-id: 211474d2-a43e-4fab-8038-3aab35353568
    X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
    Server: Microsoft-IIS/7.5
    WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
    X-Powered-By: ASP.NET
    X-FEServer: EX-CAS
    Date: Mon, 06 Jan 2014 04:14:47 GMT
    Content-Length: 0
    Response time: 0s
     ---> Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
    ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
    Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
    WebExceptionStatus: Success
    GET https://localhost/owa/ HTTP/1.1
    User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
    Accept: */*
    Cache-Control: no-cache
    X-OWA-ActionName: Monitoring
    Cookie:
    HTTP/1.1 401 Unauthorized
    request-id: 211474d2-a43e-4fab-8038-3aab35353568
    X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
    Server: Microsoft-IIS/7.5
    WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
    X-Powered-By: ASP.NET
    X-FEServer: EX-CAS
    Date: Mon, 06 Jan 2014 04:14:47 GMT
    Content-Length: 0
    Response time: 0s
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Net.MonitoringWebClient.BaseExceptionAnalyzer.Analyze(TestId currentTestStep, HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, Action`1 trackingDelegate)
       at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.AnalyzeResponse[T](HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
       at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndSend[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse, Boolean fireResponseReceivedEvent)
       at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndGet[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
       at Microsoft.Exchange.Net.MonitoringWebClient.Authenticate.AuthenticationResponseReceived(IAsyncResult result)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
       at Microsoft.Exchange.Net.MonitoringWebClient.Owa.OwaLogin.AuthenticationCompleted(IAsyncResult result)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
       at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Bool
    States of all monitors within the health set:
    Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'EX-CAS' -HealthSet 'OWA'
    State              
    Name                                   
    TargetResource                     HealthSet                    
    AlertValue     ServerComponent    
    NotApplicable       OwaCtpMonitor                                                             
    OWA                          
    Unhealthy      None               
    States of all health sets:
    Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX-CAS'
    State              
    HealthSet                    
    AlertValue     LastTransitionTime      
    MonitorCount       
    NotApplicable       ActiveSync                   
    Healthy        1/3/2014 5:21:13 AM     
    2                  
    NotApplicable       AD                           
    Healthy        11/24/2013 6:54:18 AM  
     10                 
    NotApplicable       ECP                          
    Healthy        1/5/2014 3:03:05 AM     
    1                  
    Online             
    Autodiscover.Proxy           
    Healthy        11/20/2013 10:06:37 AM  
    1                  
    NotApplicable       Autodiscover                 
    Healthy        1/3/2014 10:18:17 PM    
    2                  
    Online             
    ActiveSync.Proxy             
    Healthy        11/20/2013 10:06:37 AM  
    1                  
    Online             
    ECP.Proxy                
        Healthy       
    11/21/2013 6:16:08 PM    4                  
    Online             
    EWS.Proxy                    
    Healthy        11/20/2013 10:06:37 AM  
    1                  
    Online             
    OutlookMapi.Proxy            
    Healthy        11/24/2013 6:54:28 AM   
    4                  
    Online             
    OAB.Proxy                    
    Healthy        11/19/2013 7:14:34 PM   
    1                  
    Online             
    OWA.Proxy                    
    Healthy        11/20/2013 10:06:37 AM  
    2                  
    NotApplicable       EDS                          
    Healthy        1/3/2014 5:19:56 AM     
    10                 
    Online             
    RPS.Proxy                    
    Healthy        1/3/2014 5:21:27 AM     
    13                 
    Online             
    RWS.Proxy                     Healthy       
    1/3/2014 5:20:09 AM      10                 
    Online             
    Outlook.Proxy                
    Healthy        1/3/2014 5:21:12 AM     
    4                  
    NotApplicable       EWS                          
    Healthy        1/3/2014 10:18:17 PM    
    2                  
    Online             
    FrontendTransport            
    Healthy        1/5/2014 3:47:09 AM     
    11                 
    Online             
    HubTransport                 
    Healthy        1/5/2014 3:47:09 AM     
    29            
    NotApplicable       Monitoring                   
    Unhealthy      1/5/2014 4:05:57 AM     
    9                  
    NotApplicable       DataProtection               
    Healthy        1/3/2014 5:25:42 AM     
    1                  
    NotApplicable       Network                       Healthy       
    1/4/2014 1:51:16 PM      1                  
    NotApplicable       OWA                          
    Unhealthy      1/5/2014 8:05:08 PM     
    1                  
    NotApplicable       FIPS                         
    Healthy        1/3/2014 5:21:12 AM     
    3                  
    Online             
    Transport                    
    Healthy        1/5/2014 4:11:00 AM     
    9                  
    NotApplicable       RPS                          
    Healthy        11/20/2013 10:07:12 AM  
    2                   
    NotApplicable       Compliance                   
    Healthy        11/20/2013 10:08:10 AM  
    2                  
    NotApplicable       Outlook                      
    Healthy        11/21/2013 6:12:54 PM   
    2                  
    Online             
    UM.CallRouter                
    Healthy        1/5/2014 3:47:10 AM     
    7                  
    NotApplicable       UserThrottling               
    Healthy        1/5/2014 4:16:42 AM     
    7                  
    NotApplicable       Search       
                    Healthy       
    11/24/2013 6:55:06 AM    9                  
    NotApplicable       AntiSpam                     
    Healthy        1/3/2014 5:16:43 AM     
    3                  
    NotApplicable       Security                     
    Healthy        1/3/2014 5:19:28 AM     
    3                  
    NotApplicable       IMAP.Protocol                
    Healthy        1/3/2014 5:21:14 AM     
    3                  
    NotApplicable       Datamining                   
    Healthy        1/3/2014 5:18:34 AM     
    3          
    NotApplicable       Provisioning                 
    Healthy        1/3/2014 5:19:56 AM     
    3                  
    NotApplicable       POP.Protocol                 
    Healthy        1/3/2014 5:20:44 AM     
    3                  
    NotApplicable       Outlook.Protocol             
    Healthy        1/3/2014 5:19:46 AM     
    3                  
    NotApplicable       ProcessIsolation             
    Healthy        1/3/2014 5:19:26 AM     
    9                  
    NotApplicable       Store                        
    Healthy        1/3/2014 5:20:38 AM     
    6                  
    NotApplicable       TransportSync                
    Healthy        11/24/2013 6:53:09 AM   
    3                  
    NotApplicable       MailboxTransport             
    Healthy        1/3/2014 5:21:11 AM     
    6                   
    NotApplicable       EventAssistants              
    Healthy        11/21/2013 6:22:01 PM   
    2                  
    NotApplicable       MRS                          
    Healthy        1/3/2014 5:20:29 AM     
    3                  
    NotApplicable       MessageTracing               
    Healthy        1/3/2014 5:18:15 AM     
    3                  
    NotApplicable       CentralAdmin                 
    Healthy        1/3/2014 5:17:25 AM     
    3                  
    NotApplicable       UM.Protocol                  
    Healthy        1/3/2014 5:17:08 AM     
    3                  
    NotApplicable       Autodiscover.Protocol        
    Healthy        1/3/2014 5:17:13 AM     
    3                  
    NotApplicable       OAB                          
    Healthy        1/3/2014 5:20:51 AM     
    3                  
    NotApplicable       OWA.Protocol                 
    Healthy        1/3/2014 5:20:52 AM     
    3                  
    NotApplicable       Calendaring                  
    Healthy        11/24/2013 6:56:59 AM   
    3                  
    NotApplicable       PushNotifications.Protocol   
    Healthy        11/21/2013 6:16:05 PM   
    3                  
    NotApplicable       EWS.Protocol                 
    Healthy        1/3/2014 5:19:07 AM     
    3                  
    NotApplicable       ActiveSync.Protocol 
             Healthy       
    1/3/2014 5:20:16 AM      3                  
    NotApplicable       RemoteMonitoring             
    Healthy        1/5/2014 3:47:09 AM     
    3
    Any solution for this alert, how to rectify it, but OWA is running perfect for all users.           

    Hi,
    Sorry for the late reply.
    Do we have Exchange 2010 coexistence?
    If it is the case, I know the following known issue:
    Release Notes for Exchange 2013
    http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx
    Please note the "Exchange 2010 coexistence" session.
    If it is not related to our problem, please check the IIS log.
    If there is any detailed error code, like 401.1, 401.2, please let me know.
    Hope it is helpful
    Thanks
    Mavis
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 CU2 to CU3 OWA now redirects to IIS page

    so i did the the update from Exchange 2013 CU2 to CU3 last night and i am unable to access OWA. when i go to the site i initially received a 403 forbidden error but i cleared out the require SSL, which somehow got re-enabled, and now it redirects to the
    IIS 8 page. 
    In IIS it seems like the redirect values for default web site got cleared away. I put in the address that was previously there and then e-mail for the whole company goes down after an IIS reset. In the default web site i entered to redirect to https://mail.contoso.com/owa
    like how it was before but that doesn't work. 
    any ideas/feedback would be great!
    Thanks!

    I guess you are running a multirole server.
    Did you try removing the OWA virtual directories -  for both Default Website and Exchange Back End site with:
    #Replace ServerName
    Remove-OwaVirtualDirectory "ServerName\owa (Default Web Site)"
    Remove-OwaVirtualDirectory "ServerName\owa (exchange back end)"
    and re-creating them again with:
    #Replace ServerName & mail.domain.com
    New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa"
    New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa" -WebSiteName "Exchange Back End"

  • Outlook 2010 SP2 - Error when editing shared calendar: Post Exchange 2013 CU2 Migration

    Hi there,
    I have a strange comportment with Outlook 2010 SP2 and Exchange 2013 CU2 and i really need your help.
    Frequently, when an user (who has the good permissions for) want to edit a shared calendar (edit a meeting or add one), he has this error message: 
    " Cannot display the folder. Your server administrator has limited the number of items you can open simultaneously. Try closing message you have opened or removing attachments and images from unsent messages you are composing "
    I see anything in the Exchange server event log but i have each time, an error message in the client event log:
    " Microsoft Office14 Alerts ID 300"
    Everything work very well with Outlook 2013.
    Many thanks in advance for your assistance, and I am looking forward to reading from you.

    Hi,
    According to your description, the issue is related to your Office 2010 client.
    And the issue can be resolved by installing the Microsoft Office 2010 Deployment Kit.
    Here are the steps you can refer to :
    1. Open a command prompt with administrative permissions.
    2. Browse to the directory that contains the Offvirt.msi.
    3. At the command prompt, run the following command:
    msiexec /i OffVirt.msi [licensing flags]
    You must enter a correct licensing flag in the following list to correctly configure the Deployment Kit. Otherwise, functionality may be incorrect.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/virtualworld/archive/2010/07/07/microsoft-has-encountered-an-error-with-licensing-and-will-need-to-close.aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch

    Dear All,
    I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
    The 2013 environment are:-
    2 X CAS server with MS NLB configured
    2X MBX server with DA
    Internal NLB/licent access: excas2013.int.my.domain
    External access (current set on 2010 as well): webmail.my.domain
    Certificate with valid subject name has been import to 2013 and 2010:
    CN: webmail.mydomain
    SAN: excas2013.int.my.domain
    SAN: excas.int.my.domain (for 2010)
    I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
    the process looks good:-
    Establish network connection (checked)
    Searching for [email protected] server settings (checked)
    Log on to server
    The process stop at "Log on to server" and a windows prompt, saying:
    The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
    Clicked OK, I can see:-
    MS Exchange Server:
    [email protected]
    Mailbox:
    =SMPT:[email protected]
    WHen I click "Check Name", it said The name cannot be resolved.
    I have no idea of what is going on. Just want some help~

    I have checked the iis log:-
    2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
    2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
    15
    2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
    2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
    2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
    2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
    80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 64 78
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 109
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 64 15
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 31
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 0 15
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 46
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 0 31
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 46

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

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

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

  • Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

    Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email        
    I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
    I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
    I recreated the profile in outlook... same thing.
    I created the profile with outlook 2013... same thing.
    There is only one user profile setup in Outlook.
    (I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
    I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
    Does anyone have any ideas?

    So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
    it IS going from your user)?

  • Exchange 2013 outlook server name is my owa URL not hash

    i was migrating from exchange 2003 to 2010 to 2013.
    after the migration and i install the exchange 2013 with exchange 2010 and configured it. the outlook not working with users that migrated to exchange 2013, and working well with the users already existing on exchange 2010.
    when i try to fix this issue i set my outlook provider using this commend   Set-OutlookProvider EXPR -CertPrincipalName
    "msstd:mail.mydomain.com"
    but unfortunately it's impacted the server name in client outlook.
    then i removed the outlook provider and create it again. but with no change. then i uninstall the CAS server and install it again but with now change too.
    now the outlook server name is my URL "mail.mydomain.com" and i need to recover it to be hash like "[email protected]"
    the outlook client version outlook 2010 sp2 & and outlook 2013

    Hi,
    Is there any error when you connect your Exchange 2013 mailbox in Outlook? Also confirm if the problematic users can access Exchange 2013 mailbox from OWA.
    Generally, Outlook uses Autodiscover service to auto setup Exchange account in Outlook. We can check the Autodiscover service in Exchange 2013 (mail.mydomain.com is pointed to Exchange 2013):
    Get-ClientAccessServer | FL Identity,fqdn,*autodiscover*
    Set-OutlookAnywhere -Identity "Exch13\Rpc (Default Web Site)" -InternalHostname mail.mydomain.com -ExternalHostname mail.mydomain.com -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl
    $True -InternalClientsRequireSsl $true
    Also make sure the name which is used in the AutoDiscoverServiceInternalUri has been included in your Exchange certificate with
    IIS service. We can restart IIS service by running IISReset /noforce from a Command Prompt window.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Publish Exchange 2013 using UAG 2010 Sp4

    Hi,
    We need to publish Exchange 2013 through UAG 2010. But we are not getting any dedicated link for UAG 2010 to publish Exchange 2013. we have UAG 2010 with SP4.
    Is there any Step by step UAG 2010 configuration link to publish Exchange 2013?
    Thanks
    jitender

    Hi Jitender,
    Based on my knowledge, publishing Exchange 2013 with UAG 2010 is similar with publishing Exchange 2010.
    I find a related Blog and Guid for your reference:
    1. Publishing Exchange Server 2010 with Forefront UAG and TMG
    http://blogs.technet.com/b/exchange/archive/2010/07/16/publishing-exchange-server-2010-with-forefront-uag-and-tmg.aspx
    2. Publishing Exchange Server 2010 with Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010
    http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=8946
    Please also notice the System requirement of both Exchange 2013 and UAG 2010.
    System Requirement
    Exchange 2013
    http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx  
    UAG 2010 SP4
    Supported Operating System
    Windows Server 2008 R2
    Servers running Forefront UAG and SP4 require the   following:
      • Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, or   Windows Server 2008 R2 DataCenter.
      • Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 CU2 will not install, Exchange is now in an unuseable state.

    I have downloaded Exchange 2013 CU2 and attempted to install it from a local drive.  Exchange 2013 is installed on a Server 2012 Standard VM in Hyper-V.  I ran the two following commands before trying to install
    setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
    Upon trying to run the installer, I recieve the following error.
    Error:
    The following error was generated when "$error.Clear();
                        & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                    " was run: "AuthorizationManager check failed.".
    During my first install attept, the error was on step 4 of 15. I have tried to rerun the setup with no luck.  I noticed the installer leaves all the Exchange services disabled, as well as winmgmt, remoteregistry, w3svc, iisadmin.  These four services
    are the critical services the errors refer to.  I have verified my execution policy is correct
    PS C:\Windows\system32> Get-ExecutionPolicy -list
    Scope                                            
    ExecutionPolicy
    MachinePolicy                                               
    Unrestricted
    UserPolicy                                                  
    Undefined
    Process                                                  
    Undefined
    CurrentUser                                                  
    Undefined
    LocalMachine                                               
    RemoteSigned
    Upon trying to rerun the setup, I have ran the following commands in order to start the critical services manually
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    set-service -startuptype
    automatic
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    Start-Service
    No matter what I do, the Exchange 2013 CU2 installer seems to fail.  I'd appreciate any possible help with this.
    Thanks,
    Chris
    To add to what I posted, I also have the following error in the event log.
    [07/22/2013 13:57:01.0279] [1] Executing:
                        & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
    [07/22/2013 13:57:01.0373] [1] The following 1 error(s) occurred during task execution:
    [07/22/2013 13:57:01.0373] [1] 0.  ErrorRecord: AuthorizationManager check failed.
    [07/22/2013
    13:57:01.0373] [1] 0.  ErrorRecord:
    System.Management.Automation.PSSecurityException: AuthorizationManager
    check failed. ---> System.Runtime.InteropServices.COMException: The
    service cannot be started, either because it is disabled or because it
    has no enabled devices associated with it. (Exception from HRESULT:
    0x80070422)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementScope.InitializeGuts(Object o)
       at System.Management.ManagementScope.Initialize()
       at System.Management.ManagementObject.Initialize(Boolean getObject)
       at System.Management.ManagementObject.Get()
       at System.Management.Automation.PsUtils.GetParentProcess(Process current)
       at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
       at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
       at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
    at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo
    commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
    at
    System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
    commandInfo, CommandOrigin origin, PSHost host)
       --- End of inner exception stack trace ---
    at
    System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
    commandInfo, CommandOrigin origin, PSHost host)
       at
    System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext
    context, PSHost host, CommandInfo commandInfo, CommandOrigin
    commandOrigin)
       at
    System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo
    commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope,
    SessionStateInternal sessionState)
       at
    System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String
    commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
       at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
    at
    System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor
    pipe, CommandParameterInternal[] commandElements, CommandBaseAst
    commandBaseAst, CommandRedirection[] redirections, ExecutionContext
    context)
       at
    System.Management.Automation.PipelineOps.InvokePipeline(Object input,
    Boolean ignoreInput, CommandParameterInternal[][] pipeElements,
    CommandBaseAst[] pipeElementAsts, CommandRedirection[][]
    commandRedirections, FunctionContext funcContext)
       at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
    [07/22/2013 13:57:01.0373] [1] [ERROR] The following error was generated when "$error.Clear();
                        & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                    " was run: "AuthorizationManager check failed.".
    [07/22/2013 13:57:01.0373] [1] [ERROR] AuthorizationManager check failed.
    [07/22/2013
    13:57:01.0373] [1] [ERROR] The service cannot be started, either
    because it is disabled or because it has no enabled devices associated
    with it. (Exception from HRESULT: 0x80070422)
    [07/22/2013
    13:57:01.0388] [1] [ERROR-REFERENCE]
    Id=AllRolesMidFileCopyComponent___af0f15afe35c4e7cba121e546f405214
    Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [07/22/2013 13:57:01.0388] [1] Setup is stopping now because of one or more critical errors.
    [07/22/2013 13:57:01.0388] [1] Finished executing component tasks.
    [07/22/2013 13:57:01.0435] [1] Ending processing Start-MidFileCopy
    [07/22/2013 13:58:09.0121] [0] End of Setup
    [07/22/2013 13:58:09.0121] [0] **********************************************
    I also have these two errors in event viewer that keep occuring. 
    Event 2280, IIS-W3SVC-WP
    The Module DLL C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll failed to load.  The data is the error.
    Event 2300, IIS-W3SVC-WP
    The
    worker process cannot access the CLR configuration file at 'C:\Program
    Files\Microsoft\Exchange
    Server\V15\bin\GenericAppPoolConfigWithGCServerEnabledFalse.config'. 
    Verify that the file exists and that the worker process has read access
    to the file.

    I kept quickly running the following two commands while the install was happening
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    set-service -startuptype
    automatic
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    Start-Service
    This caused the install to succeed. 

  • Mails were deleted automatically from inbox and sent items, even in deleted items in Exchange 2013 CU2

    Dear all:
    I encountered a problem and needs to be solved.
    We runs Exchange 2013 CU2, and some users told me that their mails in sent items and inbox were automatically delivered into "deleted items", especially in last two weeks or yesterday.
    The users said they cannot delete so many mails at one time. And now I found one user's mails in "deleted items" were also deleted this morning.
    I don't know whether it was bug or not in exchange 2013 cu2, and how to solve this problem? Thanks for any help.
    koiso 
    Technet Microsoft

    Hi koiso,
    Are there any commons among problematic users or deleted emails? For example,
    they are on the same database
    they have delegate settings
    they are using mobile phone to sync emails
    At the same time, I'd recommend you enable Mailbox Audit Log for the problematic users. For your reference:
    http://technet.microsoft.com/en-us/library/ff459237(v=exchg.150).aspx
    Regards,
    Rebecca Tu
    TechNet Community Support

  • Migrate mailboxes from Exchange 2013 to Exchange 2010

    Hello,
    We have a merger and would like to know if it is possible to migrate mailboxes from Exchange 2013 to Exchange 2010 in a cross-forest scenario.
    Or should we first upgrade destination Exchange 2010 to 2013?
    Peteris

    Hi Peteris,
    Based on my tests, we can move mailboxes from Exchange Server 2013 to Exchange server 2010. You can use the Prepare-MoveRequest.ps1 script in the EMS to prepare mailboxes for cross forest moves.
    For more information about it, here is a helpful article for your reference.
    Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
    http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
    Hope my clarification can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 CU2 to CU3 upgrade error

    I'm getting this error when running an Exchange 2013 CU2 to CU3 upgrade. Please help!
    Error:
    The following error was generated when "$error.Clear(); 
              $keyPath = "HKLM:\Software\Microsoft\WebManagement\Server";
              if (!(Get-Item $keyPath -ErrorAction SilentlyContinue))
                New-Item $keyPath -Force
              Set-ItemProperty -path $keyPath -name "EnableRemoteManagement" -value 0x1 -Type DWORD -Force;
              if (Get-Service WMSVC* | ?{$_.Name -eq 'WMSVC'})
                Set-Service WMSVC -StartupType Automatic
                Stop-SetupService -ServiceName WMSVC;
                Start-SetupService -ServiceName WMSVC
            " was run: "Service 'WMSVC' failed to reach status 'Running' on this server.".

              if (Get-Service WMSVC* | ?{$_.Name -eq 'WMSVC'})
                Set-Service WMSVC -StartupType Automatic
                Stop-SetupService -ServiceName WMSVC;
                Start-SetupService -ServiceName WMSVC
            " was run: "Service 'WMSVC' failed to reach status 'Running' on this server.".
    Is the certificate for Web Management Service (WMSvc) missing?
    If so, then you need to create a new one and assign it to the feature "Management Service" in IIS.
    Martina Miskovic

  • Migrating to Exchange 2013 from Exchange 2003, EV7, Office 2003 and XP

    What is the best approach for migrating our 300 user Exchange 2003 organisation to Exchange 2013.? We use Enterprise vault v7.5 and the clients are Office 2003 on an XP desktop.
    We are also planning to upgrade to Windows7 and Office 2013 this year so I am trying to understand the sequence. Should we just aim to upgrade to Exchange 2010 with Outlook 2010 instead?
    Many thanks.

    Hi,
    You can't install Exchange 2013 until and unless you decommission your Exchange 2003. Coexistence of Exchange 2013 with Exchange 2003 is not supported. You first need to upgrade to Exchange 2010 SP3 and then move users to Exchange 2010 and decommission your
    Exchange 2003 servers. Once you are done with the decommissioning of your Exchange 2003 server you will be able to install your first Exchange 2013 machine in your messaging infrastructure.
    Kindly mark this as answer if it fulfill your requirements. Thanks.
    Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

  • OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.

    hi ALL
    OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
    Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
    2 cas Servers
    first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
    Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
    please support
    thanks

    Hi,
    According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
    If I have misunderstand your concern, please do not hesitate to let me know.
    I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
    Please run following command to double check the database status:
    Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
    If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
    for further troubleshooting.
    Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
    Best Regards,
    Allen Wang

Maybe you are looking for