everything working through groupid so far

Author: jtviolet

docs/ActivityMonitor/Config/DellCelerraVNX/Activity.md

@@ -25,17 +25,17 @@ Checklist Item 2: Install Dell CEE
   - Open MS-RPC ports between the Dell device and the Windows proxy server(s) where the Dell CEE is installed
   - Dell CEE 8.4.2 through Dell CEE 8.6.1 are not supported for use with the VCAPS feature
   - Dell CEE requires .NET Framework 3.5 to be installed on the Windows proxy server
-- See the [Install & Configure Dell CEE](/docs/activitymonitor/config/dellcelerravnx/installcee.md) topic for instructions.
+- See the [Install & Configure Dell CEE](/docs/activitymonitor/config/dellcelerravnx/InstallCEE.md) topic for instructions.
 
 Checklist Item 3: Dell Device Configuration
 
 - Configure the ```cepp.conf``` file on the Celerra VNX Cluster
-- See the [Connect Data Movers to the Dell CEE Server](/docs/activitymonitor/config/dellcelerravnx/installcee.md#connect-data-movers-to-the-dell-cee-server) topic for instructions.
+- See the [Connect Data Movers to the Dell CEE Server](/docs/activitymonitor/config/dellcelerravnx/InstallCEE.md#connect-data-movers-to-the-dell-cee-server) topic for instructions.
 
 Checklist Item 4: Activity Monitor Configuration
 
 - Deploy the Activity Monitor Activity Agent, preferably on the same server where Dell CEE is installed
 
-  - After activity agent deployment, configure the Dell CEE Options tab of the agent’s Properties window within the Activity Monitor Console
+  - After activity agent deployment, configure the Dell CEE Options tab of the agent's Properties window within the Activity Monitor Console
 
 Checklist Item 5: Configure Dell CEE to Forward Events to the Activity Agent

docs/ActivityMonitor/Config/DellCelerraVNX/InstallCEE.md

@@ -15,9 +15,9 @@ __Step 2 –__ Follow the instructions in the Dell [Using the Common Event Enabl
 - EMC Checker Service (Display Name: EMC CAVA)
 - EMC CEE Monitor (Display Name: EMC CEE Monitor)
 
-___RECOMMENDED:___ The latest version of .NET Framework and Dell CEE is recommended to use with the asynchronous bulk delivery (VCAPS) feature.
+___RECOMMENDED:___ The latest version of .NET Framework and Dell CEE is recommended to use with the asynchronous bulk delivery (VCAPS) feature.
 
-See the [CEE Debug Logs](/docs/activitymonitor/config/dellunity/validate.md#cee-debug-logs) section for information on troubleshooting issues related to Dell CEE.
+See the [CEE Debug Logs](/docs/activitymonitor/config/dellunity/Validate.md#cee-debug-logs) section for information on troubleshooting issues related to Dell CEE.
 
 After Dell CEE installation is complete, it is necessary to [Connect Data Movers to the Dell CEE Server](#Connect-Data-Movers-to-the-Dell-CEE-Server).
 
@@ -65,17 +65,17 @@ __NOTE:__ Do not use a # charter.
 
 __Step 2 –__ Create or retrieve the ```cepp.conf``` file.
 
-If there is not a ```cepp.conf``` file on the Data Mover(s), use a text editor to create a new blank file in the home directory named ```cepp.conf```. The following is an example command if using the text editor ‘vi’ to create a new blank file:
+If there is not a ```cepp.conf``` file on the Data Mover(s), use a text editor to create a new blank file in the home directory named ```cepp.conf```. The following is an example command if using the text editor 'vi' to create a new blank file:
 
 $ vi cepp.conf
 
 > If a ```cepp.conf``` file already exists, it can be retrieved from the Data Movers for modification with the following command:
 
-$ server\_file [DATA\_MOVER\_NAME] -get cepp.conf cepp.conf
+$ server_file [DATA_MOVER_NAME] -get cepp.conf cepp.conf
 
 __Step 3 –__ Configure the ```cepp.conf``` file. For information on the ```cepp.conf``` file, see the Dell [Using the Common Event Enabler for Windows Platforms](https://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/storage-3/docu48055.pdf) guide instructions on how to add parameters or edit the values or existing parameters.
 
-__NOTE:__ The information can be added to the file on one line or separate lines by using a space and a ”\” at the end of each line, except for the last line and the lines that contain global options: ```cifsserver```, ```surveytime```, ```ft```, and ```msrpcuser```.
+__NOTE:__ The information can be added to the file on one line or separate lines by using a space and a "\"" at the end of each line, except for the last line and the lines that contain global options: ```cifsserver```, ```surveytime```, ```ft```, and ```msrpcuser```.
 
 The Activity Monitor requires the following parameters to be set in the ```cepp.conf``` file:
 
@@ -95,19 +95,19 @@ The Activity Monitor requires the following parameters to be set in the ```cepp.
 
   msrpcuser=[DOMAIN\DOMAINUSER]
 
-  pool name=[POOL\_NAME] \
+  pool name=[POOL_NAME] \
 
-  servers=[IP\_ADDRESS1]|[IP\_ADDRESS2]|... \
+  servers=[IP_ADDRESS1]|[IP_ADDRESS2]|... \
 
   postevents=[EVENT1]|[EVENT2]|...
 
   Example cepp.conf file format for the Activity Monitor:
 
   msrpcuser=[DOMAIN\DOMAINUSER running CEE services]
 
-  pool name=[POOL\_NAME for configuration container] \
+  pool name=[POOL_NAME for configuration container] \
 
-  servers=[IP\_ADDRESS where CEE is installed]|... \
+  servers=[IP_ADDRESS where CEE is installed]|... \
 
   postevents=[EVENT1]|[EVENT2]|...
 
@@ -123,20 +123,20 @@ The Activity Monitor requires the following parameters to be set in the ```cepp.
 
 __Step 4 –__ Move the ```cepp.conf``` file to the Data Mover(s) root file system. Run the following command:
 
-$ server\_file [DATA\_MOVER\_NAME]‑put cepp.conf cepp.conf
+$ server_file [DATA_MOVER_NAME]‑put cepp.conf cepp.conf
 
 __NOTE:__ Each Data Mover which runs Celerra Event Publishing Agent (CEPA) must have a ```cepp.conf``` file, but each configuration file can specify different events.
 
 __Step 5 –__ (This step is required only if using the ```msrpcuser``` parameter) Register the MSRPC user (see Step 3 for additional information on this parameter). Before starting CEPA for the first time, the administrator must issue the following command from the Control Station and follow the prompts for entering information:
 
-/nas/sbin/server\_user server\_2 -add -md5 -passwd [DOMAIN\DOMAINUSER for msrpcuser]
+/nas/sbin/server_user server_2 -add -md5 -passwd [DOMAIN\DOMAINUSER for msrpcuser]
 
 __Step 6 –__ Start the CEPA facility on the Data Mover. Use the following command:
 
-server\_cepp [DATA\_MOVER\_NAME] -service –start
+server_cepp [DATA_MOVER_NAME] -service –start
 
 Then verify the CEPA status using the following command:
 
-server\_cepp [DATA\_MOVER\_NAME] -service –status
+server_cepp [DATA_MOVER_NAME] -service –status
 
 Once the ```cepp.config``` file has been configured, it is time to configure and enable monitoring with the Activity Monitor. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) for additional information.

docs/ActivityMonitor/Config/DellCelerraVNX/Validate.md

@@ -4,7 +4,7 @@ Once the Activity Monitor agent is configured to monitor the Dell device, the au
 
 ## Validate Dell CEE Registry Key Settings
 
-__NOTE:__ See the [Configure Dell Registry Key Settings](/docs/activitymonitor/config/dellunity/installcee.md#configure-dell-registry-key-settings) topic for information on manually setting the registry key.
+__NOTE:__ See the [Configure Dell Registry Key Settings](/docs/activitymonitor/config/dellunity/InstallCEE.md#configure-dell-registry-key-settings) topic for information on manually setting the registry key.
 
 After the Activity Monitor activity agent has been configured to monitor the Dell device, it will configure the Dell CEE automatically if it is installed on the same server as the agent. This needs to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on a different server than the Windows proxy server(s) where the Activity Monitor activity agent is deployed.
 

docs/ActivityMonitor/Config/DellPowerScale/Activity.md

@@ -21,7 +21,7 @@ Checklist Item 1: Plan Deployment
 
 ___RECOMMENDED:___ You can achieve higher throughput and fault tolerance by monitoring the Isilon/PowerScale cluster with more than one pair of Dell CEE and Activity Monitor Agent. The activity will be evenly distributed between the pairs.
 
-Checklist Item 2: [Install Dell CEE](/docs/activitymonitor/config/dellpowerscale/installcee.md)
+Checklist Item 2: [Install Dell CEE](/docs/activitymonitor/config/dellpowerscale/InstallCEE.md)
 
 - Dell CEE should be installed on a Windows or a Linux server.
 

docs/ActivityMonitor/Config/DellUnity/Activity.md

@@ -4,7 +4,7 @@ A Dell Unity device can be configured to audit Server Message Block (SMB) protoc
 
 If the service is turned off, a notification will be sent to the Dell CEE framework to turn off the associated Activity Monitor filter, but the policy will not be removed.
 
-The Dell CEE Framework uses a “push” mechanism so a notification is sent only to the activity agent when a transaction occurs. Daily activity log files are created only if activity is performed. No activity log file is created if there is no activity for the day.
+The Dell CEE Framework uses a "push" mechanism so a notification is sent only to the activity agent when a transaction occurs. Daily activity log files are created only if activity is performed. No activity log file is created if there is no activity for the day.
 
 Configuration Checklist
 
@@ -20,7 +20,7 @@ Checklist Item 1: Plan Deployment
 
     - [http://support.emc.com](http://support.emc.com/)
 
-Checklist Item 2: [Install Dell CEE](/docs/activitymonitor/config/dellunity/installcee.md)
+Checklist Item 2: [Install Dell CEE](/docs/activitymonitor/config/dellunity/InstallCEE.md)
 
 - Dell CEE should be installed on the Windows proxy server(s) where the Activity Monitor activity agent will be deployed
 
@@ -41,7 +41,7 @@ Checklist Item 4: Activity Monitor Configuration
 
 - Deploy the Activity Monitor activity agent to a Windows proxy server where Dell CEE was installed
 
-  - After activity agent deployment, configure the Dell CEE Options tab of the agent’s Properties window within the Activity Monitor Console
+  - After activity agent deployment, configure the Dell CEE Options tab of the agent's Properties window within the Activity Monitor Console
 
     - Automatically sets the Dell registry key settings
 
@@ -51,4 +51,4 @@ __NOTE:__ When Dell CEE is installed on Windows proxy server(s) where the Activi
 
 - Ensure the Dell CEE registry key has enabled set to 1 and has an EndPoint set to StealthAUDIT.
 - Ensure the Dell CAVA service and the Dell CEE Monitor service are running.
-- See the [Validate Setup](/docs/activitymonitor/config/dellunity/validate.md) topic for instructions.
+- See the [Validate Setup](/docs/activitymonitor/config/dellunity/Validate.md) topic for instructions.

docs/ActivityMonitor/Config/DellUnity/Validate.md

@@ -4,7 +4,7 @@ Once the Activity Monitor agent is configured to monitor the Dell device, the au
 
 ## Validate CEE Registry Key Settings
 
-__NOTE:__ See the [Configure Dell Registry Key Settings](/docs/activitymonitor/config/dellcelerravnx/installcee.md#configure-dell-registry-key-settings) topic for information on manually setting the registry key.
+__NOTE:__ See the [Configure Dell Registry Key Settings](/docs/activitymonitor/config/dellcelerravnx/InstallCEE.md#configure-dell-registry-key-settings) topic for information on manually setting the registry key.
 
 After the Activity Monitor activity agent has been configured to monitor the Dell device, it will configure the Dell CEE automatically if it is installed on the same server as the agent. This needs to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on a different server than the Windows proxy server(s) where the Activity Monitor activity agent is deployed.
 

docs/ActivityMonitor/activitymonitor/admin/agents/add/single.md

@@ -18,7 +18,7 @@ __Step 3 –__ On the Specify Port page, specify the port that should be used by
 
 __Step 4 –__ On the Credentials To Connect To The Server(s) page, select ether Windows or Linux file monitoring. Then, enter the __User name__ and __Password__ to connect to the API Server.
 
-[![Test Account Connection](/img/product_docs/activitymonitor/activitymonitor/admin/agents/add/testaccountconnection.png)](/docs/activitymonitor/resources/images/activitymonitor/manualinstall/single/testaccountconnection.png)
+![Test Account Connection](/img/product_docs/activitymonitor/activitymonitor/admin/agents/add/testaccountconnection.png)
 
 __Step 5 –__ Click __Connect__ to test the connection. If the connection is successful, click __Next__. If the connection is unsuccessful, see the status message that appears for information on the failed connection and correct the error to proceed.
 

docs/ActivityMonitor/activitymonitor/admin/monitoredhosts/add/dellcelerravnx.md

@@ -17,7 +17,7 @@ It also provides the ability to feed activity data to other Netwrix products:
 - Netwrix Threat Prevention
 - Netwrix Threat Manager
 
-Prior to adding a Dell Celerra or VNX host to the Activity Monitor, the prerequisites for the target environment must be met. See the [Dell Celerra & Dell VNX Activity Auditing Configuration](/docs/activitymonitor/config/dellcelerravnx/activity.md) topic for additional information.
+Prior to adding a Dell Celerra or VNX host to the Activity Monitor, the prerequisites for the target environment must be met. See the [Dell Celerra & Dell VNX Activity Auditing Configuration](/docs/activitymonitor/config/dellcelerravnx/Activity.md) topic for additional information.
 
 _Remember,_ the Activity Agent must be deployed to a Windows server that acts as a proxy for monitoring the target environment.
 
@@ -51,14 +51,14 @@ Click __Next__.
 
 ![Configure Basic Options Page](/img/product_docs/activitymonitor/activitymonitor/admin/monitoredhosts/add/configurebasicoptions.png)
 
-__Step 6 –__ On the Configure Basic Options page, choose which settings to enable. The “Log files” are the activity logs created by the activity agent on the proxy host. Select the desired options:
+__Step 6 –__ On the Configure Basic Options page, choose which settings to enable. The "Log files" are the activity logs created by the activity agent on the proxy host. Select the desired options:
 
 - Report account names – Adds an __Account Name__ column in the generated TSV files
-- Add C:\ to the beginning of the reported file paths – Adds ‘C:\” to file paths to be displayed like a Windows file path:
+- Add C:\ to the beginning of the reported file paths – Adds 'C:\" to file paths to be displayed like a Windows file path:
   - Display example if checked – C:\Folder\file.txt
   - Display example if unchecked – /Folder/file.text
 - Resolve UNC paths – Adds a __UNC Path__ column and a __Rename UNC Path__ column in the generated TSV files
-  - This option corresponds to the REPORT\_UNC\_PATH parameter in the INI file. It is disabled by default. The UNC Path is in the following format:
+  - This option corresponds to the REPORT_UNC_PATH parameter in the INI file. It is disabled by default. The UNC Path is in the following format:
     - For CIFS activity – \\[HOST]\[SHARE]\[PATH]
     - Example CIFS activity – \\ExampleHost\TestShare\DocTeam\Temp.txt
     - For NFS activity – [HOST]:/[VOLUME]/[PATH]
@@ -76,9 +76,9 @@ __Step 7 –__ On the Where To Log The Activity page, select whether to send the
 
 ![File Output Page](/img/product_docs/activitymonitor/activitymonitor/admin/monitoredhosts/add/fileoutputpage.png)
 
-__Step 8 –__ If __Log File__ is selected on the __Where To Log The Activity__ page, the __File Output__ page can be configured.
+__Step 8 –__ If __Log File__ is selected on the __Where To Log The Activity__ page, the __File Output__ page can be configured.
 
-- Specify output file path – Specify the file path where log files are saved. Click the ellipses button (__...__) to open the Windows Explorer to navigate to a folder destination. Click __Test__ to test if the path works.
+- Specify output file path – Specify the file path where log files are saved. Click the ellipses button (__...__) to open the Windows Explorer to navigate to a folder destination. Click __Test__ to test if the path works.
 - Period to keep Log files – Log files will be deleted after the period entered number of days entered. The default is 10 days. Use the dropdown to specify whether to keep the Log files for a set amount of Minutes, Hours, or Days.
 - This log file is for Access Analyzer – Enable this option to have Access Analyzer collect this monitored host configuration
 
@@ -87,14 +87,14 @@ __Step 8 –__ If __Log File__ is selected on the __Where To Log The Activity__
   - While the Activity Monitor can have multiple configurations per host, Access Analyzer can only read one of them.
 - Add header to Log files – Adds headers to TSV files. This is used to feed data into Splunk.
 
-Click __Next__.
+Click __Next__.
 
 ![Syslog Output Page](/img/product_docs/activitymonitor/activitymonitor/admin/monitoredhosts/add/syslogoutput.png)
 
 __Step 9 –__ If Syslog Server is selected on the __Where To Log The Activity__ page, the Syslog Output page can be configured.
 
 - Syslog server in SERVER[:PORT] format – Type the __Syslog server name__ with a SERVER:Port format in the text box.
-  - The server name can be short name, fully qualified name (FQDN), or IP Address, as long as the organization’s environment can resolve the name format used. The Event stream is the activity being monitored according to this configuration for the monitored host.
+  - The server name can be short name, fully qualified name (FQDN), or IP Address, as long as the organization's environment can resolve the name format used. The Event stream is the activity being monitored according to this configuration for the monitored host.
 - Syslog Protocol – Identify the __Syslog protocol__ to be used for the Event stream. The drop-down menu includes:
   - UDP
   - TCP
@@ -112,11 +112,11 @@ __Step 9 –__ If Syslog Server is selected on the __Where To Log The Activity__
   - Splunk – Use this template for Splunk integration
   - Threat Manager – Use this template for Threat Manager integration. This is the only supported template for Threat Manager. See the [Netwrix Threat Manager Documentation](https://helpcenter.netwrix.com/category/stealthdefend) for additional information.
   - Custom templates can be created. Select the desired template or create a new template by modifying an existing template within the Syslog Message Template window. The new message template will be named Custom.
-- Add C:\ to the beginning of the reported file paths – Adds ‘C:\” to file paths to be displayed like a Windows file path:
+- Add C:\ to the beginning of the reported file paths – Adds 'C:\" to file paths to be displayed like a Windows file path:
   - Display example if checked – C:\Folder\file.txt
   - Display example if unchecked – /Folder/file.text
 - Resolve UNC paths – Adds a __UNC Path__ column and a __Rename UNC Path__ column in the generated TSV files
-  - This option corresponds to the REPORT\_UNC\_PATH parameter in the INI file. It is disabled by default. The UNC Path is in the following format:
+  - This option corresponds to the REPORT_UNC_PATH parameter in the INI file. It is disabled by default. The UNC Path is in the following format:
     - For CIFS activity – \\[HOST]\[SHARE]\[PATH]
     - Example CIFS activity – \\ExampleHost\TestShare\DocTeam\Temp.txt
     - For NFS activity – [HOST]:/[VOLUME]/[PATH]
@@ -139,7 +139,7 @@ The added Dell Celerra or VNX host is displayed in the Monitored Hosts table. On
 
 ## Host Properties for Dell Celerra or VNX
 
-Configuration settings can be edited through the tabs in the host’s Properties window. The configurable host properties are:
+Configuration settings can be edited through the tabs in the host's Properties window. The configurable host properties are:
 
 - [Dell Tab](/docs/activitymonitor/activitymonitor/admin/monitoredhosts/properties/dell.md)
 - [Inactivity Alerts Tab](/docs/activitymonitor/activitymonitor/admin/monitoredhosts/properties/inactivityalerts.md)