Support for Windows under Meraki Systems Manager is poor. Profiles (settings) that change device-specific settings (such as Wi-Fi SSIDs) cannot be pushed to a managed device unless the user who enrolled the device is logged in and has admin privilege...

Well, that's certainly an approach, and I can see how it would work. Rather defeats the purpose of bothering with an MDM, of course.It's not dissimilar to the way I run our macOS fleet, installing apps via Munki even though they're enrolled in Meraki...

The Meraki client service should be running in the background with admin privileges that allow it to make changes even when no user is logged in. Clearly this is possible, as any number of services run when there is no user logged in.If that's not po...

I'm also going to note that 'kudos' is singular, not plural, and does not refer to a countable quality; there is no such word as 'kudo'. In exactly the same way that you do not give someone a 'congratulation', you do not give someone a 'kudo'. But, a...

As noted elsewhere in this thread, that is precisely what Meraki have gotten wrong. There are settings on Windows that are device-specific, not user-specific, and these need to be pushed out regardless of who happens to be logged in at any given mome...