Can one admin manage 500 endpoints?

Your company just crossed 500 devices, and the IT department is still just you. Leadership assumes everything is fine because nothing has caught fire (yet). Meanwhile, you know about the postponed patches, the laptops waiting for reimaging, and the ticket queue that grows every time you take a lunch break.

So, can you manage 500 endpoints with one admin? Sometimes, but the endpoint count alone won't tell you. In this post, we'll look at what a 500-endpoint admin job involves, how to estimate the hours your environment needs, and when you can make a one-admin setup work.

What does managing a 500-endpoint fleet entail?

Here’s what you’d typically have to do when managing an ecosystem with 500 endpoints:

Patching

Microsoft releases Windows security updates on the second Tuesday of each month, plus out-of-band fixes when needed. Third-party apps follow their own schedules, and each failed install becomes a follow-up task.

Software deployment

New apps, upgrades, and removals have to reach the right devices. At 500 endpoints, installing by hand is almost never an option.

Help desk tickets

Users need help with passwords, printers, apps, and the occasional mystery error. Each ticket pulls you away from planned work.

Onboarding and offboarding

Each new hire needs a configured device and apps on day one. And whenever someone leaves, you must remove their access and handle their device according to your offboarding process. 

Device lifecycle

On a four-year refresh cycle, 500 devices means about 125 replacements a year, or 2 to 3 a week. Each one needs setup, and you also have to securely retire the old device.

Inventory and security

You need to know what runs on each device and which devices are the most vulnerable to exploits. Auditors and cyber insurers may ask you to prove it.

Everything that isn't an endpoint

In a one-admin shop, the same person usually also handles servers, the network, SaaS apps, backups, and vendors. 

How can you estimate your team's needs?

You should estimate your needs by adding up the hours your environment requires each week, not by counting the number of devices.

Here's a quick checklist you can use:

1. Pick the responsibilities that apply. Start with the table below, and add anything unique to your environment.

2. Estimate the weekly hours for each. Use real data where you can (e.g., from your project management tool), such as ticket counts and deployment history.

3. Add a buffer. Add about 20% for outages and unplanned work.

4. Divide by realistic admin hours. Meetings, vacations, and sick days reduce the hours available for work each week, so use a number below 40, such as 30.

These numbers are only an example, not a benchmark. In this case, 43 hours plus a 20% buffer comes to about 52 hours a week. Divided by 30, that's about 1.7 admins.

Here's how to read your own result:

• 1 or less: One admin can probably cover the work.

• Between 1 and 1.5: One admin may be able to get by, but only with strong IT automation or help from other teams, like developers who handle scripting or cloud servers. 

• More than 1.5: Plan for a second admin or a managed service provider (MSP). 

When to have a one-admin setup (and when not to)

A one-admin setup can work if:

• The fleet is standardized, with a few hardware models and a common set of apps

• Patching, software deployment, and reporting run on their own

• Ticket volume is low, and users can reset their own passwords

• An MSP or a parent company covers networking, servers, or security

• Leadership accepts realistic response times, like the next business day for nonurgent issues

A one-admin setup will likely fail if:

• The admin is also the help desk, network team, security team, and project manager

• Leadership expects instant responses or round-the-clock support

• The fleet mixes many hardware models, OS versions, and line-of-business apps

• Patching, imaging, and deployments happen by hand

• Only one person knows the admin credentials, so one sick day stalls IT

Read more: How to run IT with limited staff

Final thoughts

Can you manage 500 endpoints with one admin? In some environments, yes. But in many cases, the sysadmin workload can outgrow one person before the endpoint count suggests it should. Ticket volume, service expectations, fleet complexity, and tool quality decide the answer.

If manual patching and deployments fill most of your week, PDQ can automate much of that work. Try PDQ free for 14 days to see how many hours you get back.