This scenario is explained in detail at /en-us/library/bb310762.aspx. Y es, you would typically need a certificate for the autodiscovery unless you have a wildcard normally.Can/should we add an “A” pointer in the internal DNS for autodiscovery, and will that fix that problem? (We can manually put in the settings for Outlook and it works fine, just not autodiscovery internally in the domain.) What about internally? I have a few clients who can’t open Outlook and have it automatically discover its settings (in a domain).Or does the device know to ignore an SSL error and proceed? If you create an “A” record for the autodiscovery, do you also have to have an SSL for it? That’s assuming we don’t have a wildcard SSL installed (which most of our clients do not).In John’s examples, he shows both and I’m assuming he means just and no Correct?.I have a few questions regarding John Savill’s FAQ, “ How can I quickly verify that my Exchange autodiscovery is working?” (June 23, 2011, InstantDoc ID 139558): You can find more information about the infrastructure required to support secure messaging in Outlook 2010 in the Microsoft article “Plan for e-mail messaging cryptography in Outlook 2010” (/en-us/library/cc179061.aspx). The user’s email client then has to be configured to use the certificate for secure messaging. This is usually done through an internal PKI. Users must either request or be assigned a certificate for use with secure messaging. If I understand correctly, you want to know when a client receives a certificate to work with secure messaging in a program such as Microsoft Outlook. I’m glad that you found the article useful. When does a client get a private key, which is used to encrypt the message digest, decrypt messages, and sign messages? I just read Russell Smith’s excellent article, “Deciphering PKI” (May 2011, InstantDoc ID 129847).
0 kommentar(er)
