Merge pull request #5279 from EnterpriseDB/content/docs/pem/registry-fix

PEM - Updated the registry links
EnterpriseDB · Feb 19, 2024 · 767986a · 767986a · github-actions · Feb 19, 2024
2 parents 637c12a + 6b4f038
commit 767986a
Show file tree

Hide file tree

Showing 19 changed files with 23 additions and 23 deletions.
diff --git a/.../8/considerations/pem_security_best_practices/pem_application_configuration.mdx b/.../8/considerations/pem_security_best_practices/pem_application_configuration.mdx
@@ -115,7 +115,7 @@ To run scheduled jobs as a non-root user, modify the entry for the `batch_script
 To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to `true` and restart the PEM agent. PEM registry entries are located in:
 
 ```shell
-HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent\
+HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent
 ```
 
 ## Changing the pemAgent and PEM backend database server certificates

diff --git a/product_docs/docs/pem/8/managing_certificates.mdx b/product_docs/docs/pem/8/managing_certificates.mdx
@@ -198,8 +198,8 @@ To generate a PEM agent key file pair:
 
     -   On a 64-bit Windows installation, check:
 
-    ```shell
-    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\EnterpriseDB\PEM\agent
+    ```shellHKEY_LOCAL_MACHINE\SOF
+    HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent
     ```
 
     -   On a 32-bit Windows installation, check:

diff --git a/product_docs/docs/pem/8/managing_pem_agent.mdx b/product_docs/docs/pem/8/managing_pem_agent.mdx
@@ -100,7 +100,7 @@ Use the Step Definition dialog box to define the step:
 
         -   To invoke a script on a Linux system, you must modify the entry for the `batch_script_user` parameter in the `agent.cfg` file and specify the user who runs the script. You can specify either a nonroot user or root for this parameter. If you don't specify a user or the specified user doesn't exist, then the script doesn't execute. Restart the agent after modifying the file.
 
-        -   To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to `true` and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent`.
+        -   To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to `true` and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent`.
 
 After providing all the information required by the step, select **Save**.
 
@@ -235,7 +235,7 @@ On Linux systems, PEM configuration options are stored in the `agent.cfg` file,
 
 On 64-bit Windows systems, PEM registry entries are located in:
 
- `HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent`
+ `HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent`
 
 The registry contains the entries shown in the table.
 

diff --git a/product_docs/docs/pem/8/monitoring_performance/alerts.mdx b/product_docs/docs/pem/8/monitoring_performance/alerts.mdx
@@ -553,8 +553,8 @@ Use the **Nagios notification** box to instruct the PEM server to notify Nagios
     `%AlertRaisedTime%` &mdash; The time that the alert was raised or the most recent time that the alert state was changed.
 
     To invoke a script on a Linux system, you must modify the entry for the `batch_script_user` parameter of the `agent.cfg` file and specify the user to use to run the script. You can either specify a non-root user or root for this parameter. If you don't specify a user or the specified user doesn't exist, then the script doesn't execute. Restart the agent after modifying the file.
-
-    To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to true and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE/Software/Wow6432Node/EnterpriseDB/PEM/agent`.
+HKEY_LOCAL_MACHINE/Soft
+    To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to true and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent`.
 
 After you define the alert attributes, select **Edit** to close the alert definition editor and then **Save** in the upper-right corner of the Alerts table. 
 

diff --git a/product_docs/docs/pem/8/monitoring_performance/notifications.mdx b/product_docs/docs/pem/8/monitoring_performance/notifications.mdx
@@ -79,7 +79,7 @@ To define a new webhook, select the plus sign (+) in the upper-right corner of t
 You can define the webhook SSL parameters in the respective agent configuration file or registry in Windows. You can find the list of webhook SSL parameters in [PEM agent configuration parameters](../managing_pem_agent/#agent-configuration). If you add or remove any of the agent configuration parameters, you must restart the agent to apply them.
 
 -   On 32-bit Windows systems, PEM registry entries for webhooks are located in `HKEY_LOCAL_MACHINE\\Software\\EnterpriseDB\\PEM\\agent\\WEBHOOK`.
--   On 64-bit Windows systems, PEM registry entries for webhooks are located in `HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent\\WEBHOOK`.
+-   On 64-bit Windows systems, PEM registry entries for webhooks are located in `HKEY_LOCAL_MACHINE\\Software\\EnterpriseDB\\PEM\\agent\\WEBHOOK`.
 -   On Linux systems, PEM configuration options for webhooks are stored in the `agent.cfg file`, located by default in `/usr/edb/pem/agent/etc`.
 
 ![Example - Webhook SSL Parameters in agent.cfg file](../images/webhook_ssl_config.png)

diff --git a/product_docs/docs/pem/8/monitoring_performance/probes.mdx b/product_docs/docs/pem/8/monitoring_performance/probes.mdx
@@ -147,7 +147,7 @@ Use the **General** tab to modify the definition of an existing probe or to spec
     -   If you installed PEM using graphical installer: `/opt/edb/pem/agent/etc/agent.cfg`
     -   If you installed PEM using RPM: `/usr/edb/pem/agent/etc/agent.cfg`
 
-    On 64-bit Windows systems, agent settings are stored in the registry. Before creating a batch probe, modify the registry entry for the `AllowBatchProbes` registry entry and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent`.
+    On 64-bit Windows systems, agent settings are stored in the registry. Before creating a batch probe, modify the registry entry for the `AllowBatchProbes` registry entry and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent`.
 
     Batch probes are platform specific. If you specify a collection method of **Batch**, you must specify a platform type in the **Platform** field.
 

diff --git a/...docs/docs/pem/8/pem_online_help/02_toc_pem_agent/06_pem_agent_config_params.mdx b/...docs/docs/pem/8/pem_online_help/02_toc_pem_agent/06_pem_agent_config_params.mdx
@@ -10,7 +10,7 @@ legacyRedirectsGenerated:
 A number of user-configurable parameters and registry entries control the behavior of the PEM Agent. With the exception of the PEM_MAXCONN (or pem_maxconn) parameter, we strongly recommend against modifying any of the configuration parameters or registry entries listed below without first consulting EnterpriseDB support experts.
 
 > -   On 32 bit Windows systems, PEM registry entries are located in HKEY_LOCAL_MACHINE\\Software\\EnterpriseDB\\PEM\\agent
-> -   On 64 bit Windows systems, PEM registry entries are located in HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent
+> -   On 64 bit Windows systems, PEM registry entries are located in HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent
 > -   On Linux systems, PEM configuration options are stored in the agent.cfg file, located (by default) in /usr/edb/pem/agent/etc
 
 | **Parameter Name**                                                       | **Description**                                                                                                                                                                                                                                                                                          | **Value (if applicable)**                                                                                                                                                                                                                                                                              |
@@ -40,7 +40,7 @@ A number of user-configurable parameters and registry entries control the behavi
 | HeartbeatConnection (on Windows) or heartbeat_connection (on Linux)      | When set to TRUE, a dedicated connection used for sending the heartbeats.                                                                                                                                                                                                                                | By default, set to FALSE.                                                                                                                                                                                                                                                                              |
 | AllowBatchProbes (on Windows) or allow_batch_probes (on Linux)           | If set to TRUE, the user will be able to create batch probes using custom probes feature.                                                                                                                                                                                                                | By default, set to FALSE.                                                                                                                                                                                                                                                                              |
 | BatchScriptDir (on Windows) or batch_script_dir (on Linux)               | Provide the path where script file (for alerting) will be stored.                                                                                                                                                                                                                                        | On Windows, C:Usersuser_nameAppDataLocalTemp. On Linux, set to /tmp.                                                                                                                                                                                                                                   |
-| AllowBatchJobSteps (on Windows) or batch_script_user                     | Provide the username who will run the script.                                                                                                                                                                                                                                                            | On Windows, set to TRUE and restart PEM Agent. Entries located in HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent. On Linux, Restart the agent after modifying the file. If you do not specify a user, or the specified user does not exist, then the script will not be executed. |
+| AllowBatchJobSteps (on Windows) or batch_script_user                     | Provide the username who will run the script.                                                                                                                                                                                                                                                            | On Windows, set to TRUE and restart PEM Agent. Entries located in HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent. On Linux, Restart the agent after modifying the file. If you do not specify a user, or the specified user does not exist, then the script will not be executed. |
 | ConnectionCustomSetup (on Windows) or connection_custom_setup (on Linux) | Use this parameter to provide SQL code that will be invoked each time a new connection with the monitored server is established.                                                                                                                                                                         | By default, no value is provided.                                                                                                                                                                                                                                                                      |
 | ca_file (Linux only)                                                     | Provide the path where the CA certificate resides.                                                                                                                                                                                                                                                       | By default, /opt/PEM/agent/share/certs/ca-bundle.crt                                                                                                                                                                                                                                                   |
 | WebhookSSLKey (on Windows) or webhook_ssl_key (on Linux)                 | The complete path to the webhook's SSL client key file.                                                                                                                                                                                                                                                  |                                                                                                                                                                                                                                                                                                        |

diff --git a/.../pem_online_help/04_toc_pem_features/09_pem_alerting/01_pem_alerting_dialog.mdx b/.../pem_online_help/04_toc_pem_features/09_pem_alerting/01_pem_alerting_dialog.mdx
@@ -196,6 +196,6 @@ Fields on the `Notifications` tab instruct PEM to:
 -   Execute the script shown in the `Code` field when the alert is triggered.
 
 > -   To invoke a script on a Linux system, you must modify the entry for `batch_script_user` parameter of agent.cfg file and specify the user that should be used to run the script. You can either specify a non-root user or root for this parameter. If you do not specify a user, or the specified user does not exist, then the script will not be executed. Restart the agent after modifying the file. If pemagent is being run by a non-root user then the value of `batch_script_user` will be ignored and the script will be executed by the same non-root user that is being used for running the pemagent.
-> -   To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to true and restart the PEM agent. PEM registry entries are located in HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent.
+> -   To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to true and restart the PEM agent. PEM registry entries are located in HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent.
 
 Click the edit icon to close the editor and add the example to the `Alert List`; click the save icon before closing the `Manage Alerts` tab to save your work.
diff --git a/...s/pem/8/pem_online_help/04_toc_pem_features/09_pem_alerting/06_pem_webhooks.mdx b/...s/pem/8/pem_online_help/04_toc_pem_features/09_pem_alerting/06_pem_webhooks.mdx
@@ -38,7 +38,7 @@ Use the `General` tab to define the basic details of the webhook:
 You can define the Webhook SSL parameters in the respective agent configuration file or registry in windows. You can find the list of Webhook SSL parameters in [PEM Agent Configuration Parameters](../../02_toc_pem_agent/06_pem_agent_config_params/) section. If you add or remove any of the agent configuration parameters, you must restart the agent to apply them.
 
 -   On 32 bit Windows systems, PEM registry entries for Webhooks are located in HKEY_LOCAL_MACHINE\\Software\\EnterpriseDB\\PEM\\agent\\WEBHOOK
--   On 64 bit Windows systems, PEM registry entries for Webhooks are located in HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent\\WEBHOOK
+-   On 64 bit Windows systems, PEM registry entries for Webhooks are located in HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent\WEBHOOK
 > -   On Linux systems, PEM configuration options for Webhooks are stored in the agent.cfg file, located (by default) in /usr/edb/pem/agent/etc
 
 ![Example - Webhook SSL Parameters in agent.cfg file](../../images/webhook_ssl_config.png)

diff --git a/...m_online_help/04_toc_pem_features/12_pem_manage_probes/01_pem_custom_probes.mdx b/...m_online_help/04_toc_pem_features/12_pem_manage_probes/01_pem_custom_probes.mdx
@@ -34,7 +34,7 @@ Use the fields on the `General` tab to modify the definition of an existing prob
 
         Before creating a batch probe on a Linux system, you must modify the `agent.cfg` file, setting the `allow_batch_probes` parameter equal to `true` and restart the PEM agent. The `agent.cfg` file is located in `/opt/PEM/agent/etc`.
 
-        On 64-bit Windows systems, agent settings are stored in the registry. Before creating a batch probe, modify the registry entry for the `AllowBatchProbes` registry entry and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent`.
+        On 64-bit Windows systems, agent settings are stored in the registry. Before creating a batch probe, modify the registry entry for the `AllowBatchProbes` registry entry and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent`.
 
         Please note that batch probes are platform-specific. If you specify a collection method of `Batch`, you must specify a platform type in the `Platform` field.
 

diff --git a/...t_docs/docs/pem/8/pem_online_help/04_toc_pem_features/16_pem_scheduled_jobs.mdx b/...t_docs/docs/pem/8/pem_online_help/04_toc_pem_features/16_pem_scheduled_jobs.mdx
@@ -56,7 +56,7 @@ Use the context-sensitive field on the step definition dialog's `Code` tab to pr
 
 To invoke a script on a Linux system, you must modify the entry for `batch_script_user` parameter of agent.cfg file and specify the user that should be used to run the script. You can either specify a non-root user or root for this parameter. If you do not specify a user, or the specified user does not exist, then the script will not be executed. Restart the agent after modifying the file. If pemagent is being run by a non-root user then the value of `batch_script_user` will be ignored and the script will be executed by the same non-root user that is being used for running the pemagent.
 
-To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` as true and restart the PEM agent. PEM registry entries are located in HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent.
+To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` as true and restart the PEM agent. PEM registry entries are located in HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent.
 
 After providing all the information required by the step, click the `Save` button to save and close the step definition dialog.
 

diff --git a/product_docs/docs/pem/8/upgrading/moving_pem_server.mdx b/product_docs/docs/pem/8/upgrading/moving_pem_server.mdx
@@ -357,7 +357,7 @@ Before starting the server migration, make sure that the firewalls between the s
 
     On 64-bit Windows, the PEM agent registry entries are located at:
 
-    `HKEY_LOCAL_MACHINE SOFTWARE wow6432Mode EnterpriseDB PEM Agent`
+    `HKEY_LOCAL_MACHINE SOFTWARE EnterpriseDB PEM Agent`
 
     On 32-bit Windows, the PEM agent registry entries are located at:
 

diff --git a/.../9/considerations/pem_security_best_practices/pem_application_configuration.mdx b/.../9/considerations/pem_security_best_practices/pem_application_configuration.mdx
@@ -115,7 +115,7 @@ To run scheduled jobs as a non-root user, modify the entry for the `batch_script
 To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to `true` and restart the PEM agent. PEM registry entries are located in:
 
 ```shell
-HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent\
+HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent
 ```
 
 ## Changing the pemAgent and PEM backend database server certificates

diff --git a/product_docs/docs/pem/9/managing_pem_agent/managing_scheduled_jobs.mdx b/product_docs/docs/pem/9/managing_pem_agent/managing_scheduled_jobs.mdx
@@ -53,7 +53,7 @@ Use the Step Definition dialog box to define the step:
 
         -   To invoke a script on a Linux system, you must modify the entry for the `batch_script_user` parameter in the `agent.cfg` file and specify the user who runs the script. You can specify either a nonroot user or root for this parameter. If you don't specify a user or the specified user doesn't exist, then the script doesn't execute. Restart the agent after modifying the file.
 
-        -   To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to `true` and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent`.
+        -   To invoke a script on a Windows system, set the registry entry for `AllowBatchJobSteps` to `true` and restart the PEM agent. PEM registry entries are located in `HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent`.
 
 After providing all the information required by the step, select **Save**.
 

diff --git a/product_docs/docs/pem/9/managing_pem_agent/modifying_agent_configuration.mdx b/product_docs/docs/pem/9/managing_pem_agent/modifying_agent_configuration.mdx
@@ -50,7 +50,7 @@ On Linux systems, PEM configuration options are stored in the `agent.cfg` file,
 
 On 64-bit Windows systems, PEM registry entries are located in:
 
- `HKEY_LOCAL_MACHINE\Software\Wow6432Node\EnterpriseDB\PEM\agent`
+ `HKEY_LOCAL_MACHINE\Software\EnterpriseDB\PEM\agent`
 
 The registry contains the entries shown in the following table.