I also have a ticket open with support on this, since Feb 10. They have confirmed it as a known issue. It wasn't a big deal until this weekend when Apply announced a vulnerability that is being exploited in the wild. Hopefully this issue will light a fire under the development team and they will get this fixed.   Kudos @Shany for the idea of resetting the delay to 1 day to work around the problem! ... View more

I'm in!   wperry1 ... View more

I'm a little embarrassed I didn't think of that. I tried a colon, semicolon, and space (%20). It didn't occur to me to use a comma.   Thanks for your help. ... View more

Thanks @jm_peterson I thought about using tags, unfortunately we have some settings in a default profile that is applied to all devices. (Stupid move in hind site) For now, I will just move them all to a network with no profiles. I also opened a case with support. Maybe if they hear us asking for it they'll add a quarantine function to the API.   I got an update on my open case and they stated there is not currently any support for quarantine/selective wipe via the API. The support tech could not give me an ETA and did not state whether this was on the roadmap. He only suggested that I use the "Make a Wish" link to request the feature, which I have done. Hopefully this is a feature that they will enable soon. ... View more

I use the attached script to identify and tag devices that haven't checked in for 30+ days via the API. You could add a step to export the data to a CSV or other data source.   ### SET THESE VARIABLES ### # Set the number of days old before the device is tagged. $cutOffDays = 30 # You will need to set your Organization ID Here. It is probably a 5-digit number $orgId = "" # You can find this by logging in to Meraki with your account. $tennantFQDN = "xxx.meraki.com" # You will need to get an API key from Meraki and put it here $apiKey = "" # Sets verbose output of REST requests $verbose = $true # Time (MS) to wait after each REST request (If you get errors about too many/too fast API requests, increase this number until you don't) $throttleMS = 100 ### ### # Setting some headers to be used with later requests $contentType = "application/json" $headers = @{ "X-Cisco-Meraki-API-KEY" = $apiKey } # Since Meraki is using Unix Timestamps, This will be used to conver them to DATETIME values later $start = Get-Date "1970-01-01T00:00:00Z" # Set the cutoff Date $cutOffDate = (Get-Date).AddDays(-1 * $cutOffDays) # Set the tag to be used for devices over the threshold $tag = "Over$cutOffDays`Days" # This is needed for SSL REST Requests to work properly [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 function Get-SMNetworks{ # Build parameters to request the list of networks in your organization $params = @{ContentType = $contentType Headers = $headers Method = "Get" Uri = "https://$tennantFQDN/api/v0/organizations/$orgId/networks" Body = $null Verbose = $verbose } # Execute the REST request to return your organizations networks $networks = Invoke-RestMethod @params Start-Sleep -Milliseconds $throttleMS if($networks){ # If networks were found, filter the list to SME networks and return the result $networks = $networks | WHERE { $_.type -like "systems manager" } return $networks } } function Get-SMDevices{ param([string]$NetworkID, [string]$Fields) #Only proceed if a network ID was provided if($NetworkID){ $firstPass = $true $batchToken = $null # This request can only return 1000 results. Results are paged so you can retrieve all records through multiple results while($firstPass -or $response.batchToken -ne $null){ $firstPass = $false # Build the URI request and append either the requested fields or the batch token for page 2+ of results $uri = "https://$tennantFQDN/api/v0/networks/$NetworkID/sm/devices" if($batchToken){ $uri += "?batchToken=$batchToken" } elseif($fields){ $uri += "?fields=$fields" } # Execute the request $response = Invoke-RestMethod -ContentType $contentType -Headers $headers -Method Get -Uri $uri -Verbose Start-Sleep -Milliseconds $throttleMS # Update the Batch Token. Allows the next page of results to be retrieved $batchToken = $response.batchToken # Add the NetworkID to all devices returned (Used later as updates must be perfomred per network) $response.devices | Add-Member -MemberType NoteProperty -Name "NetworkID" -Value $NetworkID #Add the devices to the device collection $devices += $response.devices } return $devices } } # Load all your organization's SME Networks $networks = Get-SMNetworks # Load all devices from your SME networks $allDevices = $networks | % { Get-SMDevices -NetworkID $_.id -Fields "lastConnected" } # Get all devices that have and have not checked in in $cutOffDays days $addTag = $allDevices | SELECT id,serialNumber,tags,@{LABEL="LastConnect";Expression={$start.AddSeconds($_.lastConnected)}},NetworkID | WHERE { $_.LastConnect -lt $cutOffDate -and $_.tags -notcontains $tag } $remTag = $allDevices | SELECT id,serialNumber,tags,@{LABEL="LastConnect";Expression={$start.AddSeconds($_.lastConnected)}},NetworkID | WHERE { $_.LastConnect -ge $cutOffDate -and $_.tags -contains $tag } # These hashtables will be used to build the JSON requests and parameters for the REST Request $body = @{ "ids" = ""; "updateAction" = ""; "tags" = $tag } $params = @{ ContentType = $contentType; Headers = $headers; Method = "Put"; Uri = $null; Body = ""; Verbose = $verbose; } ### Tag Devices that have not checked in in $cutOffDays days ### foreach($network in $networks){ # This url will be used to send the tagging requests $netId = $network.id $params.uri = "https://$tennantFQDN/api/v0/networks/$netId/sm/devices/tags" # Get the devices for this network that need tags added $addTagNet = $addTag | WHERE NetworkID -eq $netId # Only execute the add tag operation if there are devices needing the tag if($addTagNet){ # Set the updateAction to add as wer are adding tags $body.updateAction = "add" # Add the device IDs to the body $body.ids = $addTagNet.id -join ", " # Convert the body to JSON $json = ConvertTo-Json $body # Add the json body to the request parameters $params.Body = $json # Execute the request to tag devices Invoke-RestMethod @params Start-Sleep -Milliseconds $throttleMS } # Get the devices for this network that need tags removed $remTagNet = $remTag | WHERE NetworkID -eq $netId # Only execute the add tag operation if there are devices needing the tag if($remTagNet){ pause # Set the updateAction to delete as wer are removing tags $body.updateAction = "delete" # Add the device IDs to the body $body.ids = $remTagNet.id -join ", " # Convert the body to JSON $json = ConvertTo-Json $body # Add the json body to the request parameters $params.Body = $json # Execute the request to tag devices Invoke-RestMethod @params Start-Sleep -Milliseconds $throttleMS } } ### ### ... View more

@BlakeRichardson Thank you for your response.   Are you aware of an ETA for iOS 13 support? I only have one user for now but I would like to do some testing in my environment before iOS 13 goes public for everyone. ... View more

I know this is an old thread/request but this seems like a no-brainer. AD groups are useless if they aren't kept up to date. ... View more

@PatrickL wrote: Exchange email owner certs can be uploaded individually or in bulk through the Owners page: https://documentation.meraki.com/SM/Other_Topics/Owners#Managing_Owners I hadn't seen that you could do a bulk upload. This may be the answer I am looking for.  ... View more

I actually tried this, unsuccessfully. I signed the Meraki CA cert so internal systems will recognize the SCEP certs as valid. The problem is there is no way, that I'm aware of, to associate the SCEP cert with the user account so Exchange could use it for authentication.  ... View more

This is one solution I have looked into and, while I could automate the process of generating carts for the users, I would need to manually manage assigning the certificates to each owner/device. Is there any (semi)automated way of assigning certificates to users through Meraki? ... View more

Thank you for the response. Unfortunately, most of our users are in the field on mobile data so restricting WiFi access would not help. ... View more

That's exactly the issue.    We quarantine all new devices on Exchange and confirm they are compliant on Meraki before we authorize them, but some users have figured out that they can remove Meraki right after doing this. They then add back the ActiveSync connection manually. The device is already authorized in Exchange so they get their mail without the device being fully managed. Users are allowed more than one device, so I can, through a very manual process, reconcile the number of compliant devices a user has on Meraki against the number of devices they have on Exchange but there is no key field in the data from Meraki that can be used to explicitly identify the same device on both Meraki SM and in Exchange.     According to the Apple developer docs, there is an attribute, EASDeviceIdentifier, which is the DeviceId for Exchange and should be accessible via MDM. If Meraki SM passed this through via the web interface or API, it could be used to reconcile compliant devices against Exchange. It is documented on the page below. https://developer.apple.com/library/content/documentation/Miscellaneous/Reference/MobileDeviceManagementProtocolRef/3-MDM_Protocol/MDM_Protocol.html   Sorry if I got a bit verbose and I welcome any help on this. I really want to lock things down and reduce the management overhead on this.   ... View more