A policy tag still lists a staff WLAN, and that WLAN profile is administratively disabled. The SSID is absent on the floor. What has to change before the tag can put it on the air?
Select an answer to reveal the explanation.
Short Explanation
The tag still has the WLAN on its list, and the profile itself is switched off. You will not hear that name until the profile is enabled. A faster beacon does not turn a disabled profile back on.
Full Explanation
A policy tag can only advertise a WLAN profile that is enabled. This staff profile is administratively disabled, so the SSID stays off the floor even though the tag still lists it. Enable the profile. Deleting the tag would remove the binding that is supposed to publish the WLAN once the profile is on. It does not enable anything. Hiding some other SSID does not enable a disabled profile. The beacon interval does not override an administrative disable. A short beacon on a disabled WLAN is still silence. The WLAN profile is administratively disabled, so the SSID is not on the air even though the policy tag still lists it. Check one live client after the change and leave the rest of the floor alone until that client matches the result you expected. Read the live counters after you retest. Exam caveat: enable the profile and confirm the tag that the access points actually use is the one that lists it. A second tag without this WLAN will keep the name dark on that floor. Operational check: enable the profile, check one access point, and confirm the staff SSID is beaconing.