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
Updated image references from ./images/ to ../images/ since images are stored in the parent 1secure/images directory, not in subdirectory image folders.
Fixed files:
- certificate-management/configure_proxy_for_rdp_connections_(installupdate_certificate_to_prevent_rdp_certificate_warnings).md
- troubleshooting/troubleshoot_failed_action_service_connections_to_windows_resources_(psremotingwinrm).md
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
Copy file name to clipboardExpand all lines: docs/kb/1secure/certificate-management/configure_proxy_for_rdp_connections_(installupdate_certificate_to_prevent_rdp_certificate_warnings).md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ This article outlines the process for installing or updating a certificate to pr
26
26
27
27
> **IMPORTANT:** The Certification Authority's post-deployment configuration must be completed after installing both prerequisite roles.
28
28
29
-
29
+
30
30
31
31
- The domain must have the **Enrollment Policy** set to enable automatic enrollment and renewal. The **Certificate Enrollment Policy** for user and computer certificates is configured in the **Group Policy** snap-in under **Default Domain Policy** (or another group policy applied to all systems that will access an NPS server on a group-by-group basis). To configure this:
32
32
@@ -40,28 +40,28 @@ This article outlines the process for installing or updating a certificate to pr
40
40
> **NOTE:** If you already have a certificate to install, you can skip to the **Adding the Certificate to Each SbPAM Proxy Server** section below.
41
41
42
42
1. Open **Certification Authority**, open your CA, right-click **Certificate Templates**, and click **Manage**.
43
-
43
+
44
44
45
45
2. In the **Certificate Templates Console**, right-click **Workstation Authentication**, and click **Duplicate Template**.
46
-
46
+
47
47
48
48
3. On the **General** tab, change the name to **Client-Server Authentication** and enable the **Publish certificate in Active Directory** checkbox.
49
-
49
+
50
50
51
51
4. On the **Subject Name** tab, enable the **Supply in the request** radio button.
52
-
52
+
53
53
54
54
5. On the **Extensions** tab, select **Application Policies** and click **Edit**. Click **Add**, then select **Server Authentication**. Click **OK** until you return to the **Properties of New Template** dialog.
55
-
55
+
56
56
57
57
6. On the **Security** tab, select **Domain Computers** and enable the checkbox to allow **Autoenroll**. Click **OK** and then close the Certificate Templates Console.
58
-
58
+
59
59
60
60
7. Back in **Certification Authority**, right-click **Certificate Templates**, hover over **New**, and click **Certificate Template to Issue**.
61
-
61
+
62
62
63
63
8. Select **Client-Server Authentication** and click **OK**.
64
-
64
+
65
65
66
66
9. On the desktop, create a text file named **request.inf** with the following content (replace the **red** text with your server certificate name):
67
67
@@ -96,44 +96,44 @@ This article outlines the process for installing or updating a certificate to pr
11. To sign the certificate request, use your preferred signing mechanism. The following example uses Active Directory Certificate Services (`https://<servername>/certsrv`).
102
-
 
102
+
 
103
103
104
104
Click **Request a certificate**, then click **advanced certificate request**.
105
105
106
106
12. Open the saved certificate signing request (**rdp.csr**) from the previous step in Notepad. Copy the certificate request into the **Saved Request** field. Select **Client-Server Authentication** from the **Certificate Template** dropdown. Click **Submit**.
107
-
107
+
108
108
109
109
Leave other settings at default values, and click **Submit**.
110
110
111
111
13. Select **DER encoded** and click **Download certificate**.
112
-
112
+
113
113
114
114
14. Open the downloaded certificate and select **Install Certificate**. Proceed with all default values and complete the wizard.
115
-
115
+
116
116
117
117
15. To export the certificate, view certificates for the current user by launching **certmgr.msc** using the Windows **Run** menu.
118
-
118
+
119
119
120
120
Right-click the installed certificate (the certificate using the **Client-Server Authentication** template) and click **Export...**.
16. In the **Certificate Export Wizard**, change the **Export Private Key** option to **Yes, export the private key**.
124
-
124
+
125
125
126
126
17. For **Export File Format**, select **Personal Information Exchange - PKCS #12 (.PFX)**. Select the following checkboxes:
127
127
128
128
- Include all certificates in the certification path if possible
129
129
- Enable certificate privacy
130
130
131
-
131
+
132
132
133
133
18. For **Security**, enter a password of your choosing and select the AES256-SHA256 encryption option (3DES is no longer recommended by NIST).
134
134
135
135
> **IMPORTANT:** For **File to Export**, the file name **must** be **rdp.pfx**. If it is named anything else, importing the .pfx file on each proxy server will not work.
136
-
136
+
137
137
138
138
19. This certificate can now be imported to each SbPAM Proxy Server.
139
139
@@ -149,7 +149,7 @@ This article outlines the process for installing or updating a certificate to pr
149
149
"C:\Program Files\Stealthbits\PAM\ProxyService\sbpam-proxy.exe" ca import -p [PATH]\rdp.pfx
150
150
```
151
151
152
-
152
+
153
153
154
154
3. The new certificate has now been imported to an SbPAM Proxy Server. Repeat this process for all SbPAM Proxy Servers if using more than one. (The default installation of SbPAM uses one proxy service on the SbPAM server itself; however, additional proxy services can be distributed.)
Copy file name to clipboardExpand all lines: docs/kb/1secure/troubleshooting/troubleshoot_failed_action_service_connections_to_windows_resources_(psremotingwinrm).md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ There are Group Policy settings used to filter the origin of WinRM requests via
87
87
88
88
Learn more about the **Allow remote server management through WinRM** Group Policy setting in [Configure Remote Management in Server Manager − Enabling or Disabling Remote Management ⸱ Microsoft 🡥](https://learn.microsoft.com/en-us/windows-server/administration/server-manager/configure-remote-management-in-server-manager#enabling-or-disabling-remote-management).
89
89
90
-
90
+
0 commit comments