我有一台Exchange 2010服务器，当我有一个非通配符证书时，其自动发现服务以前工作正常（正确configurationRPC-over-HTTP）。 在使用通配符证书replace证书后，自动发现服务会将新客户端configuration为IMAP。 这绝对不是理想的行为。 我已经应用Set-OutlookProvider命令将受信任的名称更改为msstd:*.mydomain.com 。 TestExchangeConnectivity.com表示，一切都很好，只有一个关于较旧的Windows机器上的受信任的根更新的警告。 然而自动发现显然不起作用。 我能做什么/为什么自动发现configurationIMAP而不是RPC-over-HTTP？
编辑：顺便说一句，当我手动configuration帐户，并指定所有连接速度的HTTP代理设置，它工作正常。 唯一简单的事情是在检查名称部分，它不需要DOMAIN \用户格式，而只是完整的实际名称。
编辑2：自动发现响应如下：
<?xml version="1.0"?> <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>J Shin</DisplayName> <LegacyDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=J Shin</LegacyDN> <DeploymentId>e8362375-54d7-471c-acd9-7e5116e4810e</DeploymentId> </User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>myserver.corp.mydomain.com</Server> <ServerDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=myserver</ServerDN> <ServerVersion>738280F7</ServerVersion> <MdbDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=myserver/cn=Microsoft Private MDB</MdbDN> <ASUrl>https://myserver.corp.mydomain.com/EWS/Exchange.asmx</ASUrl> <OOFUrl>https://myserver.corp.mydomain.com/EWS/Exchange.asmx</OOFUrl> <OABUrl>https://mail.mydomain.com/OAB/84798c85-90d3-45fc-a67e-72d928e57ae6/</OABUrl> <UMUrl>https://myserver.corp.mydomain.com/EWS/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <PublicFolderServer>myserver.corp.mydomain.com</PublicFolderServer> <AD>EMDDC21.corp.mydomain.com</AD> <EwsUrl>https://myserver.corp.mydomain.com/EWS/Exchange.asmx</EwsUrl> <EcpUrl>https://myserver.corp.mydomain.com/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um> <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret> <EcpUrl-sms>?p=sms/textmessaging.slab&exsvurl=1</EcpUrl-sms> </Protocol> <Protocol> <Type>EXPR</Type> <Server>mail.mydomain.com</Server> <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl> <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl> <OABUrl>https://mail.mydomain.com/OAB/84798c85-90d3-45fc-a67e-72d928e57ae6/</OABUrl> <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <SSL>On</SSL> <AuthPackage>Ntlm</AuthPackage> <CertPrincipalName>msstd:*.mydomain.com</CertPrincipalName> <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl> <EcpUrl>https://mail.mydomain.com/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um> <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret> <EcpUrl-sms>?p=sms/textmessaging.slab&exsvurl=1</EcpUrl-sms> </Protocol> <Protocol> <Type>WEB</Type> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <Internal> <OWAUrl AuthenticationMethod="Basic, Fba">https://myserver.corp.mydomain.com/owa/</OWAUrl> <Protocol> <Type>EXCH</Type> <ASUrl>https://myserver.corp.mydomain.com/EWS/Exchange.asmx</ASUrl> </Protocol> </Internal> <External> <OWAUrl AuthenticationMethod="Fba">https://mail.mydomain.com/owa/</OWAUrl> <Protocol> <Type>EXPR</Type> <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl> </Protocol> </External> </Protocol> </Account> </Response> </Autodiscover>
我希望我能早点回答这个问题，因为我已经忘记了一些细节，主要是通过反复试验来解决这个问题。 以下是我所做的：
mail.mycompany.com ） mail.mycompany.com创build了一个内部DNSlogging，指向一个只能从内部访问的接口（而不是从WAN获取NATstream量的接口） 一个问题是，当从外部进行身份validation（即不通过SSO）时，我不得不指示用户以MYCOMPANY\username格式提供他们的用户MYCOMPANY\username 。