Exchange 2013 Autodiscover and Webservices virtual directories with wrong address

Hey people,
I have 3 2013 Servers
Server 1 CAS
Server 2 & 3 MBX
having a bit of trouble here - everything was working fine after migration (about 6months ago), and now mac users can't access e-mail.
 If I try to access EWS page (https://webmail.domain.co.ao/EWS/exchange.asmx) , i get
Service
You have created a service.
To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:
svcutil.exe https://SERVER2.domain.int:444/EWS/Services.wsdl
If I try to access the autodiscover webpage, i get
<?xml version="1.0" encoding="UTF-8"?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">-<Response>-<Error Id="1286627925" Time="17:58:59.7730521"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>
When testing outlook web services, i get the following error
[PS] C:\Windows\system32>Test-OutlookWebServices
Source ServiceEndpoint Scenario Result Latency
(MS)
SERVER2.domain.int webmail.domain.co.ao Autodiscover: Outlook Provider Failure 64
SERVER2.domain.int Exchange Web Services Skipped 0
SERVER2.domain.int Availability Service Skipped 0
SERVER2.domain.int Offline Address Book Skipped 0
if i run
[PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory | fl
Creating a new session for implicit remoting of "Get-AutodiscoverVirtualDirectory" command...
RunspaceId : 9f23dad1-7806-42a6-8545-89b66847a359
Name : Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
OAuthAuthentication : True
AdfsAuthentication : False
MetabasePath : IIS://SERVER1.domain.int/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 775.38)
Server : SERVER1
InternalUrl : https://webmail.domain.co.ao/autodiscover/autodiscover.xml
ExternalUrl : https://webmail.domain.co.ao/autodiscover/autodiscover.xml
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web
Site),CN=HTTP,CN=Protocols,CN=SERVER1A,CN=Servers,CN=Exchange Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=int
Identity : SERVERONE\Autodiscover (Default Web Site)
Guid : fbed978f-7442-46ac-bb3c-53d9d7995507
ObjectCategory : domain.int/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 12/19/2013 10:30:26 AM
WhenCreated : 12/19/2013 10:30:26 AM
WhenChangedUTC : 12/19/2013 9:30:26 AM
WhenCreatedUTC : 12/19/2013 9:30:26 AM
OrganizationId :
OriginatingServer : DC2.domain.int
IsValid : True
ObjectState : Changed
and run
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | fl
RunspaceId : 9f23dad1-7806-42a6-8545-89b66847a359
CertificateAuthentication :
InternalNLBBypassUrl :
GzipLevel : High
MRSProxyEnabled : False
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Digest}
ExternalAuthenticationMethods : {Basic, Digest}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication : False
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : True
WindowsAuthentication : False
OAuthAuthentication : False
AdfsAuthentication : False
MetabasePath : IIS://SERVER1.domain.int/W3SVC/1/ROOT/EWS
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\EWS
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 775.38)
Server : SERVER1
InternalUrl : https://webmail.domain.co.ao/EWS/exchange.asmx
ExternalUrl : https://webmail.domain.co.ao/EWS/exchange.asmx
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=SERVRE1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=DOMAINL,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainl,DC=int
Identity : SERVER1\EWS (Default Web Site)
Guid : cbdd447b-54f8-4bba-9834-6c28b807711e
ObjectCategory : domain.int/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged : 12/19/2013 9:31:11 AM
WhenCreated : 12/19/2013 9:31:11 AM
WhenChangedUTC : 12/19/2013 8:31:11 AM
WhenCreatedUTC : 12/19/2013 8:31:11 AM
OrganizationId :
OriginatingServer : DC2.domain.int
IsValid : True
ObjectState : Changed
Summarizing:
webmail.domain.co.ao maps to server1
Autodiscover and exchange web services point out to server1 (CAS), but when openning the respective webpages, the result is an error.
I have already deleted and recreated the autodiscover and EWS virtual directories but with no success.
Help anyone?
Many thanks,
Andrey

Hi Andrey,
Exchange Web Service in Exchange server configuration is working for all users in your Exchange environment, not just for one specific user. If you want to double make sure the EWS service in client side, we can directly access the EWS URL in IE of your
Windows machine, and see whether a proper XML file is returned. If so, then we can safely ignore the web service test result.
As for automatic signature application, do you mean
Add a signature automatically to every message? Please try to remove the signature and reset it again to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Similar Messages

  • Creation of a second Exchange 2013 server on a different site (with the roles of MBX and CAS) fails on prepare active directory and prepare schema.

    Hello everyone
    I have a network infrastructure  consisting of 3 sites, site A, site B, and site C. i have 2 domain controllers on every site, and the AD roles are on the primary domain controller on site A. On site A I have an Exchange 2013sp1 CU6.
    I want to create a second Exchange on Site B, with the roles of mailbox (the exchange on Site A will be first DAG member and the Exchange on Site B will be the second member of the DAG) and CAS.
    First question: Is my  thought correct about installaing on the same server mailbox and CAS server?
    Second question: how many DAG witnesses I need for the DAG? One per site, or one in general (for example located on site A)
    Third question: When I am trying to perform “Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”  I receive the error
    “ Setup encountered a problem while validating the state of Active Directory:
     The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema can't be executed.  See the Exchange setup log for more information on this error. For more information, visit:
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
    I tried  to run the PrepareSchema from  the ISO of Exchange 2013 SP1 and form the extracted content of Exchange 2013SP1 CU6 archive, but still receive the same error. Any ideas?
    Thanks in advance.

    Thank you for your answer,
    I have tried to run "Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”  from
    Exchange 2013 CU6 media, but I still receive  the error:
    The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema
    can't be executed.  See the Exchange setup log for more information on this error. For more information, visit:http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
    any ideas?

  • Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

    I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
    on our system".
    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
    I've followed this post as a guide but it hasn't resolved my issue.
    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
    My Exchange environment looks like this:
    Site 1:
    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13
    Site 2:
    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13
    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
    Any help is greatly appreciated. I'd love to get rid of Unity. 
    EDIT:
    I just found this event in the event logs:
    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
    but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    9.1.2 I think it is, we upgraded to avoid the known DNS bug
    I cant see how to PM you either
    The crux of it was outlined below with some tweaks
    http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
    as any other CAS based service - point to 2013, and it will handle the rest

  • Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

    Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
    I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
    Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
    Error look like - cannot find exchange server.
    I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
    Someone have the same problem with migrated mailbox? How to solve it?
    Truly, Valery Tyurin

    You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
    Moreover, you can try this utility (
    http://www.exchangemigrationtool.com/ ) to accomplish this task.

  • Exchange 2013 migration and Lync server

    hi guys,
    i wanna upgrade my exchange 2010 to 2013 in our company.
    but i faced with a question
    will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
    plz help me 
    thanks guys

    Hi,
    you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
    Here is a guide for enabling IM in OWA:
    http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
    Just remember to point DNS to the New Exchange 2013 server and it should be fine.
    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

  • Seting up virtual directories with Weblogic

    Is there a way to set up virtual directories with Weblogic?

    It's really simple.
    I'm running out of space on the server X server
    I want to move some of the share point to the terastation; and possible new users home directory as well.
    I've tried mounting the terastation to the AD of the Xserver, but it doesn't work, for whatever reason, always return me a login error. (but I can mount any windows computer without any problem)
    DaddyPaycheck > I tried with the faqs you sent me, tried with the "update" they have posted, NONE of them worked. I contacted buffalo and they send me another "update", it didn't work either.:-(
    GeekMan > How do you have it set up?
    Any suggestions???
    thanks

  • Office 2013 Home and Business License Compatability with Windows Server 2012 R2

    Are there any license issues with installing Office 2013 Home and Business on Server 2012 R2 operating system? 
    I am having inconsistent issues installing this software on a server running this operating system.  The Office software is not being acccesed by client workstations.  Its a stand alone software installation for the server.  Are there any
    special installation procedures I must follow or software registration procedures I must follow?
    Microsoft website states Office 2013 Home and Business is compatible with Server 2012 but doesnt include the an R2 version reference.

    Hi,
    Please note only Volume Licensing editions of Office may be used on RDS host server. Since Home and Business is a Retail edition, it's not suitable/permitted if you are using RDS.
    Regards,
    Melon Chen
    TechNet Community Support

  • Exchange 2013 CU5 fresh install suffering issues with services not starting and coexistence with 2007

    Hi everyone,
    Hope you can help me out on a couple of issues I've been experiencing during the initial stages of a project to upgrade an on premise Exchange 2007 to 2013.
    On Monday last week I installed the first Exchange 2013 server into the network after a few weeks of careful planning, information gathering and remediation of our current Exchange 2007 environment and associated systems.
    The server itself has been having some issues from the word go, some of which I've resolved but none that are show stoppers but I want to get them resolved before building more servers and setting up the planned 2 x 2 node DAG's
    The main problems are as follows:
    There's usually one service that does not start following an OS restart and it's not always the same service. So far I've seen the following not start: DAG Management, Migration Workflow, Anti-spam Update, Unified Messaging, UM Call Router, Transport
    Service.
    The critical system event log entries are complaining of timeouts when the services are starting up but I can't imagine that the servers boot time is too long...  It's a 2 vCPU/12Gb vRAM VM, Windows 2012 R2
    I receive an error in the Event Log regarding RPC over HTTP Proxy
    to one of the 2007 CAS servers (not our primary one). The first error was because the Windows Component was missing but since installing it, disabling Outlook Anywhere, reenabling it, restarting the server, I now have a new error which is shown further down
    this post
    The Exchange 2013 server install is pretty default, CAS/MBX roles and some basic configuration performed such as new DNS entries, Public SSL certs installed and assigned, URL's updates, SCP updated. I have review and resolved some errors from the event logs
    for over chatty warnings about disk space (the warning is that we have loads of space...)
    This is a brief outline of the environment:
    Exchange 2007 SP3 RU13
    UK - Two physical locations in a stretch LAN (100Mb WAN)
    4 x CCR Cluster Mailbox Servers in two separate CCR Clusters
    Cluster 1 - Windows 2003 R2: One physical, one virtual server - don't ask, legacy install and I know the virtual is not a supported configuration.
    Cluster 2 - Windows 2008 R2: Two virtuals - New cluster built following a 4 day failure of Cluster 1. The aim was to move to supported config and decommission cluster 1.
    Note: Migration of Cluster 1 to Cluster 2 was halted as 2013 was so close it seemed pointless to continue the migration and instead migrate both Clusters to 2013 once in production.
    2 x Virtual Windows 2003 R2 - Hub Transport Servers
    2 x Virtual Windows 2003 R2 - Client Access Servers
    1 x Virtual Windows 2003 R2 - Unified Messaging Server
    1 x Virtual Windows 2003 R2 - Edge Transport Server (DMZ)
    US - One physical location
    1 x Physical Windows 2008 R2 - Mailbox, Client Access, Hub Transport Server
    Exchange 2013 CU5
    UK - Installed into same site along side Exchange 2007 servers
    1 x Virtual Windows 2012 R2 - Mailbox, Client Access Server
    Problem 2 Error Message - Please note, server names and domain name changed:
    Log Name:      Application
    Source:        MSExchange Front End HTTP Proxy
    Date:          18/07/2014 10:00:37
    Event ID:      3005
    Task Category: Core
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      EXC2013.domain.local
    Description:
    [RpcHttp] Marking ClientAccess 2010 server EXC2007CAS1.domain.local (https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
    Event Xml:
    <Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>
      <System>
        <Provider Name="MSExchange Front End HTTP Proxy" />
        <EventID Qualifiers="32768">3005</EventID>
        <Level>3</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-07-18T09:00:37.000000000Z" />
        <EventRecordID>64832</EventRecordID>
        <Channel>Application</Channel>
        <Computer>EXC2013.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>RpcHttp</Data>
        <Data>EXC2007CAS1.domain.local</Data>
        <Data>https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll</Data>
        <Data>System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data>
      </EventData>
    </Event>

    Hi Off2work,
    I've gone through the article and the Get-OutlookAnywhere commandlet looks fine (especially when compared with our working CAS).
    Having looked through IIS I have spotted two additional misconfigurations with a missing setting to require SSL on the RPC folder and also the .NET version was not set.
    I've now set those to Require SSL and .NET 2.0.5072 however this has made no difference following restarted of both 2007 CAS and 2013 servers.
    I could potentially reinstall the CAS server or additionally decommission it as we have two of them and the other is not causing any errors with the 2013 server. This broken CAS server doesn't even have DNS records (except it's own hostname) or firewall
    rules pointing to it, nor does it have any active client connections if I check with a quick netstat -a
    As for UM, it's next on my list following some client/server connectivity testing so I have not yet assigned the SSL to the services or setup the dial plans, etc.
    The services do start most of the time, but others then don't so it's not a consistent issue with just this service. On my current boot, the DAG Management service failed to start, but again I don't have a DAG implemented yet.
    I will see if UM drops out of that list once I've configured it shortly
    Thanks for taking the time to respond (and that goes to DareDevil too)

  • We have a Exchange 2013 server and the Mailbox Database folder is filling up with .log files.

    We are migrating from Exchange 2010 to Exchange 2013.  We have installed the Exchange 2013 but it only has a couple of mailboxes on this server, all the mailboxes are still on the Exchange 2010 server.
    I have run a Windows Backup of the Exchange 2013 but I am still seeing a ton a log files in the mailbox folder.
    Also the database file is only about 1.1 GB but the backup is now 40 GB.  
    Is there something that can be done to truncate these logs and make the backup smaller?

    Hi ,
    1.Does the full backup completed successfully ?
    2.what about the status for the below mentioned command ? Does the mailbox database headers updated with the latest time and date ?
    Get-MailboxDatabase -Status | ft name,*full* -au
    3.Just check the application event logs for the event id
     2046  and that should state that the log truncation for the mailbox databases has been initiated or not.
    4.Before initiating the backup just make the exchange writer is not on error.
    vssadmin list writers
    In case if it on error state ,please restart the Microsoft exchange replication service and check the exchange writers status again by using the above mentioned command.
    Thanks & Regards S.Nithyanandham

  • Android & WM6.5 devices can't use ActiveSync with Exchange 2013, ADFS and WAP.

    Bit of a long winded title but I was trying to sum up the issue.
    Newly installed Exchange 2013 environment; we've setup external access for OA and ActiveSync.  We've used ADFS with WAP to publish the necessary paths etc.  We've setup DNS and firewall rules etc.
    OA is perfect and can be accessed by anything with a browser.  ActiveSync is perfect for any new Windows Mobile device and any iOS device.  When we've tried to sync older WM6.5 or any Android device, it just doesn't seem to want to work.
    We've checked logs on both devices; the WM6.5 complains about a cert issue however we've took every step from installing the CA, RA and actual cert on the device to no avail.  Some android device complain about using the port 443 but no matter what
    we change this to it still won't sync.
    Unfortunately my suggestion of 'just give everyone a new phone' went down as well as...well lets just say not good :)
    I appreciate this might be an ADFS\WAP issue but thought I'd rule Exchange out first so any advice is much appreciated.

    We are having issues on connecting ActivySync on Microsoft Exchange 2013.
    OWA,OutlookAnywhere is working
    ActiveSync is not working.
    can you help us or share the configuration.
    We have Used MS UAG2010 SP4 to publish Exchange 2013 SP1 (On premises).
    Regards,
    Furqan

  • Exchange 2013 autodiscover not working from Externally

    Hi 
    i have exchange 2010 sp3(2Mb, 2hub/cas). I installed exchange 2013 servers(2MB, 2CAS). For coexistence i generated new certifcate with new cas from third party. I installed that certificate in that cas and assigned all services. i changed all my virtual
    directories service url. I didnt import the new certificate to exchange 2010 cas server and i didnt change url to legacy link.But still iam able to check exchange 2010 user mailbox owa, activesync and autodiscover without any certificate error. 
    If i try to browse owa, its going to 2013 server, if user is exchange 2010 user and its redirecting to exchange 2010 owa with same link.
    But i dont know how above things is working without importing to new certificate...
    Main problem is i am not able to configure exchange 2013 users outlookanywhere, Autodiscover from externally...
    So in tmg i pointed the outlook anywhere ip address new cas server, now both exchange 2010 and exchange 2013 users while OA from external, its keep on asking password... Not accepting it...
    Please help me to fix this issue..

    Hi ,
    On TMG please have the outlook anywhere rule like below and check the status.
    Step
    1 :
    On the TMG rule - >authentication delegation ---> select the option "no delegation users can authenticate directly"
    Step
    2 :
    on the users tab in the TMG rule - just add "all users" group on that rule.
    By having the above settings we have avoided the issues in your environment.
    Note : Based on the above setting's , Each and everyone in exchange will have a access to the outlook anywhere from external world , because there would not be having any restriction on the TMG rules.
    Please have a look in to the below link , it will give you some ideas which is related to TMG
    http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
    Thanks & Regards S.Nithyanandham

  • Exchange 2013 2 Node Multi role Servers with DAG issues connecting OWA users

    Hi
    I am on a job at the moment whereby I have 2 exchange 2013 multi role servers. Both are CAS and Mailbox servers. I have 2 databases, 1 called MBXDB01 and the other MBXDB02. MBXDBX01 is on Server 1 and 02 on Server 2.
    I have created a DAG and included both databases. Active copy of MBXDB01 is on Server 1 and MBXDB02 on Server 2
    I have configured the external and internal URLS of all virtual directories on both servers to be the same publically accessible FQDN. I have assigned the trusted cert to IIS and all other services on both servers. I have modified internal split brain DNS
    to point the FQDN used to both Server 1 and Server 2 IP addresses with a TTL of 30 seconds. And also for autodiscover.
    All test exchange connectivity comes back green and good from external and from outlook Test-Autoconfiguration autodiscover information is displayed correctly.
    The problem I am having is that when a user access the FQDN from a web browser i.e owa.domain.com/owa they get the login screen. This could be from either server 1 or 2 depending on DNS round robin. In this example lets say the user is accessing OWA on SERVER
    1 and their mailbox lives on SERVER 2.
    In this scenario when they login they get a page :( OOps Something Went Wrong and the exception is this
    A problem occurred while you were trying to use your mailbox.
    X-OWA-Error: Microsoft.Exchange.Data.Storage.UserHasNoMailboxException
    X-OWA-Version: 15.0.847.32
    X-FEServer: SERVER1
    X-BEServer: SERVER2
    The URL provides a little more info
    /auth/errorfe.aspx?httpCode=500&msg=861904327&owaError=Microsoft.Exchange.Data.Storage.UserHasNoMailboxException&owaVer=15.0.847.32&be=SERVER2&ts=130398071193518373
    However, if the user accesses OWA via the private FQDN of SERVER 2 i.e https://SERVER2/owa they are able to access their mailbox.
    It is driving me nuts.
    Has anyone got any suggestions? I am tearing my hair out here
    Thanks
    One very frustrated field engineer :)

    Hi,
    To narrow down the cause, I recommend the following troubleshooting:
    1. Please double check the DNS entries about the host name used in the OWA URL.
    2. Add A record that the host name used in the OWA URL points to server 2 IP address  in a user local host file. Then try to login OWA again.
    3. Check your event log and find if there is any error about OWA.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2013 certtificate and FQDN of CAS/MB servers

    Good Morning,
    I have read articles that say I should not need anything but the fqdn names of things like autodiscover.mycompany.com and mail.mycompany.com on the cert you install on the exchange server. I went that route and installed it on every exchange server
    but for some reason, the client gets prompted for credentials with this configuration.
    When I create a cert with all the CAS/MB FQDN names ( ie. casmb01.mycompany.pvt) on the cert, they do not get prompted and the exhttp allows the outlook client to connect properly.
    this is a 2007 to 2013 migration. I am testing just the connectivity and have not put the 2013 as the proxy yet.
    The clients also have an internal host name .pvt in the cert so I would imagine this would be a problem for outlook anywhere unless they vpn in and trust the local CA.
    Can I use only the autodiscover and mail .mycompany.com
    does anyone else have this set up this was?
    thanks
    Paul

    Here's what I would do:
    If you are planning on allowing people to access Outlook Anywhere and Active Sync Externally
    Since you can only have 1 cert bound to IIS I would create the cert via a 3rd party CA.  They will only give you a cert for publicly accessible tlds. So on that cert you will need mail.company.com, autodiscover.company.com
    and legacy.company.com.  The legacy can really be anything you want, and is needed for OWA and  ActiveSync redirection.  Once I have the cert, I would change all the virtual directories to have their respective *.company.com addresses.  In
    order for this to work properly with DNS (internally you get an internal address) you will need to create a dns zone called mail.company.com and point that to your 2013 CAS servers and another one for legacy.company.com and point that to your 2007 Servers.
    If you are not allowing any external access then you can just create whatever certs you want to via your internal CA.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • EXCHANGE 2013 - ECP AND OWA INTERNAL ERROR 500 - NEW INSTALL

    Really hoping someone can help me here.
    I first installed 2012 OS and 2013 exchange and users were getting 'Unable to open your default folder' when trying to open outlook. After much googling and nothing working I decided to put 2008 R2 on the server with 2013 Exchange. Now i am running into massive
    issues. 
    Firstly i get Internal Errror 500 after putting in credentials for ECP and OWA. I did notice that it is also defaulting straight to this URL after entering password https://localhost/owa/auth.owa
    I check the management shell and that connects without any issues. I also logged on to a computer to see what it did. After autodiscover it is not able to log onto server and then it looks like it is look for the old server information from previous server.
    Any help would be appreciated. Can i do another reinstall of OS and how am i meant to remove the previous data that it seems the server has found?

    Hi,
    According to your description, I understand that cannot login internal ECP\OWA with error 500, also autodiscover failed.
    If I misunderstand your concern, please do not hesitate to let me know.
    I notice that autodiscover “looks like it is look for the old server information from previous server”, have you installed multiple version Exchange in your environment?
    Please run below command to double check the virtual directory configuration:
    Get-OutlookAnywhere | FL Identity,*Host*,*Auth*
    Get-OwaVirtualDirectory | FL Identity,*url*,*auth*
    Get-EcpVirtualDirectory | FL Identity,*url*,*auth*
    Get-WebServicesVirtualDirectory | FL Identity,*url*,*auth*
    Get-ClientAccessServer | FL Identity,*URI*,*auth*
    Then, open IIS and check on the Application Pools to view whether MSExchangeOWAAppPool and MSExchangeECPAppPool is running on .NET Framework v4.0, and recycle virtual directory for test.
    Additional, here’s a thread about “Removing Old Exchange and installing a new one”, for your reference:
    https://social.technet.microsoft.com/forums/exchange/en-US/46ca107c-7ece-4da7-8aea-46b705793f37/removing-old-exchange-and-installing-a-new-one
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Update from Exchange 2013 Cu2 to SP1 - Outlook 2010 with SP2 clients disconnected

    Hi,
    we recently upgraded a standalone Exchange 2013 Server to SP1. Owa works fine, but all internal Outlook 2010 Clients (with SP2) get disconnected. Creating a new Profile, and testing the internal autodiscovery leeds to an Error 12030 (Connection reset) during
    the discovery process.
    I already checked the Service Point, the discovery URLs, even recreated the autodiscover virtual Directory in iis. But nothing changed.
    The self signed certificate, that was used before the update is further used, and well known to all Clients. As I tested, OWA is working well everywhere.
    Anyone some new ideas?
    Best regards
    Bernhard

    Hi,
    How did you recreate outlook profile? Manually or Automatic?
    If automatic failed, please try to recreate manually and check the result.
    If manual failed, please refer to the following methods to troubleshoot the issue:
    1>Try to open the following link and check the result:
     https://CASName/autodiscover/autodiscover.xml
    2>Try to use RCA to test outlook autodiscover and check the result.
    https://testconnectivity.microsoft.com/
    Thansk.
    Niko Cheng
    TechNet Community Support

Maybe you are looking for