If you are looking for centrally-managed wireless, then you want to make sure you get "smart" access points.
When I was looking into wireless 2-3 years ago, I found that pretty much every manufacturer of "centrally-controller wireless" products used "dumb" access points. This meant that all wireless traffic went from the laptop to the access point, then to the controller for checking against policies, then back to the access point, and then out to the destination. This means that to use a local printer, all traffic would go to the controller and back. If the controller is in a different building or part of town, this means even local LAN traffic goes across the Internet.
Colubris (now HP ProCurve) was the only company with smart access points. This means that the you configure everything on the controller, add the access points to groups on the controller, and then the controller pushes out the config details when the access point comes online. Thus, local traffic goes from the laptop to the access point to the LAN. IOW, local traffic stays local. Even if the controller is in a different city.
"Smart" access points cost a bit more, but you can do so much more with them, especially if you want to use a single controller to manage wireless in multiple buildings, locations, cities, etc.
The other nice thing about centrally managed wireless is that you can configured multiple access points with the same SSID (network name) and the wireless clients will just attach to whichever radio gives the best signal, and will switch between radios as you walk around the building. IOW, you can start with 1 access point, then expand to 10 access points, all with a single wireless network (SSID). Something that is impossible to do with consumer-grade wireless from D-Link, Linksys, and Belkin.
Have nothing but good experiences with Colubris products. These are now part of the HP ProCurve MSM series.
3Com and Cisco should be avoided at all costs. The local university spend oodles of cash, and over 5 years to get a barely usable wireless network setup using Cisco products. They like to promise features on paper, that never work in hardware "until next release". The only reason the uni still uses Cisco is that they've sunk too much money into it to just start over with something that works.
D-Link and Linksys only provide stand-alone wireless products, which means you have to manually configure each access point, which becomes its own wireless network, with its own SSID. Add second access point, and you have a second SSID to manage. Add 10 more, and you now have 12 separate SSIDs to manage. A management headache (one of our secondary schools did this ... the tech now has to enter 24 separate WPA keys for 24 separate SSIDs, requiring over 2 hours of wandering around the building connecting to each network).
