Skip to content

Commit 3ee3eb1

Browse files
damabedamabe
committed
Add file and update toc.
1 parent 7e10812 commit 3ee3eb1

2 files changed

Lines changed: 94 additions & 0 deletions

File tree

‎docs/database-engine/configure-windows/manage-certificates.md‎

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
---
2+
title: "Certificate Management (SQL Server Configuration Manager) | Microsoft Docs"
3+
ms.custom: ""
4+
ms.date: "01/16/2019"
5+
ms.prod: sql
6+
ms.prod_service: high-availability
7+
ms.reviewer: ""
8+
ms.technology: configuration
9+
ms.topic: conceptual
10+
helpviewer_keywords:
11+
- "connections [SQL Server], encrypted"
12+
- "SSL [SQL Server]"
13+
- "Secure Sockets Layer (SSL)"
14+
- "encryption [SQL Server], connections"
15+
- "cryptography [SQL Server], connections"
16+
- "certificates [SQL Server], installing"
17+
- "requesting encrypted connections"
18+
- "installing certificates"
19+
- "security [SQL Server], encryption"
20+
ms.assetid: e1e55519-97ec-4404-81ef-881da3b42006
21+
author: MikeRayMSFT
22+
ms.author: mikeray
23+
manager: craigg
24+
---
25+
# Certificate Management (SQL Server Configuration Manager)
26+
27+
This topic describes how to deploy and manage certificates across your SQL Server Failover Cluster or Always On Availability Group topology.
28+
29+
SSL/TLS certificates are widely used to secure access to SQL Server. With earlier versions of SQL Server, organizations with large SQL Server estates have needed to expend considerable effort to maintain their SQL Server certificate infrastructure—often through developing scripts and running manual commands. With SQL Server 2019, certificate management is integrated into the SQL Server Configuration Manager, simplifying common tasks such as:
30+
31+
* Viewing and validating certificates installed in a SQL Server instance.
32+
* See which certificates may be close to expiration.
33+
* Deploy certificates across Always On Availability Group machines (from the node holding the primary replica).
34+
* Deploy certificates across machines participating in a failover cluster instance (from the active node).
35+
36+
> [!NOTE]
37+
> Certificate management in SQL Server Configuration Manager can be used with lower versions of SQL Server, starting with SQL Server 2008.
38+
39+
## <a name="provision-single-server-cert"></a> To provision (install) a certificate for a single SQL Server instance
40+
41+
1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.
42+
43+
2. Right click on **Protocols for** *<instance Name>*, and then click **Properties**.
44+
45+
3. Click on **Certificate** tab, and then click the **Import** button.
46+
47+
4. Click **Browse** and select certificate file.
48+
49+
5. Click **Next** to validate the certificate. If there are no errors, click **Next** to import the certificate to the local instance.
50+
51+
52+
## <a name="provision-failover-cluster-cert"></a> To provision (install) a certificate in a Failover Cluster configuration
53+
54+
1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration”.
55+
56+
2. Right click on **Protocols for** *<instance Name>*, and then click **Properties**.
57+
58+
3. Click on **Certificate** tab, and then click the **Import** button.
59+
60+
4. Select the certificate type, and whether to import for the current node only, or for each individual cluster node.
61+
62+
5. If installing for a single node, click **Browse** and select certificate file. Then skip to step 8.
63+
64+
6. If installing a certificate for each node, click on **Next** to list possible owner nodes. Possible owners for the current SQL Server FCI will be pre-selected.
65+
66+
7. Click **Next** to select the certificate to be imported.
67+
**
68+
8. Enter the password when prompted. Look for any warnings or errors after validation.
69+
70+
9. Click **Next** to import the selected certificates.
71+
72+
> [!NOTE]
73+
> This must be done in the active node of the SQL Server Failover Cluster instance. User must have administrator permissions on all the cluster nodes.
74+
75+
## <a name="provision-always-on-cert"></a>To provision (install) a certificate in an Always On configuration
76+
77+
1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.
78+
79+
2. Right click on **Protocols for** *<instance Name>*, and then click **Properties**.
80+
81+
3. Click on **Certificate** tab, and then click the **Import** button.
82+
83+
4. Select the certificate type and click **Next** to select from the list of known Availability Groups.
84+
85+
5. Click **Next** to select certificates for each replica node. Certificates should have a file name that matches the netbios name of the nodes.
86+
87+
6. Click **Next** to import the certificate on each node.
88+
89+
90+
> [!NOTE]
91+
> This must be done from the node holding the Availability Group primary replica. User must have administrator permissions on all the cluster nodes.
92+

‎docs/database-engine/configure-windows/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -253,6 +253,8 @@
253253
href: determine-whether-the-database-engine-is-installed-and-started.md
254254
- name: Connect to the Database Engine Using Extended Protection
255255
href: connect-to-the-database-engine-using-extended-protection.md
256+
- name: Certificate Management (SQL Server Configuration Manager)
257+
href: manage-certificates.md
256258
- name: Register a Service Principal Name for Kerberos Connections
257259
href: register-a-service-principal-name-for-kerberos-connections.md
258260
- name: Client Network Configuration

0 commit comments

Comments
 (0)