Exchange Server 2013 OAB Web Distribution Configuration in Exchange 2010 & 2013 Coexistence.

Hi,
We have OAB Issue for Exchange 2010 Users in our Organization.
We have Exchange 2010 and Exchange 2013 Coexistence.While Checking in Exchange Server 2010 Server OAB properties in Org Configuration--> Mailbox-->OAB Properties -->Distribution we are not seeing any CAS servers and Its Grayed Out.
Please let us know How to add Exchange 2010 CAS in Exchange 2013 Web distribution.

They made alot changes with the OAB in Exchange 2013, and it doesn't really function in the same manner as it did in 2010.  It might be best to take a look at the following blog posts from the Exchange Team, they should give you a better understanding
on how it works and how to manage it going forward.
http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
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

Similar Messages

  • External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

    I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
    the Exchange 2010 all incoming external mails were not received. What could be the cause?

    Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
    Sniff the traffic to ensure that it is hitting 2013 directly.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 - 2003 coexistence "unable to relay"

    Hi
    I have a customer with a Exchange 2010 / 2003 coexistence. 
    The Exchange 2010 has 3 CAS/HT servers. 
    When sending mails from 2003 to the outside world, one of the CAS/HT is giving me "unable to relay".
    Right now I have removed it from the routing group connector, but do you have any ideas where to look?
    BR
    Steen

    Hello,
    If there is only AD site, the receive connector is not needed.
    If there are multiple AD sites, when you send message to other AD sites, the receive conenctor is needed. If you send message from exchange 2003 to exchange 2010 or exchange 2010 to exchange 2003, the routing group connector is needed.
    Cara Chen
    TechNet Community Support

  • Pull POP client web to Exchange Server 2013

    Hi, i am new in Microsoft Exchange Server and Email Server Administrator. At present, my company planed to have a Microsoft Exchange Server 2013 and my scope will pull data from the web-client using POP3  to the Exchange. Would you guys give me any solution
    and advice for this? Thanks a ton
    Sorry for my bad English.

    Hi,
    What’s the exact mean of “pull data from the web-client using POP3  to the Exchange”? Do you mean the Outlook client connects to Exchange 2013 with POP protocol?
    If that is the case, please enable and configure the POP in your Exchange server by the following article:
    https://technet.microsoft.com/en-us/library/bb124934(v=exchg.150).aspx
    Generally, POP3 was designed to support offline mail processing. With POP3, email messages are removed from the server and stored on the local POP3 client unless the client has been set to leave mail on the server. For more information
    about POP3 in Exchange 2013, please refer to:
    https://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx
    Regards,
    Winnie Liang
    TechNet Community Support

  • Configuring Lync Server 2013 to be a partner Application for Exchange 2013

    Hello Guys,
    I just want to share my experience while configuring Lync server 2013 to be a partner Application for exchange 2013 sever. 
    As mentioned on technet you need to run Configure-EnterprisePartnerApplication.ps1 script that ships with Exchange 2013. 
    But when I tried to run the script as described on the technet article, I found it always fails with " the accepted domain is not valid"
    I have checked my accepted domains many times and i found that there's no issues with my configured accepted domain. 
    So I started to review the script to find the issue and I found that the script was configured  as below 
    $acceptedDomains = Get-AcceptedDomain ;
      if ($acceptedDomains -eq $null)
        WriteError ("There is no accepted domain so user can not be created.")
      $acceptedDomain = $acceptedDomains[0].Name;
      if($UseDomainController -eq $true)
        $user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
      else
        $user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true; 
    which is totally wrong as below: 
    firstly it makes $AcceptedDomain variable to equal the Name of the accepted domain. 
    Not all customers configure the name of the Accepted Domain to be the Domain Name.
    Secondly  it makes $AcceptedDomain variable to equal the name of the first Accepted Domain.
    The first domain may be not the default Accepted Domain. 
    So I have configured the script as below
    $acceptedDomains = Get-AcceptedDomain | ? {$_.Default -eq "True"}  ;
      if ($acceptedDomains -eq $null)
        WriteError ("There is no accepted domain so user can not be created.")
      $acceptedDomain = $acceptedDomains.DomainName;
      if($UseDomainController -eq $true)
        $user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
      else
        $user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true; 
    I hope This help. 
    Thanks 
    Ahmed Fouad

    Hi,
    This is helpful, thanks for sharing.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Using Office Web Apps Server 2013 without SharePoint, Lync, or Exchange

    I'm trying to use the Office Web Apps Server 2013 as an online viewer of Office documents (using the Online Viewer). I've set up a New-OfficeWebAppsFarm with editing disabled, no UNC paths, and an external URL with SSL Offloaded to my Load balancer.
    I don't want to use it with SharePoint, Lync or Exchange. Just use it to view documents online (similar to Google Docs Viewer).
    However, when I point the Office Web Apps Server to a remote file online (e.x. a DOC hosted on a website), I get an error opening it.
    I've checked the health statuses of my OWA Servers, and it says Healthy.
    When I check the Event viewer of my OWA Server, I see 501 WOPI errors:
    Could not contact WOPI End Point. Error details - 'NotImplemented url - https://sample-owa-url.com/oh/wopi/files/@/wFileId?wFileId=http%3A%2F%2Fwww%2Eimr%2Esandia%2Egov%2Fimrtemplate%2Edoc&access_token=1&access_token_ttl=0'.
    It seems OWA is trying to connect to the path /oh/wopi/files....  but the server is responding NotImplemented.
    What do I have to get this to work?
    Thanks for any help!

    Did you ever find an answer? I have the exact same Issue.
    I have 2 WAC servers behind a load balancer with SSL offloaded to the LB. Both servers report healthy with Get-OfficeWebAppsMachine
    Works fine with SharePoint 2013.
    When I use it with a remote file, served using HTTP with no authentication (anonymous), I get a generic "Sorry there was a problem and we can't open this document..." error.
    In the ULS and event viewer, I see the WOPI error and 501 which basically says:
    Could not contact WOPI End Point. Error details - 'NotImplemented url - https://sample-owa-url.com/oh/wopi/files/@/wFileId?wFileId=http%3A%2F%2Fwww%2Blah%2Ecom%2FWordDocument%2Edocx&access_token=1&access_token_ttl=0'.
    I also sometimes see this:
    <HealthMessage>WordViewerWfeWatchdog reported status for WebWordViewer in category 'WfeRedirect'. Reported status: /default.aspx returned a 404, which means that we didn't have where to redirect.</HealthMessage> 
    The very interesting part s that I have a dev server, with OWA (WAC) installed, thats not going through a LB and does not use SSL, that works just fine with the same public url word document.

  • Exchange server 2013 change to web access url

    I have install & configure exchange server 2013 in my local pc. my ip address http://192.168.0.30/ecp but not access http://mail.test.com/ecp. and till i have purchased one mail so till i wants to my mail server access (send and received mail all mail
    id public and private) please send configuration url. 

    hi pardeep not sure if i understood well.. you have  private IP and you want to do send receive.. is that.. for the test you can do it but almost 90% or more, your mails will be sent to SPAMS.
    so if this is a test environment you can give a shot. let me know what kind of config you are looking for. below link will cover the config of exchange 2013. Let me know if you need more help.
    www.techieshelp.com/exchange-2013-step-by-step-configuration/
    MARK AS USEFUL/ANSWER IF IT DID
    Thanks
    Happiness Always
    Jatin

  • Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?

    Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?
    We recently upgraded from Exchange 2010 to Exchange 2013.
    The links that used OWA Web parts have completely stopped working and generate the " :( something went wrong contact your help desk" screen for domain Authenticated users other than myself. The links accessed content of a Shared Account of which
    I am an owner and can set the necessary permissions using the Outlook 2013 client.
    Using the example from the link provided below we were able to provide calendar access to all authenticated users in our area. The link for calendar still works for me but for noone else. Additionally, all navigation menus are missing when I use this link.
    <server>/owa/<SMTP address>/?cmd=contents&module=calendar&view=weekly name
    Another crafted link provided web access to our group's task list. This has completely stopped working for anyone including myself. However, when I use "open another mailbox" I am able to navigate to the needed pages.
    <server name>/owa/<SMTP address>/?cmd=contents&module=tasks
    These links were crafted using advice provided from this provided link.
    technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx
    Is it still possible to use Outlook Web App Web Parts in Exchange Server 2013 - OWA?
    Or
    Is this a misconfiguration of some sort?
    My IT support has given up and closed out the ticket stating that maybe Microsoft will fix this someday...

    Hello,
    At present, there is no official article to verify whether we can use Outlook Web App Web Parts in Exchange Server 2013. In exchange online, the Outlook Web App Parts is supported.
    Cara Chen
    TechNet Community Support
    Hi, you said this feature is supported in Exchange Online (I understand you're referring to Office 365). Can you please point me to some documentation as I was trying to use it with my E3 account and it doesn't seem to work?
    What I'm trying to acomplish is something similar to our old URL (Exchange 2010) in Office 365:
    https://ourserver.mydomain.com/owa/[email protected]/?cmd=contents&module=calendar&view=monthly
    The best I can do in Office 365 is this:
    https://outlook.com/owa/mydomain.com/[email protected]/#path=/calendar
    But it's clearly not the same and Office 365 ignores all the information I add to the URL. I would greatly appreciate something in the line of the document referred by 'MarquetteENG' (technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx)
    Thanks.
    Paulo.
    Paulo Dias - IT Pro Evangelist

  • How to clone Microsoft Exchange Server 2013 configurations from one server to another server?

    Hi! I need help of cloning Microsoft Exchange Server 2013 configurations from my first Server to the second Server. By doing this, the second Server will replace and run as per normal as the first Server is. How can this be done?
    Thanks!

    Cloning an Exchange Server is a very bad idea.  Exchange is very heavily intergrated into Active Directory and this can (and honestly not to sound scary probably will) cause major issues in your environment.  
    Also, since you cannot have 2 servers with the same name in the same domain/network running at the same time you'll need to change the name of one of the servers.   That is a huge no-no with Exchange and requires a complete uninstall/reinstall of the
    product.
    Now requirements differ between environments, but if you are in a scenario where you want to move from 1 Exchange 2013 (or 2010 for that matter) Server to another machine running the same version of Exchange AND (this is a big requirement for the failover
    cluster piece) the Operating Systems of the machines are the same (i.e going 2012r1 to 2012r1 or 2012r2 to 2012r2 and not 2012r1 to 2012r2) you can do what Brenle suggested with the DAG and DB copies. If the Operating System of the new machine is different
    (2012r1 to 2012r2) then you will will not be able to use a DAG, and will need to perform mailbox moves to move between servers.
    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

  • Installing and configuring Exchange Server 2013 on mobile boradband

    I'm trying to configure Exchange Server 2013 on my test server. But I have a mobile boradband connection for Internet. Therefore, I don't have port forwarding and a static IP. Since I'm a beginner, I want to know whether I can install and configure exchange
    server on my machine or whether there are workarounds for this. Thanks. 

    Hi,
    If you just want to work internally, I suggest build AD and DNS server on your lab and give it a static IP.
    If you want to work both internally and externally, I suggest publish your DNS.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • How to : Configure Project Server 2010 to work with Exchange Server 2013

    Hi everybody. I have a problem. I did integration success project server 2010 with exchange server 2010. But now my customer use exchange server 2013. So my question is "Have a way to integration project server 2010 with exchange server 2013 ?"

    I haven't seen any document with Project 2010 and Exchange 2013. You could still try the old document with Project 2010 and Exchange 2010.
    http://technet.microsoft.com/en-us/library/ff468700(v=office.14).aspx
    It might just work.
    Thanks Gaurav Wason MCITP, PMP

  • Configuring Multiple domain Email addresses in Exchange server 2013 for Send/Receive

    I've setup an exchange server 2013 , I have an requirement to setup email addresses for multiple domain account.
    For example - My primary email addresses - [email protected] however i need to setup multiple domain email account for single AD user.
    Example
    [email protected]
    [email protected]
    [email protected]
    I was able to setup account to receive email from different users to single mailbox users however how can i send mails from other domains email address apart from primary domain email 
    Thank you
    Benhur

    Hello,
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.
    Cara Chen
    TechNet Community Support

  • Trying to install Exchange Server 2013 and receive this error.

    Hello,
    I have a computer running Windows Server 2012 R2 Standard. I have completed all the prerequisites to install Exchange Server 2013. It all was going good until the install started. Then I received the below error. Does anyone have any suggestions? I am new
    to Exchange Server so would thank and appreciate any help I could get to resolve this issue.
    Thank You,
    Stan
    Error:
    The following error was generated when "$error.Clear(); 
    initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
    " was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:16cd035a-6201-492f-b85f-1e28cc9f9ee0,CN=Deleted Objects,DC=MULTIAXCNC,DC=local on
    the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MULTIAXCNC,DC=local points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.
       at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Here is the error I am getting and the last setup log I can find. Any help how to get past the error would be helpful.
    Thank You,
    Stan
    Error
    The following error was generated when "$error.Clear();
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.AddAccessRuleCryptographicException: Could not grant Network Service access to the certificate with thumbprint 845C42A131A8A73487400A91491182FB95B81612
    because a cryptographic exception was thrown. ---> System.Security.Cryptography.CryptographicException: Access is denied.
       at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.CAPIAddAccessRule(X509Certificate2 certificate, AccessRule rule)
       at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.AddAccessRule(X509Certificate2 certificate, AccessRule rule)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ManageExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services, String websiteName, Boolean requireSsl, ITopologyConfigurationSession dataSession, Server server,
    List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Setup Log Below
    # Default Install steps for ClientAccessRole.
    # Programmatically generated on 7/5/2014 10:58:24 PM.
    # Variable Declarations
    $RoleAllRoles = 'BridgeheadRole,GatewayRole,ClientAccessRole,MailboxRole,UnifiedMessagingRole,FrontendTransportRole,AdminToolsRole,MonitoringRole,CentralAdminRole,CentralAdminDatabaseRole,CentralAdminFrontEndRole,LanguagePacksRole,CafeRole,FfoWebServiceRole,OSPRole'
    $RoleBinPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Bin'
    $RoleCustomerFeedbackEnabled = $True
    $RoleDatacenterPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Datacenter'
    $RoleDatacenterServiceEndpointABCHContactService = '<ServiceEndpoint><Url>http://pvt-contacts.msn.com/abservice/abservice.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointDomainPartnerManageDelegation = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointDomainPartnerManageDelegation2 = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation2.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveFederationMetadata = '<ServiceEndpoint><Url>https://nexus.passport.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveGetUserRealm = '<ServiceEndpoint><Url>https://login.live.com/GetUserRealm.srf</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveServiceLogin2 = '<ServiceEndpoint><Url>https://login.live.com/RST2.srf</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointMsoFederationMetadata = '<ServiceEndpoint><Url>https://nexus.microsoftonline-p.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
    $RoleDomainController = 'MULTIAX2012.MULTIAXCNC.local'
    $RoleExternalCASServerDomain = $null
    $RoleFqdnOrName = 'MULTIAX2012.MULTIAXCNC.local'
    $RoleInstallationMode = 'Install'
    $RoleInstallPath = 'C:\Program Files\Microsoft\Exchange Server\V15\'
    $RoleInvocationID = '20140705-2258240578829153548'
    $RoleIsAdminToolsRoleInstalled = $True
    $RoleIsBridgeheadRoleInstalled = $True
    $RoleIsDatacenter = $False
    $RoleIsDatacenterDedicated = $False
    $RoleIsFfo = $False
    $RoleIsPartnerHosted = $False
    $RoleLanguagePacksPath = 'C:\Exchange\'
    $RoleLoggedOnUser = 'MULTIAXCNC\Administrator'
    $RoleLoggingPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Logging'
    $RoleNetBIOSName = 'MULTIAX2012'
    $RoleNoSelfSignedCertificates = $False
    $RolePreviousVersion = $null
    $RoleProductPlatform = 'amd64'
    $RoleRoleName = 'ClientAccessRole'
    $RoleRoles = 'BridgeheadRole,AdminToolsRole'
    $RoleSetupLoggingPath = 'C:\ExchangeSetupLogs'
    $RoleTargetVersion = '15.00.0913.022'
    $RoleUpdatesDir = $null
    # Component tasks
    # Tasks for 'All Roles Common First' component
    # [ID = AllRolesCommonFirst___3e69ba31a53e4c29a2d6bffcf78cc614, Wt = 5, isFatal = True] "Starting the WMI service."
    7/5/2014 10:58:24 PM:
              if (Get-Service winmgmt* | ?{ $_.Name -ieq "winmgmt" })
                Set-Service winmgmt -StartupType Automatic
                Start-SetupService -ServiceName winmgmt
    # [ID = AllRolesCommonFirst___56139ce4432346ecb7936afae4c3a9cc, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:24 PM:
              & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoleName.Replace('Role','')
    # [ID = AllRolesCommonFirst___edc23bc11a4e4119a6a4ee802ff1ea49, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:24 PM:
              if ($RoleRoles)
                & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoles.Replace('Role','').Split(',')
    # [ID = AllRolesCommonFirst___62f13a063b2846a5ab20765bb7a3fc51, Wt = 5, isFatal = True] "Starting the Remote Registry service."
    7/5/2014 10:58:25 PM:Start-SetupService -ServiceName RemoteRegistry
    # [ID = AllRolesCommonFirst___00573a17b6e34c26842a6646830d57fa, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:25 PM:Set-LocalPermissions
    # [ID = AllRolesCommonFirst___77668249568048d3812fb7cdba08c58b, Wt = 1, isFatal = False] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
              $mofFilePath =  ($RoleInstallPath + "bin\Exchange.MOF");
              $mflFilePath =  ($RoleInstallPath + "bin\en\Exchange.MFL");
              compile-moffile -MofFilePath:$mofFilePath;
              compile-moffile -MofFilePath:$mflFilePath;
    # [ID = AllRolesCommonFirst___f557448f44964e5eaa5dba792a3c4f09, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCByPortRule)
    # [ID = AllRolesCommonFirst___84a0f0e2c2f44db2b537e9696c26fc3e, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCEPMapByPortRule)
    # Tasks for 'ClientAccess Permissions Configuration' component
    # [ID = ClientAccessLocalPermissionsComponent___6246589bb8494a3580c22c26e18451d1, Wt = 1, isFatal = True] "Setting folder or registry permissions for the Mailbox role: Client Access service. "
    7/5/2014 10:59:35 PM:Set-LocalPermissions -Feature:"ClientAccess"
    # Tasks for 'Exchange 2003 Registry Configuration' component
    # [ID = LegacyRegistryMarkersComponent___7d6dadc1069b42ac93eadd1143c04a1a, Wt = 1, isFatal = True] "Installing/Removing registry values used by Exchange 2003 components"
    7/5/2014 11:00:01 PM:set-ExsetdataRegistryMarkers
    # Tasks for 'Client Access Perf Counters' component
    # [ID = ClientAccessPerfCountersComponent___deb99c54869843b68426390615283ab7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:01 PM:new-PerfCounters -DefinitionFileName OwaInstallSingleCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ca78563ec1f1468982d1a2e59c6001bd, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:15 PM:new-PerfCounters -DefinitionFileName EcpPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e69a559428fb42029ca3261e795b216d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:21 PM:new-PerfCounters -DefinitionFileName RwsPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___c335490f948a4b16b5e2d2ce5f1eb9e7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:26 PM:new-PerfCounters -DefinitionFileName InfoworkerAvailabilityPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___5af856aa00ae485ca206c5cdd13e9128, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:31 PM:new-PerfCounters -DefinitionFileName InfoworkerSharingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___86121d1b951e43fb934f1f1d573362eb, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:35 PM:new-PerfCounters -DefinitionFileName ThrottlingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ea5896b92c494834b1a93c4620fcaef4, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:42 PM:new-PerfCounters -DefinitionFileName MiddleTierStoragePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___dab6f03bdf5141efb7b017c3009fb9e6, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:48 PM:new-PerfCounters -DefinitionFileName ActiveManagerClientPerfmon.xml
    # [ID = ClientAccessPerfCountersComponent___5471455db0ef4610bf68fe7ad9417e19, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:53 PM:new-PerfCounters -DefinitionFileName RmsPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___81ad52cb2950483196b52371b4d992c8, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:58 PM:new-PerfCounters -DefinitionFileName InfoworkerMailTipsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___072bf6737f1c42a0a8847ce35cf8a0c7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:03 PM:new-PerfCounters -DefinitionFileName InfoworkerUserPhotosPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___50b64611f7444bb49d50e00c206d2c13, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:08 PM:new-PerfCounters -DefinitionFileName AirSyncCounters.xml
    # [ID = ClientAccessPerfCountersComponent___f2620ff8c3754396a8ea7d77257e2895, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:14 PM:new-PerfCounters -DefinitionFileName ClientAccessRulesPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___4ef0f16c017840a583ace9f062300207, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:19 PM:new-PerfCounters -DefinitionFileName Imap4Counters.xml
    # [ID = ClientAccessPerfCountersComponent___135fb06dadd9403a83ceebb290638efe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:24 PM:new-PerfCounters -DefinitionFileName Pop3Counters.xml
    # [ID = ClientAccessPerfCountersComponent___312e8d44e92b45e0809f9d3d5dc2cfc0, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:29 PM:new-PerfCounters -DefinitionFileName WsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___3c333497697041cb854190ec31c17b18, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:48 PM:new-PerfCounters -DefinitionFileName UMClientAccessCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ba015b97cc0b4beba7b25b6cb297fcac, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:54 PM:new-PerfCounters -DefinitionFileName AutodiscoverPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___3daffea50d5a4318aab4aa737e508146, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:59 PM:new-PerfCounters -DefinitionFileName OAuthCounters.xml
    # [ID = ClientAccessPerfCountersComponent___c71073d7f1ab4c119af83efb513b3a9d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:04 PM:new-PerfCounters -DefinitionFileName InfoWorkerMessageTrackingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___abdaf0bf21f4473b88819ee85cada219, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:10 PM:new-PerfCounters -DefinitionFileName RpcClientAccessPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___9f160f3e42984edfa25b62424ebc05b5, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName RpcClientAccessServerPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e55cb179521a4dacbeaa588c6948cf14, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName AddressBookServicePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___064a7856cf7c4b0399c85cf4f3bc2f1c, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:20 PM:new-PerfCounters -DefinitionFileName RpcEntryPointsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___42325F33-A961-41FE-B6B5-5CFB3AA9820A, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:22 PM:new-PerfCounters -DefinitionFileName MapiHttpEmsmdbPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___4C04D747-3B5C-400A-980F-45504324EF42, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:28 PM:new-PerfCounters -DefinitionFileName MapiHttpNspiPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___5ab36fffacd04975bb1bc681a214bf71, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:33 PM:new-PerfCounters -DefinitionFileName ThrottlingServiceClientPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___6ca23933132d44b39d6586cb3f9f8f21, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:39 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___6602c41b35254405bed412fab7d527fe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:44 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerMdbPerformanceCounters.xml -FileMappingSize 2097152
    # [ID = ClientAccessPerfCountersComponent___74e45a45ea8c449092a10929ae24ba4b, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:50 PM:new-PerfCounters -DefinitionFileName MlbPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___a3bcb686add64cf296c8616d387d0323, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:55 PM:new-PerfCounters -DefinitionFileName MlbMultiInstancePerformanceCounters.xml -FileMappingSize 2097152
    # [ID = ClientAccessPerfCountersComponent___c00c15c4ef6f479b9f5deb852d8eda7d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:01 PM:new-PerfCounters -DefinitionFileName ProvisioningPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___fe1a2a7c828f4b57abc2e50dc09baddf, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:06 PM:new-PerfCounters -DefinitionFileName GalsyncPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___35D14CB8B01949818832943A391D77B9, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName BackSyncPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e69599d235234effb6d2740f3c52f7e1, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName AdminAuditPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___09bd11b57f6445e890391a507262cf32, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName InfoworkerMultiMailboxSearchPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___324687361E1C473A834C22A66104679f, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName ProvisioningCachePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___98C36FFEC7944065889DB24067CFD3EE, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:21 PM:new-PerfCounters -DefinitionFileName OABRequestHandlerPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___1F5A7B68C95B42568E02FAA15A05EF17, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:26 PM:new-PerfCounters -DefinitionFileName DlpPolicyTipsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___995DEA7A1AC5467C89939F5F8CE5F2AF, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:31 PM:new-PerfCounters -DefinitionFileName ConfigurationCachePerformanceCounters.xml
    # Tasks for 'Client Access Configuration' component
    # [ID = ClientAccessComponent___d5119205104847bcb275cb63b65160b6, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:03:35 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Owa\Bin\Microsoft.Exchange.Clients.Owa.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___954344d74d8849e9ae7123b91761ed9d, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:03:57 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Sync\Bin\Microsoft.Exchange.AirSyncHandler.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___6632d6c1d5054563942db4f180976238, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:04:01 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\AutoDiscover\Bin\Microsoft.Exchange.AutoDiscover.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___390b4ffddd484dcb9edc01dd725e020a, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:04:07 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\exchweb\ews\bin\Microsoft.Exchange.Services.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___178a10624c88445093855c4ede7e9b9c, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:42 PM:
              . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
              Set-NtlmLoopbackCheck $false
    # [ID = ClientAccessComponent___14a6761e144e428b93c62249acc814fe, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:42 PM:install-ClientAccessIisWebServiceExtensions
    # [ID = ClientAccessComponent___28fdfe8bec984e809cdeef6d4d59bf4e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:43 PM:
            if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})
                restart-service MSExchangeServiceHost
    # [ID = ClientAccessComponent___7816256880dc4be0baf5b005b2af8cd3, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
            if (get-service MSExchangeProtectedServiceHost* | where {$_.name -eq "MSExchangeProtectedServiceHost"})
                restart-service MSExchangeProtectedServiceHost
    # [ID = ClientAccessComponent___e95499b43bd1484dbc03098fb1b4e592, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:set-ExchangeServerRole -Identity $RoleFqdnOrName -IsClientAccessServer:$true -DomainController $RoleDomainController
    # [ID = ClientAccessComponent___f4c48e196e374cf3af269b1cea0602c8, Wt = 1, isFatal = True] "Installing/Removing the WebReady Document Viewing service."
    7/5/2014 11:04:45 PM:Install-TranscodingServiceEx
    # [ID = ClientAccessComponent___f50fd59d231140eb9b2405bbed2b93d4, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if ($RoleIsDatacenter -eq $false)
                uninstall-FBAService
    # [ID = ClientAccessComponent___9fad9d51b3ec4ecdad567ab58e470be7, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if ($RoleIsDatacenter -eq $false)
                stop-setupservice -ServiceName MSExchangeFBA
    # [ID = ClientAccessComponent___1c7a7da2ab9d41bb8db75522ad28b9db, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              $tpath = "$env:SystemRoot\system32\inetsrv\microsoft.web.administration.dll";
              add-type -Path $tpath;
              $sm = new-object Microsoft.Web.Administration.ServerManager;
              if ($sm.Sites["Exchange Back End"] -eq $null)
                $ppath = "$env:SystemDrive\inetpub\wwwroot";
                $s = $sm.Sites.Add("Exchange Back End","http", "*:81:", $ppath);
                $s.ServerAutoStart = $true;
                $sb =$s.Bindings;
                $b = $sb.Add("*:444:","https");
                $sm.CommitChanges();
    # [ID = ClientAccessComponent___a5f211d837784aea931b9ba55c39996d, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              Get-ExchangeServer $RoleFqdnOrName | Add-AdPermission -User "S-1-5-20" -ExtendedRights "Exchange Web Services Token Serialization";
    # [ID = ClientAccessComponent__SetInstallPathInMrsAppConfig, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              Set-InstallPathInAppConfig -ConfigFileRelativePath "Bin" -ConfigFileName "MsExchangeMailboxReplication.exe.config"
    # [ID = ClientAccessComponent___765cc444ba07411aa81d58397b0401fd, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if (!(get-service MSExchangeMailboxReplication* | where {$_.name -eq "MSExchangeMailboxReplication"}))
                install-MailboxReplicationService
    # [ID = ClientAccessComponent___151b722e327b42a69411df32afdbbcbb, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:46 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationFirewallRule)
    # [ID = ClientAccessComponent___7d69bb94f08245589e49eb569c6d5f4f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:46 PM:
              if (!(get-service MSExchangeMigrationWorkflow* | where {$_.name -eq "MSExchangeMigrationWorkflow"}))
                install-MigrationWorkflowService
    # [ID = ClientAccessComponent___95f051d9dc5941c4b6014181b6e5ce93, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeABRPCFirewallRule)
    # [ID = ClientAccessComponent___959c2d6566984da6b8e0e3235c1c11c2, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangePOPBeByPortRule)
    # [ID = ClientAccessComponent___29864e7462374fdb84fc75eec931d8e4, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeIMAP4BeFirewallRule)
    # [ID = ClientAccessComponent___052e1b794d0641ada4d6d417061af2a8, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeOWAByPortRule)
    # [ID = ClientAccessComponent___975efd8911fd41cca8b17462535d710e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationByPort)
    # [ID = ClientAccessComponent___023036e43f004bda9f4f4e0b1e0d233f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              Install-ResourceHealthActiveFlags
    # [ID = ClientAccessComponent___3a51c2876e2c4643bc892d2665754228, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\PushNotifications\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___FCC16AC1FFED43518F8292DBE770C621, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\emsmdb\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___E9C71786D02E40CBB1403E2E1A4B0758, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\nspi\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___abcab6b91ac844848c58b4ee66fcbea6, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
                ."$RoleInstallPath\Scripts\Install-OutlookServiceVirtualDirectory.ps1";
    # [ID = ClientAccessComponent___9D94915F-B12D-4579-93EE-36B6DF42CF4A, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
              $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
              $MapiMailboxClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\emsmdb");
              $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiMailboxAppPool_CLRConfig.config");
              Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiMailboxAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
    /processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiMailboxClientAccessPath`" /applicationPool:MSExchangeMapiMailboxAppPool /path:`"/mapi/emsmdb`""
    -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
    # [ID = ClientAccessComponent___B551AAAC-0F36-428B-B1BB-3B9AFDC9EAEF, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:50 PM:
              $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
              $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
              $MapiAddressBookClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\nspi");
              $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiAddressBookAppPool_CLRConfig.config");
              Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiAddressBookAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
    /processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiAddressBookClientAccessPath`" /applicationPool:MSExchangeMapiAddressBookAppPool /path:`"/mapi/nspi`""
    -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
    # [ID = ClientAccessComponent___178FD1A31B5949A0B4A819E39311B1FD, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:52 PM:
                $ExchangeLabsRegKey = 'HKLM:\SOFTWARE\Microsoft\ExchangeLabs'
                $E4eCertificateDistinguishedNameRegValueName = 'E4eCertificateDistinguishedName'
                if ($RoleDatacenterE4eCertificateDistinguishedName -ne $null)
                    New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eCertificateDistinguishedNameRegValueName -Value $RoleDatacenterE4eCertificateDistinguishedName -Force
                    Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. value: $RoleDatacenterE4eCertificateDistinguishedName"
                else
                    Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. Value is null."
                $E4eServiceUrlRegValueName = 'E4eServiceUrl'
                if ($RoleDatacenterE4eServiceUrl -ne $null)
                    New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eServiceUrlRegValueName -Value $RoleDatacenterE4eServiceUrl -Force
                    Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. value: $RoleDatacenterE4eServiceUrl"
                else
                    Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. Value is null."
    # [ID = ClientAccessComponent___240c7e5d07f941cfbe69a692dc33a31a, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:52 PM:
              ."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
              CreateCustomHeadersNodeForBackend 'autodiscover'
              CreateCustomHeadersNodeForBackend 'ecp'
              CreateCustomHeadersNodeForBackend 'ews'  
              CreateCustomHeadersNodeForBackend 'oab'
              CreateCustomHeadersNodeForBackend 'owa'
              CreateCustomHeadersNodeForBackend 'powershell'
              CreateCustomHeadersNodeForBackend 'pushnotifications'
              CreateCustomHeadersNodeForBackend 'rpcproxy'
              CreateCustomHeadersNodeForBackend 'sync'
              CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
              CreateCustomHeadersNodeForBackend 'mapi\nspi'
              CreateCustomHeadersNodeForBackend 'outlookservice'
    # [ID = ClientAccessComponent___75f8c93d15314369983d33ec0742e189, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:53 PM:
              New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    # Tasks for 'POP/IMAP Backend Configuration' component
    # [ID = PopImapBeComponent___d91be94d83bb4dc28e1fbdf7d94ca60e, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:05 PM:
              if (!(get-service MSExchangeIMAP4BE* | where {$_.name -eq "MSExchangeIMAP4BE"}))
                install-Imap4BeService
    # [ID = PopImapBeComponent___e2debc6ecabf457eb6f278096ad5102c, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              if (!(get-service MSExchangePOP3BE* | where {$_.name -eq "MSExchangePOP3BE"}))
                install-Pop3BeService
    # [ID = PopImapBeComponent___7ee4dbb3fe884d26bb3e060ac68061ee, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Pop3Service.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
              set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
    # [ID = PopImapBeComponent___9b86c2af9f364990aa196cb6e69905b6, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Pop3.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
    # [ID = PopImapBeComponent___01c604c08fd6402e9de6b3c45e3431c8, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Imap4Service.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
              set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
    # [ID = PopImapBeComponent___2528980001a444fcb7097d123e879728, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Imap4.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
    # [ID = PopImapBeComponent___bbfdc492aaf748298977cb9b98e00029, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:install-Imap4Container -Name:"IMAP4" -DomainController $RoleDomainController
    # [ID = PopImapBeComponent___091c98cfe0f145189c0966717496795e, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:install-Pop3Container -Name:"POP3" -DomainController $RoleDomainController
    # [ID = PopImapBeComponent___42cb9f4ac2924c27b6ebf60b92a03628, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:new-ImapSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
    # [ID = PopImapBeComponent___181f5361a5df4e7ca009f21f26f8c0d5, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:new-PopSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
    # Tasks for 'ClientAccessExchangeCertificate' component
    # [ID = ClientAccessExchangeCertificate___fb5e9028e669404d94dba90aace8c2f9, Wt = 1, isFatal = True] "Installing Client Access server certificates."
    7/5/2014 11:05:07 PM:
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController

  • Autodiscover Exchange Server 2007 and 2013 Coexistence

    Hello
    We are having some issues where some users are not being notified when their mailbox is being migrated to E2013.
    Before 2013, we never had a load balanced solution for CAS in Exchange Server 2007 or a single name space.
    Below is our current config
    AutoDiscoverServiceCN          : Server2K7CASpd
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2k7CASdr
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2013CASPD01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASPD02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    I believe that we should change the AutoDiscoverServiceInternalUri on the two 2007 CAS to ALSO be the same as our 2013 CAS.
    We know that when Outlook is opened, Autodiscover will respond with any of the 6 available CAS, and we think that those Outlook clients that are misconfigured, are those that are not getting notified when their Mailbox is moved to E2013.
    Thanks

    We are also getting inconsistent results using the Test-OutlookWebServices PS
    Test 1
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 76 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 558 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.domain.local/EWS/Exchange.asmx. The elapsed time
              was 46 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1013
    Type    : Error
    Message : When contacting https://mail.domain.local/Rpc received the error The remote server returned an error: (404) Not
              Found.
    Id      : 1017
    Type    : Error
    Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.domain.local/Rpc. The elapsed time was 93
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.
    Id      : 1021
    Type    : Information
    Message : The following web services generated errors.
                  Contacting server in EXPR
              Please use the prior output to diagnose and correct the errors.
    Test 2
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.Domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 46 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.Domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 15 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.Domain.local/EWS/Exchange.asmx. The elapsed time
              was 78 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1017
    Type    : Success
    Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://legacy.Domain.local/Rpc. The elapsed time was 187
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.

  • Outlook 2013 client, not in domain, can't connect to the Exchange 2010 server

    Good Aftermoon,
    Having issues it seems getting to the right forum but here is what I have. Currently we are running an Exchange 2010 server. OWA is configured and I am not having any issues with people connecting through it. The issue I am having is that any user that tries
    to connect through Outlook 2013 gets an error message about the proxy server and then a certificate error. I have run the tests through the toolbox and get the following results. 
    Attempting to test potential Autodiscover URL https://autodiscover.westmoreland-county.org:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.
    Additional Details
    Elapsed Time: 694 ms.
    Test Steps
    Attempting to resolve the host name autodiscover.westmoreland-county.org in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 69.89.25.150
    Elapsed Time: 284 ms.
    Testing TCP port 443 on host autodiscover.westmoreland-county.org to ensure it's listening and open.
    The port was opened successfully.
    Additional Details
    Elapsed Time: 164 ms.
    Testing the SSL certificate to make sure it's valid.
    The SSL certificate failed one or more certificate validation checks.
    Additional Details
    Elapsed Time: 245 ms.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.westmoreland-county.org on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=*.bluehost.com, OU=PositiveSSL Wildcard, OU=Domain Control Validated, Issuer: CN=PositiveSSL CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
    Elapsed Time: 201 ms.
    Validating the certificate name.
    Certificate name validation failed.
     <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_ctl02_ctl01_tmmArrow">Tell
    me more about this issue and how to resolve it</label>
    Additional Details
    Host name autodiscover.westmoreland-county.org doesn't match any name found on the server certificate CN=*.bluehost.com, OU=PositiveSSL Wildcard, OU=Domain Control Validated.
    Elapsed Time: 1 ms.
    Attempting to contact the Autodiscover service using the HTTP redirect method.
    The attempt to contact Autodiscover using the HTTP Redirect method failed.
    Additional Details
    Elapsed Time: 234 ms.
    Test Steps
    Attempting to resolve the host name autodiscover.westmoreland-county.org in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 69.89.25.150
    Elapsed Time: 14 ms.
    Testing TCP port 80 on host autodiscover.westmoreland-county.org to ensure it's listening and open.
    The port was opened successfully.
    Additional Details
    Elapsed Time: 83 ms.
    The Microsoft Connectivity Analyzer is checking the host autodiscover.westmoreland-county.org for an HTTP redirect to the Autodiscover service.
    The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
    Additional Details
    The URL specified in the location HTTP header was not HTTPS. URL: http://autodiscover.bluehost.com/Autodiscover/Autodiscover.xml
    HTTP Response Headers:
    Keep-Alive: timeout=10, max=500
    Connection: Keep-Alive
    Content-Length: 356
    Content-Type: text/html; charset=iso-8859-1
    Date: Wed, 03 Dec 2014 18:10:08 GMT
    Location: http://autodiscover.bluehost.com/Autodiscover/Autodiscover.xml
    Server: Apache
    Elapsed Time: 135 ms.
    Our setup currently our domain is being hosted and the web master has control of domain settings. 
    I am fairly new to the Excchange Server world so any suggestions that you may have as to how I can resolve this would be great. 
    Bill

    Hi Bill
    Thank you for your pos.
    You can use the following command to check whether you have purchased the certificate of audiscovery.westmoreload-country.org in your organization:
    Get-ExchangeCertificate –server CASServerName | fl
    For example: you want to return all certificates stored on the Client Access server named ClientAccess01, you will type the follow command in EMS.
    Get-ExchangeCertificate -Server ClientAccess01 | fl
    If you didn’t purchased the certificate of audiscovery.westmoreload-country.org, you could contact your certificate supplier.
    You could refer to the following link:
    https://support.microsoft.com/kb/940726?wa=wsignin1.0
    If there are any questions regarding this issue, please be free to let me know.
    Best regard,
    Jim

Maybe you are looking for