Turn on network mapping

What you will have

• Find the switch and read what it says about itself before touching it.
• Turn network mapping on and see what changes on the page.
• See the excluded clients list and know what it is for.
• Find the one per-client exception, on the client's own RMM tab, and read its three-line status honestly.
• Turn the switch back off and know what stops and what stays.

Why it works this way

Steps

1. 1

   Open Settings > RMM > Network Mapping.

   Its own settings page, listed under RMM in the left settings rail alongside Device Approval. The page heading and its own summary line read exactly: "One switch arms network mapping collection for every client. Off by default fleet-wide; exclude a rare client from its own settings."

   

2. 2

   Read the switch before touching it.

   It starts off, and the page says so in two places: the toggle itself, and the line under it, "Off - no client is being mapped." The panel's own helper text says what turning it on does: "One switch arms passive local topology reads plus a bounded local-subnet discovery sweep for every client. Off by default fleet-wide." In plain words: every client's agents would start sending what their own machine already knows about the network it sits on (its subnets, its route table, the neighbors in its ARP cache) plus a bounded scan of its own local subnet only, never anything past that bound. Those readings are what builds the picture on RMM > Network Map, covered by a future page once a device is enrolled to show it. This is new, so off is the safe starting point, and this is a new instance where nothing has been turned on yet.

   

3. 3

   Turn the switch on.

   One click, no confirmation step, applies instantly. The toggle turns on and the line under it becomes a count: this tenant showed "9 of 9 clients mapped" the moment it flipped, because every client on the roster is armed at once, not one at a time. New clients created later are armed too, automatically, from the moment they exist. A toast confirms the flip ("Network mapping turned on for the fleet"), and the flip also writes one row to Settings > Logs > Audit named netmap.global_flip, with the same count.

   

4. 4

   See the Excluded clients panel underneath.

   Its own card, right below the switch, titled Excluded clients. On a tenant where nobody has been excluded yet it reads plainly: "No client is excluded." This list is where a client shows up once it is excluded on its own RMM tab (the next step), each with an Un-exclude button to bring it straight back in. This panel only ever narrows who the switch reaches; it is never a second way to turn the whole thing off.

   

5. 5

   Open Clients, pick a client, then its RMM tab, for the one exception.

   A card near the top of the tab, titled Exclude from network mapping, with its own helper line: "This client follows the fleet-wide network mapping switch unless excluded here." Its own status line spells out exactly where this one client stands right now: with the fleet switch on and this checkbox still off, it read "Currently mapped (the fleet-wide switch is on)." Turning this one checkbox on takes this client's devices out while every other client keeps collecting; turning it back off returns the client to following the fleet switch again. This is an ordinary edit permission on the client, not the owner-level permission the fleet switch itself needs. The account used through this whole walk is a plain Staff account (shown top right), and it could flip this checkbox the same as it read every other frame on this page - Owner access was never required for it.

   

6. 6

   Turn the switch back off to close the loop.

   The same one click, no confirmation, back on the Network Mapping settings page. The line underneath returns to "Off - no client is being mapped," a second netmap.global_flip row lands in the audit log with a count of zero, and a toast confirms it ("Network mapping turned off for the fleet"). Collection itself does not stop the instant the switch flips; it stops for each client at that client's agents' next check-in. Whatever a device already reported stays on its map until it ages out, so the map keeps telling the truth about when it last actually saw something instead of going blank the moment the switch turns off. Turning the switch back on later picks collection straight back up for every client that is not excluded.

   

Other ways to do this

If it did not work

• If the toggle will not stay on, or reverts, check the account's own tier: this switch needs owner-level access (the same ceiling as deleting an RMM record), not ordinary edit access. The per-client exclude checkbox on a client's RMM tab needs only ordinary edit access on that client, so a Tech who cannot touch the fleet switch can still exclude their own client.
• If a client is not being mapped even though the fleet switch is on, check that client's own RMM tab for the Exclude from network mapping checkbox. If it is on, that one client is the exception; every other client keeps collecting.
• If the fleet switch is off, a client's own exclude checkbox does nothing either way: nobody is mapped while the switch is off, no matter how that checkbox is set.

Questions this page answers