locked
Interal OWA URL points to a failed server RRS feed

  • Question

  • Environment
    Exchange 2007
    2 CAS,/HUB servers
    1 mailbox server
    1 failed server that was a CAS and Hub. Hardware failure, can't bring it back.
    1 exchange 2003 server that may still have hooks in 2007

    Running the email autoconfiguration test it shows the internal OWA URL as https://failedserver.company.com/owa

    In EMC Server configuration, client access, owa properties the internal and external urls are set the same on both the CAS/HUB to https://webmail.company.com

    When I run Get-WebServicesVirtualDirectory it gives an error saying task was not able to connect to IIS on the server failedserver.company.com...

    What user's notice sometimes is that they can't set their OOF and see free/busy information.  Just today I found that the mailbox database that most users are in had the default public folder set to a database on the 2003 server.  I switched it to the 2007 public folder database and stopped the Exchange services on the 2003 server.  I hope those are the last hooks into the 2003 server so I can uninstall exchange 2003 from it and properly decommission it.

    What a messy situation.  We are licensed for 2013 but I've heard some horror stories which are making me hold off on upgrading.

    TIA

    Thursday, October 10, 2013 8:26 PM

All replies