Services Manager Windows: failing Windows services, IIS and containers

Services Manager Windows investigates failing Windows services, IIS sites and containers on Windows hosts, restores them and leaves account and security changes to you.

REQUEST DEMO

READ THE DOCS

Services Manager Windows is the 2501 specialty for services on Windows hosts: Windows services, IIS sites and containers. It finds why a service stopped or will not start, restores it and confirms it is healthy, within limits you set.

A Windows service stops, and the event log says so but rarely why. The cause might be a port already in use, a permission, or the service account itself, with an expired password or a locked account. Restarting all of IIS to fix one site takes every other site down too.

What 2501 does

Services Manager Windows investigates before it changes anything, from the service's settings, account and event logs to IIS sites and application pools. It names the cause, citing the Windows events behind it, restarts only the service, site or application pool concerned, or corrects an obvious configuration error, and confirms it is healthy. Service account problems that need work in Active Directory can be handed to the agent that covers it, as can a full disk.

Scope map of 2501's Services Manager Windows: it restarts only the failing IIS site or application pool, restarts the failing Windows service or corrects an obvious configuration error, cites the event logs, reads service accounts and hands Active Directory work or a full disk to the agent that covers it; account and security changes and bigger configuration changes go to a person, and it never resets all of IIS, restarts the server or switches off its security tools.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Account and security changes wait for a person: resetting a service account password, changing Active Directory permissions, configuration beyond a simple fix, and anything that looks like a security incident.
Some things are off limits: it never restarts the server, resets all of IIS at once or switches off security tools such as Windows Defender, and blacklisted commands and hosts stay out of reach.

Frequently asked

How is it different from the other service specialties? Services Manager and Services Manager Linux cover systemd services and containers on Linux, while Services Manager Windows covers Windows hosts, including IIS and service accounts.

Can it diagnose without restarting anything? Yes. In investigate-only mode it reports the cause and the fix it would make, and changes nothing.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

An IIS application pool that keeps stopping runs again beside the other sites after 2501 finds the cause, fixes it and restarts only that pool, never resetting all of IIS

Problem

IIS application pool keeps stopping

A site is down because its IIS application pool keeps stopping. How 2501 finds out why and restarts only that pool, never all of IIS, within limits you set.

See how it is handled

Services Manager Windows: failing Windows services, IIS and containers

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE