Renamed DataConnector

Solutions/WireX Network Forensics Platform/Data/Solution_WireXNetworkForensicsPlatform.json

@@ -5,7 +5,7 @@
   "Description": "The [WireX Systems](https://wirexsystems.com/) solution allows custom dashboards and workflows during forensic investigation integrated with Microsoft Sentinel.\n\r\n1. **WireX Network Forensics Platform via AMA** - This data connector helps in ingesting WireX Network Forensics Platform logs into your Log Analytics Workspace using the new Azure Monitor Agent. Learn more about ingesting using the new Azure Monitor Agent [here](https://learn.microsoft.com/azure/sentinel/connect-cef-ama). **Microsoft recommends using this Data Connector**.\n\r\n2. **WireX Network Forensics Platform via Legacy Agent** - This data connector helps in ingesting WireX Network Forensics Platform logs into your Log Analytics Workspace using the legacy Log Analytics agent.\n\n**NOTE:** Microsoft recommends installation of WireX Network Forensics Platform via AMA Connector. Legacy connector uses the Log Analytics agent which is about to be deprecated by **Aug 31, 2024,** and thus should only be installed where AMA is not supported. Using MMA and AMA on same machine can cause log duplication and extra ingestion cost [more details](https://learn.microsoft.com/en-us/azure/sentinel/ama-migrate).",
   "Data Connectors": [
 	"Solutions/WireX Network Forensics Platform/Data Connectors/WireXsystemsNFP(1b).json",
-	"Solutions/WireX Network Forensics Platform/Data Connectors/template_WireXsystemsNFP(1b).json"
+	"Solutions/WireX Network Forensics Platform/Data Connectors/template_WireXsystemsNFPAMA.json"
   ],
   "BasePath": "C:\\GitHub\\Azure-Sentinel",
   "Version": "3.0.0",

Solutions/WireX Network Forensics Platform/Package/mainTemplate.json

@@ -542,7 +542,7 @@
                               {
                                 "title": "Step A. Configure the Common Event Format (CEF) via AMA data connector",
                                 "description": "_Note:- CEF logs are collected only from Linux Agents_\n\n1. Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .\n\n2. Search for 'Common Event Format (CEF) via AMA' data connector and open it.\n\n3. Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule)\n\n\t_Note:- It is recommended to install minimum 1.27 version of AMA agent [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal ) and ensure there is no duplicate DCR as it can cause log duplicacy_\n\n4. Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine"
-
+                                
                               },
                               {
                                 "title": "Step B. Forward Common Event Format (CEF) logs to Syslog agent",
@@ -758,7 +758,7 @@
                       {
                         "title": "Step A. Configure the Common Event Format (CEF) via AMA data connector",
                         "description": "_Note:- CEF logs are collected only from Linux Agents_\n\n1. Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .\n\n2. Search for 'Common Event Format (CEF) via AMA' data connector and open it.\n\n3. Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule)\n\n\t_Note:- It is recommended to install minimum 1.27 version of AMA agent [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal ) and ensure there is no duplicate DCR as it can cause log duplicacy_\n\n4. Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine"
-
+                       
                       },
                       {
                         "title": "Step B. Forward Common Event Format (CEF) logs to Syslog agent",