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
@@ -75,17 +75,19 @@ On a CA server in your SCOM environment, follow these steps to create a certific
75
75
1. Export the CA and Intermediate CA certificate (if applicable) to the *root* store of all the management servers/gateways in the UNIX/Linux resource pool.
76
76
77
77
## Copy and edit the certificate on the Unix/Linux server
78
+
78
79
Use one of the following methods to configure the certificate on the the Unix/Linux server:
79
80
80
-
### Method 1: Configure Certificate Manually
81
+
### Method 1: Configure certificate manually
82
+
81
83
1. Copy the certificate to the Unix/Linux server for which the certificate was issued.
82
84
1. Export the private key by using the following command:
> While exporting the private key from the certificate store, include the `-nodes` paramter (stands for no DES) which instructs OpenSSL to output the private key in an unencrypted format, otherwise a new password has to be set for the new key file.
90
+
While exporting the private key from the certificate store, include the `-nodes` paramter (which stands for no Desktop Environments (DEs)). This instructs OpenSSL to output the private key in an unencrypted format. Otherwise a new password has to be set for the new key file.
89
91
90
92
1. Export the certificate by using the following command:
91
93
@@ -100,7 +102,7 @@ Use one of the following methods to configure the certificate on the the Unix/Li
1. Set the correct permissions and ownership on the private key, certificate and symbolic link:
105
+
1. Set the correct permissions and ownership on the private key, certificate, and symbolic link:
104
106
105
107
```console
106
108
chmod 600 /etc/opt/omi/ssl/omikey.pem
@@ -115,16 +117,17 @@ Use one of the following methods to configure the certificate on the the Unix/Li
115
117
scxadmin -restart
116
118
```
117
119
118
-
1. Make sure the *omi* processes are running after restarting the agent:
120
+
1. Make sure the Open Management Infrastructure (OMI) processes are running after restarting the agent:
119
121
120
122
```console
121
123
ps -ef | grep omi | grep -v grep
122
124
```
123
125
124
126
:::image type="content" source="media/use-ca-certificate-on-scom-linux-agent/command-validate-omi-processes.png" alt-text="Screenshot that shows the command to validate omi processes running." lightbox="media/use-ca-certificate-on-scom-linux-agent/command-validate-omi-processes.png":::
125
127
126
-
### Method 2: Configure Certificate with Bash Script
127
-
1. Save the following bash script extract_scx_cert.sh
128
+
### Method 2: Configure certificate with bash script
129
+
130
+
1. Save the following bash script: `extract_scx_cert.sh`
128
131
129
132
```console
130
133
#!/bin/bash
@@ -163,13 +166,13 @@ Use one of the following methods to configure the certificate on the the Unix/Li
163
166
systemctl restart omid
164
167
```
165
168
166
-
1. Change script permissions to be executed
169
+
1. Change the script permissions to be run:
167
170
168
171
```console
169
172
chmod +x /home/user/extract_scx_cert.sh
170
173
```
171
174
172
-
1. Run he following command to execute the script with the two parameters; the path to the pfx file and the password for it
175
+
1. Run the following command to run the script with these two parameters: the path to the PFX file and the password for it.
@@ -199,7 +202,7 @@ Use one of the following methods to configure the certificate on the the Unix/Li
199
202
notAfter=Jul 25 12:12:14 2033 GMT
200
203
```
201
204
202
-
> The path `/etc/opt/microsoft/scx/ssl` contains a symbolic link `scx.pem -> /etc/opt/omi/ssl/omi.pem` that is used by the SCX agent to use the OMI certificate that was created earlier.
205
+
> The path `/etc/opt/microsoft/scx/ssl` contains a symbolic link `scx.pem -> /etc/opt/omi/ssl/omi.pem` that's used by the SCX agent in order to use the OMI certificate created earlier.
203
206
204
207
1. Run a network trace on one of the management servers/gateways in the UNIX/Linux resource pool.
205
208
1. Run the following `WinRM` command against the agent and make sure you get the instance output:
0 commit comments