With many integrations, there's two options:   PULL: Where the data is PULLED from Meraki, using the APIs PUSH: where, using web hooks, syslog, data is pushed from Meraki   The Splunk integration appears to be a PULL integration, according to the APIs that it uses: https://api.meraki.com/api/v1/organizations/:org/devices/statuses/ https://api.meraki.com/api/v1/organizations/:org/uplinks/statuses/ https://api.meraki.com/api/v1/organizations/:org/devices/uplinksLossAndLatency https://api.meraki.com/api/v1/organizations/:org/networks https://api.meraki.com/api/v1/networks/:network/devices   I note that the SM endpoints are not included in there   HOWEVER, whilst not impossible, there's a little work for you to do. It looks like Splunk can ingest data using any REST based API:   https://www.splunk.com/en_us/blog/tips-and-tricks/getting-data-from-your-rest-apis-into-splunk.html   And this starts with a simple form to fill in:       Don't forget that Meraki uses a custom parameter for Auth,  X-Cisco-Meraki-API-Key: <secret key> Which should go into your headers.   Let me know how you get on....   ... View more

An old thread, but people here may be interested in recently upgraded support for Bitlocker in Systems Manager, from Windows 10 v1803 onwards:   https://documentation.meraki.com/SM/Apps_and_Software/Windows_BitLocker_Encryption_with_Meraki_Systems_Manager ... View more

We usually create our admin local user and then run our own script to install custom tools and for creating the user’s profile before handing the device to the user.   caribou ... View more

I've generally found creating a case through the portal first, then calling in with an existing ticket helps with my hold times, not sure if just by chance, or if since it is an existing case it gets higher priority.  I did sit on hold for 45 minutes recently as noted here, was the longest I've ever had to wait, and of course, the flaky network issue I needed help with had long since passed. ... View more

AWESOME!!!! ... View more

Hi Phil~ I definitely feel your pain on this one!  The KEXT issues that have come with the added security of 10.13.4 do have a viable workaround (albeit a manual one): create .mobileconfig payloads that are delivered as profiles to the macbooks.  You could have individual ones or keep a master list.     Short Version: 1. Create a apple profile / .mobileconfig file that allows the application 2. In Meraki Go to  System Manager > MDM Settings > Add Profile  > Upload custom Apple profile   For details on step 1 and some excellent info from user sshort, go to this thread: https://community.meraki.com/t5/Endpoint-Management-Systems/whitelisting-kernel-extensions-via-team-id-s/m-p/21446#M2437  edit:  I see that you ran into that thread. I do agree that this shouldn't have to be a "thing".  It's taking a bit of time for developers to catch up to these added securities at the kernel level.  I will kudos your post for sure.   ... View more

Update: I have raised a case and they were unable to replicate the issue on their end. To proof there was a issue I got a brand new out of the box machine and screen-captured the computer to show me install the certificate and then showed how it was automatically removed in 15 minutes. Still waiting for someone to get back to me about it, but it seems like they don't know what is causing it. ... View more

Thanks guys for the info, much appreciated. ... View more

I'd love if this was a feature too, could we feature request this? ... View more