topic Removing System Manager Windows Device Profile Remotely in Endpoint Security

Removing System Manager Windows Device Profile Remotely

wnofi — Fri, 08 May 2026 19:00:44 GMT

Now that SM is no longer supported, is there an easy way to remove the Windows device profile remotely, so my devices can join another MDM?

I can remove the SM Agent, not a problem. But the "Settings > Accounts > Access work or school" profile is not so easy to remove. Removing the devices from the SM dashboard does not do anything. The device enrollment profile still exists on the computer and prevents joining another MDM (Intune in this case).

The solution cannot be "log into each device and remove the account." Even though I'm looking at only 200 machines, it will still be a nightmare. I can't imagine if there were 500-1,000 or more.

Would be nice if Meraki could provide a tool to do this.

Re: Removing System Manager Windows Device Profile Remotely

Ken Stieers — Fri, 08 May 2026 19:21:49 GMT

So, I'm just spitballing because I don't have Meraki SM..

on a machine with it installed, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Search for "Meraki" or "SM Agent", or whatever other string makes sense.

You may find the uninstall string there, which will be something like "MsiExec.exe /X{guid}"

Try that from an elevated command prompt... if that works you can deploy it via whatever you do software deployments with.
That guid may be unique per version, so you may have to find all of those..

Re: Removing System Manager Windows Device Profile Remotely

wnofi — Mon, 11 May 2026 12:42:13 GMT

Hi Ken,

Thank you for the reply. I can remove the SM Agent via Powershell scripting, all good there.

It's the "Access work or school" -- "Enroll only in device management" profile that I need to remove remotely. It seems you have to go to every computer and do that manually. I'm trying to find a way to do that via a script or automation so I do not have to visit every device. The SM device management prevents enrolling in Intune, so it needs to be removed.