Windows:

Error: Script requires Administrator privileges

1. Issue

The script fails to run because the current PowerShell session lacks elevated permissions.

Error Screenshot:

Error Message:

The current Windows PowerShell session is not running as Administrator.

2. Solution

You must Run PowerShell As an Administrator:

1. Open the Start Menu and type "PowerShell".
2. Right-click on Windows PowerShell.
3. Select "Run as administrator" (as shown in the image below).

Step Screenshot:

1. Once the new window opens, navigate to your folder and re-run the script:

.\install-cognna-sensors-av.ps1 -f .\client.config.yaml -e <YOUR_ENROLLMENT_KEY>

-----------------------------------------------------------------------------------

Error: No such file or directory (Wrong Path)

1. Issue

The system cannot find the installation script because the terminal is not pointed to the folder where the files are located.

Error Screenshot:

Error Message:

The term './install-cognna-sensors-av.ps1' is not recognaized

2. Solution

You must change your directory to the exact location of COGNNA files.

Step 1: Locate the folder path Open your file explorer, go to the folder containing the scripts, and copy the path from the address bar.

Step 2: Use the cd command In your PowerShell, type cd followed by the path: cd <path_to_your_folder>

Success Screenshot:

-----------------------------------------------------------------------------------

Error: Running Scripts is Disabled on this System

1. Issue

When trying to run the script on Windows, PowerShell returns a red error stating that scripts cannot be loaded because running scripts is disabled.

Error Screenshot:

Error Message:

...cannot be loaded because running scripts is disabled on this system.

2. Solution

You need to change the execution policy to allow the script to run.

Step 1: Open PowerShell as Administrator.

Step 2: Run the following command:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process

Step 3: Confirm the change. When prompted, type A (Yes to All) and press Enter.

Step 4: Run the installation script again.

Success Screenshot:

-----------------------------------------------------------------------------------

Error: Handling Spaces in Folder Paths

1. Issue

When trying to use the cd command with a folder name that contains spaces (e.g., New folder), PowerShell returns an error:

A positional parameter cannot be found that accepts argument 'folder'.

Error Screenshot:

2.Solution

PowerShell treat a Space as a separator between different commands. If the path is not enclosed in quotes, the system thinks "New" is the path and "folder" is a separate, unknown command.

Always wrap your path in double quotes (" ") if it contains any spaces.

Success Screenshot:

-----------------------------------------------------------------------------------

Linux:

Error: This script must run as root

1. Issue

The installation fails immediately with a clear message stating that root privileges are required.

Error Screenshot:

Error String: This script must be run as root.

2. Solution

You can resolve this by using sudo or switching to the root user:

Simply add sudo at the beginning of your command to run it with root rights:

sudo ./install-cognna-sensors-av.sh -f client.config.yaml -e <YOUR_ENROLLMENT_KEY>

Success Screenshot:

-----------------------------------------------------------------------------------

Error: No such file or directory: install-cognna-sensors-av.sh

1. Issue

When trying to run the installation command, the terminal returns an error stating the file or directory does not exist.

Error Screenshot:

Error String: zsh: no such file or directory: ./install-cognna-sensors-av.sh

2. Solution

You need to navigate to the correct folder where COGNNA’s files extracted.

Step 1: Move to the correct directory cd <path_to_your_directory>

Step 2: Run the installation again ./install-cognna-sensors-av.sh -f client.config.yaml -e <YOUR_ENROLLMENT_KEY>

Success Screenshot:

-----------------------------------------------------------------------------------

Error: Permission Denied: install-cognna-sensors-av.sh

1. Issue

When attempting to run the installation script, you receive a "Permission denied" message in your terminal.

Error Screenshot:

Error String: zsh: permission denied: ./install-cognna-sensors-av.sh

2. Solution

Run the following command to make the file executable:

chmod +x install-cognna-sensors-av.sh

Next Step: Now, re-run your installation command. It should start successfully as shown below:

Success Screenshot:

-----------------------------------------------------------------------------------

Platform FAQ:

Not Receiving Weekly/Monthly Reports?
If you are not receiving your scheduled summary reports, please check your Notification Preferences to ensure they match the configuration shown below:

1. Enable Frequency for Each Report
To receive a report, you must manually select a frequency (Weekly or Monthly) for each specific report type:

• Threat Detections Summary
• Endpoints Monitoring Summary
• Threat Intelligence Hunts Summary
• Case Management Summary

2.Using "Combine All Summary Reports"
If you have enabled "Combine all summary reports", the system will consolidate everything into one single Report.

Important: Ensure the frequency (Weekly/Monthly) selected for the "Combined" option matches your expectations. If you select "Monthly" here, you will only get one email per month, even if individual reports are set to weekly.

3.Understanding the Delivery Schedule
The system follows a strict automated schedule. You will not receive an email immediately after clicking save.

• Weekly Reports: Sent every Sunday morning.
• Data Window: Each report includes all activity captured during the previous 7 days.
• First Delivery: If you activate your reports on a Tuesday, your first report will arrive the following Sunday.

💡 Quick Tip: For a cleaner inbox, we recommend checking "Combine all summary reports" and selecting Weekly to get a single, comprehensive update every Sunday.

-----------------------------------------------------------------------------------

How to Delete Assets from the Platform

If you are unable to remove an asset, please ensure you follow these mandatory steps and requirements:

1. Agent Uninstallation First

You must first uninstall the agent from the physical machine or server. The platform will not allow the deletion of an asset that is still actively communicating with the system.

2. Status Requirement

Assets can only be deleted once their status changes to "Inactive" on the dashboard. If the asset is still showing as "Fully Monitored" or "Active," the deletion option will remain unavailable.

3. Owner Permissions

The "Mark as Deleted" function is restricted. Only the Account Owner has the authorization to permanently remove assets from the organization settings.

4. Final Selection Process

Once the asset is inactive and you have the correct permissions:

• Select the specific assets from the list using the checkboxes.
• Click the "Mark as Deleted" button located at the top right of the table (as shown in the image).

-----------------------------------------------------------------------------------

How to switch Default Owner user

To change the Default Owner of the organization, the current Owner must perform the transfer manually through the settings.

Accessing User Management:

The current Owner must navigate to Home > Settings > Manage Users.

Locating the Transfer Option:

In the user list, find the name of the user who will become the new owner.

Action Button: Next to the user's name (under the "Actions" column), click the Transfer Ownership icon.

Required Permissions: Only the user currently assigned the "Owner" role has the authority to promote another user to that same role.

Finalizing: Once the transfer is confirmed, the new user will gain full administrative control, and the previous owner's role will be downgraded accordingly.

-----------------------------------------------------------------------------------

Not receiving OTP.

1- OTP Not Received in Outlook – Check Junk Folder via Browser

User reports that the OTP (verification code) was not received.
User is accessing email via Microsoft Outlook application (Desktop or Mobile).

Root Cause
The OTP email was delivered to the Junk/Spam folder.
Outlook application did not properly sync or display the Junk folder.

Solution

1. Ask the user to access their email via web browser (not the Outlook app).
2. Log in to Outlook Web.
3. Check the Junk/Spam folder.
4. Mark the OTP email as “Not Junk”.
5. Request a new OTP.