網頁

2012年9月29日 星期六

Configuring Exchange 2010 Client Access Server (part 1)

When we install Exchange 2010 on a computer, it will automatically install a default self-signed certificate for communicating between Exchange Servers. Due to this certificate never is created or signed by a trusted Root CA, it cannot use in any clients in the organization.
clip_image002The Exchange self-signed certificate will have Subject Alternative Name (SANs) that correspond to the name of the Exchange server as the server name and the server’s fully qualified domain name.
clip_image003If we want to use the self-signed certificate, administrator need to do extra steps that let clients trust these certificate. In the moment, we will do a easy solution that get a certificate from an internal CA ---- Microsoft Activity Directory Certificate Services.

How to request and enable certificate on CAS?

Run the New Exchange Certificate WizardIn EMC, click on the Server Configuration node next to click on the New Exchange Certificate… in the Actions pane. The New Exchange Certificate wizard will be launched.
clip_image005On the Introduction page , provide a friendly name as “Adatum Exchange Server” for the certificate next to click Next > button
clip_image008On the Domain Scope page, mark Enable wildcard certificate check box and then enter Root domain for wildcard as "*.adatum.com” or “adatum.com” due to we want to apply this certificate to all subdomains using wildcards. That is this option allows you to add subdomains without having to update an existing certificate in the future. (# 1)
clip_image009On the Organization and Location page, provide the related information next to click Browse… button for selecting Certificate Request File Path.
clip_image010Select a path, provide file name with extension “.req” and then save it
clip_image011Click Next > button after the request file name is specifically created and selected.
clip_image012On the Certificate Configuration page, click New button to continue the process if Configuration Summary is true.
clip_image013Click Finish button to close this wizard and continuously follow the step 1 to get the certificate issued from a CA.
clip_image014In the moment, a pending request certificate will be created. (# 2)
clip_image016
Submit the resulting certificate request file to Root CAIn I.E. or other Browsers, go to the URL of the internal Certificate Server as http://pki.dw.com/certsrv/ and login in by authenticated user next to click Request a certificate in this Web site.
clip_image023In the Request a Certificate page, click advanced certificate request
clip_image025Click Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file because we have already generated the request on the Exchange Server 2010.
clip_image027In the moment, please open the request file we generated earlier
clip_image021Select all content next to click Copy in menu
clip_image029Paste it into the Base-64 encoded certificate request field
clip_image031The result is as follows the diagram.
clip_image033Set the certificate template to Web Server
clip_image035Click Submit > button to generate the request
clip_image037Select DER encoded next to click Download certificate to save this file to one path
clip_image039
Completing a pending certificate request
In EMC, click on the Server Configuration node, navigate to Server Management to choose one server that we want to import a certificate, select the new certificate next to click on the Complete Pending Request… in the Actions pane. clip_image044Click Browse… button
clip_image045Select the certificate file that is downloaded earlier.
clip_image046Click Complete button to import a certificate to the Exchange server
clip_image047Click Finish button to close this wizard
clip_image048So does that will complete a pending certificate request (# 3) and is ready to be assigned to Exchange service.
clip_image050
Reference
(# 1) Please take care the following scenarios:
  • Wildcard certificates can’t be used in conjunction with OCS 2007 as secure communications for UM/OWA integration
  • Wildcard certificates are not supported for older mobile devices such as Windows Mobile 5.0
(# 2) When we select and open this request certificate,
clip_image018the certificate information tell us this CA Root certificate is not trusted and issued by point to itself.
clip_image019(# 3) When we select and open this request certificate again,
clip_image052In General tab, the information issued by has already been changed to Root CA
clip_image053In Certification Path tab, its chain in top level also link to Root CA.
clip_image054

沒有留言:

張貼留言

Since 2010 Design by Davidwa
©Copyright Davidwa Inc. All rights reserved.