Resolving Host IP/Hostname Mismatch and Secure Baseline Scan Failures

If you're encountering "Host IP/Hostname mismatch" errors or "Secure Baseline Technology Error" messages when running Secure Baseline scans, this is typically caused by authentication issues when one agent attempts to scan multiple remote targets.

Solution: Use Agent Group Instead of Individual Agents

The most effective solution is to use Agent Group as your scanning target instead of selecting a specific individual agent. This allows each system with an installed agent to scan itself locally, eliminating the need for remote authentication between agents.

To configure this:

1. When creating or scheduling your Secure Baseline scan

2. Select Agent Group as the target option instead of choosing a specific agent

3. This will allow all targets with installed agents to perform self-scans

Why This Works

When you select a specific agent (like "ITADMIN2-PC-SA") to scan multiple targets, that agent needs administrative credentials to remotely access and scan other machines. Without proper credentials, the scan fails with hostname mismatch errors.

Using Agent Group eliminates this issue because:

• Each target scans itself locally using its own installed agent

• No remote authentication is required between machines

• All systems with agents can participate in the scan simultaneously

Alternative Solution: Configure Proper Credentials

If you prefer to use a single agent to scan multiple targets, ensure the scanning agent has proper administrative credentials configured. The agent must have valid username and password credentials that work on all target machines it will attempt to scan.

Important Notes

• Targets without installed agents cannot be included in Secure Baseline scans

• Agent-based scanning requires an agent to be installed on each target system

• If agents don't appear in the console after installation, verify the correct agent key is being used during installation