EclipseRMM green eclipse symbolEclipseRMM

FIELD NOTES / RMM FUNDAMENTALS

Windows RMM: Managing Windows Endpoints With or Without a Domain

A Windows RMM (remote monitoring and management tool for Windows) puts a small agent on each Windows PC or server, and that agent reports to a central portal where you see which devices are online and run administrative work on them. Unlike Group Policy, it doesn't depend on Active Directory, so RMM for Windows is often how IT teams and MSPs manage workgroup PCs, small-office machines and laptops that never join a domain. This guide explains what a Windows RMM does, how it compares with the domain tools and PowerShell remoting, and what to check before you choose one.

What a Windows RMM actually does

Strip away the feature lists and an RMM for Windows does three jobs:

Many products add more on top: patching, alerting rules, remote desktop, ticketing, backup. Those extras are where products differ most and where prices climb, so it helps to decide which of them you really need before comparing tools. If you're new to the agent model, start with what an RMM agent is and how it works.

Domain vs workgroup: why it changes how you manage Windows

Windows computers are either joined to a domain or part of a workgroup. The difference decides which built-in management tools are available.

On a domain: Group Policy does a lot of the work

Microsoft describes Group Policy as "a feature of Windows that provides centralized management and configuration of operating systems, applications, and user settings". In a domain, Group Policy Objects are stored in Active Directory and linked to sites, domains and organizational units, and computers pick up their settings at startup and on periodic background refresh. That is powerful for configuration, but it assumes every computer is a domain member and can reach a domain controller.

In a workgroup: no central directory

Workgroup PCs have no domain to pull policy from. Microsoft notes that Group Policy settings can also be stored locally and edited with the Local Group Policy Editor (gpedit.msc), but that is a per-computer setting, not central management. Small offices, home workers and many MSP customers run exactly like this: a handful of PCs, a router, and no server. Checking which situation you're in is a read-only one-liner:

# Read-only: is this computer in a domain or a workgroup?
Get-CimInstance -ClassName Win32_ComputerSystem |
    Format-List Name, PartOfDomain, Domain, Workgroup, DomainRole

According to Microsoft's Win32_ComputerSystem reference, PartOfDomain is True on a domain member, and when the computer is not part of a domain the Domain property returns the workgroup name. A DomainRole of 0 means "Standalone Workstation" and 1 means "Member Workstation".

Managing workgroup PCs with PowerShell remoting: what it takes

PowerShell remoting works without a domain, but Microsoft's troubleshooting guide lists extra requirements when the computer you connect from isn't in a domain:

The reason is authentication. WinRM's own error message says that if the authentication scheme is not Kerberos, or the client computer is not joined to a domain, HTTPS must be used or the target must be in TrustedHosts. Kerberos also doesn't support IP addresses, so connecting by IP address uses NTLM and has the same requirements. Microsoft also cautions that the TrustedHosts value affects all users of the computer. On top of that, the WinRM service is disabled by default on client versions of Windows, and on client Windows Enable-PSRemoting fails on public networks by default unless you use -SkipNetworkProfileCheck, which then only allows the same local subnet.

# Read-only: what is in TrustedHosts on this computer today?
Get-Item WSMan:\localhost\Client\TrustedHosts

None of this is wrong; it's how WinRM is designed. But it adds up quickly when the PCs are spread across several small offices, sit behind different routers, or are laptops that move between networks. Remoting also needs the target to be reachable from where you are. We cover the remoting route in detail in PowerShell remote management without RDP.

How agent-based Windows RMM avoids the domain question

With an agent-based RMM, each Windows device runs a service that checks in with the RMM portal. You don't open a connection to the PC yourself; the agent reports to the service with authenticated heartbeats, and the work you authorize in the portal is carried out by that agent. Enrollment is done per device, so domain membership isn't part of the model.

Here is how that works in EclipseRMM, using only what the product pages state:

Windows RMM vs Group Policy vs PowerShell remoting

These tools overlap but aren't substitutes. A quick comparison of how each one relates to domains, based on the Microsoft documentation cited below and EclipseRMM's product pages:

QuestionGroup Policy (domain)PowerShell remoting (WinRM)Agent-based RMM
Needs a domain?Central GPOs live in Active Directory; workgroup PCs only have local policyNo, but workgroups need HTTPS or TrustedHosts plus explicit credentialsNo domain join in the enrollment model described above
Who starts the connection?The computer applies policy at startup and on refreshYour computer connects to the targetThe agent on the device checks in with the portal
Best atEnforcing configuration across domain membersAd-hoc commands on reachable machinesSeeing and administering devices spread across many sites
Shows if a device is offline?NoOnly when a connection failsYes, from heartbeats and last-seen time

Plenty of teams use more than one. A domain can keep Group Policy for configuration and still use an RMM to see every device, including the laptops and branch PCs that aren't domain-joined.

What to check before choosing a Windows RMM

FAQ

Can I manage Windows PCs remotely without a domain?

Yes. PowerShell remoting works in workgroups once you configure HTTPS or TrustedHosts and pass credentials, and an agent-based Windows RMM enrolls each device directly, without a domain join.

Is a Windows RMM a replacement for Group Policy?

Not exactly. Group Policy enforces configuration on domain members. An RMM gives you visibility and remote administration across devices, domain-joined or not. Many teams run both.

Does a Windows RMM need inbound firewall rules on each PC?

That depends on the product, so ask the vendor. In the agent model, the device's agent checks in with the service, which is different from WinRM, where your computer connects to a listener on the target.

Does EclipseRMM include remote desktop?

No. EclipseRMM focuses on PowerShell administration and device connectivity. Use a separate remote-support product for screen sharing.