- Microsoft Communicator Mac Digital Certificate File Type
- Microsoft Communicator Mac Digital Certificate File Software
- Certificate Authority
- Microsoft Communicator Mac Digital Certificate File Download
Apr 27, 2016 You can configure the CAPF to request certificates from customer-specified certificate authorities on behalf of Cisco IP Communicator, or you can configure it to generate certificates locally. The CAPF is a process by which a supported device can request an LSC by using Cisco Unified Communications Manager Administration. Jan 27, 2011 Can't sign in to Lync server using Mac Communicator 11. Message is: Either date and time settings are incorrect, or the digital certificate file is not valid or installed on your computer. If date and time are corect, see your network administrator to verify that your digital certificate file is valid and installed. May 15, 2012 Now i enetered LION os. And i installed office communicator and installed all updates and currently i run 13.1.3 in my LION os 10.7.4. Now when i enter my credentials, i get a warning message. Saying:-'either dat and time settings are incorrect or the digital certificate is not valid or installed on your computer. Oct 21, 2015 I installed the patch to Outlook to get it working, but the day after I began to have major issues logging in to Communicator due to the (familiar to some) lovely 'Either date and time settings are incorrect, or the digital certificate file is not valid or installed on your computer'.-->
Encryption and digital certificates are important considerations in any organization. By default, Exchange Server is configured to use Transport Layer Security (TLS) to encrypt communication between internal Exchange servers, and between Exchange services on the local server. But, Exchange administrators need to consider their encryption requirements for communication with internal and external clients (computers and mobile devices), and external messaging servers.
Exchange Server 2019 includes important changes to improve the security of client and server connections. The default configuration for encryption will enable TLS 1.2 only and disable support for older algorithms (namely, DES, 3DES, RC2, RC4 and MD5). It will also configure elliptic curve key exchange algorithms with priority over non-elliptic curve algorithms. In Exchange Server 2016 and later, all cryptography settings are inherited from the configuration specified in the operating system. For additional information, see Exchange Server TLS Guidance.
This topic describes the different types of certificates that are available, the default configuration for certificates in Exchange, and recommendations for additional certificates that you'll need to use with Exchange.
For the procedures that are required for certificates in Exchange Server, see Certificate procedures in Exchange Server.
Digital certificates overview
Digital certificates are electronic files that work like an online password to verify the identity of a user or a computer. They're used to create the encrypted channel that's used for client communications. A certificate is a digital statement that's issued by a certification authority (CA) that vouches for the identity of the certificate holder and enables the parties to communicate in a secure manner by using encryption.
Digital certificates provide the following services:
Encryption: They help protect the data that's exchanged from theft or tampering.
Authentication: They verify that their holders (people, web sites, and even network devices such as routers) are truly who or what they claim to be. Typically, the authentication is one-way, where the source verifies the identity of the target, but mutual TLS authentication is also possible.
Certificates can be issued for several uses. For example: web user authentication, web server authentication, Secure/Multipurpose Internet Mail Extensions (S/MIME), Internet Protocol security (IPsec), and code signing.
A certificate contains a public key and attaches that public key to the identity of a person, computer, or service that holds the corresponding private key. The public and private keys are used by the client and the server to encrypt data before it's transmitted. For Windows users, computers, and services, trust in the CA is established when the root certificate is defined in the trusted root certificate store, and the certificate contains a valid certification path. A certificate is considered valid if it hasn't been revoked (it isn't in the CA's certificate revocation list or CRL), or hasn't expired.
The three primary types of digital certificates are described in the following table.
|Self-signed certificate||The certificate is signed by the application that created it.||Cost (free).||The certificate isn't automatically trusted by client computers and mobile devices. The certificate needs to be manually added to the trusted root certificate store on all client computers and devices, but not all mobile devices allow changes to the trusted root certificate store. |
Not all services work with self-signed certificates.
Difficult to establish an infrastructure for certificate lifecycle management. For example, self-signed certificates can't be revoked.
|Certificate issued by an internal CA||The certificate is issued by a public key infrastructure (PKI) in your organization. An example is Active Directory Certificate Services (AD CS). For more information, see Active Directory Certificate Services Overview.||Allows organizations to issue their own certificates. |
Less expensive than certificates from a commercial CA.
|Increased complexity to deploy and maintain the PKI. |
The certificate isn't automatically trusted by client computers and mobile devices. The certificate needs to be manually added to the trusted root certificate store on all client computers and devices, but not all mobile devices allow changes to the trusted root certificate store.
|Certificate issued by a commercial CA||The certificate is purchased from a trusted commercial CA.||Simplified certificate deployment, because all clients, devices, and servers automatically trust the certificates.||Cost. You need to plan ahead to minimize the number of certificates that are required.|
To prove that a certificate holder is who they claim to be, the certificate must accurately identify the certificate holder to other clients, devices, or servers. The three basic methods to do this are described in the following table.
|Certificate subject match||The certificate's Subject field contains the common name (CN) of the host. For example, the certificate that's issued to www.contoso.com can be used for the web site https://www.contoso.com.||Compatible with all clients, devices, and services. |
Compartmentalization. Revoking the certificate for a host doesn't affect other hosts.
|Number of certificates required. You can only use the certificate for the specified host. For example, you can't use the www.contoso.com certificate for ftp.contoso.com, even when the services are installed on the same server. |
Complexity. On a web server, each certificate requires its own IP address binding.
|Certificate subject alternative name (SAN) match||In addition to the Subject field, the certificate's Subject Alternative Name field contains a list of multiple host names. For example: |
|Convenience. You can use the same certificate for multiple hosts in multiple, separate domains. |
Most clients, devices, and services support SAN certificates.
Auditing and security. You know exactly which hosts are capable of using the SAN certificate.
|More planning required. You need to provide the list of hosts when you create the certificate. |
Lack of compartmentalization. You can't selectively revoke certificates for some of the specified hosts without affecting all of the hosts in the certificate.
|Wildcard certificate match||The certificate's Subject field contains the common name as the wildcard character (*) plus a single domain or subdomain. For example, *.contoso.com or *.eu.contoso.com. The *.contoso.com wildcard certificate can be used for: |
|Flexibility. You don't need to provide a list of hosts when you request the certificate, and you can use the certificate on any number of hosts that you may need in the future.||You can't use wildcard certificates with other top-level domains (TLDs). For example, you can't use the *.contoso.com wildcard certificate for *.contoso.net hosts. |
You can only use wildcard certificates for host names at the level of the wildcard. For example, you can't use the *.contoso.com certificate for www.eu.contoso.com. Or, you can't use the *.eu.contoso.com certificate for www.uk.eu.contoso.com.
Older clients, devices, applications, or services might not support wildcard certificates.
Wildcards aren't available with Extended Validation (EV) certificates.
Careful auditing and control is required. If the wildcard certificate is compromised, it affects every host in the specified domain.
Certificates in Exchange
When you install Exchange 2016 or Exchange 2019 on a server, two self-signed certificates are created and installed by Exchange. A third self-signed certificate is created and installed by Microsoft Windows for the Web Management service in Internet Information Services (IIS). These three certificates are visible in the Exchange admin center (EAC) and the Exchange Management Shell, and are described in the following table:
|Microsoft Exchange||This Exchange self-signed certificate has the following capabilities: |
• The certificate is automatically trusted by all other Exchange servers in the organization. This includes any Edge Transport servers subscribed to the Exchange organization.
• The certificate is automatically enabled for all Exchange services except Unified Messaging, and is used to encrypt internal communication between Exchange servers, Exchange services on the same computer, and client connections that are proxied from the Client Access services to the backend services on Mailbox servers. (Note: UM is not available on Exchange 2019.)
• The certificate is automatically enabled for inbound connections from external SMTP messaging servers, and outbound connections to external SMTP messaging servers. This default configuration allows Exchange to provide opportunistic TLS on all inbound and outbound SMTP connections. Exchange attempts to encrypt the SMTP session with an external messaging server, but if the external server doesn't support TLS encryption, the session is unencrypted.
• The certificate doesn't provide encrypted communication with internal or external clients. Clients and servers don't trust the Exchange self-signed certificate, because the certificate isn't defined in their trusted root certification stores.
|Microsoft Exchange Server Auth Certificate||This Exchange self-signed certificate is used for server-to-server authentication and integration by using OAuth. For more information, see Plan Exchange Server integration with SharePoint and Skype for Business.|
|WMSVC||This Windows self-signed certificate is used by the Web Management service in IIS to enable remote management of the web server and its associated web sites and applications. |
If you remove this certificate, the Web Management service will fail to start if no valid certificate is selected. Having the service in this state can prevent you from installing Exchange updates, or uninstalling Exchange from the server. For instructions on how to correct this issue, see Event ID 1007 - IIS Web Management Service Authentication
The properties of these self-signed certificates are described in the Properties of the default self-signed certificates section.
These are the key issues that you need to consider when it comes to certificates in Exchange:
You don't need to replace the Microsoft Exchange self-signed certificate to encrypt network traffic between Exchange servers and services in your organization.
You need additional certificates to encrypt connections to Exchange servers by internal and external clients.
You need additional certificates to force the encryption of SMTP connections between Exchange servers and external messaging servers.
The following elements of planning and deployment for Exchange Server are important drivers for your certificate requirements:
Load balancing: Do you plan to terminate the encrypted channel at load balancer or reverse proxy server, use Layer 4 or Layer 7 load balancers, and use session affinity or no session affinity? For more information, see Load Balancing in Exchange 2016.
Namespace planning: What versions of Exchange are present, are you using the bound or unbound namespace model, and are you using split-brain DNS (configuring different IP addresses for the same host based on internal vs. external access)? For more information, see Namespace Planning in Exchange 2016.
Client connectivity: What services will your clients use (web-based services, POP, IMAP, etc.) and what versions of Exchange are involved? For more information, see the following topics:
Certificate requirements for Exchange services
The Exchange services that certificates can be assigned to are described in the following table.
|IIS (HTTP)||By default, the following services are offered under the default website in the Client Access (frontend) services on a Mailbox server, and are used by clients to connect to Exchange: |
• Exchange ActiveSync
• Exchange admin center
• Exchange Web Services
• Offline address book (OAB) distribution
• Outlook Anywhere (RPC over HTTP)
• Outlook MAPI over HTTP
• Outlook on the web
• Remote PowerShell*
Because you can only associate a single certificate with a website, all the DNS names that clients use to connect to these services need to be included in the certificate. You can accomplish this by using a SAN certificate or a wildcard certificate.
|POP or IMAP||The certificates that are used for POP or IMAP can be different from the certificate that's used for IIS. However, to simplify administration, we recommend that you also include the host names that are used for POP or IMAP in your IIS certificate, and use the same certificate for all of these services.|
|SMTP||SMTP connections from clients or messaging servers are accepted by one or more Receive connectors that are configured in the Front End Transport service on the Exchange server. For more information, see Receive connectors. |
To require TLS encryption for SMTP connections, you can use a separate certificate for each Receive connector. The certificate must include the DNS name that's used by the SMTP clients or servers to connect to the Receive connector. To simplify certificate management, consider including all DNS names for which you have to support TLS traffic in a single certificate.
To require mutual TLS authentication, where the SMTP connections between the source and destination servers are both encrypted and authenticated, see Domain Security.
|Unified Messaging (UM)||For more information, see Deploying Certificates for UM. |
Note: UM is not available in Exchange 2019.
|Hybrid deployment with Microsoft Office 365||For more information, see Certificate Requirements for Hybrid Deployments.|
|Secure/Multipurpose Internet Mail Extensions (S/MIME)||For more information, see S/MIME for message signing and encryption.|
* Kerberos authentication and Kerberos encryption are used for remote PowerShell access, from both the Exchange admin center and the Exchange Management Shell. Therefore, you don't need to configure your certificates for use with remote PowerShell, as long as you connect directly to an Exchange server (not to a load balanced namespace). To use remote PowerShell to connect to an Exchange server from a computer that isn't a member of the domain, or to connect from the Internet, you need to configure your certificates for use with remote PowerShell.
Best practices for Exchange certificates
Although the configuration of your organization's digital certificates will vary based on its specific needs, information about best practices has been included to help you choose the digital certificate configuration that's right for you.
Use as few certificates as possible: Very likely, this means using SAN certificates or wildcard certificates. In terms of interoperability with Exchange, both are functionally equivalent. The decision on whether to use a SAN certificate vs a wildcard certificate is more about the key capabilities or limitations (real or perceived) for each type of certificate as described in the Digital certificates overview.
For example, if all of your common names will be in the same level of contoso.com, it doesn't matter if you use a SAN certificate or a wildcard certificate. But, if need to use the certificate for autodiscover.contoso.com, autodiscover.fabrikam.com, and autodiscover.northamerica.contoso.com, you need to use a SAN certificate.
Use certificates from a commercial CA for client and external server connections: Although you can configure most clients to trust any certificate or certificate issuer, it's much easier to use a certificate from a commercial CA for client connections to your Exchange servers. No configuration is required on the client to trust a certificate that's issued by a commercial CA. Many commercial CAs offer certificates that are configured specifically for Exchange. You can use the EAC or the Exchange Management Shell to generate certificate requests that work with most commercial CAs.
Choose the right commercial CA: Compare certificate prices and features between CAs. For example:
Verify that the CA is trusted by the clients (operating systems, browsers, and mobile devices) that connect to your Exchange servers.
Verify that the CA supports the kind of certificate that you need. For example, not all CAs support SAN certificates, the CA might limit the number of common names that you can use in a SAN certificate, or the CA may charge extra based on the number of common names in a SAN certificate.
See if the CA offers a grace period during which you can add additional common names to SAN certificates after they're issued without being charged.
Verify that the certificate's license allows you to use the certificate on the required number of servers. Some CAs only allow you to use the certificate on one server.
Use the Exchange certificate wizard: A common error when you create certificates is to forget one or more common names that are required for the services that you want to use. The certificate wizard in the Exchange admin center helps you include the correct list of common names in the certificate request. The wizard lets you specify the services that will use the certificate, and includes the common names that you need to have in the certificate for those services. Run the certificate wizard when you've deployed your initial set of Exchange 2016 or Exchange 2019 servers and determined which host names to use for the different services for your deployment.
Use as few host names as possible: Minimizing the number of host names in SAN certificates reduces the complexity that's involved in certificate management. Don't feel obligated to include the host names of individual Exchange servers in SAN certificates if the intended use for the certificate doesn't require it. Typically, you only need to include the DNS names that are presented to the internal clients, external clients, or external servers that use the certificate to connect to Exchange.
For a simple Exchange Server organization named Contoso, this is a hypothetical example of the minimum host names that would be required:
mail.contoso.com: This host name covers most connections to Exchange, including Outlook, Outlook on the web, OAB distribution, Exchange Web Services, Exchange admin center, and Exchange ActiveSync.
autodiscover.contoso.com: This specific host name is required by clients that support Autodiscover, including Outlook, Exchange ActiveSync, and Exchange Web Services clients. For more information, see Autodiscover service.
Properties of the default self-signed certificates
Some of the more interesting properties of the default self-signed certificates that are visible in the Exchange admin center and/or the Exchange Management Shell on an Exchange server are described in the following table.
|Microsoft Exchange||Microsoft Exchange Server Auth Certificate||WMSVC|
|Subject Alternative Names (CertificateDomains)||• <ServerName> (for example, Mailbox01) |
• <ServerFQDN> (for example, Mailbox01.contoso.com)
|Has private key (HasPrivateKey)||Yes (True)||Yes (True)||Yes (True)|
|EnhancedKeyUsageList*||Server Authentication (188.8.131.52.184.108.40.206.1)||Server Authentication (220.127.116.11.18.104.22.168.1)||Server Authentication (22.214.171.124.126.96.36.199.1)|
|NotBefore||The date/time that Exchange was installed.||The date/time that Exchange was installed.||The date/time that the IIS Web Manager service was installed.|
|Expires on (NotAfter)||5 years after ||5 years after ||10 years after |
|Public key size (PublicKeySize)||2048||2048||2048|
|Services||IMAP, POP, IIS, SMTP||SMTP||None|
*These properties aren't visible in the standard view in the Exchange Management Shell. To see them, you need to specify the property name (exact name or wildcard match) with the Format-Table or Format-List cmdlets. For example:
Get-ExchangeCertificate -Thumbprint <Thumbprint> Format-List *
Get-ExchangeCertificate -Thumbprint <Thumbprint> Format-Table -Auto FriendlyName,*PrivateKey*
For more information, see Get-ExchangeCertificate.
Further details about the default self-signed certificates that are visible in Windows Certificate Manger are described in the following table.
|Microsoft Exchange||Microsoft Exchange Server Auth Certificate||WMSVC|
|Signature hash algorithm||sha1||sha1||sha1|
|Key usage||Digital Signature, Key Encipherment (a0)||Digital Signature, Key Encipherment (a0)||Digital Signature, Key Encipherment (a0), Data Encipherment (b0 00 00 00)|
|Basic constraints||• |
Typically, you don't use Windows Certificate Manger to manage Exchange certificates (use the Exchange admin center or the Exchange Management Shell). Note that the WMSVC certificate isn't an Exchange certificate.-->
Before you can establish a Partner Center account, you need to get a code signing certificate to secure your digital information. This certificate is the accepted standard for establishing your company’s ownership of the code you submit. It allows you to digitally sign PE binaries, such as .exe, .cab, .dll, .ocx, .msi, .xpi and .xap files.
Step 1: Obtain an EV certificate
- Microsoft requires an extended validation (EV) code signing certificates from partners enrolled and authorized for Kernel Mode Code Signing as part of the Microsoft Trusted Root Certificate Program. If you already have an approved EV certificate from one of these authorities, you can use it to establish a Partner Center account. If you don’t have a certificate, you’ll need to buy a new one.
Step 2: Buy a new code signing certificate
If you don’t have an approved EV code signing certificate, you can buy one from one of the certificate authorities below.
Extended validation code signing certificates
On the DigiCert Code Signing Certificates for Sysdevs page, click Start.
On the DigiCert Order Form page (Step 1), in the Code Signing section, click EV Code Signing Certificate, fill out the rest of the form, and then click Continue.
Follow the instructions provided by DigiCert to buy a certificate.
Step 3: Retrieve code signing certificates
Once the certificate authority has verified your contact information and your certificate purchase is approved, follow their directions to retrieve the certificate.
You must use the same computer and browser to retrieve your certificate.
If you’re setting up a new Partner Center account, follow the steps in Register for the Hardware Program.
If you’ve already set up a Partner Center account and need to renew a certificate, follow the steps in Add or Update a code signing certificate.
Code Signing FAQ
This section provides answers to frequently asked questions about code signing for Windows 10. Additional code signing information is available on the Windows Hardware Certification blog.
HLK Tested and Dashboard Signed Drivers
- A dashboard signed driver that has passed the HLK tests will work on Windows Vista through Windows 10, including Windows Server editions. This is the recommended method for driver signing, because it allows a single process for all OS versions. In addition, HLK tested drivers demonstrate that a manufacturer has rigorously tested their hardware to meet all of Microsoft's requirements with regards to reliability, security, power efficiency, serviceability, and performance, so as to provide a great Windows experience. This includes compliance with industry standards and adherence with Microsoft specifications for technology-specific features, helping to ensure correct installation, deployment, connectivity and interoperability. For more information about the HLK, see Windows Hardware Compatibility Program.
Windows 10 Desktop Attestation Signing
- A dashboard signed driver using attestation signing will only work on Windows 10 Desktop and later versions of Windows.
- An attestation signed driver will only work for Windows 10 Desktop; it will not work for other versions of Windows, such as Windows Windows 7, Windows 8.1, or Windows Server 2016 and greater.
- Attestation signing supports Windows 10 Desktop kernel mode and user mode drivers.
Windows 10 Earlier Certificate Transition Signing
- The below only applies to Windows 10 1803 and lower. As of Windows 10 1809, these will no longer work.
- A driver signed with any certificate issued after July 29th, 2015, with time stamping, is not recommended for Windows 10.
- A driver signed with any certificate that expires after July 29th, 2015, without time stamping, will work on Windows 10 until the certificate expires.
Cross-Signing and SHA-256 Certificates
Microsoft Communicator Mac Digital Certificate File Type
Cross-signing describes a process where a driver is signed with a certificate issued by a Certificate Authority (CA) that is trusted by Microsoft. For more information, see Cross-Certificates Overview.
- Windows 8 and later versions support SHA-256.
- Windows 7, if patched, supports SHA-256. If you need to support unpatched devices that run Windows 7, you need to either cross-sign with a SHA-1 certificate or submit to the Dashboard for signing. Otherwise, you can either cross-sign with SHA-1 or SHA-2 certificate or create an HLK/HCK submission for signing.
- Because Windows Vista doesn’t support SHA-256, you need to either cross-sign with a SHA-1 certificate or create an HLK/HCK submission for Windows Vista driver signing.
- A driver cross-signed with a SHA-256 certificate (including an EV certificate) issued prior to July 29th, 2015 will work on Windows 8 and later. It will not work on Windows Vista or Windows Server 2008.
- A driver cross-signed with a SHA-256 certificate (including an EV certificate) issued prior to July 29th, 2015 will work on Windows 7 or Server 2008R2 if the patch issued through Windows Update earlier this year has been applied. For more information, see Availability of SHA-2 Hashing Algorithm for Windows 7 and Windows Server 2008 R2 and Microsoft security advisory: Availability of SHA-2 code signing support for Windows 7 and Windows Server 2008 R2: March 10, 2015.
- A cross-signed driver using a SHA-1 certificate issued prior to July 29th, 2015 will work on all platforms starting with Windows Vista through Windows 10.
- A cross-signed driver using a SHA-1 or SHA-256 certificate issued after July 29th, 2015 is not recommended for Windows 10.
- For more information about the effort to move to SHA-256 Certificates, see Windows Enforcement of Authenticode Code Signing and Timestamping
- Enterprises may implement a device guard policy to modify the driver signing requirements using Windows 10 Enterprise edition. Device Guard provides an enterprise-defined code integrity policy, which may be configured to require at least an attestation-signed driver. For more information about Device Guard, see Device Guard certification and compliance.
Microsoft Communicator Mac Digital Certificate File Software
- Windows Server 2016 and greater will not accept attested device and filter driver signing submissions.
- The dashboard will only sign device and filter drivers that have successfully passed the HLK tests.
- Windows Server 2016 and greater will only load dashboard signed drivers that have successfully passed the HLK tests.
- As of October 31, 2015, your Hardware Dev Center dashboard account must have at least one EV certificate associated with it to submit binaries for attestation signing or to submit binaries for HLK certification.
- The submitted binaries themselves must be signed.
OS Support Summary
This table summarizes the driver signing requirements for Windows.
|Attestation Dashboard Signed||HLK Test Passed Dashboard Signed||Cross-signed using a SHA-1 certificate issued prior to July 29, 2015|
|Windows 8 / 8.1||No||Yes||Yes|
|Windows 10||Yes||Yes||No (as of Windows 10 1809)|
|Windows 10 - DG Enabled||*Configuration Dependent||*Configuration Dependent||*Configuration Dependent|
|Windows Server 2008 R2||No||Yes||Yes|
|Windows Server 2012 R2||No||Yes||Yes|
|Windows Server >= 2016||No||Yes||Yes|
|Windows Server >= 2016 – DG Enabled||*Configuration Dependent||*Configuration Dependent||*Configuration Dependent|
|Windows IoT Enterprise||Yes||Yes||Yes|
|Windows IoT Enterprise- DG Enabled||*Configuration Dependent||*Configuration Dependent||*Configuration Dependent|
|Windows IoT Core(1)||Yes (Not Required)||Yes (Not Required)||Yes (Cross signing will also work for certificates issued after July 29, 2015)|
*Configuration Dependent –With Windows 10 Enterprise edition, organizations can use Device Guard to define custom driver signing requirements. For more information about Device Guard, see Device Guard certification and compliance.
Microsoft Communicator Mac Digital Certificate File Download
(1) Driver signing is required for manufacturers building retail products (i.e. for a non-development purpose) with IoT Core. For a list of approved Certificate Authorities (CAs), see Cross-Certificates for Kernel Mode Code Signing. Note that if UEFI Secure Boot is enabled, then drivers must be signed.