REF: E14 Outlook Provider

-

 

Exchange 2010 Set-OutlookProvider
http://technet.microsoft.com/en-us/library/bb123683.aspx

The Set-OutlookProvider cmdlet creates the global settings for the Autodiscover service.
It sets the AutoDiscoverConfig object under theGlobal Settings object in Active Directory and sets the attributes specified in the parameters listed in the Parameters section.

The Autodiscover Service and Outlook Providers - how does this stuff work?

http://blogs.technet.com/b/exchange/archive/2008/09/26/3406344.aspx

By default three Outlook Providers are used to configure settings individually for Exchange RPC protocol or internal clients (EXCH), Outlook Anywhere (EXPR) and WEB.

  • The EXCH setting references the Exchange RPC protocol that is used internally. This setting includes port settings and the internal URLs for the Exchange services that you have enabled.
  • The EXPR setting references the Exchange HTTP protocol that is used by Outlook Anywhere. This setting includes the external URLs for the Exchange services that you have enabled, which are used by clients that access Exchange from the Internet.
  • The WEB setting contains the best URL for Outlook Web Access for the user to use. This setting is not in use.

a. If the request is made by an Outlook Exchange RPC client, the EXCH provider will return the InternalUrl configured on the best CAS server for the following services: Availability Service, OAB virtual directory and Unified Messaging virtual directory.

b. If the request is made by an Outlook Anywhere Exchange HTTP client, the EXPR provider will return the External URL configured on the best CAS server for the same services: Availability Service, OAB virtual directory and Unified Messaging virtual directory and ExternalHostName for Outlook Anywhere.

Note: If the ExternalUrl is not set, the CAS will fail-back returning the InternalUrl.

When, if and how do you modify Outlook Providers?

http://blogs.technet.com/b/exchange/archive/2008/09/29/3406352.aspx

Scenario 1: Multiple AD sites where both CAS servers are Internet-Facing and Outlook Anywhere is enabled. Each Client Access Server has its own certificate installed. The User1 mailbox is located on a Mailbox server on AD site 1, and User2 mailbox on a Mailbox server on AD site 2. Both Outlook clients are on the Internet, thus they will connect through Outlook Anywhere.

Note: Autodiscover is configured properly on the Internet as Autodiscover.fourthcoffee.com.

When the User1 connect to Autodiscover.fourthcoffee.com server, the Autodiscover service will identify the request comes from an Outlook client and then will return both InternalURLs and ExternalURLs.

In this scenario we will explain the importance of not changing Outlook providers. As the parametersServer and CertPrincName are $null. The Service Discovery will return to the client the best CAS for Outlook Anywhere, in this case mail1.fourthcoffee.com.

image

Remember that the Outlook provider is a global setting in Active Directory. What would happen if you have modified the parameter Server to mail1.fourthcoffee.com?

Set-OutlookProvider EXPR -Server mail1.fourthcoffee.com

This setting will force all Outlook Anywhere clients, User1 and User2 to connect to the same CAS servermail1.fourthcoffee.com no matter where the user mailbox is located, preventing the Service Discovery to provide the best CAS.

Another issue could result if you decided to change Outlook Anywhere ExternalHostName toOutlookanywhere.fourthcoffee.com. The setting on the EXPR Outlook provider set tomail1.fourthcoffee.com will prevent Outlook Anywhere to connect since the mail1.fourthcoffee.com is not longer available.

 

Clean EXPR

[PS] C:\Windows\system32>Set-OutlookProvider -Identity expr -CertPrincipalName $null -Server $null

[PS] C:\Windows\system32>Get-OutlookProvider -Identity expr | fl


RunspaceId           : c392df9f-35db-4b37-9e44-181a96df4c52
CertPrincipalName    :
Server               :
TTL                  : 1
OutlookProviderFlags : None
AdminDisplayName     :
ExchangeVersion      : 0.1 (8.0.535.0)
Name                 : EXPR
DistinguishedName    : CN=EXPR,CN=Outlook,CN=AutoDiscover,CN=Client Access,CN=MSFT,CN=Microsoft Exchange,CN=Services,CN
                       =Configuration,DC=corp,DC=com
Identity             : EXPR
Guid                 : ecdbfb18-69a4-4275-8bec-c14e1b73045d
ObjectCategory       : corp.com/Configuration/Schema/ms-Exch-Auto-Discover-Config
ObjectClass          : {top, msExchAutoDiscoverConfig}
WhenChanged          : 5/4/2012 10:05:49 AM
WhenCreated          : 3/11/2008 10:46:40 AM
WhenChangedUTC       : 5/4/2012 2:05:49 AM
WhenCreatedUTC       : 3/11/2008 2:46:40 AM
OrganizationId       :
OriginatingServer    : RDC02.corp.com
IsValid              : True

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more