First Server Setup

This guide provides a detailed walkthrough of connecting your first server to PatchCTL, including verification steps and initial configuration.

Before You Begin

Ensure you have:

• Completed the Quick Start Guide or have the agent installed
• Your server appearing in the PatchCTL dashboard

Understanding the Initial Scan

When a new agent connects, it performs several operations:

1. System identification - Hostname, IP, OS version, hardware specs
2. Package scan - Full inventory of installed packages
3. Update check - Available updates from configured repositories
4. CVE correlation - Matching packages against known vulnerabilities

This initial scan typically completes within 2-5 minutes.

Verifying Server Data

Basic Information

In the dashboard, click on your server to view its details:

Field	Description
Hostname	Server's hostname
IP Address	Primary network interface IP
OS	Distribution and version
Kernel	Running kernel version
Agent Version	Installed PatchCTL agent version
Last Seen	Time since last heartbeat

Hardware Information

The agent collects system specifications:

• CPU - Model and core count
• RAM - Total and available memory
• Disk - Root filesystem usage

Package Information

Navigate to the Packages tab to see:

• Total installed packages
• Packages with available updates
• Security updates available

Configuring Server Tags

Tags help organize your fleet for targeting schedules and filters.

Adding Environment Tags

1. Click Edit on the server details page
2. Select an Environment:
   • production
   • staging
   • development
   • testing

Adding Custom Tags

1. Click Add Tag
2. Enter a tag name (e.g., web-server, database, us-east)
3. Click Save

Tag Strategy

Use consistent tag naming across your fleet. Common patterns:

• Role: web, db, cache, worker
• Location: us-east, eu-west, datacenter-1
• Team: platform, security, data

Running Your First Patch

Manual Patch (Single Server)

1. From the server details page, click Actions → Install Updates
2. Review the list of available updates
3. Choose update type:
   • All updates - Install everything available
   • Security only - Only security-related packages
4. Click Install
5. Monitor progress in the Activity tab

Viewing Patch Results

After patching completes:

1. Check the Activity tab for the operation status
2. View Packages tab to confirm updates applied
3. Note if a reboot is required (kernel updates, etc.)

Next Steps

With your first server connected and verified:

1. Add more servers - Scale your fleet
2. Create schedules - Automate patching
3. Review CVEs - Prioritize vulnerabilities
4. Invite team members - Collaborate on patch management

Common Questions

How often does the agent check in?

The agent sends a heartbeat every 5 minutes and performs a full package scan every 6 hours.

Can I force an immediate scan?

Yes. From the server details page, click Actions → Refresh to trigger an immediate heartbeat and package scan.

What data is sent to PatchCTL?

The agent sends:

• System identification (hostname, IP, OS)
• Hardware specs (CPU, RAM, disk)
• Installed packages and versions
• Available updates

The agent does not send:

• File contents
• User data
• Network traffic
• Command output (beyond patch results)