You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/database-engine/configure-windows/manage-certificates.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ manager: craigg
26
26
27
27
This topic describes how to deploy and manage certificates across your SQL Server Failover Cluster or Always On Availability Group topology.
28
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:
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 had 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
30
31
31
* Viewing and validating certificates installed in a SQL Server instance.
32
32
* See which certificates may be close to expiration.
@@ -40,53 +40,53 @@ SSL/TLS certificates are widely used to secure access to SQL Server. With earlie
40
40
41
41
1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.
42
42
43
-
2. Rightclick on **Protocols for***<instanceName>*, and then click**Properties**.
43
+
2. Right-click **Protocols for***<instanceName>*, and then select**Properties**.
44
44
45
-
3.Click on**Certificate** tab, and then click the **Import** button.
45
+
3.Choose the**Certificate** tab, and then select **Import**.
46
46
47
-
4.Click**Browse** and select certificate file.
47
+
4.Select**Browse** and select the certificate file.
48
48
49
-
5.Click**Next** to validate the certificate. If there are no errors, click**Next** to import the certificate to the local instance.
49
+
5.Select**Next** to validate the certificate. If there are no errors, select**Next** to import the certificate to the local instance.
50
50
51
51
52
52
## <aname="provision-failover-cluster-cert"></a> To provision (install) a certificate in a Failover Cluster configuration
53
53
54
54
1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration”.
55
55
56
-
2. Rightclick on **Protocols for***<instanceName>*, and then click**Properties**.
56
+
2. Right-click **Protocols for***<instanceName>*, and then choose**Properties**.
57
57
58
-
3.Click on**Certificate** tab, and then click the **Import** button.
58
+
3.Choose the**Certificate** tab, and then select **Import**.
59
59
60
60
4. Select the certificate type, and whether to import for the current node only, or for each individual cluster node.
61
61
62
-
5. If installing for a single node, click**Browse** and select certificate file. Then skip to step 8.
62
+
5. If installing for a single node, choose**Browse** and select certificate file. Then skip to step 8.
63
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.
64
+
6. If installing a certificate for each node, choose **Next** to list possible owner nodes. Possible owners for the current SQL Server FCI are pre-selected.
65
65
66
-
7.Click**Next** to select the certificate to be imported.
66
+
7.Choose**Next** to select the certificate to be imported.
67
67
**
68
68
8. Enter the password when prompted. Look for any warnings or errors after validation.
69
69
70
-
9.Click**Next** to import the selected certificates.
70
+
9.Select**Next** to import the selected certificates.
71
71
72
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.
73
+
> Complete these steps in the active node of the SQL Server Failover Cluster instance. User must have administrator permissions on all the cluster nodes.
74
74
75
75
## <aname="provision-always-on-cert"></a>To provision (install) a certificate in an Always On configuration
76
76
77
77
1. In SQL Server Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.
78
78
79
-
2. Rightclick on **Protocols for***<instanceName>*, and then click**Properties**.
79
+
2. Right-click **Protocols for***<instanceName>*, and then select**Properties**.
80
80
81
-
3.Click on**Certificate** tab, and then click the **Import** button.
81
+
3.Choose the**Certificate** tab, and then select **Import**.
82
82
83
-
4.Select the certificate type and click**Next** to select from the list of known Availability Groups.
83
+
4.Choose the certificate type and select**Next** to select from the list of known Availability Groups.
84
84
85
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
86
87
87
6. Click **Next** to import the certificate on each node.
88
88
89
89
90
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.
91
+
> Complete these steps from the node holding the Availability Group primary replica. User must have administrator permissions on all the cluster nodes.
0 commit comments