Mac and Linux Operations
Requirements to Scan and Patch Linux Mac/Linux Scanning problems Mac/Linux Remediation issues
- How to delete the .\gfi_temp hidden folder
- Scan produces credential errors, but the credentials used are correct
- 'Missing patches scan; Yum package manager failed' Error When Scanning CentOS 8 or RHEL 8 For Missing Patches
- Resolving Detection Issues when Scanning MacBook
- Resolving "Missing one of the required utilities: Expect or GDB or diff" Errors while Scanning Linux computer
- Guiding on Using LanGuard for Linux Servers Updates
- Resolving the Linux Systems Scanning 'Apt Package Manager Failed' Error
- Resolving the error "Could no connect to SSH" with failing Linux scanning and patch remediation
- Creating a New Scanning Profile for Linux Machines To Avoid Being Stuck and Getting Timeouts / Irrelevant Errors During a Scan
- Troubleshooting Linux Scanning and Patch Deployment
- A full UDP scan to a Linux machine does not complete, or is done very slowly
- Basic Linux Troubleshooting Commands
- Error: ‘Access Is Denied. Check This for More Details’ When Scanning a Linux Computer
- Remediation Jobs Error: Installer: Must Be Run as Root to Install This Package
- Mac Scanning Error: 'Mac OS X Tool 'Softwareupdate' Failed and Returned 'Softwareupdate: Must Be Run as Root (102)'
- Unable to Scan or Deploy Missing Patches to Mac OS X Computers
- Enabling SSH Daemon in Mac OS X
- Why does LanGuard Display Errors When Scanning Linux or Mac Systems via SSH?
- What are the Requirements to Scan and Patch Linux Computers with LanGuard?
- What are the Requirements to Scan and Patch macOS Computers with LanGuard?
- Why do Linux or MAC scans not list installed updates / patches?
- Linux and macOS Scanning and Remediation Operations Overview
- macOS Versions Supported in GFI LanGuard
- Why are Mac Scans Failing with 'Error connecting to SSH: 10061'?