FAQ - All platforms

Client Accounts (Status & Visibility)

Applies to: Medulla – Agents
Version:5.4.3 or later
Environment: On-Premise - Shared SaaS and Private SaaS
Category: Support

Why do some endpoints appear offline even though they are powered on?
Why are the inventory reports or reported information incomplete or incorrect?

Packages

Medulla Modules Packages / All versions / Public and private SaaS and On-premise / Maintenance

I can't add a file to my package.
I created a package but it’s not available for deployment—why?
Why isn’t my package available on the Kiosk package addition page?

Console & Administration

Medulla / All versions / Public and private SaaS and On-premise / Maintenance

Why is the console slow, unstable, or inaccessible?
How do I resolve user permission issues?
Why don’t I have access to certain groups, audits, or scheduled tasks?
What should I do if the console freezes or I encounter XMPP errors?

Remote Maintenance & Getting Started

Medulla Modules Computers / All versions / Public and private SaaS and On-premise / Maintenance

What to do if remote access (VNC/RDP/PMAD) isn't working?

Set the agent to Debug

Medulla / All versions / Public and private SaaS and On-premise / Maintenance

Setting the agent toDEBUG mode couldn’t be simpler.

Go to the agentconf.ini file located at: C:\Program Files\Medulla\etc\agentconf.ini

In the [global] section

Windows Agent Issue

Medulla / All versions / Public and private SaaS and On-premise / Maintenance

Is your issue related to an interaction betweenMedulla and a Windows workstation (agent not reporting, actions not applied, workstation not visible, etc.)?

To facilitate troubleshooting, Medulla provides a verification script that allows you to check network connectivity, the agent’s status, and the workstation’s configuration.

Download the script:
https://dl.medulla-tech.io/nc/windows_connection_check_signed.ps1

(right-click on the link below, then click "Save link as...")

Test Prerequisites

Before you begin, make sure you have downloaded the script above and prepared the machines.

On the Windows client machine with the Medulla agent:

image.png

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

# Answer "Yes for all" (Y or T) if prompted

For PowerShell v7.5.4: 

There is no need to unblock the script. You must run the command shown above.

It will ask if you want to allow the publisher of the script; simply confirm by clicking R or A.

image.png

Medulla Server Test <- Windows Client Workstation

Verify direct communication between the server and the client workstations.

On the Client Workstation (Source): Run the test against the server’s hostname or IP address.

.\windows_connection_check_signed.ps1 -Target <SERVER_IP> -Mode pulse

A log file is created (in the location from which you run the script) and summarizes the tests performed: LOG_Test_Flux.txt

If you encounter permission errors when creating the log file, try placing the script in the user’s Downloads folder, or grant the windows_connection_check.ps1 script permission to create a file in that location.

Medulla On-Premise

If you have a Medulla On-Premise server, you can also run a server diagnostic test from the workstation:

On the Medulla Server (Source): Run the test against the workstation’s hostname or IP address.

./medulla_connection_check.sh -c client.example.com

Recommendation: Please attach the LOG_Test_Flux.txt file when submitting a support request.