Your biggest problem will be that the clients makes the decision on where they are going to roam, and as much as enterprise wireless system can try and persuade that, ultimately it's up to the client vendor if there firmware will recognise those features and obey them. Also, roaming will not work between the two system as there is no authentication key caching happening between the two systems, therefore you are disassociating and re-associating between different vendor AP's   I have a deployment of Cisco and Meraki between two floor and roaming and association between floors is an issue  ... View more

As much as I've known that Meraki does not support Dot1X to do AP authentication, that is really annoying from a secure edge scenario, especially when using Cisco switching (and furthermore when Cisco AP support Dot1x) Why does Meraki not support this... Saying this, we have also had issues with Cisco AP's doing Dot1x auth to switchports that fail when the port is configured as a trunk   The one thing you can look at if you have ISE is to use MAB and profiling to identify it as a Meraki AP, however there is a catch, from the little I've been looking into this so far there is no unique identifier (i.e. certificate detail) you can get from the AP to truly trust it.   ... View more

Hi Enrico   One thing to be aware of if using Apple product, and some Android and Microsoft products, is that when a device is not associated to a network, the MAC address could be randomized and therefore render locationing useless, so unless you can get your users to associate to the wireless your outcomes on this could be varied.   This is one of the reason most vendors are now going to Bluetooth for location analytics ... View more