A shopping center uses AireOS controllers with Cisco Wave 2 APs. A separate WLAN named Guest- 012345678-WLAN is used for guest wireless clients. Management needs location analytics to determine popular areas. CMX must track only associated clients. What must be selected on the CMX server settings?

The core requirement is to perform location analytics using Cisco CMX but to limit the tracking to only clients that are actively connected to the network. By default, CMX processes location data for both associated clients and unassociated (probing) clients. To meet the requirement of tracking only associated clients, the administrator must configure CMX to ignore the data from probing devices. The "Exclude probing clients" setting (or unchecking "Include Probing Clients") is the specific function designed for this purpose, ensuring analytics are based solely on devices that have completed the association process with an AP.

B. Duty Cycle Cutoff: This setting is used in Hyperlocation to filter out non-Wi-Fi interference sources based on their transmission patterns, not to distinguish between associated and probing clients.
C. Enable Locally Administered MAC Filtering: This filters devices that use randomized MAC addresses. It does not filter based on the client's association state with the network.
D. Enable Location MAC Filtering: This feature is used to manually create a list of specific MAC addresses to either include or exclude from location calculations, not to filter all clients based on their state.

1. Cisco Connected Mobile Experiences (CMX) 10.6 Configuration Guide: In the "Configuring Analytics Service" section, it states, "By default, CMX includes both associated and probing clients in the analytics. To exclude probing clients, you must uncheck the Include Probing Clients check box." This directly corresponds to the action described in option A. (Reference: System > Settings > Analytics page description).

2. Cisco Wireless Controller Configuration Guide, Release 8.10: The section on "Configuring CMX" details the Network Mobility Services Protocol (NMSP) which the controller uses to send client information to CMX. This information includes the client's MAC address and association status, which allows CMX to differentiate between associated and probing clients for features like analytics. (Reference: Chapter: Mobility Services, Section: Configuring CMX).

3. Cisco CMX Configuration Guide, Release 10.5: Under the "Configuring System Settings" chapter, the Analytics tab settings are described. The guide explains that the "Include Probing Clients" checkbox controls whether unassociated clients are used in analytics calculations. Unchecking it achieves the goal of only tracking associated clients. (Reference: System Settings > Analytics Tab).